Question

Write a systems engineering management plan (SEMP) for a project of your choice. The project proposal should consist of the following:

1. Title page
2. Executive Summary
3. Document History
4. Table of Contents
   1. Introduction
   2. Purpose
   3. Document Overview
   4. System Overview
   5. Project Schedule
   6. References
5. System Engineering Processes
   1. Project Organization
   2. Environments
   3. Decision-Making Process
   4. System Engineering Model
   5. System Engineering Processes
      1. Configuration Management
      2. Requirements Engineering
      3. Functional Analysis
      4. Design Processes
      5. Development Processes
         • Software
         • Hardware
         • System Integration
         • Build Management
   6. Verification
   7. Validation
6. Specialty Engineering
7. System Deployment
   1. Site preparation
   2. System installation
   3. System checkout
   4. User training
   5. Support engineer training
8. Product Support
   1. Maintenance
   2. Logistics support
   3. Disposal

sounds good

Answer 1

Systems Engineering Management Plan (SEMP)

The Systems Engineering Management Plan (SEMP) is a comprehensive and effective tool used to assist in the management of systems engineering efforts. It is intended to guide the work of all those involved in the project. The SEMP is comprised of three main sections: technical project planning and control, systems engineering process, and engineering specialty integration. The contents of each section must be tailored to the specific effort. A model outline and example SEMP are provided. The target audience is those who are familiar with the systems engineering approach and who have an interest in employing the SEMP as a tool for systems management. The goal of this document is to provide the reader with an appreciation for the use and importance of the SEMP, as well as provide a framework that can be used to create the management plan.

Purpose:

The Systems Engineering processes used for the Ocean Observatories Initiative (OOI) System of Systems are multidimensional in nature. There is a vertical dimension of systems engineering processes and procedures that, in their application, decompose the system from statements of user needs into SoS, System, Subsystem, Component, and finally product definitions, and then support the integration, testing, and delivery of the integrated systems. This is interwoven with a horizontal dimension that deals with the System Development Life Cycle (SDLC). Ocean Leadership (OL) and the Implementing Organizations (IOs) have selected an Iterative SDLC for OOI, which demands the repetitive application of the systems engineering process within iterations. The third dimension is the knowledge and skills of our systems engineering staff developed through their experiences on previous projects, formal systems engineering training, and specific OOI-provided training.

Scope:

Subsystems and component engineering efforts (hardware and software) accomplished throughout the program. It includes the Systems Engineering processes used by OL and all of the IOs and as a result, the IOs do not maintain separate or subordinate SEMPs.

This SEMP incorporates and combines relevant aspects of traditional System Engineering Management Plans and Software Development Plans. It covers all stages in both hardware and software system life cycles, and the integrated OOI life cycle from requirements definition through deployment and into operations.

Precedence and References

Precedence In the event of conflict between/among plans, policies and guidelines, the following precedence shall exist when not specifically identified. First, the OOI PEP, then the OOI SEMP, then the remaining OOI pertinent documents as equal importance. The SEMP spawns all other engineering plans on the project. The OOI Program Director, or designee, shall have authority to resolve any conflict between/among guidelines/direction.

References The following documents are provided for guidance and reference. The only “official” version of any document is the most recent CCB approved version. They are maintained in the OOI Document Management System (DMS).

Project Execution Plan (PEP)

Systems Engineering Management Plan (SEMP)

Integrated Master Schedule (IMS)

Configuration Management Plan (CMP)

Cost Estimating Plan (CEP)

Quality Assurance and Quality Control (QA/QC) Plan

Commissioning Plan (CP)

Earned Value Management System (EVMS) Plan

Environmental Health and Safety (EH&S) Plan

Final Network Design (FND

Risk Management Plan (RMP)

A Contractors SEMP should address the following:

1. Organization of the development team, along with their physical location and facilities needs
2. Technical environments for a project and how they will be managed. It should also discuss the interaction with the pre-production and production environments.
3. Description of the evaluation and decision-making process to be used when resolving technical questions
4. System Engineering Methodology:
   • Configuration Management: Include a description of how project configuration items (e.g. source code) will be managed.
   • Requirements Verification and Validation: Include a description of how the Use Cases will be clarified and expanded, requirements validated, and updated requirements reviewed and approved by the project office.
   • The Architecture and Design Process (both logical and physical design), including how issues will be discussed and resolved.
   • The software development methodology to be used that reflects the requirements (for iterative builds and incremental releases).
   • The hardware development and configuration methodology to be used that reflects the requirements (for iterative builds and incremental releases).
   • The build management process used to create and manage builds.
   • The testing process to be used that encompasses the requirements.
5. Description of how external interfaces will be developed and managed.
6. Description of how data conversion development will be performed and managed.
7. Implementation Planning to include a description of how you will manage the deployment of system functionality, the training required for both end-users and technical staff, the coordination/communication needed to prepare the target environments.
8. Production Support strategy
9. A description of how production support will be done concurrently with development, given the incremental release requirements for the project.