L01 - Intro

L01 - Intro - EE 361 Fundamentals of Software Engineering 1...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon

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

View Full DocumentRight Arrow Icon

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

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: EE 361 Fundamentals of Software Engineering 1 January 11, 2008 Introduction 1 Fundamentals of Software Engineering Why even consider software engineering (part 1)? Suppose that you are working for a company that provides landscaping services across a large metropolitan area. Your boss asks you to manage the development of a new billing system youve assembled a great team of developers and acquired all the state of the art technologies and tools your team has talked at length with the accounting manager and written a detailed set of requirements youre set to go should be no problem six months later project is late and over budget developers have been working overtime for weeks and one has already quit and you dont think you are any closer to completion the accounting team keeps claiming that the software doesnt do what they need and they keep sending through change requests the accounting group sends a continual flood of bug reports so what went wrong? whatever it was it is something that most companies get wrong 1 January 11, 2008 Introduction 2 Some Facts and Figures: According to the Standish Group research (report in 2001); only 28% of software projects in 2000 succeeded entirely 23% were cancelled the rest (some 49%) were challenged they were late (by 63% on average) over budget (by 45%) lacking features (33%) or all of the above The New Zealand Ministry of Justice had a $42 million Case Management System that was $8 million over budget and a year late when rolled out in 2003. Of the 27 benefits expected of the system, only 16 have been realized. Reportedly, the only challenges faced by the developers were those common to large and complex systems!! 1 January 11, 2008 Introduction 3 Fundamentals of Software Engineering So, to repeat, why even consider software engineering? Software development is hard Its important to make a distinction between easy systems One developer, one user, experimental use only and hard systems Multiple developers, multiple users, products for the marketplace Our experiences with easy systems (as hard as you find they are to develop) are very misleading The techniques dont scale up very well Lets consider an analogy If youre building a bridge over a little creek, the job is easy. You can find some boards or tree trunks, lay other boards across them, and you have the job done If youre building a bridge over the St. Lawrence River, this clearly is not going to work -- the techniques dont scale up!...
View Full Document

Page1 / 16

L01 - Intro - EE 361 Fundamentals of Software Engineering 1...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online