Presentation is loading. Please wait.

Presentation is loading. Please wait.

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.

Similar presentations


Presentation on theme: "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."— Presentation transcript:

1 CM Spec analysis Markup from discussion 15/3

2 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

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

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

5 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

6 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

7 http://open-services.net/bin/view/Main/CmSpecificationV2 Set of 6 states  “State predicate properties Set of relationships  “Relationship properties:

8 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

9 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

10 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

11 PLM CR rel Activity method assignment Affected items assignment

12 Version comments dcterms has today  Resource A “has versions” Resource B  Resource B “is version of” Resource A  http://web.resource.org/rss/1.0/modules/dcterm s/

13 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

14 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


Download ppt "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."

Similar presentations


Ads by Google