Product Viewpoint

The Product Viewpoint pattern creates elements and a diagram that describe the value that the products offer to external parties such as customers or other stakeholders  It allows them to visualize one or more products' composition in terms of their constituent business, application, or technology services  and any number of contracts or other agreements. The channels (interfaces) through which this product is offered, and the events associated with the product can also be represented in this viewpoint.

Figure 1. Shows a Business Layer Diagram with a centrally located Product  related to a number of including: Values, Contracts, Business Interfaces.
Discussion
To provide a designing view for product developers, product managers, process and domain architects and others who are concerned with aspects such as product development or the value offered by the products of the enterprise.

It is typically used in product development to design and specify a product that will meet a customer's or other stakeholder's expectations. This is typically done by analysis of existing services that can be combined together or by the creation of additional services required by the product. It will form a valuable definition and specification for business process architects and others that need to design and provide the business processes and technology capability for the product to be realized.

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 Product and other elements to suit the initiative.
·	Create additional Values, Contracts, Business Interfaces, Business Roles, and Application Services and add other relationship as needed.
Create additional relationships as needed.

The following is a list of next steps you may want to perform after working with this pattern.
·	Relate the Product element to other elements in the model including Requirements and Capabilities..
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
Baselines
Maintenance Items

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.