The Dragon1 method recognizes different products to be created in the various processes. Not every product is a specialized architecture product, but each product is essential to create by the architect.
This section of the method will provide a listing of the architecture products and their importance (essential, important, or nice to have).
Architecture Dossier
Whether you put your architecture in documents, a repository, or a tool, defining a dossier per era and year you're working with architecture is necessary. Without having an architecture dossier, it is tough to find your documents.
Accessibility of Products
Next to having an architecture dossier, architecture documents must be accessible to architects and stakeholders. So, make them available via a tool platform or intranet. Also, make them searchable.
Maintaining and Managing Products
There must be some process for maintaining, managing, and governing your architecture products. It will enormously increase the effectiveness and efficiency of the organization.
Top 25
The top 25 products that are always created when working with architecture are:
- Design book or PXA, containing:
- Infographic with strategic key figures and trends
- Cross-Reference Matrix Business Goals-Projects
- Business Case ROI visualization
- Architecture Framework - status report
- Architecture Vision (design sketch/drawing of a total concept)
- Structural Vision (enterprise model, business model, information model, or technical model)
- Presentation of Board and Directors: Why Work with Architecture?
- Principle detail drawing of core concepts
- Situation Sketches / Drawings of usage and workplaces
- Environment sketch/drawing of the value chain/collaboration network
- Stakeholder analysis (onions model)
- Artist Impression of the Service Delivery of the Organization
- Personas of Owner-Client & Stakeholders
- Design sketch/drawing of Enterprise Governance & Compliance (GRC)
- Storyboard of an implementation scenario
- Enterprise Architecture Blueprint
- Process landscape
- Application Landscape
- IT Landscape
- Reference Architecture Overview
- Solution Architecture Concepts Diagrams
- Business, Information, or Technology Roadmap
- (non) Functional Requirements / Capability view of a core-system
- (non) Technical Requirements / Capability view of a core system
- Every project should have at least a functional and technical visualization of the solution it is creating