April 2009  

 

 

  

 

RUP-Elaboration Phase

RUP Phase II - In-depth definition of your software application's functionality

Elaboration involves focusing on lower-level (detailed) requirements and object-oriented architectural design.  Detailed requirements are converted  into use cases, resulting in a Use Case Model.

During Phase II the types of requirements to be collected and their attributes are identified and defined.  Customer management and staff stakeholders, - being the users of the system under development, are interviewed.  Their requests are documented in detail.  A formally structured hierarchical catalog of detailed software requirements is then compiled.

The business object model is also developed during RUP Phase II.

 

RUP Phase II Deliverables

II-A. The Requirements Management Plan
II-B. Stakeholder Requests Document
II-C. The Software Requirements Plan
II-D. The Business Object Model

Elaboration Phase Deliverables

II-A. The Requirements Management Plan

Describes the types of requirements needed to define the system. These types will then be used to collect the system�s requirements from the client and their staff stakeholders. Each requirement type may have a customized set of attributes assigned to it.

Types of Requirements

  • Non-Functional Requirements

  • System Constraints

  • General System Features

  • System Business Functionality Detail

  • Requirements Change requests

Typical Types of Requirement Attributes

  • Requirement�s priority

  • Development Costs

  • Benefits to the organization

Deliverable: 

  • Requirements Management Plan created in Rational Requisite Pro �

 

II-B. The Stakeholder Requests Document

The system analyst creates the stakeholder requests document, which is used in collecting the actual requirements.

  • establish a set of questions, to be asked during a stakeholder interview, that will yield all the facts required to define the system

  • Categories

  • Priorities

  • Requirement Interrelationships

Deliverable: 

  • A Stakeholder Requests Document created in Rational Requisite Pro �

 

II-C. The Software Requirements Plan

This is a detailed compendium of customer requirements for the proposed application. This document will contain sufficient detail to allow the developer(s) to design and construct the proposed software application.

Deliverable: 

  • Software requirements plan created in Rational RequisitePro �

 

II-D. The Business Object Model

This document is a high-level definition of the customer�s business processes and their interactions. The functional requirements captured operate within these business process domains.

  • Describes the realization of business use cases.

  • Describes the interaction among business objects

Deliverable:

  • Business Object Model created with Rational Rose �

Last  |  Next