Rational Unified Process(RUP)

Focusing on Nine Disciplines of RUPBy. Pawan Kumar

RUP v2003 Lifecycle

The Business Modeling DisciplineThe goal is to understand the business of the organization, usually confined to the scope of the business that is relevant to the system being developed.

Working closely with project stakeholders, you will:1. Assess the current status of the organization, including

your ability to support a new system2. Explore the current business processes, roles, and

responsibilities3. Identify and evaluate potential strategies for

reengineering the business processes4. Develop a domain model which reflects that subset of

your business

The Requirements DisciplineThe goal is to elicit, document, and agree upon the scope of what is and what is not to be built. This information is used by analysts, designers, and programmers to build the system, by testers to verify the system, and by the project manager to plan and manage the project.

Activities of the Requirements discipline include:1. Working closely with project stakeholders to understand their

needs2. Defining the scope of the system. 3. Exploring usage, business rules, the user interface, and

technical (non-functional) requirements via appropriate modeling techniques

4. Identifying and prioritizing new or changed requirements as they are identified throughout a project

The Analysis and Design DisciplineThe goal is to analyze the requirements for the system and to design a solution to be implemented, taking into consideration the requirements, constraints and all applicable standards and guidelines.

Critical activities of this discipline include:1. Formulating, and then defining, a candidate architecture

for a system2. Constructing a proof-of-concept, or spike, to validate a

candidate architecture3. Understanding (analyzing) the requirements for the

system4. Design of components, services, and/or modules5. Network, user interface, and database design

The Implementation Discipline

The goal is to transform the design into executable code and to perform a basic level of testing, in particular unit testing.

Primary activities include:1. Understanding and evolving the design model2. Writing program source code3. Implementing components, services, and/or modules4. Unit testing source code5. Integrating the code into subsystems and/or a

deployable build

The Test Discipline• The goal is to perform an objective evaluation to

ensure quality. This includes finding defects, validating that system works as designed, and verifying that the requirements are met.

Critical activities include:1. Defining and planning testing efforts2. Developing test cases3. Organizing test suites4. Running tests5. Reporting defects

The Deployment DisciplineThe goal is to plan for the delivery of the system and to execute the plan to make the system available to end users.

Activities within this discipline include:1. Planning the deployment strategy2. Developing support and operations material3. Creating deployment packages4. Organizing alpha/beta/pilot testing efforts5. Deploying software to installation sites6. Training end users7. Managing acceptance testing efforts

The Configuration and Change Management Discipline

The goal is to manage access to the project’s work products. This includes not only tracking versions over time but also controlling and managing changes to them.

Critical activities of this discipline include:1. Managing change requests2. Planning configuration control3. Setting up the CM environment4. Monitoring and reporting configuration status5. Changing and delivering configuration items6. Managing baselines and releases

The Project Management Discipline

The goal is to direct the activities that take place on the project. This includes managing risks, directing people (assigning tasks, tracking progress, etc.), and coordinating with people and systems outside the scope of the project to be sure that it is delivered on time and within budget.

Critical activities include:1. Initiating a new project2. Managing project staff3. Enhancing the relationship with external teams and resources4. Risk management5. Estimating, scheduling, and planning6. Managing an iteration7. Closing out a phase or project

The Environment Discipline

The goal is to support the rest of the effort in terms in ensuring that the proper process, guidance(standards and guidelines), and tools (hardware, software, etc.) are available for the team as needed.

The critical activities of this discipline are:1. Tailoring the process materials for an individual project

team2. Identifying and evaluating tools3. Installing and setting up tools for the project team4. Supporting the tools and process throughout a project