[工学]面向对象软件工程英文讲义第一章.pptVIP

Object-Oriented Software Engineering WCB/McGraw-Hill, 2008Stephen R. Schachsrs@  CHAPTER 1 THE SCOPE OF OBJECT-ORIENTED SOFTWARE ENGINEERING Outline Historical aspects Economic aspects Maintenance aspects Requirements, analysis, and design aspects Team development aspects Why there is no planning phase Outline (contd) Why there is no testing phase Why there is no documentation phase The object-oriented paradigm Terminology Ethical issues 1.1 Historical Aspects 1968 NATO Conference, Garmisch, Germany Aim: To solve the software crisis Software is delivered Late Over budget With residual faults Standish Group Data Data on 9236 projects completed in 2004 Cutter Consortium Data 2002 survey of information technology organizations 78% have been involved in disputes ending in litigation For the organizations that entered into litigation: In 67% of the disputes, the functionality of the information system as delivered did not meet up to the claims of the developers In 56% of the disputes, the promised delivery date slipped several times In 45% of the disputes, the defects were so severe that the information system was unusable Conclusion The software crisis has not been solved Perhaps it should be called the software depression Long duration Poor prognosis 1.2 Economic Aspects Coding method CMnew is 10% faster than currently used method CMold. Should it be used? Common sense answer Of course! Software Engineering answer Consider the cost of training Consider the impact of introducing a new technology Consider the effect of CMnew on maintenance 1.3 Maintenance Aspects Life-cycle model The steps (phases) to follow when building software A theoretical description of what should be done Life cycle The actual steps performed on a specific product Waterfall Life-Cycle Model Classical model (1970) Typical Classical Phases Requirements phase Explore the concept Elicit the client’s requirements Analysis (specification) phase Analyze the client’s