Second part of Dragon1
Dragon1 'Way of Working' elaborates on the second part of Dragon1. Various tools are available in the ‘way of representing’, and the architect and other stakeholders can optimally collaborate on visual enterprise architecture within the company. What is expected of everyone?
Dragon1 also proposes setting up the company to support working with visual enterprise architecture. For example, where does the company start working with visual enterprise architecture? And how can you grow as a company to the next level of maturity in working with visual enterprise architecture?
The following paragraphs outline which working methods concepts of Dragon1 are essential to working with visual enterprise architecture. These working method concepts are presented in the framework of the working method. Why is Dragon1 built up from these working methods concepts, and what are the mutual relationships between these working methods concepts?
Way of Working Framework
The Dragon1 way of working can be described as a whole with an architecture framework. The framework consists of eight working method concepts. The working method is mainly about the question: who does what, when, how, and why. The starting point here is that the better the collaboration between architects and stakeholders is aligned, the better and more efficiently the company can work with visual enterprise architecture.
The Way of Working Framework shows the most important concepts that are part of the way of working of the method.
Architecture Role Playing
The concept of Architecture Role Playing indicates which groups of people within the company should play a role in working with visual enterprise architecture, according to Dragon1. Dragon1 indicates the most essential tasks, powers, and interests each person has in working with visual enterprise architecture. And how to collaborate on visual enterprise architecture as optimally as possible.
Architects
The concept of Architects focuses on the architectural role of 'the architect'. The architect deals with the essential parts of working with visual enterprise architecture, such as creating architectural designs that lead to various architectures. Dragon1 provides a suggestion here on how the architect as a person should view the architectural work. What does that mean for the architect when organizing his work? And what does that mean for the architectural services he can offer the company?
Design Assignment and Design Strategy
The concept ‘Design Assignment’ and the concept ‘Design Strategy’ are recognized as separate concepts. But together they form the most critical discipline of the architect, according to Dragon1. Both concepts give the architect handles on how he can best engage in his architectural work. Which specific strategies or approaches can he use for this?
Architecture Products
The concept of Architecture Products has also been recognized as a separate concept, because this concept includes several essential products that result from the architectural work processes. The architectural products that are often only made by architects and for which high-quality requirements are set are called the professional products of an architect.
Architecture Organization
The concept of Architecture Organization indicates that an internal organization can be set up when a company has become enthusiastic about working with visual enterprise architecture. With what and how can you as a company best start with visual enterprise architecture according to Dragon1?
Architecture Maturity
And the concept of ‘Architecture Maturity’ indicates how the company, using the architecture maturity model of Dragon1, can determine how far the company is in working with visual enterprise architecture. What steps can the company take to grow to the next level of working with visual enterprise architecture?