Abstract
The aim of this study is to build a reference model for the selection of Open Source tools for the management of customer requirements in IT projects. The construction of the reference model results from the needs of companies producing software which are also interested in streamlining the process of managing requirements using Open Source tools. This interest in Open Source tools is, in turn, a consequence of licensing costs, integration with the rest of the portfolio, and support costs. The advantage of Open Source tools is their low license cost and the ease of their adaptation, provided that there is access to a reference model for their adaptation. The problem of the IT market is the lack of such reference models for selecting Open Source tools. Therefore, the authors undertook to build such a model and to apply it in supporting the requirements development process in IT projects.
To achieve the objective, the study was divided into four main parts. The first elaborates on the issue of selecting tools in the software development cycle, indicating the need for departments creating IT systems to use appropriate tools for the given organization. The second part is devoted to the approach to the selection of tools supporting the requirements development process. The purpose of this section is to diagnose the state of IT projects and the lack of support for the requirements development process. The third (the main) part presents the idea to construct a reference model for the selection of tools to support the requirements development process. The structure and development prospects of the model are also discussed here. The fourth part is entirely devoted to examples of the application of the reference model in several IT projects.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Ambler, S.: Survey Says: Agile Works in Practice - Agile software development methods and techniques are gaining traction. Addison-Wesley (2006)
Boehm, B.: A view of 20th and 21st century software engineering. In: Proceedings of 28th International Conference on Software Engineering (ICSE 2006), pp. 12–29. ACM Press (2006)
Broy, M.: Requirements engineering as a key to holistic software quality. In: Levi, A., Savaş, E., Yenigün, H., Balcısoy, S., Saygın, Y. (eds.) ISCIS 2006. LNCS, vol. 4263, pp. 24–34. Springer, Heidelberg (2006)
Chrabski, B., Zawistowski, P.: Architecture of information systems in modern telecommunication companies. Przegląd Telekomunikacyjny 12/2011, Bogdan Zbierzchowski, Krystyn Plewko, Hanna Wasiak, SIGMA NOT, Warszawa, pp. s.1626–s.1631 (2011) ISSN 1230-3496
Why do projects fail?, reasons of IT projects failures (2009), http://workflow.com.pl/pl/tag/the-standish-group
Global Association for Software Quality Requirements Engineering Qualifications Board, Sylabus dla Certyfikacji ReqB (2011)
Hooks, I.F., Farry Kristian, A.: Customer-Centered Products: Creating Successful Products Through Smart Requirements Management. Amacom, New Nork (2001)
IBM, Jazz Plan Jam, Rational Innovate Conference (2012), https://jazz.ideajam.net
IBM, IBM Rational RequisitePro Datasheet (2007), ftp://ftp.software.ibm.com/software/rational/web/datasheets/reqpro.pdf
IBM, IBM Rational Requirements Composer Datasheet (2011), http://public.dhe.ibm.com/common/ssi/ecm/en/rad14076usen/RAD14076USEN.PDF
Kruchten, P.: Architectural Blueprints—The “4+1” View Model of Software Achitecture. IEEE Software 12(6) (1995)
Nikula, U., Sajaniemi, J., Kälviäinen, H.: A State-of-the-practice Survey on Requirements Engineering in Small- and Medium-sized Enterprises, Research Report 1, Telecom Business Research Center Lappeenranta (2000)
Nuseibeh, B., Easterbrook, S.: Requirements engineering: a roadmap. In: Proceedings of the Conference on the Future of Software Engineering, pp. 35–46. ACM Press (2000)
Ovum, Ovum Application Lifecycle Management Report (2009), http://www.rationalindia.in/ibm-rational-the-recognized-leader-in-alm/
Schmidt, P.: Reasons for failure of projects, why it is worth using a methodology (2008), http://pmanager.pl/index.php?option=com_content&view=article&id=145&Itemid=53
Wiegers, K.E.: More about Software Requirements. Microsoft Press (2006)
Author information
Authors and Affiliations
Corresponding author
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer International Publishing Switzerland
About this paper
Cite this paper
Chrabski, B., Orłowski, C. (2013). A Reference Model for the Selection of Open Source Tools for Requirements Management. In: Zamojski, W., Mazurkiewicz, J., Sugier, J., Walkowiak, T., Kacprzyk, J. (eds) New Results in Dependability and Computer Systems. Advances in Intelligent Systems and Computing, vol 224. Springer, Heidelberg. https://doi.org/10.1007/978-3-319-00945-2_9
Download citation
DOI: https://doi.org/10.1007/978-3-319-00945-2_9
Publisher Name: Springer, Heidelberg
Print ISBN: 978-3-319-00944-5
Online ISBN: 978-3-319-00945-2
eBook Packages: Chemistry and Materials ScienceChemistry and Material Science (R0)