Dragon1 Views and Perspectives

From Dragon1 | wiki
Jump to: navigation, search

Contents

Introduction

Architects design and supervise the realization of information systems, business models and enterprise structures. Architects design and realize these for the owner/client and stakeholders.

The owner/clients are often CxOs, Board members and managers. Stakeholders are often manager, employees, customers, shareholders and government.

Also architects support owner/clients and stakeholders in optimal align of enterprise entities with regards to the enterprise, business or IT strategy.

During the design and realization constantly decisions have to be made by owner/clients stakeholder to make sure all the requirements are answered in the design

In order to support owner/client and stakeholder in their decision making architects make use of (draw or generate) views and perspectives. These views and perspectives contain information and visual annotations maijg it easy for decision makers to take the correct decisions.

What are the Dragon1 Views and Perspectives ?

Dragon1 recognizes the following related concepts: views, perspectives, viewpoints, visualizations and viewers.

A view is defined as the set of entities, attributes, relationships, states and situations a viewer sees when he looks from a certain viewpoint (point of view) towards something (an object or subject) in a context. A view is what you see.

A visualization is a graphical representation of a view . In your mind or on paper you visualize a view.

A viewer is a person look at a view. Viewers are often owner/client, stakeholders, contractors and engineers.

A viewpoint is the place or location in a context you are standing to look from towards something.

A perspective is defined as a set of views that are aligned, morphed or have been made consistent to create a coherent whole.

Why do architects work with views and perspectives?

Architects work with views and perspectives because you can add information to models of systems and structures the stakeholders and decision makers can use to take the right decisions.

Architects normaly create designs with models. These models are sometimes so technical stakeholders like decision makers cannot make anything of it. By creating views and perspectives based on the models more people can understand the models and take the right decisions with it.

With views and perspectives architects can make states, relationships (dependencies) and situations visible that normally are not visible or clearly to be seen for any stakeholder.

An overview of the Dragon1 Views and Perspectives

Views and Perspectives are classified as follows:

The views or perspectives subject or object can be any type of entity, such as systems, business functions,stakeholders role, business processes, quality aspects. But the subject can also be a situation or scenario. In fact it can be anything.

Views and Perspectives can be detailled or global (an overview), view can be specific or generic.

Example Types of Views are:

  • Functional Views of a system
  • Technical Views of a system
  • Analysis Views of a system
  • The Programmers Design Views of a software system
  • Deployment Views of a system
  • Financial view of a company
  • The projects budget view
  • The products maintenance cost view
  • Research view of a company
  • Procurement view of a company
  • Compliance view of a company
  • Governance view of a company
  • Sea view of a hotel
  • Customer view of the companies service delivery
  • A management overview of the company
  • The owners quality perspective of the company
  • The industries compliance perspective of the company
  • The employees career perspective of the company


The viewpoint that lead to a view normally does not carry the same name, but a name that logically could lead to having this view

Examples of application of Dragon1 Views and Perspectives

See Also

Comparing Views with Models and Visualizations


References

  • Zachmann
  • Tapscott (BWAIT views)
  • Krüchten (4+1 views)
  • IEEE 1471
  • ISO/IEC 42010:200

External Links