Case Study on Rational Unified Process
Rational Unified Process (RUP) is a package distributed by IBM. The Rational Unified Process (RUP) is an iterative software development process framework created by the Rational Software Corporation, a division of IBM. RUP is not a single concrete prescriptive process, but rather an adaptable process framework, which is tailored by the development organizations and software project teams that will select the elements of the process that are appropriate for their needs. The product includes a hyperlinked knowledge base with sample artifacts and detailed descriptions for many different types of activities. RUP is included in the IBM Rational Method Composer (RMC) product which allows customization of the process. RUP is based on a set of building blocks, or content elements, describing what is to be produced, the necessary skills required and the step-by-step explanation describing how specific development goals are to be achieved. The main building blocks, or content elements, are:
Roles (who) – A Role defines a set of related skills, competencies, and responsibilities.
Work Products (what) – A Work Product represents something resulting from a task, including all the documents and models produced while working through the process.
Tasks (how) – A Task describes a unit of work assigned to a Role that provides a meaningful result.
Within each iteration, the tasks are categorized into nine disciplines: six "engineering disciplines" (Business Modeling, Requirements, Analysis and Design, Implementation, Test, Deployment) and three supporting disciplines (Configuration and Change Management, Project Management, Environment).The use of these tools is not standardized and is subject to interpretation. Some shops may prepare report mock-ups. I have frequently seen these done in Excel. These could be part of the appendix to the requirements documents. The requirements should be a description in non-technical terms (“English”) of the business rules being implemented.
Roles (who) – A Role defines a set of related skills, competencies, and responsibilities.
Work Products (what) – A Work Product represents something resulting from a task, including all the documents and models produced while working through the process.
Tasks (how) – A Task describes a unit of work assigned to a Role that provides a meaningful result.
Within each iteration, the tasks are categorized into nine disciplines: six "engineering disciplines" (Business Modeling, Requirements, Analysis and Design, Implementation, Test, Deployment) and three supporting disciplines (Configuration and Change Management, Project Management, Environment).The use of these tools is not standardized and is subject to interpretation. Some shops may prepare report mock-ups. I have frequently seen these done in Excel. These could be part of the appendix to the requirements documents. The requirements should be a description in non-technical terms (“English”) of the business rules being implemented.