Issue 16289: Assurance Cases under development or Incomplete (sacm-rtf) Source: MITRE (Mr. Samuel Redwine, samredwine(at)verizon.net) Nature: Revision Severity: Critical Summary: SACM standard must accommodate assurance cases under development as this is expected to be a common usage ­ transferring assurance cases among their developers or maintainers. This includes those incomplete. In addition to incompleteness, decisions may yet to be concerning option options including the type of certain relations ­ e.g. does an inference relation challenge or not. As the relative distinctions are not always known, particularly early in assurance cases construction, which currently abstract classes should be concrete classes should be reviewed and changed as required to accommodate this. Recording explicit options yet to be decided among (and optionally their effects) could be useful (and also relevant to patterns). More elements similar in name to the UnknownSubject might be included if required to meet this need. Resolution: Revised Text: Actions taken: May 27, 2011: received issue Discussion: This issue is being deferred to the future RTF due to the lack of time to have a discussion. Disposition: Deferred End of Annotations:===== m: webmaster@omg.org Date: 27 May 2011 14:21:48 -0400 To: Subject: Issue/Bug Report ******************************************************************************* Name: Samuel T. Redwine, Jr. Employer: Sam Redwine Consulting mailFrom: samredwine@ieee.org Terms_Agreement: I agree Specification: Argumentation Metamodel (ARM) Section: 7.1, 8 FormalNumber: ptc/2010-08-36 Version: FTF - Beta 1 Doc_Year: 2010 Doc_Month: August Doc_Day: Day Page: 3, 7-16 Title: Assurance Cases under development or Incomplete Nature: Revision Severity: Critical CODE: 3TMw8 B1: Report Issue Description: SACM standard must accommodate assurance cases under development as this is expected to be a common usage ­ transferring assurance cases among their developers or maintainers. This includes those incomplete. In addition to incompleteness, decisions may yet to be concerning option options including the type of certain relations ­ e.g. does an inference relation challenge or not. As the relative distinctions are not always known, particularly early in assurance cases construction, which currently abstract classes should be concrete classes should be reviewed and changed as required to accommodate this. Recording explicit options yet to be decided among (and optionally their effects) could be useful (and also relevant to patterns). More elements similar in name to the UnknownSubject might be included if required to meet this need.