IDEF0/Activity Model – Functional Decomposition OV5 Activity Model Diagrams OV5 Node Tree Diagram Context or Level 0 Functional Hierarchy IDEF0/Activity Model – Functional Decomposition IDEF0 diagram – two formats functional decomposition and Hierarchy Simple but portrays a lot of information Functional Decomposition Start with Context diagram (level 0), single box ie finance, HR, External Reporting Input, Controls, Outputs, Mechanism (ICOM) are added and labelled. Decompose to the sub functions – level 1 System Architect supports creation of child diagram Move ICOM line/arrow down to appropriate sub functions – Balancing as you go. System Architect supports Balancing Functional Hierarchy All the diagrams can be summaries into a hierarchy of functions System Architect support auto generation of hierarchy diagram from a series of Functional decomposition – if built with parent child relationship. Sys Arch builds the series of Functional Decomposition from an hierarchy but does not include ICOM lines/arrows. Shows functions and input, outputs but does show the sequence or flow control. Need a different type of diagram to show this - BPMN Level 1, sub functions of level 0 Revised Feb 06

Example of a BPMN Diagram Model the sequence flow using BPMN. Easy to understand by IT and business Supports linking with data and organisation/roles via swimlanes Supports parent child relationship Customised to include information on systems/applications Support simulation and Activity Based Costing Able to link Events to Inputs and Outputs from the matching IDEF0 diagrams, ie the ICOM arrows/lines Notice use of Doc Block, provides self documenting feature (some limitations though, hopefully Popkin will improve in future releases) Decide what swim lanes will represent and be consistent. Pools = Organsiations, Lanes = Roles. Recommend not naming sequence lines except after Decision blocks. We included System Functions as one of the attributes for Processes. This allowed us to create matrix showing process to system functions. System functions were mapped to the modules in the Finance application ie General Ledger, Acct Payable etc. Remember these diagram types are modelling the bottom two layers of lexicon hierarchy. Revised Feb 06

Each node represents an Activity model diagram. There are levels. This group of nodes is at Level 3 and comes from node 4 from the level above. This node is represented by an OV5 Activity Model diagram shown on the left hand side below. Note Naming conventions between OV5 and OV6 can be used to help support this type of relationship. This OV5 Activity Model diagram represents the group of nodes from the node tree. One or more Operational Activity(s) (the rectangular symbols) can be described or defined using an OV6 BPMN diagram. Each node represents an Activity model diagram. There are levels. Each function (operational activity) in the bottom level nodes were defined by a process flow diagram (BPMN diagram.. The steps involved in carrying out this activity can be represented by an OV6 BPMN Process Flow diagram. The OV6 diagram is therefore a child diagram of the OV5 node. NB: The OV6 diagram is labelled with the same name as the Operations Activity symbols it represents, this is the recommended naming convention to use. Revised Feb 06

Tips and Hints for Creating OV5 & OV6 in SA Do Activity models first Top down vs Bottom up, it is probably best to consider both, sometime you do not know where the bottom is! Manipulating ICOM arrows is awkward and time consuming, work from the bottom up Make changes to Activity Model first then auto generate Node Trees. Collect data in spreadsheet form, you can import into System Architect. Draw diagrams, whiteboard or paper first then reproduce in the tool. Drag Definitions from browser or use choices button. Collect description and other attributes as you go. Use mixed teams with Business experts and models when you collect data Backup and make copies of encyclopedia before making major changes Check for duplicate and consistency of names as you load, correcting in excel can be more efficient To fix errors/inconsistencies in definition data export to excel then import using the delete all and add new data options in System Architect Validate and reformat Word diagram reports, cut and paste corrections Turn off auto name for sequence lines and hide names Remember the journey is just as important as the end product. Revised Feb 06