7. UNIT IMPLEMENTATION.ppt

7. UNIT IMPLEMENTATION Software Engineering Roadmap: Chapter 7 Focus “Implementation” Learning Goals Be able to ... … specify standards ... select coding style … code with correctness justification … identify quality goals 1. Introduction to implementation RoadMap for Unit Implementation RoadMap for Unit Implementation 1. Confirm the detailed designs you must implement code only from a written design (part of the SDD) 2. Prepare to measure time spent, classified by: residual detailed design; detailed design review; coding; coding review; compiling repairing syntax defects; unit testing (see chapter 7) repairing defects found in testing 3. Prepare to record defects using a form default: major (requ. unsatisfied), trivial, or neither default: error, naming, environment, system, data, other 4. Understand required standards for coding for the personal documentation you must keep see the case study for an example 5. Estimate size and time based on your past data 6. Plan the work in segments of ± 100 LOC Using Reverse Engineering for Very Detailed Design Unified Process USDP Implementation Model Constituents USDP Implementation Model Constituents USDP Subsystem Interfaces USDP Subsystem Interfaces Implement Code 1/2 1. Plan the structure and residual design for your code (complete missing detailed design, if any) note pre- and post-conditions note the time spent 2. Self-inspect your design and/or structure note time spent, defect type, source (phase), severity 3. Type your code do not compile yet try methods listed below apply required standards code in a manner that is easiest to verify use formal methods if appropriate Implement Code 2/2 4. Self-inspect your code -- do not compile yet convince yourself that your code does the required job the compiler will never do this for you: it merely checks syntax! note time spent, defects found, type, source, severity 5. Compile your code repair syntax defects note time spent, defect type, source, severity , and