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.

Slides:



Advertisements
Similar presentations
Dr. Leo Obrst MITRE Information Semantics Information Discovery & Understanding Command & Control Center February 6, 2014February 6, 2014February 6, 2014.
Advertisements

OLSC PLM Workgroup1 DOORS input for OSLC Storyboard V0.2 15/4 Gray Bachelor.
Configuration management
Configuration Management
FPA – IFPUG CPM 4.1 Rules.
OSLC PLM Workgroup1 Towards detailed use cases and alignment to OSLC V0.2 Gray Bachelor 19 th July 2011.
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
1 Software Requirement Analysis Deployment Package for the Basic Profile Version 0.1, January 11th 2008.
January Ron McFadyen1 Use Cases in the UML Functionality under consideration is represented by use cases (named ellipses) enclosed in a box.
OSLC PLM Workgroup1 Analysing the PLM reference model V0.3 Gray Bachelor.
SE 555 Software Requirements & Specification Requirements Management.
Further Data Modelling …and the effect of time. Plan Introduction Structured Methods –Data Flow Modelling –Data Modelling –Relational Data Analysis –Further.
IIBA Denver | may 20, 2015 | Kym Byron , MBA, CBAP, PMP, CSM, CSPO
The OOA Process - I Steps and Rules Objects and Structures.
Configuration Management
CSSE 375 Software Construction and Evolution: Configuration Management
UML Class Diagrams: Basic Concepts. Objects –The purpose of class modeling is to describe objects. –An object is a concept, abstraction or thing that.
This chapter is extracted from Sommerville’s slides. Text book chapter
Question 1: (20 Points – 4 Points Each)
XP New Perspectives on XML Tutorial 4 1 XML Schema Tutorial – Carey ISBN Working with Namespaces and Schemas.
Configuration Management Managing Change. Points to Ponder Which is more important?  stability  progress Why is change potentially dangerous?
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.
The Data Attribution Abdul Saboor PhD Research Student Model Base Development and Software Quality Assurance Research Group Freie.
OSLC Working group meeting1 PLM extensions proposal feedback Updated from OSLC workgroup call 18/10/11.
OSLC ALM-PLM interoperability Discussion. OSLC PLM extensions Product Product, Version isVersionOf AMG54556_002 Product, View hasView AMG54556/001-View.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
Configuration Management (managing change). Starter Questions... Which is more important?  stability  progress Why is change potentially dangerous?
1 CMPT 275 Phase: Design. Janice Regan, Map of design phase DESIGN HIGH LEVEL DESIGN Modularization User Interface Module Interfaces Data Persistance.
1 UML Basic Training. UML Basic training2 Agenda  Definitions: requirements, design  Basics of Unified Modeling Language 1.4  SysML.
CS3773 Software Engineering Lecture 04 UML Class Diagram.
Integrating Modeling Tools in the Development Lifecycle with OSLC Miami, October 2013 Adam Neal (Presenter) Maged.
Taxonomic Concept Transfer Schema Robert Kukla. Transfer Schema Taxonomic units of interest? Which details do we need to record? What relationships between.
OSLC PLM Workgroup1 ALM-PLM terms Prep for Oct 5th.
OSLC PLM Workgroup visit URL for terms of usage1 OSLC PLM Workgroup PLM Scenarios Systems Engineering scenario “Systems Engineer Reacts to Changed Requirements”
Use Case Driven Analysis Requirements Use Case Use Case Description System Sequence Diagram Chapter 5.
1 Tutorial 12 Working with Namespaces Combining XML Vocabularies in a Compound Document.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
SCORM Course Meta-data 3 major components: Content Aggregation Meta-data –context specific data describing the packaged course SCO Meta-data –context independent.
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.
Sept Ron McFadyen1 Use Cases Introduced by Ivar Jacobson in 1986 literal translation from Swedish ”usage case” Used to capture and describe.
OSLC Core extensions proposal
1 Chapter 12 Configuration management This chapter is extracted from Sommerville’s slides. Text book chapter 29 1.
Ontology Evaluation, Metrics, and Metadata in NCBO BioPortal Natasha Noy Stanford University.
Synchronise work on DEXs and reference data between PLCS pilots and OASIS/PLCS Workshop #3 10 – 11 November 2004.
PRO/ARC and TST/PRO joint sessions at TP20 Group Name: oneM2M TP20 Source: Peter Niblett, IBM Meeting Date:
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.
OASIS ebXML Registry Standard Open Forum 2003 on Metadata Registries 10:30 – 11:15 January 20, 2003 Kathryn Breininger The Boeing Company Chair, OASIS.
McGraw-Hill/Irwin© 2008 The McGraw-Hill Companies, All Rights Reserved Chapter 17 Object-Oriented Design and Modeling Using the UML.
© OSLC OSLC PLM Workgroup1 OSLC Core extensions proposal Update of the Core WG proposal V0.9.
Describing resources II: Dublin Core CERN-UNESCO School on Digital Libraries Rabat, Nov 22-26, 2010 Annette Holtkamp CERN.
1 CAA 2009 Cross Cal 9, Jesus College, Cambridge, UK, March 2009 Caveats, Versions, Quality and Documentation Specification Chris Perry.
SysML/AP233 Mapping Status INCOSE IW MSDS Report Phil Spiby and Allison Feeney 1.
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.
OSLC PLM Workgroup1 Towards detailed use cases and alignment to OSLC V0.1 Gray Bachelor 18 th July 2011.
Allison Barnard-Feeney Dr Phil Spiby
Configuration Management
Use Case Model.
Unified Modeling Language
Configuration Management
SysML 2.0 Model Lifecycle Management (MLM) Working Group
Data Dictionaries ER Diagram.
Configuration Management (managing change)
UML to XSD.
UML Class Diagrams: Basic Concepts
LESSON 01 Hands-on Training Execution
Database Design Hacettepe University
New Perspectives on XML
Presentation transcript:

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 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

STEP supports PLM representation of System & Product decomposition e.g. AP233

PLM Reference model can be further built out to support model driven development Base diagram from OMG Applied in the PLM Reference Model

CRs typically don’t exist stand alone CR can be an enhancement or a correction or some combination  Prioritised for criticality, value  Grouped by impact area  Grouped and sequenced for effectivity CRs need to be associated and managed (inc merge, split, superced

CR resource behaviour Have today Need  Identify in product and/or system context  Heterogeneous problem list (of affected items)  Heterogeneous solution list  Enterprise approval  Group, sequence, deprecate

Set of 6 states  “State predicate properties Set of relationships  “Relationship properties:

CM 1 of 2 QuestionOSLC CM AnswerPLM Reference model Answer How is a CR defined ?CR is a type. A CR resource has a shape which prescribe a set of mandatory attributes CR is not currently addressed in the PLM Reference Model. AP233 and AP239 have the possibility How is a CR uniquely identifiedGlobally by a URI. Within the service provider by a dcterms identifier within a given container scope (relative to) By a CR id within an enterprise or container scope (repository) What determines the rules for representing a CR ? CM Spec 2.0 Model rules (RDF) Resource shape per scenario (Create, Query, Instance state FILE_SCHEMA (('AP233_SYSTEMS_ENGINEERING_ARM_LF')); (To validate) What is the visibility of the CR description ? Global? Header includes the names, time stamp, org How is CR meta-data defined ? E.g. organisational ownership Title and identifier are mandatory plus optional properties defined by service provider properties In the PM Schema ID, name and description see Work Request / Work Order page How is the relationship between CR and other resources defined ? Named optional relationship properties available for use properties Activity method assignment Affected items assignment How to version a CR ?Dcterms: Modified date changes the http header etag ITEM & ITEM_VERSION associated with a VIEW_DESCRIPTION CR Req Implem System or product context Controlled config

CR 2 of 2 QuestionOSLC AnswerPLM Reference model Answer How are groups of CR organised ? Identifying as a group Treat as a group e.g. Approve, implement, assign to a block or an organisational unit as group e.g. a black box approach “satisfiedby” Short hand By a common attribute or through association with say back to another OSLC resource like single Requirement oslc_cm:relatedChangeRequest (valid via tags e.g. oslc_cm:implementsRequirement OSLC lacks the explicit “isComposedBy” CRs can be grouped for implementation as a change activity and an effectivity AP239 has effectivity parameters Check in AP233 / AP239 Identify interdependency 3 types * related - Identifies a loose relationship between a Change Request and referenced resource. These relationships can be used to name associated resources managed by other service providers. * tracks - Identifies that a Change Request is used to track the lifecycle of referenced resource. From the CM tool perspective, these relationships can be used to track work that needs to be done for referenced resources. * affects - Indicates that the Change Request affects, has been predetermined to have impact, related resource. These property relationships can be used to understand the potential impact of referenced resources. Uses: URI (not titles) (Uses is not well defined e.g. to mean “isComposedby” Uses is a reference to another resource (as opposed to the strong decomposition inherent in UML) Open set (not supported) Tracelink here e.g. for an external link CR Req Implem System or product context Controlled config

AP233 Module 1042 In the Project Mngmnt schema Work request id mand Version mand Purpose Description (opt  Affected items Number Type  Status Work Order  Authorisation for Work request

PLM CR rel Activity method assignment Affected items assignment

Version comments dcterms has today  Resource A “has versions” Resource B  Resource B “is version of” Resource A  s/

CR Context 1 of 2 QuestionOSLC AnswerPLM Reference model Answer How is the root context defined ? (Using a tiering concept for context Service Provider (may not be the authority STEP Filename and date created (as a snapshot for data exchange Organisation ? Have parts been assigned to blocks ? What constrains the context description ? FILE_SCHEMA (('AP233_SYSTEMS_ENGINEERING_ARM_LF')); #20=ACTIVITY_METHOD('XSLT_Extract','XSLT Extract of STEP Part 21 Data File from Topcased SysML XMI','','For initial creation of dataset'); In what context is a requirement valid ? Valid everywhere Qualified by associations e.g. Query project name in a WI See above CR Req Implem System or product context Controlled config

CR Context 2 of 2 QuestionOSLC AnswerPLM Reference model Answer How is project, product or system context defined ? e.g. a WI within a Jazz project as a proxy for a new System release ? e.g. a name or property of a baseline / cfg ? Identity, name and a version in reality this as an entry point to a config #23600=SYSTEM('23600','HybridSUV','HybridSUV System'); #23610=SYSTEM_VERSION('1','HybridSUV System Element Version',#23600); How is product & system coding and classification supported ? Not available except by tags or attributes to a thing – tags or attributes (see note below about requirements specifically Use the PRT or PRODUT or SYSTEM structure to define a taxonomy and then create associations How is a CR associated with a project, product or system coding & classification ? Through a CR attribute Locate via Product or Product View Definition CR Req Implem System or product context Controlled config