2008
DOI: 10.21236/ada482224
|View full text |Cite
|
Sign up to set email alerts
|

Survivability Assurance for System of Systems

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
15
0

Year Published

2009
2009
2021
2021

Publication Types

Select...
3
2
2

Relationship

2
5

Authors

Journals

citations
Cited by 13 publications
(15 citation statements)
references
References 2 publications
0
15
0
Order By: Relevance
“…The process of developing a well-articulated mission thread that systems engineers, software engineers, and security experts can share and analyze provides an opportunity to uncover missing or incomplete requirements as well as differences in understanding, faulty assumptions, and interactions across system and software boundaries that could contribute to security concerns and potential failure (Ellison et al 2008).…”
Section: Resultsmentioning
confidence: 99%
See 1 more Smart Citation
“…The process of developing a well-articulated mission thread that systems engineers, software engineers, and security experts can share and analyze provides an opportunity to uncover missing or incomplete requirements as well as differences in understanding, faulty assumptions, and interactions across system and software boundaries that could contribute to security concerns and potential failure (Ellison et al 2008).…”
Section: Resultsmentioning
confidence: 99%
“…By evaluating the composition in addition to the components, systems engineers can validate that the composition as conceived, then designed, and finally built will perform with expected security. Confirmation that the components appropriately respond to expected operational use increases confidence that the system will function as intended even in the event of an attack (Ellison et al 2008). The simplest way to show the value of this approach is through an example.…”
Section: Mission Thread Analysismentioning
confidence: 99%
“…Information is available from the SEI about the applicability of assurance cases to dependability [56], security [57], and survivability [58].…”
Section: Assurance Casesmentioning
confidence: 99%
“…The protocols and interfaces that the system defines are often not meant for communication, collaboration, or evolution beyond this specific domain. This lack of foresight in the systems' architecture places extra strain [20] when these systems are required to collaborate with other systems. There is also the principle of encapsulation [21] in systems engineering to consider.…”
Section: Incompatible Interfacesmentioning
confidence: 99%