This is an old revision of the document!
The existing strategy for software and system assurance is already defined by the Systems and software Quality Requirements and Evaluation (SQuaRE). It establishes a common framework for analysis and exchange of information related to system assurance and trustworthiness, and defines the following kinds of assurance that need to be addressed: Information Assurance (IA), Safety Assurance (SfA), Software Assurance (SwA), Mission Assurance (MA) and System Assurance (SysA).
[nick]1st sentence in next paragraph seems circular, given the list above. Is it saying you need to address the listed types of assurance to better support these types of assurance?
These measures of trustworthiness assist in facilitating systems to better support security, safety, software, and information assurance. DIDO Communities are selling their software and “coinage” products based on being reliable, trustworthy, and secure. Therefore, formal assurances should be considered for each of these kinds of assurance within a DIDO.