Application Specification
Application Specification
Requirements Specification
A requirement specification document lists and describes all the key features
of an application and explains the functions that the target
application/system should be able to perform. The importance of having a
1
2
3
Functional Requirements
Functional requirements describe the features and functionalities of the
application. It is generally a good idea to start with relatively high-level
functional requirement that can be broken down into several lowerlevel requirements. Use case headings can usually be utilized as titles
for high-level functional requirements
Functional Requirement ID<id>
Description: <Summarize the basic flow of events, actors, and goals, providing context and im
Assumptions
Persona
<User Persona>
Impact
Primary Actor
<Identify groups of people who will use the product and desc
Input
<Define the event(s) that trigger this function and data requ
Action
Output
Business Rules
Exceptions
Dependencies
<Dependencies>
Non-Functional Requirements
Non-functional requirements do not describe the functions offered by
the application. Instead, they represent important, quality-related
issues. Due to the inherent characteristics of the mobile context of use,
the following requirements should, at minimum, be taken into
consideration when listing non-functional requirements:
Non Functional Requirements
Volumetric
Performance
Audit Requirements
Business Security and Data Protection
Disaster Recovery Requirements
Usability
SLA Requirements
Implementation Considerations
Operational Reporting Requirements
Interfacing Requirements
Interfacing requirements constitute a separate category for
requirements. These requirements differ from functional requirements
in one crucial aspect: they are usually defined in a very detailed level
already in the requirement specification (in terms of technical
implementation).
Interfacing Requirement ID<id>
Description: <Describe the interaction that occurs in this use case. Summarize the basic cours
Assumptions
Impact
Source System
Target System
Input Data
<Define the event(s) that trigger this function and data req
Output Data
<Define the event(s) that trigger this function and data exp