What Should a Good Software Requirements Specification Include? Results of a Survey

• Autorzy: Rączkowska-Gzowska Karolina , Walkowiak-Gall Anita

Identyfikatory

DOI

10.2478/fcds-2023-0004

• Języki publikacji: EN

Abstrakty

EN

Software requirements specification is an important foundation of the software development process. It documents the requirements, expectations, and restrictions for a system to be developed. It should describe what the produced system will offer in detail and unambiguously. It should also provide a realistic basis for estimating product costs, risks, and schedules. Still, it is difficult to prepare a useful specification effectively. We want to propose an approach to creating a good specification. We started the work from scratch by determining what the scope of the specification should be. We asked people who work on IT projects what information is and should be included in the specifications with which they work. This paper presents results from a survey conducted with 163 participants who have experience working on commercial software development projects. The main observation is that the content of requirements specification differs with respect to project characteristics, such as industry or financing method. We also noticed that the information about integration with external systems and functionalities most often appears in the SRS.

Słowa kluczowe

EN

software development process; Software Requirements Specification; survey

• Wydawca: Wydawnictwo Politechniki Poznańskiej
• Czasopismo: Foundations of Computing and Decision Sciences
• Rocznik: 2023
• Tom: Vol. 48, No. 1
• Strony: 57--81
• Opis fizyczny: Bibliogr. 43 poz., rys., tab.

Twórcy

autor

Rączkowska-Gzowska Karolina

• Faculty of Information and Communication Technology Wroclaw University of Science and Technology

autor

Walkowiak-Gall Anita

• Faculty of Information and Communication Technology Wroclaw University of Science and Technology

Bibliografia

• [1] Ali W., Rafiq A., and Majeed M. N. Requirements engineering in software houses of pakistan. International Journal of Modern Education and Computer Science, 6(9): 47, 2014.
• [2] Amaral L. M., Siqueira F. L., and Brandão A. A. F. A survey on requirements notations in software engineering research. In Proceedings of the 37thACM/SIGAPP Symposium on Applied Computing, page 1291-1298. Association for Computing Machinery, 2022.
• [3] Barata J. C., Lisboa D., Bastos L. C., and Neto A. Agile requirements engineering practices: a survey in brazilian software development companies. arXiv preprintarXiv:2202.12956, 2022.
• [4] Brown J. D. Using surveys in language programs. Cambridge, England: Cambridge University Press., 2001.
• [5] Christine C. and Dean B. J. The Cambridge Guide to Research in Language Teaching and Learning. Cambridge University Press, 2016.
• [6] Davis A., Overmyer S., Jordan K., Caruso J., Dandashi F., Dinh A., Kincaid G., Ledeboer G., Reynolds P., Sitaram P., Ta A., and Theofanos M. Identifying and measuring quality in a software requirements specification. In [1993] Proceedings First International Software Metrics Symposium, pages 141-152, 1993.
• [7] Fernández D. M., Wagner S., Kalinowski M., Felderer M., Mafra P., Vetrò A., Conte T., Christiansson M.-T., Greer D., Lassenius C., et al. Naming the pain in requirements engineering: A design for a global family of surveys and first results from germany. Empirical software engineering, 22(5): 2298-2338, 2017.
• [8] Gobov D. and Huchenko I. Requirement elicitation techniques for software projects in ukrainian it: an exploratory study. In 2020 15th Conference on Computer Science and Information Systems (FedCSIS), pages 673-681. IEEE, 2020.
• [9] Gobov D. and Huchenko I. Software requirements elicitation techniques selection method for the project scope management. In ITPM, pages 1-10, 2021.
• [10] Gobov D. and Huchenko I. Modern requirements documentation techniques and the influence of the project context: Ukrainian it experience. In International Conference on Computer Science, Engineering and Education Applications, pages 260-270. Springer, 2022.
• [11] Gross A. and Doerr J. What do software architects expect from requirements specifications? results of initial explorative studies. In 2012 First IEEE International Workshop on the Twin Peaks of Requirements and Architecture (Twin-Peaks), pages 41-45, 2012.
• [12] Gross A. and Doerr J. What you need is what you get!: The vision of view based requirements specifications. In 2012 20th IEEE International Requirements Engineering Conference (RE), pages 171-180, 2012.
• [13] Groves L., Nickson R., Reeve G., Reeves S., and Utting M. A survey of software requirements specification practices in the new zealand software industry, 1999.
• [14] Gupta A. and Siddiqui S. A survey of software requirements specification ambiguity. Journal of Engineering and Applied Sciences, 14: 3046-3061, 09 2019.
• [15] Hess A., Doerr J., and Seyff N. How to make use of empirical knowledge about testers’ information needs. In 2017 IEEE 25th International Requirements Engineering Conference Workshops (REW), pages 327-330, 2017.
• [16] Institute of Electrical and Electronics Engineers, Inc. Iso/iec/ieee 29148. systems and software engineering - life cycle processes - requirements engineering, 2018.
• [17] International Institute of Business Analysis. Business analysis body of knowledge (babok guide) version 3, 2015.
• [18] International Requirements Engineering Board. Ireb cpre foundation level syllabus version 3.1, 2022.
• [19] Jarzębowicz A. and Połocka K. Selecting requirements documentation techniques for software projects: a survey study. In 2017 Federated Conference on Computer Science and Information Systems (FedCSIS), pages 1189-1198. IEEE, 2017.
• [20] Jarzębowicz A. and Sitko N. Communication and documentation practices in agile requirements engineering: a survey in polish software industry. In EuroSymposium on Systems Analysis and Design, pages 147-158. Springer, 2019.
• [21] Jedlitschka A., Ciolkowski M., Denger C., Freimut B., and Schlichting A. Relevant information sources for successful technology transfer: A survey using inspections as an example. In First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007), pages 31-40, 2007.
• [22] Kamsties E., von Knethen A., and Reussner R. A controlled experiment to evaluate how styles affect the understandability of requirements specifications. Information and Software Technology, 45(14): 955-965, 2003.
• [23] Kitchenham B. A. and Pfleeger S. L. Personal Opinion Surveys, pages 63-92.Springer London, London, 2008.
• [24] Lauesen S. Software requirements: styles and techniques. Pearson Education, 2002.
• [25] Lethbridge T. A survey of the relevance of computer science and software engineering education. Proceedings 11th Conference on Software Engineering Education, pages 56-66, 1998.
• [26] Medeiros J., Goulão M., Vasconcelos A., and Silva C. Towards a model about quality of software requirements specification in agile projects. In 2016 10th International Conference on the Quality of Information and Communications Technology (QUATIC), pages 236-241, 2016.
• [27] Medeiros J., Vasconcelos A., Goulão M., Silva C., and Araújo J. An approach based on design practices to specify requirements in agile projects. In Proceedings of the Symposium on Applied Computing, page 1114-1121. Association for Computing Machinery, 04 2017.
• [28] Medeiros J., Vasconcelos A., Silva C., and Goulão M. Quality of software requirements specification in agile projects: A cross-case analysis of six companies. Journal of Systems and Software, 142: 171-194, 2018.
• [29] Menzel I., Mueller M., Gross A., and Doerr J. An experimental comparison regarding the completeness of functional requirements specifications. In 2010 18th IEEE International Requirements Engineering Conference, pages 15-24, 2010.
• [30] Méndez Fernández D., Wagner S., Kalinowski M., Schekelmann A., Tuzcu A., Conte T., Spínola R., and Prikladnicki R. Naming the pain in requirements engineering: comparing practices in brazil and germany. 01 2015.
• [31] Parnas D. L. and Madey J. Functional documents for computer systems. Science of Computer programming, 25(1): 41-61, 1995.
• [32] Project Management Institute. Business analysis for practitioners a practice guide, 2015.
• [33] Reggio G., Leotta M., Cerioli M., Spalazzese R., and Alkhabbas F. What are iot systems for real? an experts’ survey on software engineering aspects. Internet of Things, 12, 2020.
• [34] Reggio G., Leotta M., and Ricca F. Who knows/uses what of the uml: A personal opinion survey. In Dingel J., Schulte W., Ramos I., Abrahão S., and Insfran E., editors, Model-Driven Engineering Languages and Systems, pages149-165. Springer International Publishing, 2014.
• [35] Saavedra R., Ballejos L. C., and Ale M. Software requirements quality evaluation: State of the art and research challenges. In 14th Argentine Symposium on Software Engineering, 2013.
• [36] Shah U. S. and Jinwala D. C. Resolving ambiguities in natural language software requirements: A comprehensive survey. SIGSOFT Softw. Eng. Notes, 40(5): 1-7, 2015.
• [37] Tomassetti F., Torchiano M., Tiso A., Ricca F., and Reggio G. Maturity of software modelling and model driven engineering: A survey in the italian industry. In 16th International Conference on Evaluation & Assessment in Software Engineering (EASE 2012), pages 91-100, 2012.
• [38] Villamizar H., Kalinowski M., Viana M., and Fernández D. M. A systematic mapping study on security in agile requirements engineering. In 2018 44th Euromicro conference on software engineering and advanced applications (SEAA), pages 454-461. IEEE, 2018.
• [39] Wagner S., Fernández D. M., Felderer M., and Kalinowski M. Requirements engineering practice and problems in agile projects: results from an international survey. arXiv preprint arXiv:1703.08360, 2017.
• [40] Wagner S., Fernández D. M., Felderer M., Vetrò A., Kalinowski M., Wieringa R., Pfahl D., Conte T., Christiansson M.-T., Greer D., et al. Status quo in requirements engineering: A theory and a global family of surveys. ACM Transactions on Software Engineering and Methodology (TOSEM), 28(2): 1-48, 2019.
• [41] Walkowiak-Gall A. and Gall D. PIM-PSM pattern-aware transformations. In Kosiuczenko P. and Śmiałek M., editors, From requirements to software: research and practice, pages 101-117. Polish Information Processing Society, 2015.
• [42] Walonick D. Survival Statistics. StatPac, Inc., 1997.
• [43] Wiegers K. and Beatty J. Software Requirements. Best practices. Microsoft Press, 2013.

Uwagi

Opracowanie rekordu ze środków MEiN, umowa nr SONP/SP/546092/2022 w ramach programu "Społeczna odpowiedzialność nauki" - moduł: Popularyzacja nauki i promocja sportu (2022-2023).