Legacy Issue Number: 16815
Source: Adelard LLP ( Luke Emmet)
Incorporate 12.1.1 AdministrativeElement (abstract) (p71) in a coherent way into merged SACM metamodel
Reported: SACM 1.0b1 — Tue, 29 Nov 2011 05:00 GMT
Disposition: Resolved — SACM 1.0b2
Change text 15.1.1 AdministrativeElment (abstract), page 91 into 15.1.1 ProjectElment (abstract)
Change definition of the AdministrativeElement section 15.1.1, page 91 from
AdministrativeElement is an abstract class representing non-essential elements of the
Evidence Metamodel that assist in managing evidence collection, interpretation,
evaluation, and exchange processes.
ProjectElement represents the auxiliary elements of the Evidence Metamodel that are
involved in the statements related to managing evidence collection, interpretation,
evaluation, and exchange processes.
Change superclass of AdministrativeElement to 'EvidenceElement' (page 91)
Remove text from Attributes of the AdministrativeElement on page 91:
id:String Globally unique identifier of a SACM evidence element.
Add text to Attributes of the AdministrativeElement on page 91:
name:String Name of the ProjectElment.
content:String The statement in a selected language that is the description of the content
of the element
Add Associations subsection of the AdministrativeElement on page 91:
property:ProjectProperty[0..*] properties of the Project Element - zero or more
predicates to the main clause in which the current element is the subject)
Add to semantics of the ProjectElement the following:
The properties of a ProjectElement make assertions regarding the current element (use
the current element as the subject of the corresponding clauses). Therefore, the following
properties for a ProjectElement can be readily interpreted in the above way:
DependsOn when a subject element is an Activity (for example, verbalized as " Activity
A2 depends on Activity A1")
HasRoleIn when the subject element is a Stakeholder (for example, verbalized as " Bob is
the president of the organization SupplierCorporation")
Satisfies when a subject element is an Activity (for example, verbalized as" Activity A2
satisfies project objective Perform Search")
All ProjectProperties clauses directly owned by a ProjectElement shall be interpreted
with the ProjectElement as the main subject. For example, "Person Researcher depends
on activity Perform Search and satisfies project objective Find evidence"
Add class ProjectElement to Figure 10.1 EvidenceElements
Replace Figure 10.1 with the following (this also contains resolution to several related
issues ). <<diagrams on p 94 of ptc/2012-06-04>> Rename 15.2 ProjectActivities Class Diagram into
15.2 ProjectElements Class Diagram
Change text on page 94 from
ProjectActivities Class Diagram defines Activity AdministrativeElement and its owned
properties. Activity element facilitates management of evidence collection and evaluation
ProjectElements Class Diagram defines several auxiliary elements that are used in
various statements as predicate clauses for some main clause in which the subject is some
evidence element. The elements defined at this class diagram are collectively referred to
as the project elements. They are required to express various evidence statements related
to evidence collection, evaluation and evidence management.
Move sections 15.3.1. CollectionMethod (abstract), 15.3.2 Service, 15.3.3 Method, 15.3.4
Tool into the section 15.2 ProjectElements Class Diagram.
Move sections 15.4.1. Originator (asbtract), 15.4.2. Person, 15.4.3 Organization into the
section 15.2 ProjectElements Class Diagram.
Move section 15.5.1. EvidenceRequest into the section 15.2 ProjectElements Class
change superclass of EvidenceRequest to ProjectElement
remove association 'provenance' of EvidenceRequest.
Create class diagram ProjectElements based on Figure 15.2 and former ProjectActivities
Change superclass of CollectionMethod (section 15.3.1 page 98) to ProjectElement
Change superclass of Originator (section 15.4.1 page 100) to ProjectElement Remove section 15.3 Methods (see also related resolution 16818)
Remove section 15.4 Originators (see also related resolution 16818)
Remove section 15.5 Request class diagram.
Updated: Fri, 6 Mar 2015 20:58 GMT