Marco Antonio García Carrión
ABSTRACT
Requirements traceability is an important quality factor in the life cycle of the software, there is a lot of software standards that demands his implementation, for example, ISO/IEC 29110, a standard for very small entities; however, projects of small organizations do not perform an adequate application of traceability. In the literature there are proposals with a high level of abstraction; the realization of a traceability information model for small software development organizations provides a narrow alternative, reducing the gap between the theory and the reality in software development. We present a traceability information model for small organizations within the framework of ISO/IEC 29110, in this way organizations access an illustrative and reusable traceability solution that allows them to improve the quality of software development. The article contemplates the definition of the models.
- Marco Toranzo, Jaelson Castro, and Elton Mello. 2002. UmaProposta para Melhorar o Rastreamento de Requisitos. In WER. 194--209.Google Scholar
- Patricio Letelier. 2002. A framework for requirements traceability in UML-based projects. In Proc. of 1st International Workshop on Traceability in Emerging Forms of Software Engineering. 173--183.Google Scholar
- OrlenaGotel, Jane Cleland-Huang, Jane Huffman Hayes, Andrea Zisman, Alexander Egyed, Paul Grünbacher, Alex Dekhtyar, Giuliano Antoniol, and Jonathan Maletic. 2012. The grand challenge of traceability (v1. 0). In Software and Systems Traceability. Springer, 343--109.Google Scholar
- OrlenaGotel, Jane Cleland-Huang, J Huffman Hayes, Andrea Zisman, Alexander Egyed, Paul Grünbacher, and Giuliano Antoniol. 2012. The quest for ubiquity: A roadmap for software and systems traceability research. In Requirements Engineering Conference (RE), 2012 20th IEEE International. IEEE, 71--80. Google ScholarDigital Library
- Jane Cleland-Huang, Orlena CZ Gotel, Jane Huffman Hayes, Patrick Mäder, and Andrea Zisman. 2014. Software traceability: trends and future directions. In Proceedings of the on Future of Software Engineering. ACM, 55--69. Google ScholarDigital Library
- Rainer Dreves, Frank Hällmayer, Lutz Haunert, Bernhard Sechser, and Armin Rieß. 2016. A method to realize traceability in development processes. Journal of Software: Evolution and Process 28, 11 (2016), 1011--1019. Google ScholarDigital Library
- Telmo Oliveira de Jesus and Michel dos Santos Soares. 2017. A Multi-Criteria Analysis of Techniques and Tools for Tracing Software Requirements. IEEE Latin America Transactions 15, 5 (2017), 922--927.Google ScholarCross Ref
- Richard Torkar, Tony Gorschek, Robert Feldt, Mikael Svahnberg, Uzair Akbar Raja, and Kashif Kamran. 2012. Requirements traceability: a systematic review and industry case study. International Journal of Software Engineering and Knowledge Engineering 22, 03 (2012), 385--433.Google ScholarCross Ref
- Klaus Pohl. 2010. Requirements engineering: fundamentals, principles, and techniques. Springer Publishing Company, Incorporated. Google ScholarDigital Library
- Klaus Pohl. 1996. Process-centered requirements engineering. John Wiley & Sons, Inc. Google ScholarDigital Library
- Matthias Jarke. 1998. Requirements tracing. Commun. ACM 41, 12 (1998), 32--36. Google ScholarDigital Library
- Marta Silvia Tabares, Fernando Arango, and Raquel Anaya. 2006. Una revisión de modelos y semánticas para la trazabilidad de requisitos. Revista EIA 6 (2006), 33--42.Google Scholar
- Orlena CZ Gotel and CW Finkelstein. 1994. An analysis of the requirements traceability problem. In Requirements Engineering, 1994., Proceedings of the First International Conference on. IEEE, 94--101.Google ScholarCross Ref
- Balasubramaniam Ramesh and Matthias Jarke. 2001. Toward reference models for requirements traceability. IEEE transactions on software engineering 27, 1 (2001), 58--93. Google ScholarDigital Library
- Ian Spence and LesleeProbasco. 2000. Traceability strategies for managing requirements with use cases. Rational Software White Paper (2000).Google Scholar
- Julio CSP Leite and AP Oliveira. 1995. A client oriented requirements baseline. In Requirements Engineering, 1995., Proceedings of the Second IEEE International Symposium on. IEEE, 108--115. Google ScholarDigital Library
- Julio Cesar Sampaio do Prado Leite, Gustavo Rossi, Federico Balaguer, Vanesa Maiorana, Gladys Kaplan, Graciela Hadad, and Alejandro Oliveros. 1997. Enhancing a requirements baseline with scenarios. In Requirements Engineering, 1997., Proceedings of the Third IEEE International Symposium on. IEEE, 44--53. Google ScholarDigital Library
- Jaelson Castro, Rosa Pinto, Andréa Castor, and John Mylopoulos. 2002. Requirements traceability in agent oriented development. In International Workshop on Software Engineering for Large-Scale Multi-agent Systems. Springer, 57--72.Google Scholar
- Jaelson Castro, Manuel Kolp, and John Mylopoulos. 2002. Towards requirements-driven information systems engineering: the Tropos project. Information systems 27, 6 (2002), 365--389. Google ScholarDigital Library
- Castro, R Candida, AM Castor, and J Mylopoulos. 2003. Requirements Traceability in Agent Oriented Software Engineering. Book chapter In Software Engineering for Large-Scale Multi-Agent Systems: Research Issues and Practical Applications, LNCS 2603 (2003). Google ScholarDigital Library
- Giulio Antoniol, Jane Cleland-Huang, Jane Huffman Hayes, and Michael Vierhauser. 2017. Grand Challenges of Traceability 2017. Grand Challenges of Traceability: The Next Ten Years (2017), 6.Google Scholar
- Paul Arkley and Steve Riddle. 2005. Overcoming the traceability benefit problem. In Requirements Engineering, 2005. Proceedings. 13th IEEE International Conference on. IEEE, 385--389. Google ScholarDigital Library
- Ralf Dömges and Klaus Pohl. 1998. Adapting traceability environments to project-specific needs. Commun. ACM 41, 12 (1998), 54--62. Google ScholarDigital Library
- Gilbert Regan, Fergal McCaffery, Kevin McDaid, and Derek Flood. 2012. Traceability-Why do it?. In International Conference on Software Process Improvement and Capability Determination. Springer, 161--172.Google ScholarCross Ref
- Luis Hernán García Paucar, Claude Y Laporte, Yaylli Arteaga, Marco Bruggmann, et al. 2015. Implementation and certification of ISO/IEC 29110 in an IT startup in Peru. Software Quality Professional (SQP) (2015).Google Scholar
- Claude Y Laporte, Mirna Munoz, Jezreel Mejia Miranda, and Rory V OâĂŹConnor. 2018. Applying Software Engineering Standards in Very Small Entities: From Startups to Grownups. IEEE Software 35, 1 (2018), 99--103.Google ScholarCross Ref
- Ronald Houde, Claude Y Laporte, and GaëlBlondelle. 2016. ISO/IEC 29110 Deployment Packages and Case Study for Systems Engineering: The "Not-So-Secret" Ingredients That Power the Standard. In INCOSE International Symposium, Vol. 26. Wiley Online Library, 1276--1292.Google ScholarCross Ref
- Claude Y Laporte, Rory V O'Connor, and Gauthier Fanmuy. 2013. International systems and software engineering standards for very small entities. (2013).Google Scholar
- Christian Neumuller and Paul Grunbacher. 2006. Automating software traceability in very small companies: A case study and lessons learne. In Automated Software Engineering, 2006. ASE'06. 21st IEEE/ACM International Conference on. IEEE, 145--156. Google ScholarDigital Library
- Patrick Mäder. 2017. Benefits and Challenges of Software Traceability in Development Projects. Grand Challenges of Traceability: The Next Ten Years (2017), 52.Google Scholar
- Patrick Mäder and Alexander Egyed. 2015. Do developers benefit from requirements traceability when evolving and maintaining a software system? Empirical Software Engineering 20, 2 (2015), 413--441. Google ScholarDigital Library
- Patrick Mader et al. 2016. Preventing Defects: The Impact of Requirements Traceability Completeness on Software Quality. IEEE Transactions on Software Engineering (2016).Google Scholar
- SunilNair, Jose Luis De La Vara, and SagarSen. 2013. A review of traceability research at the requirements engineering conference re@ 21. In Requirements Engineering Conference (RE), 2013 21st IEEE International. IEEE, 222--229.Google Scholar
- OrlenaGotel, Jane Cleland-Huang, Jane Huffman Hayes, Andrea Zisman, Alexander Egyed, Paul Grünbacher, Alex Dekhtyar, Giuliano Antoniol, Jonathan Maletic, and Patrick Mäder. 2012. Traceability fundamentals. In Software and Systems Traceability. Springer, 3--22.Google Scholar
- Rosa Candida Pinto, Carla TLL Silva, and Jaelson Castro. 2005. A Process for Requirement Traceability in Agent Oriented Development. In WER. 221--232.Google Scholar
- George Spanoudakis, Andrea Zisman, Elena Pérez-Minana, and Paul Krause. 2004. Rule-based generation of requirements traceability relations. Journal of systems and software 72, 2 (2004), 105--127.Google ScholarCross Ref
- Klaus Pohl. 1996. PRO-ART: Enabling requirements pre-traceability. In Requirements Engineering, 1996., Proceedings of the Second International Conference on. IEEE, 76--84. Google ScholarDigital Library
- OrlenaGotel and Anthony Finkelstein. 1997. Extended requirements traceability: Results of an industrial case study. In Requirements Engineering, 1997., Proceedings of the Third IEEE International Symposium on. IEEE, 169--178. Google ScholarDigital Library
- Åsa G Dahlstedt and Anne Persson. 2005. Requirements interdependencies: State of the art and future challenges. In Engineering and managing software requirements. Springer, 95--116.Google Scholar
- Jane Cleland-Huang, OrlenaGotel, Andrea Zisman, et al. 2012. Software and systems traceability. Vol. 2. Springer. Google ScholarDigital Library
- Siti Rochimah, Wan MN Wan Kadir, and Abdul H Abdullah. 2007. An evaluation of traceability approaches to support software evolution. In Software Engineering Advances, 2007. ICSEA 2007. International Conference on. IEEE, 19--19. Google ScholarDigital Library
- Markus Herrmannsdoerfer, Sander D Vermolen, and Guido Wachsmuth. 2010. An extensive catalog of operators for the coupled evolution of metamodels and models. In International Conference on Software Language Engineering. Springer, 163--182. Google ScholarDigital Library
- Tassio Vale, Eduardo Santana de Almeida, Vander Alves, UiráKulesza, NanNiu, and Ricardo de Lima. 2017. Software product lines traceability: A systematic mapping study. Information and Software Technology 84 (2017), 1--18. Google ScholarDigital Library
- Jane Cleland-Huang. 2015. Toward Meaningful Industrial-Academic Partnerships. IEEE Software 32, 1 (2015), 18--21.Google ScholarCross Ref
- ClaesWohlin, Aybuke Aurum, Lefteris Angelis, Laura Phillips, Yvonne Dittrich, Tony Gorschek, HakanGrahn, KennetHenningsson, Simon Kagstrom, Graham Low, et al. 2012. The success factors powering industry-academia collaboration. IEEE software 29, 2 (2012), 67--73. Google ScholarDigital Library
Index Terms
- Traceability information model for very small entities with ISO/IEC 29110
Recommendations
Applying ISO/IEC 29110 to ISO/IEC 62304 for Medical Device Software SME
ICCBD 2019: Proceedings of the 2nd International Conference on Computing and Big DataMedical Device (MD) and Medical Device Software (MDS) imperatively precise as they are dealing with human life and human health. Nowadays, medical device product manufactured by small and medium companies/entities/organization, which diverge from the ...
Using ArchiMate to model ISO/IEC 29110 standard for very small entities
Highlights- ArchiMate language is proposed for modeling the ISO/IEC 29110 standard.
- ...
AbstractPaper concentrates on the ISO/IEC 29110 standard aimed at improving systems and software engineering life cycle processes in very small entities, which has been recently developed and started to be implemented worldwide. With the ...
Introducing requirements traceability support in model-driven development of web applications
In this work, we present an approach that introduces requirements traceability capabilities in the context of model-driven development of Web applications. This aspect allows us to define model-to-model transformations that not only provide a software ...
Comments