1. OSLC PLM Workgroup1 Towards detailed use cases and alignment to OSLC V0.1 Gray Bachelor 18 th July 2011

2. OSLC PLM Workgroup2 Pains to target Increasing time and cost to manage integrity of complex system designs and its relevant requirements Increasing impact of an error arising from system design not updated correctly from changes Increasing need to coordinate work across larger and more dispersed work locations and organisational responsibilities

3. OSLC PLM Workgroup3 Business goal To reduce the time and cost to manage changes to complex systems arising from changes to requirements

4. OSLC PLM Workgroup4 There are 3 related concerns The primary domains of the target operating environment are  Product design  Enterprise integration  Corporate compliance

5. OSLC PLM Workgroup5 Product design

6. OSLC PLM Workgroup6 Existing OSLC sources Activity diagram  Who does what when Sequence diagram  Which system component does what when

7. OSLC PLM Workgroup7 Which roles Product change administrator (Should System Engineer (Must Sub-system owner (Should Software Engineer (Could Business analyst (Should IT administrator (Could Enterprise Integration developer (Must Application support leader (Could

8. OSLC PLM Workgroup8 Which scenarios OSLC PLM SE Scenario #1  A Systems Engineer responds to a change in requirements OSLC PLM EI Scenario #1  A Business Analyst identifies required information and process support for a SE scenario  An Integration Developer delivers process support through enterprise integration  An IT administrator deploys process support to users  An Application support leader handles problems with the deployed process support

9. OSLC PLM Workgroup9 Outline of Scenario #1 1. Assign & communicate the change request ( a1, a2, a3) Assign change request context Communicate change request Locate change request from notification 2. Apply request context to establish impacted requirements & implementation (a4, a5, a6) Locate requirements in change request context Create new revision of requirements context and reserve for editing Open new revision of context 3. Locate re-usable implementations to meet changed requirements (a7) Located reusable implementation to satisfy change? (A decision that drives alternative flows) 4a. Either update solution by way of adaption of re-usable implementations (a8, a9, a10, a13, a14, a15) Add selected implementation to change request as solution Merge selected implementation into context Trace to discipline responsibility Analyse detailed requirements & existing implementation Design minor updates to existing implementation Design by sub-team needed ? 4b. Or design solution by original design (a10, a11, a12, a15) Trace to discipline responsibility Design new implementation Add new design to change request solution Design by sub-team needed ? 5. Approve change request solution (a16, a17) Passed review of implementation for change request closure? Close change request * Note: 4 has alternative flows

10. OSLC PLM Workgroup10 Scenario Activity Diagram – 1 of 3 Page 1 of 3 Page 2 of 3

11. OSLC PLM Workgroup11 SE use-cases (1 of a3: View CR and its Product context a4: View impacted / new requirements View My CRs 1 Plan work a5: Reserve affected items a5: Create new revision of impacted configuration Start work a3: Locate CR a4: Explore associated information Collaborate with colleagues a6: Edit new revision Note 1: Assume CR is assigned, not claimed

12. OSLC PLM Workgroup12 Scenario Activity Diagram – 2 of 3 Page 2 of 3 Page 3 of 3 Page 2 of 3 Page 1 of 3 CR

13. OSLC PLM Workgroup13 SE use-cases (2 of Propose changes to requirements a7: Identify candidate solutions Update existing requirements a8: Add solution candidates to working set a7: Identify re-usable requirements Propose candidate solutions Collaborate with colleagues a14: Minor updates to solution Commit changes to requirements Gain approval for requirements changes a7: Identify impacted requirements Gain approval for system level candidates Gain approval for system level changes a9: Assess impact of working set changes Notify colleagues Search requirement catalog Search system catalog

14. OSLC PLM Workgroup14 SE use-cases (3 of Verify systems level design a11: System level design to meet changed requirements Propose system level changes Commit system level changes Gain approval for system level changes a12: Add system level design changes to solution proposal Collaborate with colleagues Notify colleagues Manage system level design changes

15. OSLC PLM Workgroup15 Scenario Activity Diagram – 3 of 3 Page 3 of 3 Page 2 of 3

16. OSLC PLM Workgroup16 SE use-cases (4 of Collaborate with colleagues a15: Identify sub-system owner a11: Preparation for sub-system or discipline engineering Notify project manager Approval for sub-system or discipline engineering a11: Proposal for sub-system or discipline engineering Estimate sub-system or discipline engineering Support the system level design Handle changes to system level design Release system level design package to sub-system Support design review Notify colleagues a16: Approve sub-system engineering Escalate sub-system engineering Search people catalog

17. OSLC PLM Workgroup17 Activity diagram analysis We don’t say what artefacts need to be dominated What is the vital meta-data to make association ?

18. OSLC PLM Workgroup18 Object diagram Role User Org CR Product Requirement set Requirement Configuration Note Issue Catalog Review meeting System component Verification artefact Approval Work item Plan System artefactRequirement artefact Product artefact CR artefact Target Practice BugWork estimate Budget Customer Order Market segment Product family Portfolio

19. OSLC PLM Workgroup19 Supporting objects and types Document Model configuration Model element Types Use case Activity diagram Sequence diagram Stakeholder requirement System requirement State machine Algorithm Regulatory requirement Practice catalog Capability catalog Product catalog Requirements catalog System catalog System component catalog People catalog Test case Verification result Metric Configuration More detailed related objects

20. OSLC PLM Workgroup20 SE use-cases (1 of a3: View CR and its Product context a4: View impacted / new requirements View My CRs 1 Plan work a5: Reserve affected items a5: Create new revision of impacted configuration Start work a3: Locate CR a4: Explore associated information Collaborate with colleagues a6: Edit new revision Note 1: Assume CR is assigned, not claimed

21. OSLC PLM Workgroup21 More detailed use case a3.1: Open CR a4: View impacted / new requirements View My CRs 1 a3: Locate CR Login Set my profile a3.3: View CR product context a3.2: Explore & view CR Query product context Query CR Query requirements Query requirements baseline a3.4: Locate CR affected requirements Query Work Item Open Work Item

22. OSLC PLM Workgroup22 Next steps For detailed area identified  Clarify objects  Identify attributes  Identify use of existing services  Identify extensions Propose to look at the preceding stage to build up the CR