Quality Attributes - Architecting Systems to Meet Customer Expectations

Croll, Paul R.

doi:10.1109/systems.2008.4518988

Cited by 8 publications

(1 citation statement)

References 6 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Yet, having established that software undeniably is part of the system, it is astonishing how often a software architecture is not developed. One U.S. Department of Defense study noted that, based on in-depth review of 52 programs, inadequate software architectures is one of the top 10 systemic issues, whereas Croll asserts that the system architecture is incomplete without the software architecture [19].…”

Section: B Failing To Architect the Entire Systemmentioning

confidence: 99%

Giant Slayer: Will You Let Software be David to Your Goliath System?

Blanchette

2016

Journal of Aerospace Information Systems

View full text Add to dashboard Cite

Modern aerospace systems are marvels of engineering. Their amazing achievements are due in large part to software, yet relatively few project personnel, especially project management staff, understand or appreciate the significance of it. The lack of understanding and attention to software often dooms large aerospace projects to significant delay if not outright failure. As a motivation, several software-related aerospace incidents, from benign to calamitous, are recounted here to demonstrate the extent of the problem. Frequently repeated oversights witnessed on many large aerospace projects are then reviewed, with an eye toward what can (and should) be done to avoid the pitfalls. The intent is to empower the reader with information and ideas to prevent software from slaying the giant systems that it is built to support. Nomenclature t = time

show abstract

Section: B Failing To Architect the Entire Systemmentioning

confidence: 99%