The Unified Process (UP) builds upon the classic processes and tries to incorporate the best parts of agile frameworks at the same time.

UML – Unified Modeling Language, contains a robust methodology for modeling an object oriented system. UML is used throughout Part 2 of the book

Phases of the Unified Process

Similar to the traditional model, UP has separate phases that are semi-aligned to traditional process models.

Inception is a combination of Communication and Planning.

Elaboration is a combination of Planning and Modeling.

Construction is the same.

Transition is a combination of Construction and Deployment.

Production – is the process of moving software through Deployment.

The Unified Process was originally found on Access 2 Learn

Assistant Professor

Walter Wimberly is an Assistant Professor at a regional college in Tennessee, teaching Computer Science in the Software Engineering track. He works as a student advisor, oversees curriculum changes, develops new courses, and manages the advisory panel.
Walter taught full time for about 7 years, before going back into “industry” as a full stack Software Developer for a dozen years. There he focused on web based projects coding in JavaScript/jQuery and utilizing the Bootstrap CSS Framework on the front-end, and coding in PHP, ASP/ASP.Net, SQL on the back-end.

Since he loves teaching, he taught as an adjunct web and digital media classes for eight (8) years, while working in industry, and has since returned to teaching full time.

He has been married for over 25 years, and is father to several special needs boys. As such, he is working on some projects to help others who have special needs to be self-sufficient, and support the care givers of those with special needs. Check out his Autism blog for more info.

Similar Posts

Security Analysis

ByWalter Wimberly

Security requirements are nonfunctional requirements that strongly influence the architectural design of software systems.  Security requirements and other requirements can conflict with one another. A common example is that security and usability are often at odds with one another, and a balance between the two must be found. Therefore you have to determine how secure do you…

Design with the Concept of Software Engineering in Mind

ByWalter Wimberly

This is the last step between modeling our problems and coding our solutions. Each of the elements in our requirements model helps provide us with necessary information that can be used to solve our problem. While the book has the models and design being two separate steps, in many cases you will find that they…

Interface Analysis

ByWalter Wimberly

A software developer might have a different “mental image” of the software than the users which may be different than the stakeholders. However, since the user is the one who will be using it, shouldn’t they be the one who has the most consideration for the interface? This doesn’t necessarily mean talking them about what…