ORM 2008 An Adaptable ORM Metamodel to Support

ORM 2008 An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 2/12/2022 Baba Piprani 1 (1 SICOM Canada) , Marlena Borg 2, Josée Chabot 2, Éric Chartrand 2 (2 Transport Canada) Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 1

Your presenter…Baba Piprani, SICOM Canada Senior IT Consultant with over 30 yrs standardization experience…Computer Languages, SQL, Conceptual Schema, Data Modelliing, IRDS, Metadata Registry, MOF… Developed award winning implementations of standards-based Data Quality Firewalls for advanced generation architecture data warehouses and Web based applications using SBVR, ORM, NIAM, Master Data Management, Metadata Repositories/Registries using SQL DBMSs incorporating Service Oriented Architectures… Clients: Canadian Government departments Transport, Foreign Affairs, Defence, Superintendent of Financial Systems, Public Works…including private sector, and CNIS (China National Institute for Standardization) Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 2

Agenda 1. Why Requirements Traceability? 2. Scenario: ORM based SDLC 3. Positioning Requirements in the SDLC 4. Business Requirements Metamodel Definitional 5. Business Requirements Metamodel – Tracking 6. Corporate SDLC mapping 7. Summary Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 3

Focus of paper. . . Provide an ORM schema and attribute based SQL schema depicting an actual implementation, and explain its usage in a reallife scenario Address need for requirements traceability High level overview of ORM based SDLC ORM Metamodel used for requirements tracking Usage scenarios in implementation Mapping to Corporate development life cycle model Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 4

Agenda 1. Why Requirements Traceability? 2. Scenario: ORM based SDLC 3. Positioning Requirements in the SDLC 4. Business Requirements Metamodel Definitional 5. Business Requirements Metamodel – Tracking 6. Corporate SDLC mapping 7. Summary Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 5

1. 1. Why Requirements Traceability? Applications development may take several months to years. . . Staff transition takes away business requirements background and knowledge Requirements traceability metamodel enables: traceability provides assurance of requirements being current requirement not lost and is being addressed Provides systematic method to analyze and maintain requirements lineage Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 6

1. Why Requirements Traceability? - Benefits for Organization: Provides continuity promotes good data governance protection of corporate memory Increased stakeholder confidence in IT shop Increased productivity of project staff Increasingly contributes towards meeting objectives and plans Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 7

1. Why Requirements Traceability? - Benefits for Business Client or Stakeholder: Eliminates or reduces time and effort to completely explain or rationalize requirements Improve confidence in systems development process and the final product will be fully reflective of their needs Enables scope management instead of scope creep Improve confidence in system output results Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 8

1. Why Requirements Traceability? - Benefits for System Developer: Requirements would be documented in one place. . . thus Reducing time and effort required to analyze requirements Efficiently track the requirements Eliminate need to repeat or locating requirements during project staff transition or lengthy delay between phases Quickly identify conflicting or redundant requirements Facilitate accurate verification that requirement has been addressed Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 9

Agenda 1. Why Requirements Traceability? 2. Scenario: ORM based SDLC 3. Positioning Requirements in the SDLC 4. Business Requirements Metamodel Definitional 5. Business Requirements Metamodel – Tracking 6. Corporate SDLC mapping 7. Summary Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 10

An ORM based System Development Life Cycle at Transport Canada Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 11

An ORM based System Development Life Cycle at Transport Canada Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 12

An ORM based System Development Life Cycle at Transport Canada Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 13

Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 14

NIAM/ORM BPWin Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey ERWin Bridge An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 15

Agenda 1. Why Requirements Traceability? 2. Scenario: ORM based SDLC 3. Positioning Requirements in the SDLC 4. Business Requirements Metamodel Definitional 5. Business Requirements Metamodel – Tracking 6. Corporate SDLC mapping 7. Summary Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 16

Harmonizing the Business Requirements to the SDLC Model Suite Many SDLCs typically have a separate requirements collection phase along with identified deliverables… Search for the Holy Grail…. hoping to receive a Wal-Mart style packaged set of requirements! Hah! Enterprises usually start of in earnest with some kind of usable methodology…Use Cases, Functional Requirements doc, etc… Ends up in some divorced system development incarnation that is non-reflective of the specifications Business rules are buried somewhere in the code, with redundant code modules, totally missing business rules…etc…. Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 17

Reality of Business Requirements… Accumulate over several years in the form of e-mails, meeting minutes, memos, reports, consultant studies etc… In TC Transportation of Dangerous Goods Inspector Information System, we had over 150 docs over 10 years reflecting the business requirements as noted above… We needed to use what we had and not re-invent the wheel (Hey…as a consultant, I am not complaining if we went to reinvent the wheel!---but being down-to-earth, why go dejavu…? ) The ORM Metamodel for Business Requirements was born, based on collected documents… Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 18

Agenda 1. Why Requirements Traceability? 2. Scenario: ORM based SDLC 3. Positioning Requirements in the SDLC 4. Business Requirements Metamodel Definitional 5. Business Requirements Metamodel – Tracking 6. Corporate SDLC mapping 7. Summary Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 19

Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 20

Agenda 1. Why Requirements Traceability? 2. Scenario: ORM based SDLC 3. Positioning Requirements in the SDLC 4. Business Requirements Metamodel Definitional 5. Business Requirements Metamodel – Tracking 6. Corporate SDLC mapping 7. Summary Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 21

Track the requirement to an implementation component… Requirement may be implemented in several components… Only take the most primitive applicable component Can share the implementation of a requirement across components, but each needs to be primitive Duplicate requirements handled by family patriarch Added versioning and temporal… Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 22

Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 23

ER based metamodel for Business Requirements Transformed from ORM (Definitions) Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 24

ER based metamodel for Business Requirements Transformed from ORM (as implemented) Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 25

Table 1: Example Extract from on-gong requirements tracking…over 500 requirements DOCUMENT_I D REQ UIRE MEN T_SE Q_ID REQUIREMENT_TITLE_TXT REMEN T_STA TUS_C D IIS-004 40 Allow searching by manager name IIS-004 41 Allow searching by company name IIS-004 42 Allow searching by province IIS-004 43 Capture contact's e-mail address IIS-004 44 Produce a graph of companies having high violations IIS-004 45 Produce a graph of companies having high instance of certain violations IIS-005 R 1 1 Allow user to view and edit tombstone data IIS-005 R 1 2 Capture business type IIS-005 R 1 3 Capture dangerous good handled IIS-005 R 1 4 Capture means of containment used IIS-005 R 1 5 Capture means of transport used IIS-005 R 1 6 Keep a historical record of previous data values Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 26

Agenda 1. Why Requirements Traceability? 2. Scenario: ORM based SDLC 3. Positioning Requirements in the SDLC 4. Business Requirements Metamodel Definitional 5. Business Requirements Metamodel – Tracking 6. Corporate SDLC mapping 7. Summary Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 27

To Corporate SDLC mapping… Transport Canada uses Fujitsu’s Macroscope SDLC Requirement that all systems development docs be mapped The Macroscope doc identifier is created and the requirement from the ORM metamodel is mapped to that Macroscope doc…thus meeting corporate requirements Model is extended…(not shown) Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 28

Agenda 1. Why Requirements Traceability? 2. Scenario: ORM based SDLC 3. Positioning Requirements in the SDLC 4. Business Requirements Metamodel Definitional 5. Business Requirements Metamodel – Tracking 6. Corporate SDLC mapping 7. Summary Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 29

Summary Business requirements traceability metamodel provides the much required requirements lineage Captures all facets and incarnations of business requirements “as-they-happen…” Metamodel enables tracking of documents, tracking of actual requirements---projected into the realization and implementation of the stated requirements Metamodel allows navigability across multiple models involved in the SDLC, and supports the zig-zag or other development processes The requirement propositions have been ‘lobbed’ over to the user’s court for verification! Baba Piprani, Marlena Borg, Josée Chabot, Éric Chartrand, 12 Nov 2008, Monterrey An Adaptable ORM Metamodel to Support Traceability of Business Requirements across System Development Life Cycle Phases 30