Return to Requirements

Functional Requirements define the basic system behavior. Essentially, they are requirements stating what the system does or must not do, and can be thought of in terms of how the system responds to inputs. Functional requirements usually define if/then behaviors and include calculations, data input, and business processes.

Functional Requirements are features that allow the system to function as it was intended. Put another way, if the functional requirements are not met, the system will not work. Functional requirements are product features and focus on user requirements. Functional Requirements can be used during all phases of a project Lifecycle independent of the development model (i.e., Waterfall Model or Agile Model). In the Waterfall method, these requirements are generally specified early on in the process. In the Agile method, they can be applied throughout each Sprint or applied during specific Sprints.

• Note: Because these are Functional Requirements, they need to be written specifically for the system being specified in the proposal or solicitation.

In DIDO, the following areas minimally cover Functional Requirements:

The goal of hardware functional requirement is to decide which hardware architectures are going to be supported and which, if any, will be left out.

1. 4.2.1 Platforms

   • C.1 Embedded Systems

     1. C.1.1 Embedded Subsystem
     2. C.1.2 Standalone Embedded Systems
     3. C.1.3 Networked Embedded Systems
   • C.2 Servers

     1. C.2.1 Software Servers
     2. C.2.2 Hardware Servers
   • C.3 Desktops
   • C.4 Handheld Computers
   • C.5 Supercomputers
   • C.6 Network Devices

• 4.2.2 Access Control