Software Architecture: Managing Design for Achieving Warfighter Capability
Abstract
Software engineers will typically spend 50% or more of the total software development time designing software architecture, and that architecture may provide up to 80% of a modern weapon system's functionality. Increasingly, these systems will operate within a network or other system-of-systems architecture. Obviously, the requirements driving that architectural design effort and the process for tracing requirement to functions, insight into the process, and control of the effort are critical for the successful development of the capability needed by the warfighter. The DoD typically monitors and controls system technical development through implementation of the Baselines, Audits and Technical Reviews within an overarching Systems Engineering Process (SEP) (Defense Acquisition University, 2004, December, chap. 4). Because of the relatively immature software engineering environment, significantly more analysis and development of the requirements is required. In addition, the software architectural design effort is dependent on in-depth requirements analysis, is resource intensive, and must occur very early in the process. Effective management and implementation of design metrics is essential in developing software that meets the warfighters' needs. This management and metrics effort supplements and supports the system technical development through the Baselines, Audits and Technical Reviews.
Document Details
- Document Type
- Technical Report
- Publication Date
- Apr 30, 2007
- Accession Number
- ADA493709
Entities
People
- Brad Naegle
Organizations
- Naval Postgraduate School