1 / 14

CM Spec analysis

CM Spec analysis. Markup from discussion 15/3. Summary of the scenario by way of the key business entities & their relationships. Pre-condition (Before. Is based upon or applies to*. CR. * Assuming basic triaging has been done prior to the start of the scenario. At some context version V’.

olesia
Download Presentation

CM Spec analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

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 Pre-condition (Before Is based upon or applies to* CR * Assuming basic triaging has been done prior to the start of the scenario At some context version V’ System or product context Controlled config Req Implem Post-condition (After Is implemented by At some new context version V’’ CR System or product context System or product context Controlled config Controlled config Req Implem Req Implem Updated to achieve the CR 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 Applied in the PLM Reference Model Base diagram from OMG

  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. Have today Need Identify in product and/or system context Heterogeneous problem list (of affected items) Heterogeneous solution list Enterprise approval Group, sequence, deprecate CR resource behaviour

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

  8. CR System or product context Req Implem Controlled config CM 1 of 2

  9. CR System or product context Req Implem Controlled config CR 2 of 2

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

  13. CR System or product context Req Implem Controlled config CR Context 1 of 2

  14. CR System or product context Req Implem Controlled config CR Context 2 of 2

More Related