80 likes | 195 Views
Yes, we need hundreds of methodologies!!!. It is only in this way we get to know what we do and how we can do “ this what ” better!!!!. Mira Kajko-Mattsson Department of Computer and Systems Sciences Stockholm University and Royal Institute of Technology Sweden. 1.
E N D
Yes, we need hundreds of methodologies!!! It is only in this way we get to know what we do and how we can do “this what” better!!!! Mira Kajko-Mattsson Department of Computer and Systems Sciences Stockholm University and Royal Institute of Technology Sweden 1
Development, evolution and maintenance in ancient times Programmer Manager • No process model (write code, fix code) • No documentation • The programmer was the craftsman? • The work product of ”these craftsmen” was not always of good quality
Programmer Manager Manager Manager With time, however……
Large amount of functionality is never delivered Only as subset of delivered functionality is frequently used The product is late, overbudgeted, defective, never delivered, useless, of low quality, etc. The product quality is too low Engineers are overworked Lack of product and process knowledge Software cost exceed hw cost The product is difficult to change With time, however…… We should act like engineers, like software engineers Manager Manager Manager
Attempts to improve development V-model Spiral model Incremental development • OOAD • CBD • Agile development • Daily Build • Formal methods • MDA
Software EngineeringcontraGood Enough Software Development I wouldn’t like to fly a plane having good enough software We are now challenging the Software Engineering term .
We need process models because they • lay out what needs to be done. • Improve communication within the organization • enable repetition of success • ensure that lessons learned are paid heed to • improve • schedule and budget predictability • cycle time • productivity • quality (as measured by defects) • customer satisfaction • employee morale • increase return on investment • decrease cost of quality • ......