Requirements

Question 1

What makes a good requirement?

Answer 1

1. Unique number
2. Precise
3. Testable
4. Unambiguous
5. Bounded
6. Consistent

Question 2

Types of requirements

Answer 2

1. (BRD) Business Requirement Document
2. (FRD) Functional Requirement Document
3. Non-Functional Requirement Document
4. (URD) User Requirement Document
5. (SRD) System Requirement Document

Question 3

BRD

Answer 3

(Business Requirement Document):
A high-level document that contains business goals, like an executive summary

Example: User shall be able to create an Email ID in Gmail Application

Question 4

FRD

Answer 4

(Functional Requirement Document):
Contains detailed Technical information about the software (Function - user needs to do something)

Example: User can navigate in between ‘Inbox’ and ‘Sent’ in Gmail upon logging in

Question 5

3. Non-Functional Requirement:

Answer 5

Requirement that does not have any functionality (System does automatically, without user’s action)

Example: Security, Firewall, time out

Example: Bank app logs out automatically after 20 mins of being inactive

Question 6

URD

Answer 6

(User Requirement Document):
Contains information about the user like authorization, role, permission, admin etc.
Example: Admin of Gmail application is able to check any Gmail account

Question 7

SRD

Answer 7

(System Requirement Document):
The most important document in SDLC, because it contains information about all the other requirements. This document contains detailed information about: Hardware, Connecting devices, Software, Operating System, Database

Example: Apple is compatible with iPhone only