A Systems Engineering Management Plan

Part 1: Project Proposal (1–2 pages)
Throughout this course, you will be developing a systems engineering management plan (SEMP) for a project of your choice. This week, you will choose a project and develop a proposal. The project can be for a systems engineering problem of your choosing, or it can be for the standard class problem. If you choose a problem other than the standard problem, it must be approved by the instructor. The proposal should consist of the following:
• Working title: Systems Engineering Management Plan
• Project summary (1/2–1 page): This will provide the context for all decisions made in the SEMP.
o Short description of the focus of the systems engineering effort (1/2–1 page)
o Identifies key assumptions about the systems engineering project implementation
• Working list of project references (4–8 references): This will be used to guide your research. It is not the final list, but should be enough to give you a good start on your project (4–8 references should be provided).
Turn in your proposal to your instructor to get approval before beginning the project.
Part 2: Document Shell for SEMP
In the Discussion Board assignment for this week, you chose a SEMP template for your project. Create your shell document using the chosen SEMP template. You will add to this document each week as you complete your individual projects. Each week, you will populate the shell document with information that will be identified by section name. The final SEMP will be the Key Assignment that you turn in at the end of the course. The following is the standard template for the SEMP that is provided for the class. Your shell document may differ if you decided as a class to use a different template or if you have decided to use your own template (approved by the instructor).
1. Title page
2. Executive Summary
3. Document History
4. Table of Contents
a. Introduction
b. Purpose
c. Document Overview
d. System Overview
e. Project Schedule
f. References
5. System Engineering Processes
a. Project Organization
b. Environments
c. Decision-Making Process
d. System Engineering Model
e. System Engineering Processes
i. Configuration Management
ii. Requirements Engineering
iii. Functional Analysis
iv. Design Processes
v. Development Processes
 Software
 Hardware
 System Integration
 Build Management
f. Verification
g. Validation
6. Specialty Engineering
7. System Deployment
a. Site preparation
b. System installation
c. System checkout
d. User training
e. Support engineer training
8. Product Support
a. Maintenance
b. Logistics support
c. Disposal
———————————————————————————
SEMP New Content
This week, you will begin adding information to your SEMP document shell. The following information should be added to your project:
• Title Page
o This is the information you developed in Week 1.
• Document History
o This section should identify all document changes.
o It should have initial release, at a minimum, and it will identify updates made as a result of the review process in Week 4.
• Table of Contents
o It should be autogenerated from the shell and, in the final version, regenerated from the body of the project.
o The table of contents should be between 2–4 levels deep.
o It should contain a list of figures and a list of charts if there are any in your project.
• Introduction: This is the introduction to your project, which should contain the following:
o Purpose: Purpose of the document, which clearly identifies the purpose of your SEMP
o Document Overview: A descriptive overview of the document, which identifies how the document is laid out
o System Overview: A brief overview of the systems engineering project and how this document fits into the project
 The overview must provide enough information so that the reader has a high-level understanding of the project.
o Project Schedule: A high-level notional project schedule that identifies the key milestones associated with the engineering project and the target start and finish dates
 The key milestones will show the schedule of yearly builds and the project phases associated with each build.
Add this information to your SEMP document, and submit it for grading.
———————————————————————————
This week, you will continue work on your SEMP by completing the System Engineering Processes section. The following information should be completed and added to your SEMP. Describe the details for each of the systems engineering processes.
New Content: Systems Engineering Processes
• Organization: Describe the project’s organization and team locations.
• Environments: Describe the technical environment for the project and how it will be managed. Include the tools and the descriptions of handoffs between the tools for each subteam. (For example, describe the handoff from requirements engineering to design.)
• Decision-Making Process: Describe the decision-making process(es) used in the project. This should include trade studies, control boards, working groups, and other forums.
• System Engineering Model: Describe the system engineering model used and the rationale for its choice. Include a description of the analysis that was done to choose an engineering model. Include the reason for the choice of models. Include a trade-off of at least 2 different models.
• Systems Engineering Processes: Describe the following processes used in the project:
o Configuration Management: Describe the configuration for all system components, interfaces, and other artifacts produced by the engineering process.
o Requirements Engineering: Describe how requirements will be clarified, expanded, validated, updated, reviewed, and approved.
o Functional Analysis: Describe how requirements will be grouped into an initial system structure.
o Design: This includes the hardware and software design.
o Development:
 Build Management
 Describe the process used to create, manage, and transmit builds.
 Software Development
 Hardware Development
 System Integration
o Verification
o Validation
Add these descriptions to the Systems Engineering Processes section of your SEMP document, and submit it for grading.
———————————————————————————
Key Assignment Draft
Part 1: SEMP New Content (minimum 3 pages)
Complete the following sections in your SEMP document:
• Specialty Engineering: Discuss specialty engineering that must be performed for the product. (Specialty engineering is the engineering that is done to implement the “ilities” discussed earlier in the course). Also, identify the processes that will ensure that the specialty engineering will be done. At a minimum, include reliability, maintainability, safety, and security.
• System Deployment: Discuss the following:
o Site preparation: Identify and discuss the processes that will make sure that site preparation for the system’s deployment are identified and completed.
o System installation: Identify and discuss the processes that will ensure that the system installation tasks are identified and completed.
o System checkout
o User training: Identify and discuss the user training processes.
o Support engineer training: Identify and discuss training processes for the support engineers.
• Product Support:
o Maintenance: Identify and discuss system maintenance processes.
o Logistics support: Identify and discuss logistics processes. These are the processes associated with obtaining spare parts for the system. This is usually handled by logistics specialists.
o Disposal: Identify and discuss disposal processes.
Part 2: Key Assignment Draft (minimum 12 pages, excluding title page and TOC)
• Update your Key Assignment document based on the feedback that you received on past assignments.
• Submit your Key Assignment document for grading.
———————————————————————————
Key Assignment
The final step in developing the SEMP is to write an executive summary. The executive summary should be a 1-page paper that distills key information from the SEMP to present at an executive level. You will also review the SEMP document and produce the final version. Updates should be made based on peer and instructor feedback.
The deliverables for this week are as follows:
• Update the SEMP document based on peer and instructor feedback.
• Executive Summary (1 page)
o Present the key points of the SEMP in a summary document for the executives.
• SEMP (final version of Key Assignment)
o Review the entire document for any changes and improvements that you would like to make.
o Ensure that the final document contains all information that is necessary for the agreed-upon SEMP template.
o Update your references (2–5 pages).
o The final document should be at least 12–15 pages (not including the title, TOC, and reference pages).