Purpose

Steps

Heuristics

Artifacts

   The purpose of the application context diagram is to identify stakeholders that influence, or are influenced by your product. The diagram will also provide a graphical overview of the problem domain, or ecosystem in which the product will operate. The application context conveys to the entire organization the extent of influence of the product.

1. 1. Begin with a blank UML communication diagram.
   

2. 2. Add the title and date / version to the diagram.
   

3. 3. Add your product as an object instance (box) in the center of the diagram.
   

4. 4. Provide an appropriate, understandable name for your product (hint, “system” is not a good name!)
   

5. 5. Brainstorm the potential stakeholders, and add them to the diagram arrayed around the product. Label each stakeholder with a suitable name.
   

6. 6. For each stakeholder, consider how they might exchange information with the product.
   

7. 7. Add arrows to the diagram to show the flow of information between the product and the stakeholders.
   

8. 8. Label the arrows with an simple name. Use separate arrows for each direction.
   

9. 9. If stakeholders interact only with other stakeholders, indicate the information flow between the stakeholders.

1. • Information labels on arrows should be simple. Additional details can be provided in the next step if necessary.
   

2. • Consider all potential stakeholders, including users, financiers, existing (legacy) systems, regulatory agencies, and even the competition.
   

3. • Stakeholders may be artifacts generated or consumed by the product.
   

4. • The stakeholders should be limited to the problem domain, and not introduce new solution-domain entities of the product.

The Application Context (Example)