{[ promptMessage ]}

Bookmark it

{[ promptMessage ]}

soft_engg_lecture13 - Software Engineering Asim Banerjee...

Info icon This preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon
Software Engineering Asim Banerjee 25 th February 2010 [email protected]
Image of page 1

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 2 Lecture Seating Plan (Sample) #1 #2 #3 #4 #5 #6 #7 #8 #9 Stage #10 #11 #12 #13 #20 #21 #24 #23 #22
Image of page 2
IT314 - Software Engineering 3 The Requirements Problem The goal of software development is to develop quality software – on time and on budget – that meets the customer’s real needs The project success depends on good requirements gathering and management. Requirements errors are the most common type of system development error and the most costly to fix A few key skills can significantly reduce requirement errors and thus improve software quality.
Image of page 3

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 4 Customer – Types (1/2) The customers can be of different types viz. The customer can be an external entity, purchase order in hand, whom we must convince to disregard our competitor’s claims and buy our product because it is easier to use, has more functionality and in the final analysis, is just better The customer could be sitting down the hall or across the country, waiting anxiously for that new application to do their tasks more efficiently, so that the company we work for will ultimately be more profitable and our jobs more rewarding and just more fun
Image of page 4
IT314 - Software Engineering 5 Customer – Types (2/2) The customers … different types viz. (continued) The customer can be a company that has hired us to develop the software, based on expectations that the software developed will be of the highest quality achievable at today’s state of the art and will transform the company into a more competitive, more profitable organization in their marketplace
Image of page 5

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 6 Project Failures – Causes (1/2) The three most common reasons that caused projects to exceed their original estimates were Lack of user inputs – 13% of all projects Incomplete requirements and specification – 12% of all projects Changing requirements and specifications – 12% of all projects NOTE: Other reasons could be unrealistic schedule or time frame in the first place (4%); inadequate staffing and resources (6%); inadequate technology skills (7%)
Image of page 6
IT314 - Software Engineering 7 Project Failures – Causes (2/2) Thus, one-third of the development projects run into trouble for reasons that are directly related to requirements gathering, documenting and management.
Image of page 7

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
IT314 - Software Engineering 8 Project Success - Causes The three most common reasons that caused projects to succeed are User involvement – 16% of all successful projects Executive management support – 14% of all successful projects Clear statement of requirements – 12% of all successful projects Thus the role of requirements gathering, analysis and specification cannot be over emphasized.
Image of page 8
IT314 - Software Engineering 9 Software Requirements - Definition A condition of capability needed by a user to solve a problem or achieve an objective A condition or a capability that must be met or possessed by a system to satisfy a contract, standard, specification or other formally imposed document
Image of page 9

Info icon This preview has intentionally blurred sections. Sign up to view the full version.

View Full Document Right Arrow Icon
Image of page 10
This is the end of the preview. Sign up to access the rest of the document.

{[ snackBarMessage ]}

What students are saying

  • Left Quote Icon

    As a current student on this bumpy collegiate pathway, I stumbled upon Course Hero, where I can find study resources for nearly all my courses, get online help from tutors 24/7, and even share my old projects, papers, and lecture notes with other students.

    Student Picture

    Kiran Temple University Fox School of Business ‘17, Course Hero Intern

  • Left Quote Icon

    I cannot even describe how much Course Hero helped me this summer. It’s truly become something I can always rely on and help me. In the end, I was not only able to survive summer classes, but I was able to thrive thanks to Course Hero.

    Student Picture

    Dana University of Pennsylvania ‘17, Course Hero Intern

  • Left Quote Icon

    The ability to access any university’s resources through Course Hero proved invaluable in my case. I was behind on Tulane coursework and actually used UCLA’s materials to help me move forward and get everything together on time.

    Student Picture

    Jill Tulane University ‘16, Course Hero Intern