April 2009  

 

 

  

 

Rational Requirements Management

Rational Requisite Pro - Complex Requirements Engineering & Reporting

Chuck Goolsby performs business analysis and requirements engineering with the perspective of a veteran project leader, enterprise database software developer and as an effective communicator and negotiator between business and technical teams.

Chuck Goolsby utilizes Requisite Pro� to manage the accurate definition of complex hierarchies of business and functional requirements, and applies that knowledge-base to the development of business and functional use case models.

Chuck Goolsby performs Requisite Pro setup and administration, database management, ReqPro template and API based  customizations, project structure setup and team requirements mentoring.

Requisite Pro manages the collection and dynamic change of software requirements during the entire software project life-cycle.

Requirements documentation supporting software development is created at the beginning of the project and is updated during the project's iterative life-cycle development process.

All required features of the system are identified.  The developer attends meetings with the client to  document the who, what, when, where and why of the project.  Requirements are categorized, prioritized, linked and submitted for client review and approval.

Requirements provide a roadmap for the elaboration of use cases and further models of the system to be built, resulting in an accurately built application.

Detailed Requirements help eliminate the common project risk factor of adding major changes to application functionality "downstream."  Such changes in design can cost 50 to 200 times more than the cost of planning those features up-front. 

Requirements traceability across the Rational toolset allows for requirements change, defect tracking and accurate testing using a consistent workflow process that is visible to technical management and teams as well as business stakeholders at all levels.

Chuck Goolsby works to achieve consensus on project requirements, limiting risks and assuring project success.
Requisite Pro Customization
Complex Requirements Hierarchies
Advanced Use Case Development
Integration with Rational Rose, etc.

Rational Requisite Pro Features

 
Project security control through user permissions  administration
Definition of project documents types, requirement types, templates
Definition of requirement attributes
Importation of requirements from external databases and documents
Importation other external project documents
Management of text-based Use Cases
Linkage of Requisite Pro Use Cases with Rational Rose
Customization of Menus
Assessment of the impact of the changing requirements using the repository
Management of project scope and change throughout all project phases
Integration between Requisite Pro and Rational Rose, ClearQuest and SoDa
 
 

Inception Phase Requisite Pro Deliverables

  • I-A. The Vision Document - This document provides the development team and the customer with a common understanding of the business and technical reasons for the creation of the proposed software application.

  • I-B. The Business Glossary:      1) Tracks of terms and acronyms specific to the system development project at hand;  2) Provides  English-language definitions for non-technical project participants;  3) Allows changes in project terminology to be tracked and recorded as the project grows during its life-cycle.

Elaboration Phase Requisite Pro 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

  • II-B. The Stakeholder Requests Document - The system analyst creates the stakeholder requests document, which is used in collecting the actual requirements.

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

    • Establishes requirement categories, priority categories and requirement Interrelationship definitions used during the client staff interview process

  • 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 developers to design and construct the proposed software application.

These essential requirements documents are updated throughout the iterative phases of the Rational Unified Process software development cycle.  Rational Requisite Pro organizes and automates the complexity involved in both original requirements definition and during the ongoing client change request process that almost always occurs during the software project lifecycle.

 

Last | Next