Activity Hierarchy (ECM Mapping) Artifact Description and Purpose The activity hierarchy describes relationships of activities – that are normally conducted by individuals (not technology) in the course of achieving a mission or business goal, This hierarchy with the associated ECM/ESL mapping table, extends the capabilities hierarchy. Essentially, this further refines the program architecture program’s scope. Figure 9. Activity Hierarchy Example Underlying Architecture Information Types (primitives) Manual Activity – Necessary Relationships The hierarchy should be a parent-child relationship where the – children completely define the parent and are mutually independent. When mapping activities to the ECM/ESL the intent is to match the concepts at the most equivalent level of detail. Typical Audiences and Usage The activity hierarchy depicts the full scope of operational – activities supported or required by the program. Its primary consumers are enterprise managers, peer program managers, portfolio managers, or other stakeholders requiring a simple view of program scope. It should be noted that the activities depicted in this view can be shown in many of the supporting activity diagrams (below). When properly constructed this view will help answer the question: Have the processes the program supports improved or been Activity (Business Process) Diagram Artifact Description and Purpose The Activity Diagram, as illustrated in Figure 9, describes – the activities that are normally conducted by individuals (not technology) in the course of achieving a mission or business goal. The parent activities should derive from the concepts defined Activity Hierarchy and should be decomposed to a level necessary to demonstrate commonality or differences between the performances of activities with respect to enterprise standard processes (where present). In cases where such diagrams are necessary to demonstrate business process improvement (re-engineering), the diagrams must clearly show the improved process and describe the nature of the improvements. Figure . Example Activity Diagram (BPMN example)\ Underlying Architecture Information Types (primitives) Manual Activity, Information – Exchange, Person Performer, Organizational Performer, Entity. Necessary Relationships describes business activities or tasks, input and output – (Information Exchange) flows between activities, and flows to/from activities that are outside the boundaries of the architecture. Activities should be arranged by Person Performer. Information exchanges should be linked explicitly to required data (at the appropriate level based upon the maturity of the architecture). At detail levels, system or service performers may be used to show those interactions. Alternatively, Person Performers could be added to detail levels of the Service Interaction Diagrams.
Activity Hierarchy (ECM Mapping) Artifact Description and Purpose – The activity hierarchy describes relationships of activities that are normally conducted by individuals (not technology) in the course of achieving a mission or business goal, This hierarchy with the associated ECM/ESL mapping table, extends the program’s capabilities hierarchy. Essentially, this further refines the program architecture scope. Figure 9. Activity Hierarchy Example Underlying Architecture Information Types (primitives) – Manual Activity Necessary Relationships – The hierarchy should be a parent-child relationship where the children completely define the parent and are mutually independent. When mapping activities to the ECM/ESL the intent is to match the concepts at the most equivalent level of detail. Typical Audiences and Usage – The activity hierarchy depicts the full scope of operational activities supported or required by the program. Its primary consumers are enterprise managers, peer program managers, portfolio managers, or other stakeholders requiring a simple view of program scope. It should be noted that the activities depicted in this view can be shown in many of the supporting activity diagrams (below). When properly constructed this view will help answer the question: Have the processes the program supports improved or been Activity (Business Process) Diagram Artifact Description and Purpose – The Activity Diagram, as illustrated in Figure 9, describes the activities that are normally conducted by individuals (not technology) in the course of achieving a mission or business goal. The parent activities should derive from the concepts defined Activity Hierarchy and should be decomposed to a level necessary to demonstrate commonality or differences between the performances of activities with respect to enterprise standard processes (where present). In cases where such diagrams are necessary to demonstrate business process improvement (re-engineering), the diagrams must clearly show the improved process and describe the nature of the improvements. Figure . Example Activity Diagram (BPMN example)\ Underlying Architecture Information Types (primitives) – Manual Activity, Information Exchange, Person Performer, Organizational Performer, Entity. Necessary Relationships – describes business activities or tasks, input and output (Information Exchange) flows between activities, and flows to/from activities that are outside the boundaries of the architecture. Activities should be arranged by Person Performer. Information exchanges should be linked explicitly to required data (at the appropriate level based upon the maturity of the architecture). At detail levels, system or service performers may be used to show those interactions. Alternatively, Person Performers could be added to detail levels of the Service Interaction Diagrams.