Issue 16281: Scope of availability of change management information (sacm-rtf) Source: MITRE (Mr. Samuel Redwine, samredwine(at)verizon.net) Nature: Revision Severity: Critical Summary: Timing or change management information needs to be able to be associated with anything as anything can change over time. This includes for example with Attributes (and any Properties). In addition, how to best handle changes and change information over time needs to be reviewed throughout SACM. The version and change management related information ­ although often kept in a CM system ­ needs to be exchangeable along with an assurance case. At least one exchange standard for CM information exists, TECHAMERICA EIA-836B: Configuration Management Data Exchange and Interoperability, publication date: Mar 1, 2010. It is reportedly both ANSI and DoD approved. (http://engineers.ihs.com/document/abstract/BMVKACAAAAAAAAAA) One option is for this to be appropriately included by reference. Versioning should be available for everything. Identification and “HasVersion” attribute should be associated with a near root element, or this availability should be achieved in some other fashion. The standard should not restrict its availability and smallness of possible granularity of elements it may be applied to. Resolution: Revised Text: Actions taken: May 26, 2011: received issue Discussion: The first part of the request has been already addressed through the resolutions 16730 and related. The second part of the request seems to be addressed (at least in part) through the element Supersedes. Further discussion on this topic is deferred to a future RTF. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 26 May 2011 15:05:49 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Samuel T. Redwine, Jr. Employer: Sam Redwine Consulting mailFrom: samredwine@ieee.org Terms_Agreement: I agree Specification: Software Assurance Evidence Metamodel (SAEM) Section: 8.1.10, 10.2 FormalNumber: ptc/2010-08-37 Version: FTF - Beta 1 Doc_Year: 2010 Doc_Month: August Doc_Day: Day Page: 37,-39 Title: Scope of availability of change management information Nature: Revision Severity: Critical CODE: 3TMw8 B1: Report Issue Description: Timing or change management information needs to be able to be associated with anything as anything can change over time. This includes for example with Attributes (and any Properties). In addition, how to best handle changes and change information over time needs to be reviewed throughout SACM. The version and change management related information ­ although often kept in a CM system ­ needs to be exchangeable along with an assurance case. At least one exchange standard for CM information exists, TECHAMERICA EIA-836B: Configuration Management Data Exchange and Interoperability, publication date: Mar 1, 2010. It is reportedly both ANSI and DoD approved. (http://engineers.ihs.com/document/abstract/BMVKACAAAAAAAAAA) One option is for this to be appropriately included by reference. Versioning should be available for everything. Identification and .HasVersion. attribute should be associated with a near root element, or this availability should be achieved in some other fashion. The standard should not restrict its availability and smallness of possible granularity of elements it may be applied to.