Dragon1 EA Framework

From Dragon1 | wiki
Jump to: navigation, search

Contents

What is an Architecture Framework

An architecture framework establishes a common practice for using, creating, interpreting, and analyzing architecture descriptions within a particular domain of application or stakeholder community. ISO/IEC/IEEE 42010 formalizes a framework as a set of predefined, interconnected viewpoints.

An architecture framework conforming to the standard includes:

  • identification of the relevant stakeholders in the domain;
  • the concerns arising in that domain;
  • architecture viewpoints framing those concerns and
  • correspondence rules integrating those viewpoints.

Frameworks conforming to the standard often include processes, methods, tools and other practices beyond those specified above.

What is the Dragon1 EA Framework?

Dragon1 Viewed High Level as an ISO Compliant Architecture Framework

The following picture is a detailled overview of Dragon1 as EA Framework.


Dragon1-EA-Framework.png

Introduction

The Dragon1 EA Framework is presented in detail on this page showing the specific parts from the Dragon1 EA Method making up an Architecture Framework.

Dragon1 defines different types of structures for which various defined stakeholders have certain recognized needs en concerns. Also the stakeholder have performance and quality requirements regarding these structures and integral solutions and their environment for concerns and needs. Architects capture the needs, concerns, ambitions, goals and requirements of stakeholders and create architectures (total concepts) and architecture designs for the desired TO-BE situations of structures and or integral solution. In Dragon1 architects use extensively visualizations to communicate the architectures (total concepts) and architecture designs to stakeholders. The visualizations in Dragon1 are almost always decision supprting visual reports and giving stakeholders the power to manage quality and risks in projects, innovations and organizational changes. The visualizations show different views and perspectives of models of the environment, structure or solution.

The Dragon1 EA Framework Capability/Reference Model

The Dragon1 Structures and Integral Solutions

Dragon1 defines environments such global or national business domains, industries or branches. Examples these environments are government, telecom, finance, insurance, health, care, education, safety and transport.

Within these environments different types of structures are present.

Dragon1 defines, not limited these, the following enterprise-structures for which architecture designs can be made by architects using Dragon1:

  • Organizations such as a Enterprise or Institution
  • Enterprise or Business Governance
  • Business, Business Domain, Business Function, Business System and Business Services
  • Information Faclities, Information Domains, Information Function, Information Systems and Information Services
  • IT-Infrastructure, Technical Domains, Technical Functions, Technical Systems and Technical Services
  • Integral Organisational Safety Security and Information Security

Dragon1 defines integral solutions such as combinations of new business processes and information systems.

Read more about Dragon1 Structures.

The Dragon1 Stakeholders in the Domain

Dragon1 defines, not limited to these, the following types of stakeholders and stakeholders roles:

  • Owner Clients, such as Board members and directors
  • Architects, such as EA, GA, BA, IA, TA, SecA and SolA
  • Primary Stakeholders, such as management team and chiefs of departmens
  • Quality Controllers
  • Project Managers
  • Engineers

The Needs and Concerns of the Stakeholders

Dragon1 recognizes basic needs and concerns for the defined stakeholders. Examples of these basic needs and concerns are given below:

  • Owner-Client -> Needs: Realization of Change, Competitive Strategy, Agile Organization - Concerns: Budget spending, Risk, Out of Control
  • Management -> Needs: Planning and execution of goals - Concerns: resource availability, IT-quality, quality of services to clients
  • Employees -> Pleasant Working Environment, Career - Concern: Salary, Job Change, Process Change

Performance and Quality Requirements for Structures and Solutions

In Dragon1 stakeholders are the entities (persons or organizations) who want to have functions present in structures and solutions.

Regarding these functions they require for a certain performance of quality of these functions.

In Dragon1 requiring for these performance an quality is made easy throughout the process of project of design and realizing structures and solutions.

Architects make frequent use of visualizations to show what impact and effect certain requirement have on the design and realization of the structure of solutions.

Viewpoints of the Needs, Concerns and Requirements

Stakeholders in Dragon1 are provided with visualizations of views and perspectives of models.

These visualizations (graphical representation) and views (concents / information) are optimal aligned to the needs and concerns of the stakeholders.

A viewpoint is defined as the set of entities and attributes that are of interest to stakeholder when looking at architecture visualizations from a certain rolebased point of view.

So a viewpoint does not prescribe how a visualization should look like, but prescribe what entities and attributes as infomation minimal must be present in a view or model (where view is a kind of filter on a model).

A financial manager who looks at an IT-overview of the business will want to know what IT costs. So financial information must be shown in the visualization or else the visualization is of no use for the financial manager.

An IT-manager who look at an financial-overview of the business will want to know what IT is present to enable the business used. So IT-information must be shown in the visualization or else the visualization is of no use for the IT-manager.

With Dragon1 is is made easy to create visualisations, like conceptsketches, principle-drawing and structure vision that suite the needs and concerns (viewpoints) of Financial, IT and HR manager in seperate visualizations but also in one visualizations.

This is enabled because Dragon1 distinguishes between views and perspectives.

Viewpoints usually address one or a short set of concerns of needs, in order no to make the make viewpoint to complex.

Correspondance Rules Integrating the Viewpoints

In Dragon1 generic rules are defined that make sure the viewpoints of the various stakeholders are consistent with eachother. Enabling the integration of viewpoints. Architects need to defined their own correspondence rules to keep their viewpoints and view consistent and integrateble.

Example of generic Dragon1 correspondence rules are:

  • A concept consist of collaboration elements at a logical level, and consists of collaborating components at a physical level
  • A view is a filter on a model or a subset of a model. A view never can contain more entities or attributes than a model constains.
  • Architectures consists of concepts. Architecture is synonym to totalconcept.


No model, view, perspective or visualization informal or formal may ever deny these rules or else the views and visualizations will become inconsistent.

These generic rules are defined in the Dragon1 EA Method Metamodel and the Dragon1 SPACE Architecture Style.

Examples of architect specific correspondence rules are:

  • A process always has output and always produces products, services or parts of products or services.
  • An application is show for software application and always can be view logical as information system entity. An application is not a logical term.
  • An paying customer always must have at minimum one product or services related to it.

These specific rules must be defined as overall metamodel that go together with / combine the viewpoints, views and models that are part of the architecture design.

Dragon1 Architectures and Architecture Designs

In dragon1 architects are viewed as designers of totalconcepts.

Dragon1 identifies a set of generic structure for which architecture can be designed.

Common architectures are:

  • Enterprise Architecture
  • Business Architecture
  • Information Architecture
  • Technical Architecture
  • Security Architecture

In Dragon1 architecture is synonym for totalconcept. In an architecture design of a structure or solution, the totalconcept is the first level of architecture design.

The levels of architecture design in Dragon1 are:

  • Conceptual Architecture Design
  • Prelimenary Architecture Design
  • Final Architecture Design
  • Detailled Architecture Design

Common architecture-designs are:

  • Enterprise Architecture Design
  • Business Architecture Design
  • Information Architecture Design
  • Technical Architecture Design
  • Security Architecture Design

Dragon1 Processes

Working with Visual Enterprise Architecture is divided in to eight architecture working processes:

  • Initiation & Startup of Working with Architecture
  • Governance & Management of Architecture
  • Development of Architecture
  • Application of Architecture
  • Communication of Architecture
  • Maintenance of Architecture
  • Quality Control of Architecture
  • Implementation of Architecure

Dragon1 Tools

To be able to re-use your architecture products and create consistent architecture products for Dragon1 specialized web based EA Tool have been created.

These EA Tools are repository based, so everything you administer is stored in a database.

Four module of the web based EA Tool Dragon1 | Enterprise Architect are:

  • Resource Center
  • Architecture Repository
  • Visual Designer
  • Models Atlas

On the www.dragon1.com website you find more information about Dragon1 EA Tools.

See Also