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

OSLC PLM Workgroup2 What’s in here ? This is working material used to build out the OSLC PLM scenarios to support more detailed workings on Spec usage and extension by way of detailed use-cases and data analysis leading to service identification and modification This aims to work up ideas ahead of building up more formal models

OSLC PLM Workgroup3 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

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

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

OSLC PLM Workgroup6 Product design

OSLC PLM Workgroup7 Existing OSLC sources Activity diagram  Who does what when Sequence diagram  Which system component does what when

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

OSLC PLM Workgroup9 Which scenarios OSLC PLM SE Scenario #1  A Systems Engineer responds to a change in requirements OSLC PLM SE Scenario #2 New  A Product Change owner assigns a change to a product release plan OSLC PLM EI Scenario #1 New  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

OSLC PLM Workgroup10 OSLC PLM SE Scenario #1 A Systems Engineer responds to a change in requirements

OSLC PLM Workgroup11 Outline of OSLC PLM SE 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

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

OSLC PLM Workgroup13 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

OSLC PLM Workgroup14 Scenario Activity Diagram – 2 of 3 Page 2 of 3 Page 3 of 3 Page 2 of 3 Page 1 of 3 CR

OSLC PLM Workgroup15 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

OSLC PLM Workgroup16 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

OSLC PLM Workgroup17 Scenario Activity Diagram – 3 of 3 Page 3 of 3 Page 2 of 3

OSLC PLM Workgroup18 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

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

OSLC PLM Workgroup20 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

OSLC PLM Workgroup21 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

OSLC PLM Workgroup22 More detailed analysis of the Requirement Change Handling towards OSLC service alignment

OSLC PLM Workgroup23 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

OSLC PLM Workgroup24 Example of use cases: understanding the impact of changes to Requirements 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 Colouring represents different “levels” aN were in the Activity diagram, aN.M are new

OSLC PLM Workgroup25 Next steps Align to sequence diagrams 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

OSLC PLM Workgroup26 OSLC PLM SE Scenario #2 New A Product Change owner assigns a change to a product release plan

OSLC PLM Workgroup27 Assumptions about CRs These arise from  customer request or marketing input (requests  internal feedback from quality assessment  analysis of field problems i.e. bugs that require more significant action

OSLC PLM Workgroup28 The CR preparation area to focus upon The assignment of the CR to a product context  Identity, version or release  Organisation, product responsible Optionally  The association of CR with any related requirements, requests or associated information  The association of a the CR with an existing (e.g. in process) configuration

OSLC PLM Workgroup29 Clarification of what mean to achieve by assignment and association The primary goal is to assign a CR to a target development org, responsible and activity to answer the customers question  “who is assigned to work on my request ?” The secondary goal is to assign a CR to a target product, release / system build plan, to answer the customers question  “when will it be available?” We may associate requirements and existing configurations as targets, candidates or hints prior to significant work beginning  Work may start using one configuration as a basis and be switched to another as work progresses or plans finalised, even up to a late stage of commitment in some cases  Requirements may get altered as the work proceeds, there is likely to be some changes up until a commit point where a core set of requirements becomes a must/shall and others marked for attention by development depending upon available time/resource. Typically organisations only assign resource to the must/shall, in some cases the assigned requirements and their ranking priorities are modified in flight such as to alter the CR and/or requirement to another CR, release, requirement

OSLC PLM Workgroup30 Out of scope Assessment of importance Analysis of feasibility, high level design or solutioning Estimating, Costing and revenue estimation Refinement of Cust Request to Formal CR CR triage, split, group, merge, consolidate, refine and extend Portfolio trade-off or scenarios prior to commitment Risk assessment Release planning Commitment to Plan Spin off to new product, variant or devt (e.g. project, org) Grouping in a queues prior to handling Escalation to win product responsibility acceptance Descoping or changes to assignment Negotiation of requirements to meet and contract a CR

OSLC PLM Workgroup31 CR handling cases CRs that prescribe a (target) product release (Yes CRs that need to be negotiated prior to acceptance by a product owner (OOS) CRs that fall into a single product area (Yes CRs that span multiple products (OOS CRs where there is an existing devt stream CRs where there is no existing stream (OOS) CRs that are queued not fully assigned (OOS

OSLC PLM Workgroup32 Introduction to the CR assignment and association use cases A relatively full and rich set of steps are shown These of course can be collapsed to  Query available products – select one  Query available versions – select one  Query available requirements baselines – select one  Query available requirements – select n  Query available configurations – select one

OSLC PLM Workgroup33 Sketch of the preceding Activity Diagram: Assigning a CR to a Product Context Assign to product area responsible Assign to orgs Assign to product families Assign to products 1 Assign to releases 1 Assign to CR stream Product unassigned Assign to product manager Assign to portfolio manager Assign to release manager Assign to architect analyst/SE Validate product assignment Capture notes Raise issues to addressAnalyse description Consult product analysts Approve Note 1 – one product release only Confirm product assignment Notify responsibles

OSLC PLM Workgroup34 Example of use cases: Assigning a CR to a Product Context (Basic stuff same as before a3.1: Open CR View My CRs 1 a3: Locate CR Login Set my profile a3.2: Explore & view CR Query CR Query Work Item Open Work Item Colouring represents different “levels” aN were in the Activity diagram, aN.M are new ….. Overleaf

OSLC PLM Workgroup35 Example of use cases: Assigning a CR to a Product Context Select available products a3.3: View CR product context Query products Associate Product Context with CR 1. Colouring represents different “levels” aN were in the Activity diagram, aN.M are new 2. a3.3 is included if a context is already assigned Identify available products Select available product version Identify available product releases Query product versions Approve product context Query Product Context of CR Validate product context

OSLC PLM Workgroup36 Sketch of the preceding Activity Diagram: Optionally associating requirements Existing requirements linked ?Validate existing requirements Analyse descriptionLocate relevant requirements Capture notes Raise issues to address Identify product coverage Identify product responsibility Update product responsibility ? Consult SMEs Validate product assignment Approve Select / propose relevant requirements Confirm associated requirements Call meetings / raise to-dos Support CR/Req mtgs Notify responsibles

OSLC PLM Workgroup37 Example of use cases: Optionally associating requirements (Basic stuff same as before a3.1: Open CR View My CRs 1 a3: Locate CR Login Set my profile a3.2: Explore & view CR Query CR Query Work Item Open Work Item Colouring represents different “levels” aN were in the Activity diagram, aN.M are new ….. Overleaf

OSLC PLM Workgroup38 Example of use cases: Optionally associating requirements Select product context requirements a3.3: View CR product context Query requirements Associate Requirement with CR 1. Colouring represents different “levels” aN were in the Activity diagram, aN.M are new 2. Side by side comparison is out of scope here Identify product context requirements Select requirement Identify available requirements Query products Validate associated requirements Query Product Context of CR Evaluate product context of identified requirements Query product versions Approve associated requirements Query associated Requirements of CR

OSLC PLM Workgroup39 Sketch of the preceding Activity Diagram: Optionally associating configurations Existing configurations linked ? Validate existing configurations Analyse description Locate relevant configurations from product releases Capture notes Raise issues to address Identify product coverage Identify product responsibility Update product responsibility ? Consult SMEs Validate product assignment Approve Locate relevant configurations from requirements Select / propose relevant configurations Confirm associated configurations Call meetings / raise to-dos Support CR/Req mtgs Notify responsibles

OSLC PLM Workgroup40 Example of use cases: Optionally associating configurations (Basic stuff same as before a3.1: Open CR View My CRs 1 a3: Locate CR Login Set my profile a3.2: Explore & view CR Query CR Query Work Item Open Work Item Colouring represents different “levels” aN were in the Activity diagram, aN.M are new ….. Overleaf

OSLC PLM Workgroup41 Example of use cases: Optionally associating configurations Select product context configurations a3.3: View CR product context Query configurations Associate Configuration with CR 1. Colouring represents different “levels” aN were in the Activity diagram, aN.M are new 2. Side by side comparison is out of scope here Identify product context configurations Select configuration Identify available configurations Validate associated configurations Query Product Context of CR Evaluate product context of identified configurations Approve associated configurations Identify product configurations of associated requirements Associate Configuration with Requirement and CR Query Requirement Associated with CR Query associated Requirements of CR

OSLC PLM Workgroup42 Proposal at 19/7 1.Organisational assignment OOS 2.If Product “included in” and “consists of” allow n:m assignment i.e. loose collections then Product Family can be treated as a type of Product, hence deprecated 3.Validation of relevance of assignment and association is by query with possible annotation by SME/Analyst i.e. judgement not by testing configuration rules 4.Address assignment to 1 product release only 5.Re-Confirm product assignment, requirement and configuration association should include saving or “registering” the relationship

OSLC PLM Workgroup43 Changes V0.1 Initial version V0.2 Updates to include the CR assignment to product context and relevant requirements