Unified Process Introduction Course

The Unified Process is a software engineering process that spans the entire project lifecycle and guides the development team in conducting both management and engineering activities. This two-day overview course provides an introduction to the Unified Process that emphasizes the explanation of key concepts including the use case requirements approach, controlled iterative development, and early validation of software architecture. The course’s structure follows the process’ four phases and nine disciplines, with a strong emphasis on key activities and iterative development. Participants apply the principles of iterative, use-case driven development in a challenging half-day exercise.

The Unified Modeling Language (UML) is used where appropriate to illustrate process activities and documentation. The Unified Process is available as an online product in which the process roles, activities, artifacts, and tool support are described. This online product will be used to illustrate process details.

Upon completion of this course, the participant will be able to:
> Identify the best practices for modern software engineering and the benefits they provide
> Recognize the key concepts and terminology used within the Unified Process
> Describe the full software development lifecycle in terms of phases and disciplines
> Identify the benefits of a use-case driven, architecture-centric approach
> Describe an iterative, risk-driven approach to planning a software development project
> Recognize the importance of supporting the process with automated tools

The software development process
What is a process?
Why use a formal software development process
Benefits of a process

The six best practices of modern software engineering
Develop iteratively
Manage requirements
Use component-based architecture
Model visually
Continuously verify quality
Control changes

Dynamic structure of the Unified Process
Four phases
Many iterations
Lab 1: Develop high level plan for the example application

Static structure of the Unified Process
Nine disciplines
Activities
Roles

Use case driven
Basics of requirements management with use cases
Understand what it means to be use case driven
Lab 2: Plan detailed iterations for the example

Architecture centric
Basics of software architecture
4+1 views of architecture
Understand what it means to be architecture-centric

Discipline details
Project management
Requirements
Analysis and design
Implementation
Deployment
Test
Configuration and change management
Environment
Business modeling

Iteration workflows by phase
Inception iteration
Early elaboration iteration
Late construction iteration
Discipline emphasis shifts over time
Artifacts evolve over time
Lab 3: Manage change and plan remaining iterations of the example

Configuring and implementing the Unified Process
Strategies & tactics for configuring and implementing a process
A development case
6 Steps to adopting a process
2 Levels of process configuration
Common changes made to the Unified Process