Unfied process

Unified process

• What is that?
• is an iteractive and incremental software development framework from whic a customized process can be defined.
• 

Best practices

• 
• 1._ development software iteratively
• 2._ manage requirements
• 3._ Use component based Arquitectures
• 4._ Visually models software
• 5._ verify software quality
• 6._ control changes to software

Components

• The undified process framework is made up to the following components
• -cycles
• -phases
• -iterations
• -diciplines (also know as workflows)
• -activities
• _artifacts
• -workers
• 

Dicipline and Phases

• Diciplines are:
• -Business modeling
• -Requirements
• -Analisis and designe
• -imolementation
• -testing
• -development
• configuration and change management
• -Enviroment
• The four phases are:
• -Inception phase
• -elaboration phase
• -construction phase
• -transisition phase

business modeling

• The diciplines
• The business modeling diciolines focused on efforts to understand the organization, its processes, and the problem domain, the dicipline focuse on understanding the following factor and how they may impact or related to te software being considereed.
• - Enterprise business rules
• -Enterprise business process model
• -Enterprise domain model
• -Enterprise vision
• -Organization models

Deployment

• the deployment dicipline is focused on planning the deployment of, and actually deploying the software that is being complete the cycle
• -planning the deployment
• -developing support and operations materials
• -planning alpha,beta and pilot testing effort
• -deploying the software
• -training end users
• managing acceptance testing efforts
• 

construction phase

• in this phase the main focus goes to the development of components and others feactures of the system that is being developed, this is the phase when coding takes place
• At the end of this the first released of the software product is expected and this is major criterion of it mileston
• 

transition Phase

• The transition phase of the framework is were the software is deployed to end users and is essentially a broad "beta" test of the application.
• Users beging to use the new software, issues are identified and potentially corrected and any feacture that were delayed and deployed
•