This document discusses functional and non-functional requirements. Functional requirements describe the behavior of a system and support user goals, while non-functional requirements describe how the system works and make it more usable. Functional requirements should include data descriptions, screen operations, workflows, and access controls. Non-functional requirements should cover usability, reliability, performance, and supportability. Non-functional requirements are further classified into categories like process, delivery, implementation, and external constraints.

1. Functional and Non
Functional

2. Part of requirement
 Functional &
 Non-Functional Requirement.

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

7. Non Functional Requirement Should
Include
 Usability
 Reliability
 Performance
 Supportability

8. Classification of Non Functional
Requirement
 Process requirement
 Delivery requirement
 Implementation Requirement
 Standard Requirement
 Product Requirement
 Visibility Req.
 Reliability Req.
 Safety Req.
 Efficiency Req.
 Performance/Capacity Req.
 External Requirement
 Legal Constraints
 Economic Constraints
 Interoperability Req.