1 / 7

Guide to Developing Operational Rules Model

Step-by-step instructions and template for creating an OV-6a Operational Rules Model, including identifying product timescales, referencing existing architecture products, selecting formal language, and documenting operational rules.

ngary
Download Presentation

Guide to Developing Operational Rules Model

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. OV-6a Template Operational Rules Model – step-by-step instructions and template Click the mouse button to see the next slide. Use the browser Back button to return to the Tutorial.

  2. Four Steps in developing your OV-6aStep 1 - Identify the Product's Timescale • Decide on the timescale that this product is expected to represent (as-is, to-be, transitional) • Multiple timescales are often needed for each product; a separate OV-6a should be produced for each timescale that is needed

  3. Step 2 - Reference Existing Architecture Products • Activity Model (OV-5) • Review the activities documented in your OV-5 and determine those relevant to the scope of the operational rules model • Logical Data Model (OV-7) • Review the entity types, attribute types, and domain values documented in your OV-7and determine those relevant to the scope of the operational rules model

  4. Step 3 - Select Formal Language • Choose the appropriate means of communicating the architecture's operational rules. Examples include: • Process Logic diagrams (IDEF1X) • A Process Logic diagram template has been provided at the end of this presentation • Structured English • No template is provided. Any word processor can be used to write Structured English

  5. Step 4 - Document Operational Rules • Operational Structural Assertion Rules Set • Record the static aspects of business rules based upon the entity types and relationship types • Operational Action Assertion Rules Set • Record the dynamic aspects of business rules. This includes specification of integrity conditions, constraints and role-based authorisations to execute specific actions. • Operational Derivation Assertion Rules Set • Determine and record the algorithms used to compute or derive facts

  6. Template • A Process Logic diagram template has been provided, following this slide • Don’t forget to update your Integrated Dictionary (CV-2) with any new terms or abbreviations introduced in the OV-6a • Delete the instruction slides when OV-6a completed

  7. ENTITY TYPE NAME ENTITY TYPE NAME ENTITY TYPE NAME ENTITY TYPE NAME KEY ATTRIBUTE A KEY ATTRIBUTE B KEY ATTRIBUTE C ___________________________ NON-KEY ATTRIBUTE D NON-KEY ATTRIBUTE E NON-KEY ATTRIBUTE F NON-KEY ATTRIBUTE G KEY ATTRIBUTE A KEY ATTRIBUTE B KEY ATTRIBUTE C ___________________________ NON-KEY ATTRIBUTE D NON-KEY ATTRIBUTE E NON-KEY ATTRIBUTE F NON-KEY ATTRIBUTE G KEY ATTRIBUTE A KEY ATTRIBUTE B KEY ATTRIBUTE C ___________________________ NON-KEY ATTRIBUTE D NON-KEY ATTRIBUTE E NON-KEY ATTRIBUTE F NON-KEY ATTRIBUTE G KEY ATTRIBUTE A KEY ATTRIBUTE B KEY ATTRIBUTE C ___________________________ NON-KEY ATTRIBUTE D NON-KEY ATTRIBUTE E NON-KEY ATTRIBUTE F NON-KEY ATTRIBUTE G “Category-of” relationship “Category-of” relationship “Category-of” relationship OV-6a Operational Rules Model template relationship name relationship name relationship name

More Related