Information Technology Reference
In-Depth Information
Change is more manageable.
Higher level of reuse.
The project team can learn along the way.
Better overall quality.
2.3.2.1.2
Disadvantages
Extensive knowledge is required—Someone needs initially to learn and under-
stand the Unified Process so that he or she can develop, tailor, or enhance the
Unified Process for new type of project, situation, and requirements.
Contradictory advice—The new version may be in contradiction with the Unified
Process or RUP, or other process materials, at certain points. Having the source
material available “as is” may cause confusion unless people understand that
you have overridden portions of it. An effective approach is to set a specific
design scheme for your pages and then make sure that everyone is aware that
your pages are official and that all other pages are simply reference.
Complexity—Providing a process in which people must understand the base
description and then understand the changes to it at another location may be
confusing for some people.
2.3.2.1.3
Suitability
The Unified Process with several different flavors (enhancements) from IBM,
Oracle, and Agile are used more commonly in IT; however, the could be cur-
tailed to the specific need. For example, the Rational Unified Process provides a
common language and process for business engineering and software engineer-
ing communities, as well as shows how to create and maintain direct traceability
between business and software models. Yet the Basic Unified Process was an
enhancement to the Unified Process that is more suited for small and simple
projects.
2.3.2.2 eXtreme Programming. Although many agile methodologies have
been proposed during the past decade (e.g., ASD: Adaptive Software Develop-
ment, the Crystal Family; DSDM: Dynamic Systems Development Method; FDD:
Feature-Driven Development; ISD: Internet-Speed Development; PP: Pragmatic Pro-
gramming; and SCRUM, RUP: Rational Unified Programming) (Abrahamsson et al.,
2003), (Highsmith, 2001), here the focus is on the best known and most widely used
of the agile software development methodologies: Extreme Programming (Baird,
2003), (Van Cauwenberghe, 2003).
In the early 1990s, the concept of a simple, yet efficient, approach to software
development was already under consideration by Kent Beck and Ward Cunningham
(Wells, 2001). In early 1996, in a desperate attempt to revive the Chrysler Com-
prehensive Compensation (C3) project, the Chrysler Corporation hired Beck as a
Search WWH ::




Custom Search