Doing Final project and document deliverables

Final Project – Systems EngineeringThis final project will ensure that you understand the entire Systems Engineering process and understand how
each component fits into the Information Technology domain. We will NOT be developing a system, so this
project only takes us to Project Design Reviews and not to full Operations and Maintenance of the systems.
What will we do?
Select a system relevant to your current employer, former employer, or some other system you’d like to build. (I
recommend this not be as large as “Creating an alternative Facebook.” Choose something that seems that it
might have a reasonable number of requirements. Based on your understanding of the mission CONOP of the
system you wish to build, write a set of requirements as a document (Excel, Word) or a Relational Database.
Ensure you capture all L0 requirements and derive potential L1 requirements. Use hyperlinks to show
traceability between requirements where appropriate (or relations in a database).
Identify which of the requirements are most uncertain in terms of your ability to satisfy them and allocate
reserves (margins) to those requirements in your requirements document and justify these margins. Also identify
how each requirement will be verified later.
Consider a concept generation method / creativity technique to conceptualize the system (after you have L0 and
L1 requirements) – Mind-map, morphological matrix, or some other technique. Select a concept that your feel
would meet the needs of the requirements using a Pugh Matrix to score the concepts you generated. Create an
OPM diagram / sketch of the system to show the functions (ovals) and how they map to elements of form
(rectangles). Show any design variables you may want to consider as well. Show any obvious modules in your
concept (i.e. portions of your concept that are tightly coupled).
Derive any additional technical requirements from the concept you defined that you were not able to define in
your original requirements document. These more refined technical requirements may not be solution “neutral”
but depend on your selected concept. (Please note which of these requirements have been added following the
concept generation and system architecture phase).
Prepare a Preliminary Design Review (PDR) Data Package. The PDR is a “multi-disciplined technical review to
ensure that the system under review can proceed into detailed design, and can meet the stated performance
requirements within cost (program budget), schedule (program schedule), risk, and other system constraints”.
These document shall demonstrate:
•
•
•
•
•
•
•
•
An understanding of the Mission Requirements
Allocation and derivation of system and subsystem requirements
Definition of the CONOP
Overview of the preliminary design that meets specified requirements
Results of, or identification of, necessary trades to support preliminary design
Results of, or identification of, necessary prototyping or testing efforts necessary to support or finalize
preliminary design
Preliminary budget *
Detailed development schedule *
* These are of lesser importance and don’t have to be accurate. I just want to make you aware that in a PDR,
these will usually be an important aspect as well!
The PDR materials will be presented via video recording and should be about 30 minutes. It should discuss
everything from the CONOP of the system you are proposing to some of the alternatives you did not select, how
you selected the proposed system, and the requirements / preliminary budget / development schedule in the
PDR.
Documents to be Delivered to Instructor:
Requirements Document
Concept Generation method(s) and/or Notes
OPM Diagram
Documents highlighting the Pugh Matrix for Concept Selection
PDR presentation slides
PDR presentation video.
Learning Objectives
This assignment makes use of multiple course objectives
• Describe Systems Engineering Standards and Best Practices
• Structure key steps in systems engineering processes from stakeholder analysis to transition of systems
to operations.
• Apply the fundamental methods and tools of SE within simple to complex, real-world Information
Technology projects