This presentation is all about Requirements Engineering and Management. It is a new branch of computer science which aims at providing a structured and formal process to uncover , elicit, analyse, document, validate and manage client requirements for an IT Project

1. www.qbi.in

2. www.qbi.in

3. “You Folks Start Coding I will go and
find out what Requirements Are”
Dr. Goldsmiths Book – Real Requirements
www.qbi.in

4. www.qbi.in

5. www.qbi.in

6. CIO Magazine
Analysts report that as many as 71% of software projects that fail do so because of poor requirements
management, making it the single biggest reason for project failure - bigger than bad technology, missed
deadlines or change management fiascoes.
Christopher Lindquist, Fixing the Requirements Mess, CIO Magazine
Standish Report
The Standish CHAOS Report, which surveyed 9,236 IT projects, found that the top three causes of
project failure were lack of user input, incomplete requirements or changing requirements.
Survey of European Software Organizations
A recent survey of European software organizations identified that more than 40% perceived that they
had major problems in managing customer requirements, and more than 50% perceived that they had
major problems in the area of requirements specification.
El-Emam, K., Birk, A., Validating the ISO/IEC 15504 Measure of Software Requirements Analysis Process
Capability
www.qbi.in

7. www.qbi.in

8. www.qbi.in

9. www.qbi.in

10. – Project Title, Vision, Mission Document
– Earlier Client Interaction
– Study of Documents e.g. RFP, contracts, advt. etc
– Prior Experience
– Domain Specific Business Rules and Requirement
www.qbi.in

11. – Identify Stakeholders
– Identify Departments
– Elicitation techniques are:
Interviews, Surveys, Joint Requirement
Sessions, Demonstrations, Observations etc.
www.qbi.in

12. www.qbi.in

13. www.qbi.in

14. www.qbi.in

15. It's not right."
"It's what you said you wanted."
"Well, it's still not right."
www.qbi.in

16. www.qbi.in

17. www.qbi.in

18. www.qbi.in

19. www.qbi.in