Software Requirements basics

Requirements should be

• Interactive

• Precise

• consistent

• incomplete

Requirement can be

• non Specific

• Functional

• Domain

• Ambiguous

Following is an example of Functional Requirement

• Speed

• Accuracy

• Cash withdrawal in Banking System

• Reliability

Example of a Non functional Requirement

• Cash withdrawal in banking System

• Deposit money in a Banking System

• Speed

• Loan processing in Banking System

Domain Requirement is

• Functional

• Non Functional

• Both Functional and on Functional

Product Requirement, Efficiency Requirement, External Requirement Comes under

• Function Requirement

• Non Functional Requirement

• Both Functional and Non Functional

--------- Engineering process is used to create and maintain a system requirements document.

(a)  

User and System Requirements can be represented as

• Mathematical Notations

• natural language

• Tables

• Diagrams

• All the above

------- is used to determine if the user needs can be satisfied with the available technology and budget

(a)  

Choose the correct order of Elicitation process

a.Requirement prioritization and negotiation

b.Requirements discovery

c.Requirements documentation

d.Requirements classification and organisation

• b,c,a,d

• a,d,c,b

• b,d,a,c

• a,b,c,d