You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: Diagrams/DAF_BusinessArchitectureDiagrams.xml
+13-6Lines changed: 13 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
<?xml version="1.0" encoding="windows-1252"?>
1
+
<?xmlversion='1.0' encoding='utf-8'?>
2
2
<UMLProfileprofiletype="uml2">
3
-
<Documentationid="A10AB80D-1"name="DAF Business Architecture"version="3.2.1"notes="DAF Business Architecture"/>
3
+
<Documentationid="A10AB80D-1"name="DAF Business Architecture"version="6.0 ALFA 3"notes="DAF Business Architecture"/>
4
4
<Content>
5
5
<Stereotypes>
6
6
<Stereotypename="Application Use-Case"notes="An Application Use-Case diagram displays the relationships between consumers and providers of application services. Application services are consumed by actors or other application ser vices and the Application Use-Case diagram provides added richness in describing application functionality by illustrating how and when that functionality is used.
The purpose of the Application Use-Case diagram is to help to describe and validate the interaction between actors and their roles with applications. As the architecture progresses, the use-case can evolve from functional information to include technical realization detail.
Application use-cases can also be re-used in more detailed systems design work.
">
@@ -14,7 +14,7 @@
14
14
</Stereotype>
15
15
<Stereotypename="Requirements Diagram"notes="a DAF diagram for the creation of requirements">
<Stereotypename="Solution Concept"notes="A solution concept diagram provides a high-level orientation of the solution that is envisaged in order to meet the objectives of the architecture engagement. In contrast to the more formal and detailed architecture diagrams developed in the following phases, the solution concept represents a pencil sketch of the element involved in the expected solution at the outset of the engagement. This diagram may embody key objectives, requirements and constraints for the engagement, and also highlight work areas to be investigated in more detail with formal architecture modeling. The purpose of this diagram is to quickly on-board and align stakeholders for a particular change initiative, so that all participants understand what the architecture engagement is seeking to achieve and how it is expected that a particular solution approach will meet the needs of the enterprise.
">
<Stereotypename="Capability Based Planning"alias="Diagram"notes="A DAF (Digital Architecture Framework) diagram for Capability-Based Planning visually represents an organization's capabilities and their alignment with supporting elements such as business goals, processes, and technology solutions.">
0 commit comments