• Like
  • Save
Overview of Requirements Engineering and Management
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Overview of Requirements Engineering and Management

  • 327 views
Published

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, …

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

Published in Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
327
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. www.qbi.in
  • 2. www.qbi.in
  • 3. “You Folks Start Coding I will go andfind out what Requirements Are” Dr. Goldsmiths Book – Real Requirements www.qbi.in
  • 4. www.qbi.in
  • 5. www.qbi.in
  • 6. CIO MagazineAnalysts report that as many as 71% of software projects that fail do so because of poor requirementsmanagement, making it the single biggest reason for project failure - bigger than bad technology, misseddeadlines or change management fiascoes.Christopher Lindquist, Fixing the Requirements Mess, CIO MagazineStandish ReportThe Standish CHAOS Report, which surveyed 9,236 IT projects, found that the top three causes ofproject failure were lack of user input, incomplete requirements or changing requirements.Survey of European Software OrganizationsA recent survey of European software organizations identified that more than 40% perceived that theyhad major problems in managing customer requirements, and more than 50% perceived that they hadmajor problems in the area of requirements specification.El-Emam, K., Birk, A., Validating the ISO/IEC 15504 Measure of Software Requirements Analysis ProcessCapability 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. Its not right." "Its what you said you wanted." "Well, its still not right." www.qbi.in
  • 16. www.qbi.in
  • 17. www.qbi.in
  • 18. www.qbi.in
  • 19. www.qbi.in