SV-11 Template

1. SV-11 Template Physical Data 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. Five Steps in developing your SV-11Step 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 SV-11 should be produced for each timescale that is needed

3. Step 2 - Reference Existing Architecture Products • Identify the components in your Logical Data Model (OV-7) relevant to the scope of the Physical Data Model. Identify applicable: • Entity types • Attribute types • Relationship types • Domain values

4. Step 2 - Reference Existing Architecture Products, continued … • Determine the rules relevant to the scope of the SV-11 • Review the operational rules documented in the Operational Rules Model (OV-6a) • Review the system rules documented in the Systems Rules Model (OV-10a)

5. Step 2 - Reference Existing Architecture Products, continued … • Identify applicable performance parameters • Documented in your System Performance Parameters Matrix (SV-7) • Identify Information Exchange Requirements • Documented in your Operational Node Connectivity Description (OV-2)

6. Step 2 - Reference Existing Architecture Products, continued … • Reference System Interface Description (SV-1) toidentify components applicable to the scope of your SV-11: • Systems • System elements • Systems interfaces • System nodes • Identify the tools cited in your Overview and Summary (CV-1) product that are pertinent to the development of your SV-11 (such as CASE tools, data dictionary products, etc)

7. Step 3 - Reassess Tool Selection Decision • Re-evaluate the tool decision documented in your Overview and Summary (CV-1) in light of the knowledge of the operational and systems environment gained as a result of producing architectural products • Determine whether the initial data model tool(s) decision is appropriate; modify or update this decision as necessary

8. Step 4 – Decide on Method of Building SV-11 • For some purposes, an Entity-Relationship Diagram (ERD) will suffice. A template has been provided at the end of this presentation • A Data Definition Language may also be used in the cases where shared databases are used to integrate systems • References to message format standards may suffice for message-oriented implementations • Descriptions of file formats may be used when file passing is the mode used to exchange information • Interoperating systems may use a variety of techniques to exchange data, and thus have several distinct partitions in their Physical Data Model with each partition using a different form

9. Step 5 – Develop Physical Database Design • Determine and document the components of the physical database • This includes database schemas to accommodate collection and manipulation of data, performance expectations, security considerations and the maintenance of data integrity • Design System Structure • Define the procedures based on how the architecture's operational activities will be implemented • Define target activities sufficiently to describe the way in which they operate; this provides a common basis for procedure design

10. Step 5 – Develop Physical Database Design, continued … • Design Preliminary Data Structures • Summarise data usage from the logical data model and design user codes • The specific approach depends upon the database management system that will manage data storage • This task defines the data viewed by components of information systems for the purposes of providing definitions for data management software and designing procedures that access the data • It also provides a controlled basis for designing storage structures for specific media and computing environments • Design Procedures • Define dialog procedures, design layouts, system behaviour and procedure actions associated with each procedure

11. Template • An Entity-Relationship Diagram template has been provided, following this slide • No templates are provided for Data Definition Language, message format standards or file formats, which are all text-based methods of producing an SV-11 • Don’t forget to update your Integrated Dictionary (CV-2) with any new terms or abbreviations introduced in the SV-11 • Delete the instruction slides when SV-11 completed

12. ENTITY NAME ENTITY NAME ENTITY NAME ENTITY NAME PRODUCT CUSTOMER ORDER SV-11 Physical Data Model – ERD Template Zero Crow’s Feet – Top, Left, Right and Bottom One and only one (horizontal) Building Blocks One and only one (vertical) One (horizontal) RELATIONSHIP VERB TEXT One (vertical) ENTITY NAME Sample Entity-Relationship Diagram SALES REPRESENTATIVE WAREHOUSE STORES SERVES LISTS PLACES