The systems engineering case studies will assist in discussion of both successful and unsuccessful methodologies, processes, principles, tools, and decision material to assess the outcome of alternatives at the program/system level. In addition, the importance of using skills from multiple professions and engineering disciplines and collecting, assessing, and integrating varied functional data will be emphasized. When they are taken together, the student is provided real-world, detailed examples of how the process attempts to balance cost, schedule and performance.
The utilization and mis-utilization of systems engineering learning principles will be highlighted, with special emphasis on the conditions that foster and impede good systems engineering practice. Case studies should be used to illustrate both good and bad examples of acquisition management and learning principles, to include whether:
•
Every system provides a balanced and optimized product to a customer
•
Effective Requirements analysis was applied
•
Consistent and rigorous application of systems engineering Management standards was applied
•
Effective Test planning was accomplished
•
There were effective major Technical program reviews
•
Continuous Risk assessments and management was implemented
•
There were reliable Cost estimates and policies
•
They used disciplined application of Configuration Management
•
A well defined System boundary was defined
•
They used disciplined methodologies for complex systems
•
Problem solving incorporated understanding of the System within bigger environment (customer’s customer)
The systems engineering process transforms an operational need into a set of system elements. These system elements are allocated and translated by the systems engineering process into detailed requirements. The systems engineering process, from the identification of the need to the development and utilization of the product, must continuously integrate and balance the requirements, cost, and schedule to provide an operationally effective system throughout its life cycle.
Defines standard
Replaced/Superseded by document(s)
Cancelled by
Amended by
File | MIME type | Size (KB) | Language | Download | |
---|---|---|---|---|---|
Hubble SE Case Study.pdf | application/pdf | 2.49 MB | English | DOWNLOAD! |
Provides definitions
Introduction
The Department of Defense continues to develop and acquire joint systems and to deliver needed capabilities to the warfighter. With a constant objective to improve and mature the acquisition process, it continues to pursue new and creative methodologies to purchase these technically complex systems. A sound systems engineering process, focused explicitly on delivering and sustaining robust, high-quality, affordable products that meet the needs of customers and stake holders must continue to evolve and mature. Systems engineering is the technical and technical management process that results in delivered products and systems that exhibit the best balance of cost and performance.