<Your Project Name Here>
Concept of Operations
<Course, Semester, Year>
Modification history:
|
Version |
Date |
Who |
Comment |
|
v0.0 |
08/15/00 |
G. H. Walton |
Template |
|
v1.0 |
<date here> |
<who> |
<put comment to summarize the changes made in this version> |
|
... |
|
|
|
Team Name: <your team name here>
Team Members:
Contents of this Document
The Proposed System
<brief description: 1 or 2 paragraphs>
<list or narrative description of the needs for a new or modified system. 1 paragraph to 1 page>
The Proposed System: Users and Modes of Operation
<Brief (1 - 3 sentences each) description of each class of user and each mode of operation for the proposed system>
The Proposed System: Operational Scenarios
<Brief (1 paragraph each) description of the major operational scenarios for the proposed system. Include typical scenarios and a few atypical scenarios (errors, high risk situations, etc.)>
The Proposed System: Operational Features
Must Have: <list of these features, in priority order>
Would Like to Have: <list of these features, in priority order>
The Proposed System: Expected Impacts
<Brief (1-2 paragraph) description of the expected impacts of the proposed system development and implementation>
Expected Improvements: <list them>
Disadvantages: <list them>
Limitations: <list them>
Risks: <list them>
Alternatives and Tradeoffs: <list them>
Template created by G. Walton (GWalton@mail.ucf.edu) on August 30, 1999 and last modified on August 15, 2000.
This page last modified by <your name here> (<your e-mail address text and link here> ) on <modification date here>