2008
DOI: 10.1504/ijsse.2008.018141
|View full text |Cite
|
Sign up to set email alerts
|

Network-centric military system architecture assessment methodology

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
11
0

Year Published

2010
2010
2020
2020

Publication Types

Select...
3
3
2

Relationship

2
6

Authors

Journals

citations
Cited by 16 publications
(11 citation statements)
references
References 2 publications
0
11
0
Order By: Relevance
“…The following indicators can be employed for assessing how well a specified architecture such as High Level Architecture (HLA) (IEEE 2000) enables an M&S application to possess a desired set of quality characteristics under a set of indented uses (Balci and Ormsby 2008):…”
Section: Architecture Quality Indicatorsmentioning
confidence: 99%
“…The following indicators can be employed for assessing how well a specified architecture such as High Level Architecture (HLA) (IEEE 2000) enables an M&S application to possess a desired set of quality characteristics under a set of indented uses (Balci and Ormsby 2008):…”
Section: Architecture Quality Indicatorsmentioning
confidence: 99%
“…Architecture evaluation can be approached from any one of the four Ps, but a combination of all four provides the best balance and results in a much higher level of confidence in the evaluation. Therefore, an architecture should be assessed from the four perspectives by way of assessing: [Balci and Ormsby 2008] 1. the architecture itself as a product, 2. the process used in creating the architecture, 3. the quality of the people employed in creating the architecture, and 4. architecture development project characteristics (e.g., capability maturity, documentation, planning, risk management).…”
Section: Sp 51 Evaluate the Architecture Based On The Four Psmentioning
confidence: 99%
“…A risk-driven approach is advocated for architecture evaluation. The evaluation should consider all potential risks including the following: [Balci and Ormsby 2008] • Acceptance Risk is the probability that the system architecture will not pass the acceptance test with respect to the prescribed acceptance criteria. • Integration Risk is the probability that the system architecture components will not be successfully integrated.…”
Section: Sp 52 Evaluate the Architecture Following A Risk-driven Appmentioning
confidence: 99%
“…NCSs can leverage a variety of middleware products to provide services and therefore can be composed of heterogeneous components (Balci & Ormsby, 2008). Middleware is defined as a software layer between applications and network operating systems that is intended to easily resolve the issues of heterogeneity and distribution for software engineers (Emmerich, Aoyama, and Sventek, 2007).…”
Section: The Internet and Network Centric Systemsmentioning
confidence: 99%