Improving the weaknesses of RUP for Project Management
Keywords:
RUP, PMBOK, PMI, framework, disciplines, iteration, artifactsAbstract
The objective of this article is to identify the weaknesses in the methodology Rational Unified Process (RUP) for Project Management Software. RUP is a software development process whose characteristics are: iterative, use case driven, architecture-centric and early management of risks. It is a two-dimensional process that means is comprised of phases and disciplines. A study is to identify and classify the weaknesses of RUP using Cause-Effect Diagram. Having identified the problems, we propose a solution looking for the best practices for project management in the PMBOK. The PMBOK has a project management framework, major processes are grouped into nine areas of knowledge and shows the level of activity of each process based on time.Downloads
Downloads
Published
Issue
Section
License
Copyright (c) 2010 Lenis Wong Portillo, Fernando Torres Sánchez
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
AUTHORS RETAIN THEIR RIGHTS:
a. Authors retain their trade mark rights and patent, and also on any process or procedure described in the article.
b. Authors retain their right to share, copy, distribute, perform and publicly communicate their article (eg, to place their article in an institutional repository or publish it in a book), with an acknowledgment of its initial publication in the Revista de investigación de Sistemas e Informática.
c. Authors retain theirs right to make a subsequent publication of their work, to use the article or any part thereof (eg a compilation of his papers, lecture notes, thesis, or a book), always indicating its initial publication in the Revista de investigación de Sistemas e Informática (the originator of the work, journal, volume, number and date).
