Rational Unified Process: Best Practices for Software development Teams
2
4. Visually model software
5. Verify software quality
6. Control changes to software
Develop Software Iteratively Given today’s sophisticated software systems, it is not possible to sequentially
first define the entire problem, design the entire solution, build the software and then test the product at the end. An
iterative approach is required that allows an increasing understanding of the problem through successive
refinements, and to incrementally grow an effective solution over multiple iterations. The Rational Unified Process
supports an iterative approach to development that addresses the highest risk items at every stage in the lifecycle,
significantly reducing a project’s risk profile. This iterative approach helps you attack risk through demonstrable
progress frequent, executable releases that enable continuous end user involvement and feedback. Because each
iteration ends with an executable release, the development team stays focused on producing results, and frequent
status checks help ensure that the project stays on schedule. An iterative approach also makes it easier to
accommodate tactical changes in requirements, features or schedule. [1, 2, 10]
Manage Requirements The Rational Unified Process describes how to elicit, organize, and document required
functionality and constraints; track and document tradeoffs and decisions; and easily capture and communicate
business requirements. The notions of use case and scenarios proscribed in the process has proven to be an excellent
way to capture functional requirements and to ensure that these drive the design, implementation and testing of
software, making it more likely that the final system fulfills the end user needs. They provide coherent and traceable
threads through both the development and the delivered system. [7]
Use Component-based Architectures The process focuses on early development and baselining of a robust
executable architecture, prior to committing resources for full-scale development. It describes how to design a
resilient architecture that is flexible, accommodates change, is intuitively understandable, and promotes more
effective software reuse. The Rational Unified Process supports component-based software development.
Components are non-trivial modules, subsystems that fulfill a clear function. The Rational Unified Process provides
a systematic approach to defining an architecture using new and existing components. These are assembled in a
well-defined architecture, either ad hoc, or in a component infrastructure such as the Internet, CORBA, and COM,
for which an industry of reusable components is emerging. [5]
Visually Model Software The process shows you how to visually model software to capture the structure and
behavior of architectures and components. This allows you to hide the details and write code using “graphical
building blocks.” Visual abstractions help you communicate different aspects of your software; see how the
elements of the system fit together; make sure that the building blocks are consistent with your code; maintain
consistency between a design and its implementation; and promote unambiguous communication. The industry-
standard Unified Modeling Language (UML), created by Rational Software, is the foundation for successful visual
modeling. [4, 12]
Verify Software Quality Poor application performance and poor reliability are common factors which
dramatically inhibit the acceptability of today’s software applications. Hence, quality should be reviewed with
respect to the requirements based on reliability, functionality, application performance and system performance. The
Rational Unified Process assists you in the planning, design, implementation, execution, and evaluation of these test
types. Quality assessment is built into the process, in all activities, involving all participants, using objective
measurements and criteria, and not treated as an afterthought or a separate activity performed by a separate group.
Control Changes to Software The ability to manage change is making certain that each change is acceptable,
and being able to track changes is essential in an environment in which change is inevitable. The process describes
how to control, track and monitor changes to enable successful iterative development. It also guides you in how to
establish secure workspaces for each developer by providing isolation from changes made in other workspaces and
by controlling changes of all software artifacts (e.g., models, code, documents, etc.). And it brings a team together to
work as a single unit by describing how to automate integration and build management.
5星 · 超过95%的资源 需积分: 9 46 浏览量
2007-12-30
13:26:07
上传
评论
收藏 831KB PDF 举报 
无所喂2014-07-26没有看过这个文档，不予置评，谢谢!
