Abstract
Since 1999, Rational’s Unified Process (RUP) is being offered as a guideline for software projects using the Unified Modeling Language (UML). RUP has been advertised to be iterative, and incremental, use case-driven and architecture-centric. These claims are discussed while RUP core concepts like phase, iteration, discipline (formerly: workflow) and milestone are reviewed in more detail. It turns out that the RUP constitutes a considerable step towards a broad dissemination of software process modelling ideas but some of the RUP definitions and structures lack clear structure and are too complex and overloaded for practical use.
Among others, I see the following particular problems: (1) phases do still dominate the process and iteration structure, (2) the term “software architecture” is not clearly defined and its role is still underestimated, (3) RUP “disciplines” are a partly redundant concept complicating the process more than supporting it, (4) powerful and transparent structuring principles like recursion and orthogonality do not get the attention they deserve. As an alternative, our model for Evolutionary, Object-oriented Software development (EOS) is contrasted with the RUP.
Similar content being viewed by others
References
DeMarco, T., Lister, T.: Peopleware – Productive projects and teams. Dorset House Publ. Co., 1987
Floyd, Ch., Reisin, F.-M., Schmidt, G.: STEPS to software development with users. In: Ghezzi, C., McDermid, J. (eds.) ESEC ’89, Second European Software Eng. Conference, LNCS, vol. 387. Springer, 1989, pp. 48–64
Hesse, W.: Theory and practice of the software process – a field study and its implications for project management. In: Montangero, C. (ed.) Software Process Technology, 5th European Workshop, EWSPT 96, LNCS, vol. 1149. Springer, 1996, pp. 241–256
Hesse, W.: Improving the software process guided by the EOS model. In: Proc. SPI ’97 European Conference on Software Process Improvement. Barcelona, 1997
Hesse, W., Noack , J.: A Multi-Variant Approach to Software Process Modelling. In: Jarke, M., Oberweis, A. (eds.) CAiSE’99, LNCS, vol. 1666. 1999, pp. 210–224
Hesse, W.: RUP – A process model for working with UML? Critical Comments on the Rational Unified Process. Book chapter in: Siau, K. et al. (eds.) Unified Modeling Language. Idea Group Publ., 2001
Jacobson, I.: Object-Oriented Software Engineering – A Use Case Driven Approach. Revised Printing, Addison-Wesley, 1993
Jacobson, I., Booch, G., Rumbaugh, J.: The Unified Software Development Process. Addison-Wesley, 1999
Kruchten, Ph.: The Rational Unified Process (An Introduction). Addison Wesley, 1999
Royce, W.: Software Project Management – A Unified Framework. Addison Wesley, 1998
Rational Unified Process – Product Overview. http://www.rational.com/products/rup as of 18 August 2003
Schewe, K.D.: UML: A Modern Dinosaur? – A Critical Analysis of the Unified Modelling Language. In: Jakkola, H., et al. (eds.) Information Modelling and Knowledge Bases XII. Proc. 10th European-Japanese Conf., vol. 67, IOS Press, 2001, pp. 185–202
Störrle, H.: “Describing Fractal Processes with UML”. Proc PROFES – 3rd European Workshop on Product Focused Software Process, LNCS, vol. 2188. Springer, 2001
Unified Modeling Language (UML) 1.5 Documentation. OMG document formal/03-03-01. Rational Software Corp., Santa Clara, CA 2003. http://www.rational.com/uml/resources/ documentation as of 18th August 2003
Versteegen, G.: Das V-Modell ’97 in der Praxis – Grundlagen, Erfahrungen, Werkzeuge. dpunkt-Verlag, 1999
Author information
Authors and Affiliations
Corresponding author
Rights and permissions
About this article
Cite this article
Hesse, W. Dinosaur meets Archaeopteryx? or: Is there an alternative for Rational’s Unified Process?. Softw Syst Model 2, 240–247 (2003). https://doi.org/10.1007/s10270-003-0033-y
Received:
Accepted:
Published:
Issue Date:
DOI: https://doi.org/10.1007/s10270-003-0033-y