3. Functional Requirement
Describe the behavior of system
Support users goals, tasks or activities
Detailed and specified in the system design
It contain unique name and number
Helps to reader to understand why requirement is needed.
4. Functional Requirement Should include
Description of data to be entered
Description of operation performed by each screen
Description of work flows performed by the system
Who can enter the data into a system
5. Specification of Functional Requirement
Purpose of the Document
Scope
Business Process
Data and Integration
Performance
6. Non Functional Requirement
How system works?
It make system more tangible
Related the usability of system
Judge the operation of system, rather than specific behaviors
Process requirements
Requirements which are a consequence of organisational policies and procedures e.g. process standards used, implementation requirements, etc.
Product requirements
Requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc.
External requirements
Requirements which arise from factors which are external to the system and its development process e.g. interoperability requirements, legislative requirements, etc.