Exploring Impact of Requirements Engineering on Other IT Project Areas – Case Study

Aleksander Jarzębowicz, Katarzyna Poniatowska

Abstract


Requirements Engineering (RE) is recognized as one of the most important (yet difficult) areas of software engineering that has a significant impact on other areas of IT projects and their final outcomes. Empirical studies investigating this impact are hard to conduct, mainly due to the great effort required. It is thus difficult for both researchers and industry practitioners to make evidence-based evaluations about how decisions about RE practices translate into requirement quality and influence other project areas. We propose an idea of a lightweight approach utilizing widely-used tools to enable such an evaluation without extensive effort. This is illustrated with a pilot study where the data from six industrial projects from a single organization were analyzed and three metrics regarding the requirement quality, rework effort, and testing were used to demonstrate the impact of different RE techniques. We also discuss the factors that are important for enabling the broader adoption of the proposed approach.

Keywords


Requirements Engineering, Impact, Evaluation, Case study

Full Text:

PDF

References


@inproceedings{jarzebowicz2019,

title={What is Troubling IT Analysts? A Survey Report from Poland on Requirements-related Problems},

author={Jarz{k{e}}bowicz, Aleksander and {'S}lesi{'n}ski, Wojciech},

booktitle={Proc. of 20th KKIO Software Engineering Conference, Engineering Software Systems: Research and Praxis, AISC series vol. 830},

pages={3--19},

year={2018},

organization={Springer}

}

@inproceedings{liechti2017beyond,

title={Beyond dashboards: on the many facets of metrics and feedback in agile organizations},

author={Liechti, Olivier and Pasquier, Jacques and Reis, Rodney},

booktitle={2017 IEEE/ACM 10th International Workshop on Cooperative and Human Aspects of Software Engineering (CHASE)},

pages={16--22},

year={2017},

organization={IEEE}

}

@inproceedings{radlinski2012,

title={Empirical analysis of the impact of requirements engineering on software quality},

author={Radli{'n}ski, {L}ukasz},

booktitle={International Working Conference on Requirements Engineering: Foundation for Software Quality},

pages={232--238},

year={2012},

organization={Springer}

}

@inproceedings{sethia2014,

title={The effects of requirements elicitation issues on software project performance: An empirical analysis},

author={Sethia, Neetu Kumari and Pillai, Anitha S},

booktitle={International Working Conference on Requirements Engineering: Foundation for Software Quality},

pages={285--300},

year={2014},

organization={Springer}

}

@article{gorschek2008,

title={Requirements engineering: In search of the dependent variables},

author={Gorschek, Tony and Davis, Alan M},

journal={Information and Software Technology},

volume={50},

number={1-2},

pages={67--75},

year={2008},

publisher={Elsevier}

}

@article{wieringa2006,

title={Requirements engineering paper classification and evaluation criteria: a proposal and a discussion},

author={Wieringa, Roel and Maiden, Neil and Mead, Nancy and Rolland, Colette},

journal={Requirements engineering},

volume={11},

number={1},

pages={102--107},

year={2006},

publisher={Springer}

}

@article{runeson2009,

title={Guidelines for conducting and reporting case study research in software engineering},

author={Runeson, Per and H{"o}st, Martin},

journal={Empirical software engineering},

volume={14},

number={2},

pages={131},

year={2009},

publisher={Springer}

}

@inproceedings{broy2006,

title={Requirements engineering as a key to holistic software quality},

author={Broy, Manfred},

booktitle={International Symposium on Computer and Information Sciences},

pages={24--34},

year={2006},

organization={Springer}

}

@inproceedings{cheng2007,

title={Research directions in requirements engineering},

author={Cheng, Betty HC and Atlee, Joanne M},

booktitle={2007 Future of Software Engineering},

pages={285--303},

year={2007},

organization={IEEE Computer Society}

}

@article{carrizo2014,

title={Systematizing requirements elicitation technique selection},

author={Carrizo, Dante and Dieste, Oscar and Juristo, Natalia},

journal={Information and Software Technology},

volume={56},

number={6},

pages={644--669},

year={2014},

publisher={Elsevier}

}

@article{khan2015,

title={An empirical study of software requirements verification and validation techniques along their mitigation strategies},

author={Khan, H and Asghar, Ikram and Ghayyur, S and Raza, Mohsin},

journal={Asian Journal of Computer and Information Systems},

volume={3},

number={03},

year={2015}

}

@article{wellsandt2014,

title={Qualitative comparison of requirements elicitation techniques that are used to collect feedback information about product use},

author={Wellsandt, Stefan and Hribernik, Karl A and Thoben, Klaus-Dieter},

journal={Procedia CIRP},

volume={21},

pages={212--217},

year={2014},

publisher={Elsevier}

}

@article{maalem2016,

title={Challenge of validation in requirements engineering},

author={Maalem, Sourour and Zarour, Nacereddine},

journal={Journal of Innovation in Digital Ecosystems},

volume={3},

number={1},

pages={15--21},

year={2016},

publisher={Elsevier}

}

@article{zhang2007,

title={Effective requirements development-a comparison of requirements elicitation techniques},

author={Zhang, Zheying},

journal={Software Quality Management XV: Software Quality in the Knowledge Society, E. Berki, J. Nummenmaa, I. Sunley, M. Ross and G. Staples (Ed.) British Computer Society},

pages={225--240},

year={2007}

}

@inproceedings{deoliveira2017,

title={Challenges of aligning requirements engineering and system testing in large-scale agile: A multiple case study},

author={de Oliveira Neto, Francisco Gomes and Horkoff, Jennifer and Knauss, Eric and Kasauli, Rashidah and Liebel, Grischa},

booktitle={2017 IEEE 25th International Requirements Engineering Conference Workshops (REW)},

pages={315--322},

year={2017},

organization={IEEE}

}

@article{mcmanus2007,

author = {McManus, John and Wood-Harper, Trevor},

title = {Understanding the Sources of Information Systems Project Failure - A study in IS project failure},

journal = {Management Services Journal},

year = {2007},

volume = {51},

pages = {38--43},

}

@article{mendez2017,

title={Naming the pain in requirements engineering: Contemporary problems, causes, and effects in practice},

author={Fern{'a}ndez, D M{'e}ndez and Wagner, Stefan and Kalinowski, Marcos and Felderer, Michael and Mafra, Priscilla and Vetr{`o}, Antonio and Conte, Tayana and Christiansson, M-T and Greer, Desmond and Lassenius, Casper and others},

journal={Empirical software engineering},

volume={22},

number={5},

pages={2298--2338},

year={2017},

publisher={Springer}

}

@article{kopczynska2018,

title={An empirical study on catalog of non-functional requirement templates: Usefulness and maintenance issues},

author={Kopczy{'n}ska, Sylwia and Nawrocki, Jerzy and Ochodek, Miros{l}aw},

journal={Information and Software Technology},

volume={103},

pages={75--91},

year={2018},

publisher={Elsevier}

}

@techreport{chaos2014,

title={Chaos Report},

author={The Standish Group},

institution={available: https://www.projectsmart.co.uk/white-papers/chaos-report.pdf},

year={2014}

}

@inproceedings{przybylek2018,

title={Utilizing online collaborative games to facilitate agile software development},

author={Przyby{l}ek, Adam and Kowalski, Wojciech},

booktitle={2018 Federated Conference on Computer Science and Information Systems (FedCSIS)},

pages={811--815},

year={2018},

organization={IEEE}

}

@inproceedings{ambroziewicz2018,

title={Applying Use Case Logic Patterns in Practice: Lessons Learnt},

author={Ambroziewicz, Albert and {'S}mia{l}ek, Micha{l}},

booktitle={Proc. of 20th KKIO Software Engineering Conference, Engineering Software Systems: Research and Praxis, AISC series vol. 830},

pages={34--49},

year={2018},

organization={Springer}

}

@inproceedings{mendez2014,

title={In quest for requirements engineering oracles: dependent variables and measurements for (good) RE},

author={Fern{'a}ndez, Daniel M{'e}ndez and Mund, Jakob and Femmer, Henning and Vetr{`o}, Antonio},

booktitle={Proceedings of the 18th International Conference on Evaluation and Assessment in Software Engineering},

pages={3},

year={2014},

organization={ACM}

}

@article{sommerville2005,

title={An empirical study of industrial requirements engineering process assessment and improvement},

author={Sommerville, Ian and Ransom, Jane},

journal={ACM Transactions on Software Engineering and Methodology (TOSEM)},

volume={14},

number={1},

pages={85--117},

year={2005},

publisher={ACM}

}

@article{damian2006,

title={An empirical study of the complex relationships between requirements engineering processes and other processes that lead to payoffs in productivity, quality, and risk management},

author={Damian, Daniela and Chisan, James},

journal={IEEE Transactions on Software Engineering},

volume={32},

number={7},

pages={433--453},

year={2006},

publisher={IEEE}

}

@article{ellis2014,

title={Quantifying the impact of requirements definition and management process maturity on project outcome in large business application development},

author={Ellis, Keith and Berry, Daniel M},

journal={Requirements Engineering},

volume={18},

number={3},

pages={223--249},

year={2013},

publisher={Springer}

}

@book{juristo2010,

title={Basics of software engineering experimentation},

author={Juristo, Natalia and Moreno, Ana M},

year={2013},

publisher={Springer Science & Business Media}

}

@incollection{lethbridge2008,

title={The Management of University--Industry Collaborations Involving Empirical Studies of Software Enginee},

author={Lethbridge, Timothy C and Lyon, Steve and Perry, Peter},

booktitle={Guide to Advanced Empirical Software Engineering},

pages={257--281},

year={2008},

publisher={Springer}

}

@inproceedings{madeyski2017,

title={Software engineering needs agile experimentation: a new practice and supporting tool},

author={Madeyski, Lech and Kawalerowicz, Marcin},

booktitle={Proc. of 18th KKIO Software Engineering Conference, Software Engineering: Challenges and Solutions, AISC series vol. 504},

pages={149--162},

year={2017},

publisher={Springer}

}

@inproceedings{kamata2007,

title={How does requirements quality relate to project success or failure?},

author={Kamata, Mayumi Itakura and Tamai, Tetsuo},

booktitle={15th IEEE International Requirements Engineering Conference (RE 2007)},

pages={69--78},

year={2007},

organization={IEEE}

}

@misc{ieee830,

title={IEEE Standard 830-1998: IEEE Recommended Practice for Software Requirements Specifications},

author={IEEE},

year={1998},

organization={IEEE}

}

@inproceedings{rapp2014,

title={Lightweight requirements engineering assessments in software projects},

author={Rapp, Daniel and Hess, Anne and Seyff, Norbert and Sp{"o}rri, Peter and Fuchs, Emmerich and Glinz, Martin},

booktitle={2014 IEEE 22nd International Requirements Engineering Conference (RE)},

pages={354--363},

year={2014},

organization={IEEE}

}

@article{bormane2016,

title={Impact of requirements elicitation processes on success of information system development projects},

author={Bormane, L{=i}ga and Gr{v{z}}ibovska, J{=u}lija and B{=e}rzi{v{s}}a, Solvita and Grabis, J{=a}nis},

journal={Information Technology and Management Science},

volume={19},

number={1},

pages={57--64},

year={2016},

publisher={De Gruyter Open}

}

@article{verner2005,

title={Requirements engineering and software project success: an industrial survey in Australia and the US},

author={Verner, June and Cox, Karl and Bleistein, Steven and Cerpa, Narciso},

journal={Australasian Journal of information systems},

volume={13},

number={1},

year={2005}

}

@inproceedings{bjarnason2011,

title={Requirements are slipping through the gaps?A case study on causes & effects of communication gaps in large-scale software development},

author={Bjarnason, Elizabeth and Wnuk, Krzysztof and Regnell, Bj{"o}rn},

booktitle={2011 IEEE 19th international requirements engineering conference},

pages={37--46},

year={2011},

organization={IEEE}

}

@incollection{mossakowska2018,

title={A Survey Investigating the Influence of Business Analysis Techniques on Software Quality Characteristics},

author={Mossakowska, Katarzyna and Jarz{k{e}}bowicz, Aleksander},

booktitle={Proc. of 19th KKIO Software Engineering Conference, Towards a Synergistic Combination of Research and Practice in Software Engineering, SCI series vol. 733},

pages={135--148},

year={2018},

publisher={Springer}

}

@book{solingen1999,

title={The Goal/Question/Metric Method: a practical guide for quality improvement of software development},

author={van Solingen, DM Rini and Berghout, Egon W},

year={1999},

publisher={McGraw-Hill}

}

@misc{ieee29148,

title={ISO/IEC/IEEE Standard 29148-2011. Systems and Software Engineering - Life Cycle

Processes - Requirements Engineering},

author={ISO/IEC/IEE},

year={2011},

organization={ISO}

}

@misc{babok3,

title={A Guide to the Business Analysis Body of Knowledge (BABOK Guide) version 3},

year={2015},

author={IIBA},

organization={International Institute of Business Analysis}

}

@misc{PMIguide,

title={Business Analysis for Practitioners A Practice Guide},

year={2015},

author={PMI},

organization={Project Management Institute}

}

@misc{REQB_FL,

title={REQB CPRE Foundation Level Syllabus ver. 2.1},

year={2014},

author={REQB},

organization={Requirements Engineering Qualifications Board}

}

@misc{IREB,

title={Handbook of Advanced Level Elicitation according to the IREB Standard},

year={2019},

author={IREB},

organization={International Requirements Engineering Board}

}

@misc{versionone2018,

title={12th Annual State of Agile Report, https://explore.versionone.com/state-of-agile/versionone-12th-annual-state-of-agile-report},

author={VersionOne},

year={2018},

organization={VersionOne}

}




DOI: https://doi.org/10.7494/csci.2020.21.3.3618

Refbacks

  • There are currently no refbacks.