unified process

The Unified process (UP)

Slide 2

• what is it?
• is an iterative and incremental software development framework from which a customized process can be defined. The framework contains many components and has been modified a number of time to create several variations.
• The most popular variations include the rational inified process (RUP)
• THE KEY CHARACTERISTIICS OF THE UNIFIED PROCESS ARE:
• - it is an iterative and incremental development framework.
• -It is architecture-centric with major work being done to define and validate an architectural design for most coding is done.
• -It is use-case and UML model driven with nearly all requirements being documental in one of those forms.
• In general, the unified process is built around idea of incorporaying six specific. Those best practices are:
• 1. Development Sofware iteratively
• 2.Manage Requirements
• 3.Use component-based Architectures
• 4. Visually Model sofware
• 5. Visually sofware Quality
• 6.Control Changes to software

History

• Much of the concepta in the unified process began with work Ivar Jacobson did at Erickon in the 1960's.
• In 1996 Rational Software acquired the Objectory PROCESS AND COMPANY, jACOBSON WORKED AT rATIONAL AND TEAMED UP WITH GRADY BOOCH AND JIM RUMBAUGH AND TOGETHER THEY SPENT THE NEXT SEVERAL YEARS FUTHER DEVELOPING THE OBJECTORY PROCESS. IN 1998, RATIONAL CHANGED THE NQME FOR rATIONAL OBJECTORY PROCESS TO THE RELATIONAL INIFIED PROCESS.

Slide 4

• THE UNIFIED PROCESS FRAMEWORK IS MADE UP OF THE FOLLOWING COMPONETS
• CYCLES
• PHASES iTERATIONS
• DISCIPLINES
• ACTIVITIES ARTIFACTS
• WORKERS
• THE DISCIPLINES ARE:
• BUSINESS MODELING
• REQUIREMENTS
• ANALYSIS AND DESIGN
• IMPLEMENTATION
• TESTING
• DEPLOYMENT
• CONFIGURATION AND CHANGE MANAGEMENT
• PROJECT MANAGEMENT
• ENVIRONMENT

Slide 5

• The four phases are:
• lnception phase
• Elaboration phase
• Construction phase
• Transltlon phase

Slide 6

• The disclpllnes are:
• Business Modeling
• Requlrements
• Analysis and Deslgn
• lmplementation
• Testing
• Deponment
• Configuration and Change Management
• Project Management
• Environment

Slide 7

• Requirements
• The requirements discipline in RUP Is like the requirements discipline in pretty much every other
• software process The main difference is that RUP requirements are highly focused in the form of
• UML models and Use Cases (both diagrams and descriptions).

Slide 8

• Analysis and Design
• The Analysis and Design dlsclpline would be better named the Solution Analysis and Design
• discipline In my opinion. This Is because the requirements are analyzed from a solution design
• perspective, rather than a requirements analysis perspective. Specific activities that are part of this
• discipline include:
• Understanding and analyzing the requirements for the system
• Defining a candidate architecture for a system
• Constructlng a proof—of-concept or prototype to validate a candidate architecture
• Design of components, services, and/or modules
• Design of interfaces (network, user, and databases)

Slide 9

• Implementation
• The Implementation discipline consists of coding, unit testing, and integration of the software.
• Testing
• The Testing discipline is focused on quality assurance of the software being released in that cycle or iteration. It includes such activities as:
• Plannlng test efforts
• Creating test cases
• Runnlng tests
• Reporting defects

Slide 10

• Deployment
• The Deployment discipline is focused on planning the deployment of, and actually deploying, the
• software that is being completed that cycle, phase or iteration.
• Configuration and Change Management
• The Configuration and Change Management discipline is focused on managing change to the
• project’s work products.