上 Typical Classical Phases e Requirements phase Explore the concept Elicit the client's requirements 9 Analysis(specification) phase Analyze the clients requirements Draw up the specification document Draw up the software project management plan What the product is supposed to do Software Engineering
Software Engineering Typical Classical Phases Requirements phase • Explore the concept • Elicit the client’s requirements Analysis (specification) phase • Analyze the client’s requirements • Draw up the specification document • Draw up the software project management plan • “What the product is supposed to do
上应 ypical Classical Phases( contd) o Design phase Architectural design followed b · Detailed design “ How the product does it” 9 Implementation phase Coding Unit testing Integration Acceptance testing Software Engineering
Software Engineering Typical Classical Phases (contd) Design phase • Architectural design, followed by • Detailed design • “How the product does it” Implementation phase • Coding • Unit testing • Integration • Acceptance testing
上应 ypical Classical Phases( contd) e Postdelivery maintenance Corrective maintenance Perfective maintenance Adaptive maintenance ④ Retirement Software Engineering
Software Engineering Typical Classical Phases (contd) Postdelivery maintenance • Corrective maintenance • Perfective maintenance • Adaptive maintenance Retirement
CBM Classical and Modern Views of Maintenance e Classical maintenance Development-then-maintenance model e This is a temporal definition Classification as development or maintenance depends on when an activity is performed Software Engineering
Software Engineering 1.3.1 Classical and Modern Views of Maintenance Classical maintenance • Development-then-maintenance model This is a temporal definition • Classification as development or maintenance depends on when an activity is performed
Classical Maintenance Defn-Consequence 1 e A fault is detected and corrected one day after the software product was installed Classical maintenance e The identical fault is detected and corrected one day before installation Classical development Software Engineering
Software Engineering Classical Maintenance Defn — Consequence 1 A fault is detected and corrected one day after the software product was installed • Classical maintenance The identical fault is detected and corrected one day before installation • Classical development