Design Specification ( Project Proposal )

profileoluwafemi45
ProjectProposalTemplate-V3-180814.docx

Project Proposal Template

(8/14/18)

Title Page:

Document Title:

CLIN:

Version Number:

Version Date:

Team Name:

Lead Author:

Contributing Author(s):

1. Introduction

1.1. Document Purpose ( 1 paragraph)

This section indicates the purpose of the document and identifies the name of the system you propose to develop or upgrade.

1.2. Team Members (<0.5 page)

This section provides the names of the people on your team.

1.3. References (<0.5 page)

This section lists the references relevant to this document. At a minimum is should indicate this template.

2. Project Scope (1 paragraph)

This section indicates that you will be developing a context-level architecture, stakeholder requirements, system architecture, and system requirements for your system of interest.

3. Stakeholders and Statement of Need (<0.5 pages)

This section identifies the customer for the system and the principal system users. It also provides a one or two sentence “statement of need.”

4. System Functionality/Capabilities (< 1 page)

This section provides a list of the 3-5 most important capabilities that the principal stakeholders generally the user) want the system to have (if it is a new system) or the 3-5 most important new or improved capabilities that the principal stakeholders want the system to have (if it is an existing system).

5. Measures of Effectiveness (< 0.5 pages)

This section identifies and defines the principal 3-5 system-level measures of effectiveness (MOEs) for your system. MOEs are parameters that express how well the most important system capabilities must be performed. This should be a table that indicates each MOE, provides a definition that makes clear how it is to be determined (measured), and a desired threshold value (with units).

6. System Concept (~ 1 page)

This section provides a brief description of: 1) what the system does; 2) what elements make up the System of Interest and brief description of what they do; 3) who the users are; 3) what the environment consists of (i.e., external systems that the system and users interact with); and 4) how the system interacts with the users and environment to provide the desired capabilities.

Copyright © 2018 John MacCarthy. All rights reserved. Page 1