Last updated November 14, 2009 15:00, by Bruce Schubert

Campbell Prediction System

Software Requirements Specification

Version 0.3

Bruce Schubert

Revision History

Name Date Reason for Changes Version
Bruce Schubert November 7, 2009 Created. 0.1
Bruce Schubert November 9, 2009 Added context diagram 0.2
Bruce Schubert November 14, 2009 Added threshold of control use case 0.3



This Software Requirements Specification (SRS) describes the functional and non-functional requirements for the Campbell Prediction System (CPS) project. This document is intended for the team members that will implement and verify the correctness of the system.


This project will manifest a training tool and decision support system based on the Campbell Predition System methods to compute, project and visualize potential fire behavior, trigger points and alignments-of-forces on the fireground. See the CPS Vision Document for an expanded description.

Definitions, Acronyms and Abbreviations

A user or external system that interacts with the system.
Campbell Prediction System
Fire Behavior Analyst
Software Requirements Specification
A description of system behavior, in terms of a sequence of actions, as observed by the user.


  1. Vision Document


[This subsection should describe what the rest of the Software Requirements Specification contains and explain how the document is organized.]

Overall Description

The following context diagram, which is based on a data flow diagram, shows the system boundary and connections between the system and its universe.

Figure 1. Context Diagram.

Use-Case Model Survey

Figure 1. High Level Use Case Diagram.

Figure 2. Main System Level Use Case Diagram.

Assumptions and Dependencies

[This section describes any key technical feasibility, subsystem or component availability, or other project related assumptions on which the viability of the software described by this Software Requirements Specification may be based.]


Specific Requirements

[This section of the Software Requirements Specification should contain all the software requirements to a level of detail sufficient to enable designers to design a system to satisfy those requirements and testers to test that the system satisfies those requirements. When using use-case modeling, these requirements are captured in the use cases and the applicable supplementary specifications. If use-case modeling is not used, the outline for supplementary specifications may be inserted directly into this section.]

Use-Case Reports

[In use-case modeling, the use cases often define the majority of the functional requirements of the system, along with some non-functional requirements. For each use case in the above use-case model, or subset thereof, refer to, or enclose, the use-case report in this section. Make sure that each requirement is clearly labeled.]


Supplementary Requirements

Figure 3. Non-functional Requirements Diagram.

Supporting Information

[The supporting information makes the Software Requirements Specification easier to use. It includes
• Index
• Appendices
These may include use-case storyboards or user-interface prototypes. When appendices are included, the Software Requirements Specification should explicitly state whether or not the appendices are to be considered part of the requirements.]
  • Mysql
  • Glassfish
  • Jruby
  • Rails
  • Nblogo
Terms of Use; Privacy Policy;
© 2014, Oracle Corporation and/or its affiliates
(revision 20160708.bf2ac18)
Please Confirm