THE PROBLEMS OF DEFINITION AND ANALYSIS OF SOFTWARE REQUIREMENTS

Yu.I. Grytsiuk, I.F. Leshkevych

Abstract


Successful operation of the software largely depends on the proper organization of work to identify and analyze its requirements. Therefore the study aims at systematic analysing of the subject area. The results obtained enabled certain describing of the immediate problems related to procedures, and also identifying and analysing software requirements. The analysis has found activities to effectively address these issues and provide the main indicators of the quality of future software. A formalized model for implementation of procedures to identify and analyse software requirements is improved. The study has defined that potential experts can gain all the relevant competences in the process of solving specific problems in different subject areas both during training and production activities. The authors have highlighted the procedure for software requirements analysis can be quite extensive and resource intensive requiring detailed knowledge of the subject area and use subtle psychological skills. Moreover, many scientists and practitioners singled out the following main stages of the procedure of software requirements analysis: definition of interested parties in software development; interviews with interested parties on their needs in the future of software; joint session for definition of requirements for the software; sets of the requirements for the software contract in style; measurable targets for future software application; prototype – a model of future software; precedents – the technology for documenting requirements for software; specification of requirements for software. To conclude, firstly for proper software operation all the certain competences of field experts are required when performing specific tasks in various subject areas both during training and production activities. Secondly, urgent problems concerning procedures of determining requirements for software and the ways of their avoidance and mitigation are distinguished. Finally, appropriate procedures regarding the definition and analysis of software requirements are improved in the formalized model.

Keywords


systems analysis; subject area; analyst activities; definition of requirements for software; software requirements analysis; quality software; model definition and analysis of software requirements

Full Text:

PDF

References


Belchikov, Ya., & Birshtejn, M. M. (1989). Delovye igry. Riga: AVOTS, 304 p. [іn Russian].

Blagodatskih, V. A., Volnin, V. A., & Poskakalov, K. F. (2005). Standartizacija razrabotki programmnyh sredstv: uchebn. posob. Moscow: Finansy i statistika, 288 p. [іn Russian].

Bobalo, Yu. Ya., Volochii, B. Yu., Lozynskyi, O. Yu. et al. (2013). Matematychni modeli ta metody analizu nadiinosti radioelektronnykh, elektrotekhnichnykh ta prohramnykh system: monohrafiia. Lviv: Vyd-vo Lvivskoi politekhniky, 300 p. [іn Ukrainian].

Bоegh, J., Depanfilis, S., Kitchenham, B., & Pasquini, A. A. (1999). Method for Software Quality Planning, Control, and Evaluation. IEEE Software, 16(2), 69–77. https://doi.org/10.1109/52.754056

Futrell, R. T., Shafer, D. F., & Shafer, L. I. (2003). Quality software project management. New York: Prentice Hall PTR, 1136 p.

Gilb, T. (1988). Principles of Software Engineering Management. Reading MA: Addison Wesley, 464 p.

IEEE 1031-2011. (2008). IEEE Guide for the Functional Specification. Retrieved from: https://standards.ieee.org/findstds/standard/ 1031-2011.html

IEEE 1061-26157. (1998). Standard for Software Quality Metrics Methodology. Retrieved from: http://www.techstreet.com/cgi-bin/detail?product_id = 26157 (data obrashhenija: 20.06.2008).

IEEE 830-1998. (1998). Recommended Practice for Software Requirements Specifications. New York: IEEE, 44 p.

ISO/IEC, ISO/IEC 25000. (2005). Software Engineering – Software Product Quality Requirements and Evaluation (SQuaRE) – Guide to SQuaRE. – Geneva: International Organization for Standardization. Retrieved from: http://www.iso.org/iso/iso_catalogue/ catalogue_tc/catalogue_detail.htm?csnumber = 35683 (data obrashhenija: 26.07.2008).

Kobern, A. (2011). Sovremennye metody opisanija funkcionalnyh trebovanij k sistemam. Moscow: Lori, 263 p. [іn Russian].

Kungurcev, A. B., Kalinina, S. A., & Novikova, N. A. (2013). Model processa opredelenija trebovanij k programmnomu produktu. Visnyk NTU "KhPI". Seriia: Novi rishennia v suchasnykh tekhnolohiiakh, 38(1011), 55–61. Kharkiv : Vyd-vo NTU "KhPI". [іn Russian].

Kungurcev, A., Blazhko, A., & Marulin, S. (2010). Metodika provedenija obuchenija osnovam proektirovanija programmnyh sistem v vide rolevyh kompjuternyh igr. Godishnik na tehnicheski universitet. In 3 vols. Vol. 1: Sbornik dokladov ot jubilejnoj nauchnoj konferencii s mezhdunarodnym uchastiem (pp. 123–126). Varna: Varna. [іn Russian].

Lavrishheva, E. M., & Petruhin, V. A. (2006). Metody i sredstva inzhenerii programmnogo obespechenija: uchebn. posob. Moscow: Izd-vo Moskovskogo fiziko-tehnicheskogo instituta, 304 p. [іn Russian].

Leffingujell, D., & Uidrig, Don. (2002). Principy raboty s trebovanijami k programmnomu obespecheniju. Moscow–Sankt-Petersburg: Izd. dom "Viljams", 450 p. [іn Russian].

Lukina, M. (2003). Tehnologija intervju: uchebn. posobie [dlja VUZov]. Moscow: Aspekt Press, 480 p. [іn Russian].

McConnell, S. (2013). Sovershennyj kod. Master-klass. Moscow: Izd-vo "Russkaja redakcija", 896 p. [іn Russian].

McCall, J., Richards, P., & Walters, G. (1977). Factors in Software Quality. Three volumes: NTIS AD-A049-014, AD-A049-015, AD-A049-055. Retrieved from: http://oai.dtic.mil/oai/oai?&verb = getRecord&metadataPrefix = html&identifier = ADA049014 (data obrashhenija: 17.05.2008).

Mishhenko, V. O., Pomorova, O. V., & Govorushhenko, T. A. (2012). CASE-ocenka kriticheskih programmnyh sistem. In 3 vols. Vol. 1: Kachestvo; pod red. V. S. Kharchenko. Kharkov: NAU "KhAI", 201 p. [іn Russian].

Pomorova, O. V., & Hovorushchenko, T. O. (2013). Suchasni problemy otsiniuvannia yakosti prohramnoho zabezpechennia. Radioelektronni ta kompiuterni systemy, 5, 319–327. Kharkiv : NAU "KhAI". [іn Ukrainian].

Vedenina, V. (2013). Delovaja igra i ee vozmozhnosti. Retrieved from: http://tolerance.ru/teacher/kabinet/business-game.html (data obrashhenija: 26.02.2013). [іn Russian].

Vigers, K. (2004). Razrabotka trebovanij k programmnomu obespecheniju : per. s angl. Moscow: Izd.-torg. dom "Russkaja Redakcija", 576 p. [іn Russian].

Yakovyna, V., Seniv, M., Chabaniuk, Ya., Fedasiuk, D., & Khimka, U. (2010). Kryterii dostatnosti protsesu testuvannia prohramnoho zabezpechennia. Visnyk Natsionalnoho universytetu "Lvivska politekhnika". Seria: Kompiuterni nauky ta informatsiini tekhnolohii, 672, 346–358. [іn Ukrainian].




DOI: https://doi.org/10.15421/40270433

Refbacks

  • There are currently no refbacks.