Software Waterfall Life Cycle

Requirements

Construction

Design

Testing

Delivery and Installation

Operations and Maintenance

Concept Exploration

Prototype

Spiral Model

www.extremeprogramming.org

Software Construction

From SWEBOK 2004

Software Construction

• Goal is to– Minimize complexity

• Use standards• Abstraction, low coupling, high cohesion• Encapsulation, information hiding• Separation of interface from implementation

– Anticipate change• No literal values in code (control access to data)• Incremental development

– Facilitate testing• Code reviews, unit testing, automated testing

Code Completehttp://www.cc2e.com/

• Key Decisions– Choice of programming language– Programming conventions– Your location on the technology wave– Selection of major construction practices

• Version control tool and integration procedure• IDE and tool set• Pair programming versus individually• Test-driven development versus traditional• Unit testing tool• Formal reviews

Construction Measurement

• Measuring progress– Number of classes finished, LOC, test cases– Number of requirements implemented– Code metrics

• Complexity measures

– Code inspections– Errors detected and fixed