1 / 4

IDEF0/Activity Model – Functional Decomposition

OV5 Activity Model Diagrams. OV5 Node Tree Diagram. Context or Level 0. Functional Hierarchy. IDEF0/Activity Model – Functional Decomposition. Level 1, sub functions of level 0. Example of a BPMN Diagram.

mcarlo
Télécharger la présentation

IDEF0/Activity Model – Functional Decomposition

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OV5 Activity Model Diagrams OV5 Node Tree Diagram Context or Level 0 Functional Hierarchy IDEF0/Activity Model – Functional Decomposition Level 1, sub functions of level 0

  2. Example of a BPMN Diagram

  3. 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. 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.

  4. Tips and HintsforCreating 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.

More Related