Requirements
Documentation

1. Introduction

r

Gather general information that pertains to the project.  Plus, team members involved in the capturing of information and or those whose approval is needed to retain information.

Purpose

Scope

r

Provide a concise description of the project and its purpose, including benefits, objectives, and goals. Relate the project to corporate goals or business strategies.

Project References

Applicability

Intended Audience and Reading Suggestions

Approvals

Request Manager

Request Stakeholder

Jason Goldman

Apr13-Apr28

Date

Comments

Signature

___________________

Software Analyst

Project Manager

Technical Lead

Developer

Points of Contact

Operations Contact

Dr. Larry Dunlop

Client Services Contact

2. Current System Summary

r

Outlines current system, including a brief history of current application and operational functionality.

Background

Patents

a

All Files
and Folders

Patent History.xlsx

a

Patent_List.docx

a

Trademarks.docx

a

Research

Studies

Current Functionality

Objectives

Current Methods and Procedures

Equipment Being Used

Input and Output

Provisions in the Existing System Design

Deficiencies

3. Design Considerations

r

Describes the way the proposed system will develop.  Might be used to include additional technical requirements.

System Description

System Functions

User Requirements

Data Flow Diagrams

Logical Data Model/Data Dictionary

Flexibility

4. Proposed Methods and Procedures

r

Describes proposed methods and procedures. Outlines aspects that are part of a previous or existing system and how the proposed system will improve the current application.

Summary of Improvements

Functional Improvements

Improvements to Existing Capabilities

Timeliness

Summary of Impacts

User Organizational Impacts

User Operational Impacts

User Developmental Impacts

Assumptions and Constraints

Hardware limitations (timing requirements, memory requirements)

Interfaces to other applications

Specific technologies

Tools

Databases to be used

Parallel operations

Language requirements

Communications protocols

Security considerations

Design conventions or programming standards

Prototypes

Prototypes principally help with design decisions and user interface design

6. Detailed Characteristics

r

Provides a detailed description of the functions to be performed and the performance requirements of the proposed system.

Functional Area System Functions

All Files
and Folders

Function Rules.docx

a

Functional Guidelines.xlsx

a

Batches

r

Queries to be generated by the systemInterfaces to other systems including data from presently used manual forms

Inputs

Subtopic

Subtopic

Subtopic

Subtopic

Outputs

Subtopic

Subtopic

Subtopic

Subtopic

Failure Contingencies

Backup

Fallback

Degraded Modes of Operation

5. Performance Requirements

r

Standards that need to be implemented for security purposes, databases, legal requirements, and privacy concerns.

Options Maintenance

Account Default

Template Behavior

Software Interface

Documentation

Other Requirements

Security Requirements

Security & Privacy Requirements

Loss or corruption of data

Disclosure of secrets or sensitive information

Disclosure of privileged/privacy information about individuals

Corruption of software or introduction of malware, such as viruses

Database requirements

Internationalization requirements

Legal requirements

Reuse objectives

Glossary

r

Define all the terms necessary for this project as well as acronyms and abbreviations.

Glossary