SACM 1.0b2 FTF Avatar
  1. OMG Issue

SACM — Incorporate 12.1.4 AdministrativeProperty (abstract) (p74) in a coherent way into merged SACM metamodel

  • Key: SACM-126
  • Legacy Issue Number: 16818
  • Status: closed  
  • Source: Adelard LLP ( Luke Emmet)
  • Summary:

    Incorporate 12.1.4 AdministrativeProperty (abstract) (p74) in a coherent way into merged SACM metamodel

  • Reported: SACM 1.0b1 — Tue, 29 Nov 2011 05:00 GMT
  • Disposition: Resolved — SACM 1.0b2
  • Disposition Summary:

    Rename section 15.1.4 AdministrativeProperty (abstract) into ProjectProperty (abstract) (page 92)
    Change definition of AdministrativeProperty from
    AdminstrativeProperty is an abstract class that represents owned properties of
    AdminstrativeElement. This class is added to enhance the readability of the model.
    into
    ProjectProperty represents statements related to the structure of ProjectElement. These
    statements are predicate clauses where the main clause describes some project element.
    The subject of the ProjectProperty clause is a ProjectElement.
    Rename superclass of ProjectProperty to EvidenceProperty
    Add class ProjectProperty to EvidenceAssertions class diagram
    Change semantics from
    Defined by concrete subsclasses
    into
    Defined by concrete subclasses
    Add section ProjectProperties Class Diagram
    move section 15.1.4 ProjectProperty (abstract) to the new section
    Add Figure ProjectProperties Class Diagram <<diagram on p 103 of ptc/2012-06-04>> Move section 15.4.4 HasRoleIn to the new section
    change superclass of HasRoleIn from EvidenceProperty to ProjectProperty
    add Constraints section as follow:

    • ProjectElement shall not be affiliated with self, either directly or indirectly
      Remove class RequiresTool (the corresponding section is missing in the document, so it
      does not need to be removed)
      Move section 15.2.6. DependsOn to the new section change superclass of the DependsOn to ProjectProperty (page 97)
      Change text on page 97 from
      DependsOn element represents a relationship between the owner Activity element and
      another Activity element that is identified as the activity attribute of the DependsOn
      element.
      into
      DependsOn element represents a relationship between the owner project element and
      another project element that is identified as the element attribute of the DependsOn
      element. DependsOn element is a clause where the main subject is the ProjectElement
      that owns the current element. For example, this clause can be used to specify
      dependencies between Activities in an evidence collection project.
      Change associations from
      activity:Activity[1] Activity that the current activity depends on.
      into
      element:ProjectElement[1] Project element that the subject element depends on.
      Change semantics section from
      DependsOn element represents a state of affairs that the owner Activity is associated with
      another Activity identified as the activity attribute of the DependsOn element.
      into
      DependsOn element represents a state of affairs that the subject project element depends
      on another project element identified as the 'element' attribute of the DependsOn
      element.
      In Constraints subsection, change text 'Activity' into "ProjectElement'.
      Remove class isAssociatedWith and the corresponding section 15.2.5, page 97
      Remove class RequiresMethod and the corresponding section 15.2.4 page 97
      Move section 15.2.3. Satisfies, page 96 to the new section
      Change the superclass of the Satisfies element to ProjectProperty
      Change the associations from
      objective:ProjectObjective[1] Project objective that is satisfied by the activity.
      into
      element:ProjectElement[1] Project element that is satisfied by the current element.
      Change text from
      Satisfies element represents a relationship between the owner Activity element and a
      ProjectObjective object that is identified as the objective attribute of the Satisfies
      element.
      into
      Satisfies element represents a relationship between the owner project element and another
      project element that is identified as the element attribute of the Satisfies element. The
      Satisfies element is a clause where the main subject is the ProjectElement that owns the
      current element. For example, this clause can be used to specify that a certain Activity
      satisfies a certain ProjectObjective in an evidence collection project.
      Change associations of Satisfies into
      element:ProjectElement[1] Project element (such as a ProjectObjective) that is satisfied
      by the subject project element
      Change the semantics subsection from Satisfies element represents a state of affairs that the owner Activity object satisfies the
      ProjectObjective identified as the objective attribute of the ProjectObjective element.
      into
      Satisfies element represents a state of affairs that the owner project element satisfies
      another ProjectElement (such as a ProjectObjective) identified as the 'element' attribute of
      the Satisfies element.
      Other changes to the ProjectProperties Class Diagram are described in the related
      resolution 16816 (EvidenceContainer)
  • Updated: Fri, 6 Mar 2015 20:58 GMT