OLSC PLM Workgroup1 DOORS input for OSLC Storyboard V0.2 15/4 Gray Bachelor.

Slides:



Advertisements
Similar presentations
Chapter 7 System Models.
Advertisements

Cost Report Changes to Improve Accuracy of Cost-Based DRG Weights Cost Report Workgroup Findings September 2007.
Chapter 11 Designing the User Interface
Story 1 Preconditions – Step00
ONLINE DISSERTATION HELP METHODOLOGY SECTION
1 CS 446 – Tutorial 6 Frid. Nov. 6 th, 2009 Implementation Tutorial.
Slide 01 (of 22)Title 26/04/2010 Version 1.0 GUIDE to ‘SIMPLE’ Mouse click to continue AN OVERVIEW OF BT’s CONVEYACE INVOICE RECONCILIATION ASSISTANCE.
North American Electric Reliability Council 1 Coordinate Operations Standard Jason Shaver Standard Drafting Team Chair September 29, 2005.
OSLC PLM Workgroup1 Towards detailed use cases and alignment to OSLC V0.2 Gray Bachelor 19 th July 2011.
Use Case & Use Case Diagram
Chapter 3 Designing a Newsletter
OSLC PLM Workgroup1 Analysing the PLM reference model V0.3 Gray Bachelor.
July 11 th, 2005 Software Engineering with Reusable Components RiSE’s Seminars Sametinger’s book :: Chapters 16, 17 and 18 Fred Durão.
InterPARES Project Joanne Evans, School of Information Management and Systems, Monash University Description Cross-domain Description Cross Domain - Metadata.
Modified from Sommerville’s originalsSoftware Engineering, 7th edition. Chapter 8 Slide 1 System models.
PowerPoint Presentation for Dennis & Haley Wixom, Systems Analysis and Design Copyright 2000 © John Wiley & Sons, Inc. All rights reserved. Slide 1 Process.
7. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Detailed Object-Oriented Requirements Definitions  System Processes—A Use.
Functional Requirements – Use Cases Steve Chenoweth & Chandan Rupakheti (Chapters 14, 21 – Requirements Text)  Quiz question 9 relates to this, when you’ve.
Software engineering Olli Alm Lecture 2: requirements, modelling & representation.
Chapter 13: Designing the User Interface
Instructions & Notes This template was created to help you: – Show the team where you are going via slides representing each planned activity. – Keep your.
CMPT 275 Software Engineering
Software Engineering 8. System Models.
For OSLC PLM Workgroup meeting 7th Dec Analysis of the OSLC Specs and the PLM Reference model in the context of SE Scenario #1 V0.6 December 7 th.
1 Chapter 2 Revision: Documentation DFD System FC.
OSLC ALM-PLM interoperability Discussion. OSLC PLM extensions Product Product, Version isVersionOf AMG54556_002 Product, View hasView AMG54556/001-View.
Methods For Web Page Design 6. Methods Why use one? What it covers –Possibly all stages Feasibility Analysis Design Implementation Testing –Maybe just.
Chapter 7 Structuring System Process Requirements
1 Project Name Team Lead Location Month XX, Year.
Story 2 Preconditions – Step2.0 AMG54556/002 Top Level HSUVExample released and Open in Teamcenter Rich Client Requirements Manager.
Requirement Engineering. Review of Last Lecture Problems with requirement Requirement Engineering –Inception (Set of Questions) –Elicitation (Collaborative.
CMPT 275 Software Engineering
University Of Palestine. Department of Information Technology.
OSLC PLM Workgroup1 ALM-PLM terms Prep for Oct 5th.
Welcome to “Creating an eLearning Course”. Navigating the Course.
22 November Databases. Presentations Tega: news 1954 Prediction.
OSLC PLM Workgroup visit URL for terms of usage1 OSLC PLM Workgroup PLM Scenarios Systems Engineering scenario “Systems Engineer Reacts to Changed Requirements”
IFS310: Module 6 3/1/2007 Data Modeling and Entity-Relationship Diagrams.
Unified Modeling Language User Guide Section 4 - Basic Behavioral Modeling Chapter 16 - Use Cases Chapter 17 - Use Case Diagrams.
OLSC PLM Workgroup1 DOORS input for OSLC Storyboard V0.1 Gray Bachelor.
OSLC PLM Reference model April Summary of the OSLC PLM Reference Model V0.4 April 4th 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
Topic 5 Initiating a project
OSLC Core extensions proposal
INFO3600 Capstone Projects Week 4. Overview Where should you be now? What are the pragmatics of getting established? The grading over the next 2 weeks.
System Requirements Specification
Power Point Tutorial Sharon Lipka,BS.,C-RT(R). PowerPoint uses a graphical approach to presentations in the form of slide shows that accompany the oral.
OSLC PLM Workgroup 7/12/20101 The PLM Reference model in the context of SE Scenario #1 V0.6 December 7 th 2010 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
OSLC PLM workgroup workings1 OSLC PLM Spec analysis Consolidation from previous discussions 29/3 inc meeting notes.
© OSLC OSLC PLM Workgroup1 OSLC Core extensions proposal Update of the Core WG proposal V0.9.
INFORMATION X INFO415: Systems Analysis.
UPLOADING DOCUMENTS IN MURA. Two Options 1.Upload as a “page” in your navigation (preferred)  Easier to find, delete and maintain  Can upload revisions.
CM Spec analysis Markup from discussion 15/3. Summary of the scenario by way of the key business entities & their relationships CR Req Implem System or.
Draft for discussion1 OSLC PLM roadmap discussion Aug 30 th 2011 Rainer Ersch Gray Bachelor V0.4 updated at meeting Aug 30th.
OSLC PLM Reference model February Summary of the OSLC PLM Reference Model V0.2 February 22 nd 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
Software Testing-STLC
OSLC PLM Workgroup1 Towards detailed use cases and alignment to OSLC V0.1 Gray Bachelor 18 th July 2011.
Component and Deployment Diagrams
Recall The Team Skills Analyzing the Problem (with 5 steps)
TRADING STOCK PAGE 295 NAME, TEACHER AND DATE.
Use Case Model.
Conducting the performance appraisal
Process Modelling Chapter 6.
Abstract descriptions of systems whose requirements are being analysed
Conducting the performance appraisal
How to Use the Story Board Layout
COMP 208/214/215/216 – Lecture 7 Documenting Design.
Using Use Case Diagrams
Systems Design Project Deliverable 3
How to Use the Story Board Layout
Chapter 4: Project Integration Management
Presentation transcript:

OLSC PLM Workgroup1 DOORS input for OSLC Storyboard V0.2 15/4 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 Derived from REQ REQ A No issatisfiedby Derived from REQ REQ A No issatisfiedby Supports the variants Post of Step 2.2 REQ A No issatisfiedby Supports the variants Post of Step 2.2 REQ A No issatisfiedby Supports the variants 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 REQ A Derived from REQ A Issatisfiedby link to ?? Decide on Implementation ref REQ A No issatisfiedby Derived from REQ A Issatisfiedby link to ?? Decide on Implementation ref 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 Mikes 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

OLSC PLM Workgroup11 Overview from Neal – current status

OLSC PLM Workgroup12 Changed req after base line

OLSC PLM Workgroup13 Query contents of a baseline set

OLSC PLM Workgroup14 Changes and issues V0.2Update 15/4 with Neal and Mike Implementation refs need checking