User

Business

Technical

Functional

Process

Gather and manage all requirements

Highlight relationships between requirements

Capture and link all related information

Use this map to capture the requirements for your project

Priority 1

Priority 2

Priority 3

Priority 4

Priorities

Yes!

Important

Both ways

Reference

Postponed

Arrows

Go

For discussion

Possibility

Progress

Careful

Caution

Risk

Flags

Great idea

Decision

Date

Budget

Emergency

Study

Balance

Map Marker Legend

Click link to see the feature used in the map

Click notes to see how to use the feature

Add a map marker legend to your map

Add a floating topic

Insert notes into a topic

Add map markers (icons) to a topic

Add relationships between two topics

Link a topic to a file or web page

Add links to files from folders on your desktop or network

Display Microsoft Excel ranges in topics

MindManager features used within this map.

About this Map

Purpose

Scope

Project References

Applicability

Intended Audience and Reading Suggestions

Request Manager

Jason Goldman4/13/07 : 4/28/071 hour(s)R: Follow up.

Date

Comments

___________________Signature

Request Stakeholder

Software Analyst

Project Manager

Technical Lead

Developer

Dr. Larry DunlopOperations Contact

Client Services ContactPoints of Contact

Approvals

1. Introduction

Patent History.xlsx

Patent_List.docx

Trademarks.docx

All Filesand FoldersPatents

Research

Studies

Background

Current Functionality

Objectives

Equipment Being Used

Input and Output

Provisions in the Existing System Design

Deficiencies

Current Methods and Procedures

2. Current System Summary

System Description

User Requirements

Data Flow Diagrams

Logical Data Model/Data Dictionary

System Functions

Flexibility

3. Design Considerations

Functional Improvements

Improvements to Existing Capabilities

Timeliness

Summary of Improvements

User Organizational Impacts

User Operational Impacts

User Developmental Impacts

Summary of Impacts

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 program-ming standards

Assumptions and Constraints

Prototypes principally help with design decisions and user interface designPrototypes

4. Proposed Methods and Procedures

Glossary

Options Maintenance

Account Default

Template Behavior

Software Interface

Documentation

Security Requirements

Loss or corruption of data

Disclosure of secrets or sensitive information

Disclosure of privileged/privacy information about individuals

Corruption of software or introduc-tion of malware, such as viruses

Security & Privacy Requirements

Database requirements

Internationalization requirements

Legal requirements

Reuse objectives

Other Requirements

5. Performance Requirements

Files on your desktop or network can be linked to your maps. The links in this example are not active.

Function Rules.docx

Functional Guidelines.xlsx

All Filesand Folders

Functional Area System Functions

Input 1.

Input 2.

Input 3.

Input 4.

Inputs

Output 1.

Output 2.

Output 3.

Output 4.

Outputs

Batches

Backup

Fallback

Degraded Modes of Operation

Failure Contingencies

6. Detailed Characteristics

RequirementsDocumentation