Implementation refers partly to the transfer that is desired from the current situation to the target situation, and partly to the packaging of work that aims to change the business.
In project contexts, WBS (Work Breakdown Structure) is often used to describe deliverables and activities, and in agile development, Epics is the overall planning object that is broken down into smaller parts and iterations are planned in different lengths of time.
Prime Arch is based on proven standards and combines traditional EA frameworks with agile methodological frameworks. For a summary analysis, read "Implementation hierarchy in different standards".
Implementation is divided in two categories: change and user description. Change refers to the desired shift from the current situation to the target situation. Also, it refers to packaging of the works aiming to make a transition happen in the business. In the context of a project, WBS (Work Breakdown Structure) is often used. When it comes to agile development, Sprint is the central planning object to which user stories and features (technical functions) are connected.
User Descriptions is an umbrella term for user stories and use case. Both of these concepts are ways of describing users' needs. The first one starts from the user's goal and the second one starts from how the user wants to integrate with an application.
An example on how change could be modelled:
Implementation is divided into two categories: change and user description. Change refers partly to the transfer that is desired from the current situation to the target situation, and partly to the packaging of work that aims to change the business. In project contexts, WBS (Work Breakdown Structure) is often used and in agile development, Sprint is the central planning object to which user stories (eng: user story) and features (technical functions) are linked.
ArchiMate defines the implementation objects as follows:
Below is a schematic picture of how the gap between two plateaus can be bridged, partly by work packages where Epic has been broken down to Capabilities and Features, and partly by work packages, Stages have been broken down to Releases and Sprints.
Deliverables must realize important parts of the business and in order for it to be right, control is required. Below is an example of how a Capability is connected to different dimensions:
Another important aspect of the implementation is to show the division of responsibilities in terms of the organization.
The example below shows examples of how agile teams organized in trains within a program are assigned responsibility for sprints and features:
Meta Object
C = Core
E = Extended
Meta objects in different levels
View Types
