1. THE UNIFIED PROCESS UP Programming

2. What is the unified process  The Unified Process is a programming methodology that emphasizes the right blend of programming and designing.  UP is based off an “Incremental Iterative” method of developing software.  This is to be contrasted with “Waterfall Design”

3. Waterfall Design - The enemy  Waterfall Design – The art of spending way to much time speculating about things that are, at the time of speculation, too far away to grasp.

4. Project Lifecycle in the unified Process  There are four major periods in the UP lifecycle  Inception  Elaboration  Construction  Transition

5. Inception  The purpose of this phase is to collaborate with the customer to gather features and come up with a business model.  Afterwards, the developers are to identify Use Cases and rank them according to three criteria  High Risk  High Business Value  High Architectural Value

6. Elaboration  Once the developers have learned enough about what the customer wants from them, the Elaboration phase begins.  In this phase, the developers, through a series of 1 to 4 week iterations, select a handful of the most important use cases every iteration and implement them.  Elaboration itself is generally 4 to 6 iterations long.

7. Construction  After the elaboration phase is over, the foundational architecture of the project should be laid out.  Think ”wide and shallow”  Construction then begins and the developers fully dress all use cases.  The developers then implement the rest of the project, Use Case by Use Case.

8. Transition  After the project is fully constructed, the product is released to the end users and feedback is used to polish the system.  Critical testing of the entire system should have been done a long time ago, so don’t even think about saving major tests for now.

9. Review of the UP lifecycle

10. Time commitment per UP Phase

11. Conclusion  Now you should be familiar with the overall lifecycle of the Unified Process.  You should be familiar with these terms:  Incremental Iterative vs. Waterfall Design  Inception, Elaboration, Construction, Transition  Use Cases (risk, business, architecture)