Mapping RUP roles to small software development teams

12Citations
Citations of this article
33Readers
Mendeley users who have this article in their library.
Get full text

Abstract

In the last decades the complexity of software development projects had a significant increase. This complexity emerges from the higher degree of sophistication in the contexts they aim to serve and from the evolution of the functionalities implemented by the applications However, many software corporations have a reduced dimension (micro, small or medium) which imposes a considerable constraint to the number of individuals that might be involved in each project. This limitation has obvious consequences to the individual's efficiency and effectiveness. In this paper we describe a Rational Unified Process (RUP) tailoring to simplify the number of RUP roles. With this tailoring we obtain one set of RUP roles that, without neglecting any critical role of the software development process, may easily be adopted by a small or medium software development team. In this paper, we present and justify a complete set of mapping rules between RUP roles and one possible configuration for small software development teams. © 2012 Springer-Verlag Berlin Heidelberg.

Cite

CITATION STYLE

APA

Borges, P., Monteiro, P., & MacHado, R. J. (2012). Mapping RUP roles to small software development teams. In Lecture Notes in Business Information Processing (Vol. 94 LNBIP, pp. 59–70). Springer Verlag. https://doi.org/10.1007/978-3-642-27213-4_5

Register to see more suggestions

Mendeley helps you to discover research relevant for your work.

Already have an account?

Save time finding and organizing research with Mendeley

Sign up for free