Web based enterprise architect repository for publishing an architecture on the web

Webvideo on data mappings in Sparx Enterprise Architect

Scherm inrichten van EA net behulp van panels, hide, autohide en floating panels

Informatie over de aanwezige architectuur repositories binnen de webapplicatie data docent

Enterprise Architect webviewer op basis van Form Factory CMS

Many organisations are investigating the possibilities of Big Data solutions, for example the Dutch and German Electricity Transport System Operator TenneT. Introducing Big Data is new and traditional approaches are of limited use. Think about introducing data-lab functionalities, innovative and agile approaches, new technologies like NoSql or Hadoop. How are you going to support these activities in an organisation as an architect and how can Enterprise Architect support you in adding architectural value. In this session we will discuss a reference architecture for the TenneT Data Platforms, modelling techniques, architectural patterns and agile approaches all supported by the use of Enterprise Architect. You will see examples of big data patterns, solutions and templates based on ArchiMate.

New functionalities of the Web Publication Platform

Whitepaper with the list of permissions in Sparx Enterprise Architect for administrators and modellers

New version of the Web Publication Platform

Release of the WPP

Indelen van je scherm

Gelaagde architectuur voor agile werken in een architectuur repository

Dia's van een presentatie gehouden op het innovation event van 2016. Architecten zetten traditioneel voornamelijk documenten in voor architectuurbeschrijvingen. Echter het inzetten van meerdere documenten voor het beschrijven van een architectuur is foutgevoelig en levert inconsistenties op, terwijl er veel beheerinspanning nodig is. Door de inzet van architectuur repositories is het mogelijk om de architectuur op een andere wijze te beschrijven, rekening houdend met de huidige eisen en wensen van de architectuurgebruikers. In deze presentatie gaan we in op het inzetten van Sparx Enterprise Architect als tool en wordt een Open Source Web Publicatie Platform getoond waarmee een Architectuur Repository op eenvoudige wijze via het web aan de gebruikers beschikbaar wordt gesteld. Na deelname aan deze sessie heeft u een duidelijk beeld van de (on)mogelijkheden van Architectuur Repositories.

Voorbeeld scherm van de opzet van de repository verkenner

WPP voor EA

Introductie WPP

Around an architecture repository, an organization can define a number of capabilities and goals to determine a starting point for introducing this change in the architecture capability within the organization. This defines a point on the horizon for the target architecture.

Checklist with checks that must be taken if you want to determine components within an architecture. This is an important part of the architecture process because, just like architecture documents, (part) architectures have a status. In a repository, a process must be followed for this, just like with document-based architectures.

This diagram is a viewpoint for developing a physical data model for SQL Server RDBMS. This viewpoint indicates which tables, constraints and columns can be used when drawing up an RDBMS data model. A few principles apply to the RDBMS data model:

• Physical data model is for ICT (Database specialists).
• SQL DDL statements can be generated from the Physical data model.
• Naming conventions for the database platform (SQL Server/Oracle) serve as the basis for the Naming Conventions.

The associations show the database details for the referrer and primary keys.

This model is relatively simple in design, there is an application service that is completed by one logical application function. However, in other situations this can be a more complex composition. If a register or portfolio is drawn up for the architectural building blocks, this is an additional form of aggregation. An alternative is to aggregate and group via the service portfolio. Is a point of discussion.

The composite service model shows how a service at a higher level of abstraction is composed of smaller services with a more specific character. This office automation model includes an intermediate layer of services, but that is not necessary, you could also make a direct link to Microsoft Office, depending on the context. In this elaboration, only application services are modeled and included in the composition. However, in addition to application services, you can also define business services here. Consider the combination of the implementation of Office and a service desk for questions in case of problems. That is currently out of scope, but will become relevant at some point. Relevant here is that this creates a bottleneck in the ArchiMate modeling. If desired, this bottleneck can be resolved with serving relationships. Embedding ICT business services in the lower architectural layers.

This example shows in a simple manner how the characteristics/requirements can be made transparent based on requirements, constraints, qualities and principles. This example shows how the characteristics of the different xBB can be mapped based on ArchiMate concepts. This will soon become an important mechanism in the various xBB catalogues. In addition to this approach, the characteristics can also be elaborated via the internal characteristics of the entities in EA. Such as requirements, constraint and scenario. Finally, there is the option to use tagged values. The working group has determined that making associations between ArchiMate concepts is preferable. If an elaboration with ArchiMate concepts is insufficient and you want to rely on internal properties or tagged values, this must be short-circuited.

For the application landscape Giovanna wants to develop a supporting technology architecture The technology solution is a Cloud based Infrastructure as a Service in Azure It is typical that a Virtual Machine is designed for a windows application and a relational database For a webbased implementation webforms via HTTP is used Create an ArchiMate diagram of this technology architecture

Alberto wants his ice cream parlors to be well known in terms of product quality but also from a CSR perspective There are three rules of thumb for this:

• Satisfied customers
• Happy employees
• Satisfied legislators and enforcers

Alberto would like to identify a number of stakeholders of the latter

Goal: To provide insight into the principles related to elements in order to ultimately determine the right to exist of these elements. In addition, it provides insight into which solutions implement the same principles. Not required Use the motivation elements of Archimate for this. The principle element is included there. This can possibly be supplemented with requirements/constraints to indicate the implications. The principle can be linked to an Outcome, where the rationale in the association from principle to Outcome is described. In addition, if desired, the complete motivation can be elaborated in principles, drivers, etc.

The building block model consists of the generic entities building block and catalog. These form the basis of a reference architecture. Catalogs are groupings of building blocks within a specific domain. Multiple catalogs will be created that are related to each other and overlap within the visualizations. The advantage of the design of working with catalogs and building blocks is:

• Registers are created of reusable architectural components aimed at a specific field of work.
• The use of building blocks brings standardization and encourages reuse of architectural configurations.
• Building blocks makes the architecture and development process easier.
• Architectural product catalogs aimed at specific professional fields are being developed. This has a positive influence on the service provided to the rest of the organization.

The building blocks have three specializations, the definitions of which have been worked out in detail. These descriptions are elaborated in the paragraphs below. If relevant, additional information has been added to this elaboration, such as links to Togaf and examples of the implementation of these architectural concepts The model uses a pragmatic model with regard to the associations between Service and SBB. From ArchiMate perspective, the route from service is via ABB to SBB. This is characterized by the fact that the functional aspect is well embedded in the building block model. When publishing these models, a possibility is sought to generate reports and web pages that do not contain data relevant to the model for non-architecture stakeholders, which may mean that in a number of situations the ABBs do not have to be developed. Applying the direct association between service and SBB in the modeling does not meet the viewpoints.

The business process for applications is supported by a service oriented application landscape. There is a logical service for getting a list of applicants and a list of job requests. The applicants are introduced via a webform interface. The application component used here is beaufort a COTS HR system

For effective use of the collected time registration data the data must have sufficient quality to use this as input for the Key Performance indicators Alberto wants to introduce So all employees must be aware of the effect of their registration The manager approving the hours has knowledge about when hour registration is correct or not The projects and activities to use for registration should be up to data at all times There employees are trained and the HR department is able to keep the configuration of the projects and activities When problems occur employees are helped by the service desk

One of the goals of Alberto is corporate social responsible For the job application process this means that an job applicant is content about the process and performance of the staff involved in the Job application processes This means that the employees involved have knowledge and are able to do the job application activities This means that the involved employees have sufficient knowledge about how to act in the communication with applicants

Create a service oriented model for system integration Use services and interfaces to demonstrate how the components interact Model how the HR system and the Webform system exchange information Create an ArchiMate diagram of this service orientation

For the application landscape Giovanna wants to develop a supporting technology architecture. The technology solution is a Cloud based Infrastructure as a Service in Azure It is typical that a Virtual Machine is designed for a windows application and a relational database. For a webbased implementation webforms via HTTP is used Create an ArchiMate diagram of this technology architecture Extend the model with a legend and coloring and eventually a standardized layout

Hierbij hebben we alleen de service en de interface gemodelleerd. Je zou hiermee kunnen volstaan in een cloud situatie. Echter je wilt binnen Azure waarschijnlijk meer weten, bijvoorbeeld welke virtual machines en welk deel van het dotnet raamwerk

Introduction Applying building blocks describes the design and definition of building blocks. Building blocks are introduced to an organization from the perspective of:

• Reuse.
• Decoupling
• Generalization and specialization.
< li>Standardization.
• Interaction between providers and consumers of information provision. concepts (currently applications and infrastructure, but this must also be applicable to business architecture).
• Specification of costs and revenues.
• Improve (accelerate) services.
li>
• Information security.

This document consists of the following parts:

• Model: describes the definition, characteristics and relationships of the concept building block and the associated specializations
• ArchiMate viewpoints: development of the viewpoints for the building blocks. These viewpoints are composed of a limited set of ArchiMate elements and associations.
• Examples of elaboration of the various building blocks within the ArchiMate viewpoints defined above
• Sparx implementation, how this is done is implemented in Sparx and how it is communicated/published to the various stakeholders.

Here the viewpoints are described for solution architectures in particular, based on a different approach than the method with Viewpoints as described in the ArchiMate documentation. This is an elaboration of an organization that has determined a number of viewpoints for its own context. It is important that the viewpoints are related to each other. Within the viewpoints we work with:

• Primary elements (green border), these are elements that in principle must be elaborated in these diagrams.
< li>Secondary elements (orange border) are elements that may be used in these diagrams

It is important that we keep the number of concepts relatively limited and that the different viewpoints are related to the project package template for project or solution architectures.