Application Usage Viewpoint

The Application Usage Viewpoint pattern creates elements and a diagram that describes how application services and the applications that realize them are used to support any number of business processes. It can also show the relationship between that applications that implement the services.

Figure 1. Shows an Application Layer Diagram with a Businesses Process containing child Processes and related Business Objects, Application Services and the Application Components that realize these Services.  

Discussion
To provide a designing and deciding view for enterprise, process, and application architects, operational managers and others who are concerned with aspects such as consistency and completeness, reduction of complexity.

It is useful as in the application design discipline to identify or specify the services needed by business processes and other applications. Alternatively it can be used when designing business processes by identifying the available application services. It can also be used by operational managers who are responsible for the processes to identify and understand the application services and applications required by the process.

The following is a list of some things you may want to do when working with this pattern.
·	Change the name of the diagram to suit the initiative.
·	Change the name of the Business Processes, Business Objects, Application Services and Application Components to suit the initiative.
·	Create additional Business Processes, Business Objects, Application Services and Application Components and add other relationship as needed.

The following is a list of next steps you may want to perform after working with this pattern.
·	Relate the Processes to other elements in the Model including: Capabilities and Application level elements.
Relate the Application Components to other Technology layer elements.
Use the Relationship Matrix to visualize relationships.
Use the collaboration tools such as Discussions, Chat and Reviews to engage other modelers.
Generate documentation of the model and diagram using the automatic document generator. 
Create Maintenance Items such as Issues, Decisions, Changes and Tasks  as required.

Reference
The following help topics will assist you learn about how to work with this pattern.
Archimate Technology
Diagram Layout
Tools you may find useful
The following are some of the tools that will be helpful when working with this pattern.
Document Generator
The Document Generator is a powerful facility in Enterprise Architect that allows a Database Engineer or other stakeholder to create high quality corporate or technical documentation directly from the model, suitable for internal or external audiences. For more details see the Documentation help topic.
Specification View
The Specification View can be used as a way of working with the Components and Interfaces particularly when there are a large number of elements as is typically the case when describing a system of any appreciable size. For more details see the Specification View help topic
Relationship Matrix
The Relationship Matrix provides a spreadsheet like view of two groups of elements and the relationships that exist between them. It can be a used as a powerful analysis mechanism to visually indicate how elements are related to each other and to discover which elements are missing relationships. For more details see the Relationship Matrix  help topic.
Traceability Window
The Traceability Window automatically displays the relationships that exist between Use Cases and other model elements including up-process and down-process elements. The traceability tree view can be conveniently expanded to see deeper relationships and elements displayed in the window can be located in all diagrams in which they appear. For more details see the Traceability Window  help topic.

© 2000 - 2018  Sparx Systems Pty Ltd.  All rights Reserved.