Package structure

Example of a project structure based on the status of different submodels. What is characteristic of this is that the repository has a different layout for each phase. This approach indicates that the package structure does not have to be a limitation. When introducing an architecture repository, a discussion can arise about the package structure about what the correct format is. Keep the following suggestions as a starting point:

  • The package layout can change for each part of the architecture repository
  • The package structure can easily be changed if the working method is developed. changing insights
  • Determining the layout is often managed by the model manager or custodian for the generic architecture components
  • In work or project package structures, the modelers have more freedom in the design.
  • For solution architectures, use a template as a starting point.
  • Take into account the transfer of architectural concepts in a phasing and life cycle in the package layout.
The package structure should be aimed at the modelers who work with the architectural models. Users of these models must be supported in other ways, for example by navigation diagrams.

Versie 1.0
Creatie datum 21-10-2021

Packages

  • Enterprise Architecture
    This is the established architecture of organization. It often includes the elaboration of the baseline architecture and sometimes also of the target architecture. It is important that the classification should be based on a consultation function. Architects use this as a register of the architecture for requirements inventories, but also for consulting the architectural landscapes and the frameworks within the architecture.
  • Solution architectures
    These packages develop the solutions that currently implement the change of the organization from the baseline to the target architecture. Depending on the size of the organization, you will find several descriptions of solution architectures here.
  • Workareas and projects
    Package in which modellers or teams can create their own elaborations of sub-models, or sub-elaborations of a solution. Within these packages, the modelers have a personal package in which they are free to choose their own layout and develop elements and diagrams. Please note: it is important that agreements are made about the reuse of elements that are present. It is often not allowed to reuse elements present in these personal packages, for example in solution architectures and not at all in enterprise architecture models.

Elementen

Diagrammen

Example Package structure


Copyright © Interactory Template by ColorLib

Ingelogd als 1 | NL