olsc plm workgroup1 doors input for oslc storyboard v0.1 gray bachelor
TRANSCRIPT
OLSC PLM Workgroup 1
DOORS input for OSLC Storyboard
V0.1
Gray Bachelor
OLSC PLM Workgroup 2
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 Workgroup 3
Purpose of this document
To summarise the flow of changes to the requirements that DOORS needs to represent
OLSC PLM Workgroup 4
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
Updated to achieve the CR
OLSC PLM Workgroup 5
Overall view of the scenario and naming
Story 1
1st set of changes to requirementsSteps 0.0 to 0.4
Implement the 1st set of changesSteps 1.0 to 1.X
Story 2
2nd set of changes to requirementsSteps 2.0 to 2.X
Implement the 2nd set of changesSteps 3.0 to 3.X
In the kitchenready
OLSC PLM Workgroup 6
Summary of the Scenario flow from a tools perspective – Story 1 0.0 to 0.4
We aim to show the tool status at end phase in the flow
0.0
0.2a
0.2b
0.3
0.4
OLSC PLM Workgroup 7
Story 1 Requirements changes to be shown as DOORS baselines through the scenario Requirement Context from To context Notes
Starting point All 3 exist - Pre condition 0.0
REQ-020181 A
No issatisfiedby
B
No issatisfiedby
Post of Step 0.2a
REQ-020144 A
Issatisfiedby link to
AMG60104/001
B
No issatisfiedby
Post of Step 0.2a
Text changes too Post 02b
AKY251614 A
Association with Product AMG 54556/001 and Implementation AMG60112/001
B
No issatisfiedby
Post Step 0.3
REQ-020144 B
No issatisfiedby
B
Issatisfiedby link to AMG60104/002
Post Step 1.1
AKY251614 B
No issatisfiedby
B
Issatisfiedby link to AMG60112/002
Post Step 1.2
AKY251614 B
Issatisfiedby link to AMG60112/001
B
Association with Product AMG 54556/002 and Issatisfiedby link to AMG60112/002
Post Step 1.3
OLSC PLM Workgroup 8
Story 2 New and changed requirements to be shown as DOORS baselines through the scenario Requirement Context from To context Notes
Starting point All 3 exist - Pre condition based on 1.3
REQ-020186 - A
No issatisfiedby
Post of Step 2.2
REQ-020187 - A
No issatisfiedby
Post of Step 2.2
REQ-020188 - A
No issatisfiedby
Post of Step 2.2
REQ-20144 B Issatisfiedby link to AMG60104/002 C
No issatisfiedby
Post of Step 2.3
REQ-20181 B
No issatisfiedby
C
No issatisfiedby
Post of Step 2.5
AKY251614 B Association with Product AMG 54556/002 and Issatisfiedby link to AMG60112/002
C
No issatisfiedby
Post Step 2.7
AKY251614 C
No issatisfiedby
C
iscomposedof REQ-020186
Post Step 2.7
OLSC PLM Workgroup 9
Story 2 New and changed requirements to be shown as DOORS baselines through the scenario Requirement Context from To context Notes
REQ-20144 C
No issatisfiedby
C
Issatisfiedby link to AMG60104/003 ???
Post 3.2
REQ-020187 C
No issatisfiedby
A
Issatisfiedby link to ???
Post 3.2
REQ-020188 C
No issatisfiedby
A
Issatisfiedby link to ???
Post 3.2
AKY251614 C
Issatisfiedby link to ???
C
Issatisfiedby link to ??? And Association with Product AMG 54556/003
Post 3.3
OLSC PLM Workgroup 10
Links
Mike’s page http://open-services.net/bin/view/Main/PlmScena
riosGm 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