(Please note: this article has been abstracted from the RUP as defined by the Rational Corporation who are responsible for its development. It also attempts to be concise, outlining the reasoning behind the RUP as opposed to the specific methodologies used)
Competing methods within the field of software engineering include:
| Table of contents |
|
2 Manage Requirements 3 Use component based architecture 4 Visually Model Software 5 Verify Software Quality 6 Control Changes to Software |
Given the time it takes to develop large sophisticated software systems it not possible to define the problem and build the solution in a single step. Requirements will often change throughout a projects development, due to architectural constraints, customer’s needs or a greater understanding of the original problem. Iteration allows greater understanding of a project through successive refinements and addresses a projects highest risk items at every stage of its lifecycle. Ideally each iteration ends up with an executable release – this helps reduce a projects risk profile, allows greater customer feedback and help developers stay focused.
A documentation framework is essential for any large project; hence RUP describes how to document functionality, constraints, design decisions and business requirements.
Use Cases and Scenarios are examples of artifacts prescribed by the process and have been found to be very effective at both capturing functional requirements and providing coherent threads throughout the development and deployment of the system.
Component Based Architecture creates a system that is easily extensible, promotes software reuse and intuitively understandable. A component often relates to an object in Object Orientated Programming.
The RUP provides a systematic way to build this kind of system, focusing on producing an early executable architecture before committing full scale resources on a project.
These components are often assembled within existing infrastructures such as CORBA and COM.
Abstracting your programming from it’s code and representing it using graphical building blocks is an effective way to get an overall picture of a solution. It can also allow less technically competent individuals who may have a better understanding of the problem to have a greater input.
Unified Modelling Language (UML) is the industry standard way of representing projects and is hence usually used by the RUP.
Quality Assessment is the most common failing point of all software projects, often an afterthought in such projects and even handled by a different team. The RUP assists in planning quality control and assessment built into the entire process involving all members of a team.
In all software projects change is inevitable, the RUP defines methods to control track and monitor changes. As a seemingly small change can affect applications in entirely unpredictable ways this is essential for a successful project. The RUP also defines secure workspaces allowing a programmer to be guaranteed that changes in another system will not affect his system. This ties in heavily with Component based architectures.
So far these guidelines are general, to be adhered to throughout a project's lifecycle. To capture the time dimension of a project the RUP divides a project into four distinct phases:
Develop Software Iteratively
Manage Requirements
Use component based architecture
Visually Model Software
Verify Software Quality
Control Changes to Software
See Also
External Links