2009
DOI: 10.1007/978-3-642-10373-5_14
|View full text |Cite
|
Sign up to set email alerts
|

Development of Security Software: A High Assurance Methodology

Abstract: This paper reports on a project to exercise, evaluate and enhance a methodology for developing high assurance software for an embedded system controller. In this approach, researchers at the National Security Agency capture system requirements precisely and unambiguously through functional specifications in Z. Rockwell Collins then implements these requirements using an integrated, model-based software development approach. The development effort is supported by a tool chain that provides automated code genera… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
8
0

Year Published

2010
2010
2022
2022

Publication Types

Select...
3
3
2

Relationship

2
6

Authors

Journals

citations
Cited by 12 publications
(8 citation statements)
references
References 4 publications
(5 reference statements)
0
8
0
Order By: Relevance
“…For critical systems, it has been argued that formal methods should be applied to gain higher assurance than is possible with testing [5,124,125]. For these approaches, testing may still be performed, but the verification effort is primarily focused on performing proofs.…”
Section: Coverage Analysis and Requirements Completenessmentioning
confidence: 99%
“…For critical systems, it has been argued that formal methods should be applied to gain higher assurance than is possible with testing [5,124,125]. For these approaches, testing may still be performed, but the verification effort is primarily focused on performing proofs.…”
Section: Coverage Analysis and Requirements Completenessmentioning
confidence: 99%
“…Interactive systems can be formally described as a composition of interactors (Hardin et al 2009). Interactors are more concrete than the agent model described in section 5.1, in that they introduce more structure to the specification by describing an interactive system as a composition of independent entities (Markopoulos 1997).…”
Section: Modellingmentioning
confidence: 99%
“…One of the reasons is the gap between the descriptive notations most widely used by software developers and the notations required by formal methods (Lutz 2000). To alleviate the difficulties, as part of NASA's Aviation Safety Program (AvSP), Rockwell Collins and the research group on critical systems of the University of Minnesota (USA) develop the Rockwell Collins Gryphon Translator Framework (Hardin et al 2009), providing a bridge between some commercial modelling languages and various model checkers and theorem provers (Miller et al 2010). The translation framework supports Simulink, Stateflow, and SCADE models, and it generates specifications for the NuSMV, Prover, and SAL model checkers, the ACL2 and PVS theorem provers, and generates C and Ada code (Miller et al 2010) (BAT and Kind are also included as target model checkers in (Cofer et al 2012)).…”
Section: Miller Et Al (Usa 1995-2013)mentioning
confidence: 99%
“…In this paper, we focus the dependability attributes on security, reliability and availability [1,2]. We introduce the Component-Based Dependable Software Design, Development and Validation methodology, supporting software system to meet requirement of the dependability.…”
Section: Introductionmentioning
confidence: 99%