OLSC PLM Workgroup1 DOORS input for OSLC Storyboard V0.1 Gray Bachelor

OLSC PLM Workgroup2 Aims and objective To show how real ALM tools support and represent PLM process and related information To show how DOORS 9.3 represents the OSLC PLM Reference Model through the selected scenario of a Systems Engineer responds to change in Requirements

OLSC PLM Workgroup3 Purpose of this document To summarise the flow of changes to the requirements that DOORS needs to represent

OLSC PLM Workgroup4 Summary of the key business entities & their relationships CR Req Implem System or product context Pre-condition (Before Controlled config Is based upon or applies to* Post-condition (After CR System or product context Is implemented by Req Implem Controlled config System or product context Req Implem Controlled config * Assuming basic triaging has been done prior to the start of the scenario At some context version V’ At some new context version V’’ Updated to achieve the CR

OLSC PLM Workgroup5 Overall view of the scenario and naming Story 1 1 st set of changes to requirements Steps 0.0 to 0.4 Implement the 1 st set of changes Steps 1.0 to 1.X Story 2 2nd set of changes to requirements Steps 2.0 to 2.X Implement the 2 nd set of changes Steps 3.0 to 3.X In the kitchen ready

OLSC PLM Workgroup6 Summary of the Scenario flow from a tools perspective – Story to 0.4 We aim to show the tool status at end phase in the flow a 0.2b

OLSC PLM Workgroup7 Story 1 Requirements changes to be shown as DOORS baselines through the scenario RequirementContext fromTo contextNotes Starting pointAll 3 exist-Pre condition 0.0 REQ A No issatisfiedby B No issatisfiedby Post of Step 0.2a REQ A Issatisfiedby link to AMG60104/001 B No issatisfiedby Post of Step 0.2a Text changes too Post 02b AKY251614A Association with Product AMG 54556/001 and Implementation AMG60112/001 B No issatisfiedby Post Step 0.3 REQ B No issatisfiedby B Issatisfiedby link to AMG60104/002 Post Step 1.1 AKY251614B No issatisfiedby B Issatisfiedby link to AMG60112/002 Post Step 1.2 AKY251614B Issatisfiedby link to AMG60112/001 B Association with Product AMG 54556/002 and Issatisfiedby link to AMG60112/002 Post Step 1.3

OLSC PLM Workgroup8 Story 2 New and changed requirements to be shown as DOORS baselines through the scenario RequirementContext fromTo contextNotes Starting pointAll 3 exist-Pre condition based on 1.3 REQ A No issatisfiedby Post of Step 2.2 REQ A No issatisfiedby Post of Step 2.2 REQ A No issatisfiedby Post of Step 2.2 REQ-20144B Issatisfiedby link to AMG60104/002C No issatisfiedby Post of Step 2.3 REQ-20181B No issatisfiedby C No issatisfiedby Post of Step 2.5 AKY251614B Association with Product AMG 54556/002 and Issatisfiedby link to AMG60112/002 C No issatisfiedby Post Step 2.7 AKY251614C No issatisfiedby C iscomposedof REQ Post Step 2.7

OLSC PLM Workgroup9 Story 2 New and changed requirements to be shown as DOORS baselines through the scenario RequirementContext fromTo contextNotes REQ-20144C No issatisfiedby C Issatisfiedby link to AMG60104/003 ??? Post 3.2 REQ C No issatisfiedby A Issatisfiedby link to ??? Post 3.2 REQ C No issatisfiedby A Issatisfiedby link to ??? Post 3.2 AKY251614C Issatisfiedby link to ??? C Issatisfiedby link to ??? And Association with Product AMG 54556/003 Post 3.3

OLSC PLM Workgroup10 Links Mike’s page services.net/bin/view/Main/PlmScenariosGm services.net/bin/view/Main/PlmScenariosGm Files used at 14/4  HSUVExample_Story_1.pptx: Story 1 (Requirements Change) Step by Step Description with Pictures (updated to match revisions of above)  # HSUVExample_Story_2.pptx (WORK IN PROCESS) Slides describing the Story 2 sequence, which adds two variants of the emissions requirement