Welcome to the InfoSci Platform
Reference Hub1
RUP: A Process Model for Working with UML

RUP: A Process Model for Working with UML

Wolfgang Hesse
Copyright: © 2001 |Pages: 14
ISBN13: 9781930708051|ISBN10: 193070805X|EISBN13: 9781930708990
DOI: 10.4018/978-1-930708-05-1.ch004
Cite Chapter Cite Chapter

MLA

Hesse, Wolfgang. "RUP: A Process Model for Working with UML." Unified Modeling Language: Systems Analysis, Design and Development Issues, edited by Keng Siau and Terry Halpin, IGI Global, 2001, pp. 61-74. https://doi.org/10.4018/978-1-930708-05-1.ch004

APA

Hesse, W. (2001). RUP: A Process Model for Working with UML. In K. Siau & T. Halpin (Eds.), Unified Modeling Language: Systems Analysis, Design and Development Issues (pp. 61-74). IGI Global. https://doi.org/10.4018/978-1-930708-05-1.ch004

Chicago

Hesse, Wolfgang. "RUP: A Process Model for Working with UML." In Unified Modeling Language: Systems Analysis, Design and Development Issues, edited by Keng Siau and Terry Halpin, 61-74. Hershey, PA: IGI Global, 2001. https://doi.org/10.4018/978-1-930708-05-1.ch004

Export Reference

Mendeley
Favorite

Abstract

Recently, the Rational Unified Process (RUP) has been published as the second part of Rational’s Unified Method project. The RUP is advertised as an “iterative and incremental, use case-driven, architecture-centric” process model and aims to support system designers, builders and managers working with the Unified Modeling Language (UML) by a procedural guideline. In this chapter, a brief review and a critical analysis of the RUP is attempted. Its general aim and its contribution towards more harmonisation in the software process field are acknowledged. However, its ability to reduce the complexity of software development and to clarify its interlaced structure and terminology is doubted. Major problems may result from concepts not clearly specified like workflow or architecture. In particular, RUP core concepts like phase, iteration, workflow and milestone are debated. It is argued that RUP phases and milestones do not support the requirements of modern object-oriented (and, in particular, component-based) software projects. Iteration cycles should be based on software building blocks rather than on phases and activities. As one possible alternative to the RUP, a component-based (and truly architecture-centric) process model is sketched, and a multi-variant approach to software process modelling is recommended.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.