What is a software requirement?

• The functions of a software system

• A need that software must meet

• Legal demands that software must meet

• The terms of the contract signed between client and software manufacturer

It is important to define software requirements because

• You can then recruit software developers based on the requirements

• You can determine which database should be used to store the data

• It's a practice to list these requirements in a SRS document

• The scope (boundary) of the system can be defined

Software Requirement Specification

• is a way to communicate and document software requirements in a standard and persistent manner.

• is a way to confirm that requirements are correct.

• is the tool used to gather software requirements from stakeholders.

• is a method to breakdown requirements so that they may be easily understood.

Requirement elicitation is the process of:

• breaking down requirements for easy understanding.

• gathering and discovering stakeholder requirements.

• developing models to understand the problem.

• confirming that the requirements are correct.

What are Functional requirements?

• Statements by the customer about expected functionality of the software

• Statements that define the quality requirements of software

• Statements that define how the software should function in case of a problem

• Statements that define the services offered by the software

What are non-functional requirements?

• Requirements that specify what the system will not do.

• Requirements in case a system fails and becomes non-functional.

• Criteria for operation of the system.

• Requirements that have not originated from clients.

Which non-functional requirement is important for a real-time system such as space-craft software?

• Reliability

• Performance

• Usability

• Interoperability

Requirements validation is the process of checking the requirements for: 

• discovery

• identification

• consistency

• classification

In order to determine functional requirements of a software system we should identify all

• test plans

• inputs and outputs

• non-functional requirements

• the problem to solve

User requirements are

• a list of programs you need in order to make the system

• client requirements

• a list of features the user wants from the system

• none of the above