Search My Blog & Website
Thursday, August 07, 2008
What is RUP?
RUP short for Rational Unified Process is a process for software engineering. Originally develped by Rational Software, Inc. - now acquired by IBM.
RUP focuses on the following best practices:
1. Four major phases in a software development cycle (inception, elaboration, construction and transition)
2. Within each phase RUP allows for iteration and incremental development. this supports refined requirements, risk reduction and results oriented management.
3. Disciplines which group activities by nature. There are nine disciplines defined (business modeling, requirements, analysis and design, implementation, test, deployment, configuration management, project management and environment). These disciplines spread across the four phases of a software project.
4. Manage requirements using tools that support traceability, prioritization, validation and quality management.
5. Develop component-based architectures, where components are primary concepts for design. They are self-contained modules with clear interfaces that can provide a well-defined function.
6. Visually model software using languages such as UML, or SysML. Numerous tools on the market support these languages such as IBM's Rational Suite, IBM's Telelogic DOORS, iRise, Visual Use Case, Visual Paradigm and many others.
7. Verify software quality, especially in the areas of functional, performance and reliability compliance.
8. Control changes to software through a traceable and end-to-end approach.
RUP focuses on the following best practices:
1. Four major phases in a software development cycle (inception, elaboration, construction and transition)
2. Within each phase RUP allows for iteration and incremental development. this supports refined requirements, risk reduction and results oriented management.
3. Disciplines which group activities by nature. There are nine disciplines defined (business modeling, requirements, analysis and design, implementation, test, deployment, configuration management, project management and environment). These disciplines spread across the four phases of a software project.
4. Manage requirements using tools that support traceability, prioritization, validation and quality management.
5. Develop component-based architectures, where components are primary concepts for design. They are self-contained modules with clear interfaces that can provide a well-defined function.
6. Visually model software using languages such as UML, or SysML. Numerous tools on the market support these languages such as IBM's Rational Suite, IBM's Telelogic DOORS, iRise, Visual Use Case, Visual Paradigm and many others.
7. Verify software quality, especially in the areas of functional, performance and reliability compliance.
8. Control changes to software through a traceable and end-to-end approach.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment