Chap 3 : Requirements Analysis : Important Questions & Answers

 Q1. What is SRS ?

Answer: Software requirements specification is a complete description of requirements to be fulfilled for the successful development of a software system.

Q2. What is the need/benefit of SRS?

Answer: We need SRS for the following reasons:-

1. It reduces software development effort.

2. Allows easier transfer of software to new environment.

3. Helps in overtime enhancement of software.

4. Forms a base for time and cost estimates.

Q3. What are characteristics of SRS?

Answer: Charateristics are as follows:

1. Requirements should be correct and complete.

2. It should be unambiguos.

3. They should be consistent and verifiable.

4. Each requirement should be specified once i.e. Traceable.

Q4. What are techniques of requirement gathering.

Answer: There are three basic techniques:

1. Questionnaires: A set of questions are asked to customers and stakeholders to get their views.

2. Reviews: Documents of existing systems are reviewed that match proposed system.

3. Interviews: Structured or Unstructured (MCQ) interviews are done with stakeholders.

Q5. Describe requirements engineering tasks.

Answer: There are 7 requirements engineering tasks:-

1. Inception : Understand the problem to be solved and nature of solution.

2. Elicitation : This is process of requirements gathering/

3. Elaboration: Models are developed in terms of behavior, functions and constraints.

4. Requirements Negotiation : It happens between key stakeholders.

5. SRS: System requirement specification document is prepared.

6. Requirement validation: Requirements are checked if they meet the needs.

7. Requirement management: Changes in requirements are managed.

Q6. List various stakeholders involved in requirement analysis.

Answer: Stakeholders involved in requirement analysis are:

1. Customer: Who orders the software system.

2. Users: Who uses the system.

3. Advocate: Who knows language of both users and customers.

4. Project manager: Who controls the budget and contract.

5. Software Engineer: Who develops the software.

Q7. How is requirement engineering in agile model.

Answer: In agile model, the requirements engineering is done in models like scrum model where user stories are created instead of srs document. Here requirements are collected just-in-time instead of creating detailed documents. Functional and non-functional requirements are both present in user stories and are not differentiated.

Q8. List elements of analysis model.

Answer: Elements of analysis model are as follows:

1. Scenario based element: Use case diagram, user stories.

2. Behavioural elements : Sequence diagram and state diagram.

3. Flow oriented elements: Data flow diagram or control flow diagram.

4. Class based elements: Class diagram, or collaboration diagram.

Q9. How is analysis model transformed into design model.

Answer: