Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software
En ingeniería de software, es usual hablar de prácticas a diferentes niveles, como grupos de actividades que se repiten y que entregan buenos resultados con su uso. Los requisitos no funcionales (entendidos como restricciones en los servicios o funciones del sistema) también tienen prácticas asociadas. Sin embargo, existen formas de nombramiento que no permiten generar un consenso alrededor de dichas prácticas, pues se utilizan productos de trabajo, restricciones, descripciones y otros elementos que impiden reconocer la práctica y su uso. Por ello, en este artículo se nombra un conjunto de prácticas sobre requisitos no funcionales a partir de su descripción en la literatura y tomando en consideración los elementos que requiere el buen nombr... Ver más
Guardado en:
2027-5846
11
2020-10-07
39
47
http://purl.org/coar/access_right/c_abf2
info:eu-repo/semantics/openAccess
Ingenierías USBMed - 2020
| id |
0c7f5aa733de487c4e8e91b1478246a4 |
|---|---|
| record_format |
ojs |
| institution |
UNIVERSIDAD DE SAN BUENAVENTURA |
| thumbnail |
https://nuevo.metarevistas.org/UNIVERSIDADDESANBUENAVENTURA_COLOMBIA/logo.png |
| country_str |
Colombia |
| collection |
Ingenierías USBMed |
| title |
Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software |
| spellingShingle |
Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software Zapata Jaramillo, Carlos Mario Requisitos no funcionales Prácticas Nombramiento de prácticas Practice naming Non-functional requirements Practices |
| title_short |
Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software |
| title_full |
Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software |
| title_fullStr |
Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software |
| title_full_unstemmed |
Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software |
| title_sort |
nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software |
| title_eng |
Naming practices related to non-functional requirements in the software development process |
| description |
En ingeniería de software, es usual hablar de prácticas a diferentes niveles, como grupos de actividades que se repiten y que entregan buenos resultados con su uso. Los requisitos no funcionales (entendidos como restricciones en los servicios o funciones del sistema) también tienen prácticas asociadas. Sin embargo, existen formas de nombramiento que no permiten generar un consenso alrededor de dichas prácticas, pues se utilizan productos de trabajo, restricciones, descripciones y otros elementos que impiden reconocer la práctica y su uso. Por ello, en este artículo se nombra un conjunto de prácticas sobre requisitos no funcionales a partir de su descripción en la literatura y tomando en consideración los elementos que requiere el buen nombramiento. Se espera que este conjunto de prácticas de requisitos no funcionales sirva como punto de partida para la representación detallada en estándares gráficos que se definan para ese fin.
|
| description_eng |
In software engineering we can talk about practices at different levels. Practices are understood as sets of repeatable activities for achieving good results when they are used. Non-functional requirements—constraints on services/functions of a system—also have associated practices. However, naming forms are useless for generating consensus about such practices, since elements like work products, constraints, descriptions, and so on are used, and such elements interfere with practice recognition and usage. For this reason, in this paper we name a set of practices about non-functional requirements from their description in the state of the art. We also consider the elements required by good naming of practices. We hope this set of practices about non-functional requirements can be used as a starting point for detailed presentation by using graphical standards employed for practices.
|
| author |
Zapata Jaramillo, Carlos Mario |
| author_facet |
Zapata Jaramillo, Carlos Mario |
| topicspa_str_mv |
Requisitos no funcionales Prácticas Nombramiento de prácticas |
| topic |
Requisitos no funcionales Prácticas Nombramiento de prácticas Practice naming Non-functional requirements Practices |
| topic_facet |
Requisitos no funcionales Prácticas Nombramiento de prácticas Practice naming Non-functional requirements Practices |
| citationvolume |
11 |
| citationissue |
2 |
| citationedition |
Núm. 2 , Año 2020 : Ingenierías USBMed |
| publisher |
Universidad San Buenaventura - USB (Colombia) |
| ispartofjournal |
Ingenierías USBMed |
| source |
https://revistas.usb.edu.co/index.php/IngUSBmed/article/view/4697 |
| language |
Español |
| format |
Article |
| rights |
http://purl.org/coar/access_right/c_abf2 info:eu-repo/semantics/openAccess Ingenierías USBMed - 2020 https://creativecommons.org/licenses/by-nc-sa/4.0/ |
| references |
Object Management Group. “Essence—Kernel and Language for Software Engineering Methods Version 1.2”. 2018, Recuperado de https://www.omg.org/spec/Essence/1.2/PDF [2] S. Kemmis, J. Wilkinson, Ch. Edwards-Groves, I. Hardy, P. Grootenboer, & I. Hardy. Changing practices, changing education. Singapur: Springer, 2014. [3] I. Sommerville. Software engineering 8th edition. Boston: Pearson Education, 2007. [4] W. Behutiye, P. Karhapää, D. Costal, M. Oivo, & X. Franch. “Non-functional requirements documentation in agile software development: challenges and solution proposal”. Lecture Notes in Computer Science, Vol. 10611, pp. 515-522, 2017. [5] D. Mairiza & D. Zowghi. “Constructing a catalogue of conflicts among non-functional requirements”. Evaluation of novel approaches to software engineering ENASE, pp. 31-44, 2010. [6] S. Kopczyńska, J. Nawrocki, & M. Ochodek. “An empirical study on catalog of non-functional requirement templates: usefulness and maintenance issues”. Information and software technology, Vol. 103, pp. 75-91, 2018. [7] M. Mirakhorli & J. Cleland-Huang. Tracing non-functional requirements. J. Cleland-Huang et al. (eds.), Software and systems traceability. Londres: Springer-Verlag, 2012. [8] Y. Montoya. Evaluation model for non-functional requirements of a software product. Director: Carlos Mario Zapata J. Tesis de Maestría, Universidad Nacional de Colombia, Medellín, 2016. [9] B. Barn. “Do you own a Volkswagen? Values as non-functional requirements”. Lecture Notes in Computer Science, Vol. 9856, pp. 151-162, 2016. [10] G. Robiolo, E. Scott, S. Matalonga, & M. Felderer. “Technical debt and waste in non-functional requirements documentation: an exploratory study”. Lecture Notes in Computer Science, Vol. 11915, pp. 220-235, 2019. [11] A. Barón. Modelo para la definición unificada de la práctica como constructo teórico en ingeniería de software. Director: Carlos Mario Zapata J. Tesis de Doctorado, Universidad Nacional de Colombia, Medellín, 2019. [12] F. Aburub, M. Odeh, & I. Beeson. “Modelling non-functional requirements of business processes”. Information and software technology, Vol. 103, pp. 75-91, 2018. [13] K. Adams. Non-functional requirements in systems analysis and design. New York: Springer, 2015. [14] D. Akoumianakis & C. Stephanidis. “Using non-functional requirements as design drivers for universal access”. Lecture Notes in Computer Science, Vol. 3041, pp. 141-155, 2005. [15] D. Ameller, X. Burgués, D. Costal, C. Farré, & X. Franch. “Non-functional requirements in model-driven development of service-oriented architectures”. Science of computer programming, Vol. 168, pp. 18-37, 2018. [16] D. Ameller & X. Franch. “How do software architects consider non-functional requirements: a survey”. Lecture Notes in Computer Science, Vol. 6182, pp. 276-277, 2010. [17] A. Berztiss. “Non-functional requirements in the design of software”. Lecture Notes in Computer Science, Vol. 750, pp. 375-386, 1994. [18] L. Buglione, O. Ormandjieva, & M. Daneva. “Using PSU for early prediction of COSMIC size of functional and non-functional requirements”. Lecture Notes in Computer Science, Vol. 5338, pp. 352-361, 2008. [19] R. Chopra, V. Gupta, & D. Chauhan. “Experimentation on accuracy of non functional requirement prioritization approaches for different complexity projects”. Perspectives in science, Vol. 8, pp. 79-82, 2016. [20] S. Chouali, A. Hammad, & H. Mountassir. “Assembling components using SysML with non-functional requirements”. Electronic notes in theoretical computer science, Vol. 295, pp. 31-47, 2013. [21] J. Cleland-Huang, R. Settimi, X. Zou, & P. Solc. “Automated classification of non-functional requirements”. Requirements engineering, Vol. 12, pp. 103-120, 2007. [22] M. Dabbagh, S. Lee, & R. Parizi. “Functional and non-functional requirements prioritization: empirical evaluation of IPA, AHP-based, and HAM-based approaches”. Soft computing, Vol. 20, pp. 4497-4520, 2016. [23] Ch. Gnaho, F. Semmak, & R. Laleau. “Modeling the impact of non-functional requirements on functional requirements”. Lecture Notes in Computer Science, Vol. 8697, pp. 59-67, 2014. [24] K. Gómez, C. Baron, P. Esteban, C. Gutiérrez, L. Laredo. “How to find non-functional requirements in system developments”. IFAC PapersOnLine, Vol. 51, N. 11, pp. 1573-1578, 2018. [25] I. Hussain, L. Kosseim, & O. Ormandjieva. “Using linguistic knowledge to classify non-functional requirements in SRS documents”. Lecture Notes in Computer Science, Vol. 5039, pp. 287-298, 2008. [26] S. Izukura, S. Hosono, H. Sakaki, E. Numata, K. Kimita, & Y. Shimomura. “Bridging non-functional requirements and IT service design”. Procedia CIRP, Vol. 30, pp. 24-29, 2015. [27] M. Kassab, O. Ormandjieva, M. Daneva, & A. Abran. “Non-functional requirements size measurement method (NFSM) with COSMIC-FFP”. Lecture Notes in Computer Science, Vol. 4895, pp. 168-182, 2008. [28] T. Marew, J. Lee, & D. Bae. “Tactics based approach for integrating non-functional requirements in object-oriented analysis and design”. The journal of systems and software, Vol. 82, pp. 1642-1656, 2009. [29] Y. Matsumoto, S. Shirai, & A. Ohnishi. “A method for verifying non-functional requirements”. Procedia computer science, Vol. 112, pp. 157-166, 2017. [30] E. Poort, N. Martens, I. Van de Weerd, & H. Van Vliet. “How architects see non-functional requirements: beware of modifiability”. Lecture Notes in Computer Science, Vol. 7195, pp. 37-51, 2012. [31] M. Riojas, S. Lysecky, & J. Rozenblit. Understanding non-functional requirements for precollege engineering technologies. R. Klempous & J. Nikodem (eds.), Innovative technologies in management and science. Londres: Springer-Verlag, 2015. [32] T. Shah, & S. Patel “A novel approach for specifying functional and non-functional requirements using RDS (Requirement Description Schema)”. Procedia computer science, Vol. 79, pp. 852-860, 2016. [33] S. Song, Y. Kim, S. Park, & S. Park. A non-functional requirements traceability management method based on architectural patterns. R. Lee (ed.), Computers, networks, systems, & industrial engineering. Berlin: Springer-Verlag, 2015. [34] C. Theaker & J. Whitworth. Designing with non-functional requirements. M. Lee et al. (eds.), Software quality and productivity. Dordrecht: Springer, 1995. [35] J. Zou, L. Xu, M. Yang, X. Zhang, & D. Yang. “Towards comprehending the non-functional requirements through developers’ eyes: an exploration of stack overflow using topic analysis”. Procedia computer science, Vol. 112, pp. 157-166, 2017. [36] E. Brockmann & W. Anthony. “The influence of tacit knowledge and collective mind on strategic planning”. Journal of managerial issues, Vol. 10, N. 2, pp. 204-222, 1998. |
| type_driver |
info:eu-repo/semantics/article |
| type_coar |
http://purl.org/coar/resource_type/c_6501 |
| type_version |
info:eu-repo/semantics/publishedVersion |
| type_coarversion |
http://purl.org/coar/version/c_970fb48d4fbd8a85 |
| type_content |
Text |
| publishDate |
2020-10-07 |
| date_accessioned |
2020-10-07T00:41:14Z |
| date_available |
2020-10-07T00:41:14Z |
| url |
https://revistas.usb.edu.co/index.php/IngUSBmed/article/view/4697 |
| url_doi |
https://doi.org/10.21500/20275846.4697 |
| eissn |
2027-5846 |
| doi |
10.21500/20275846.4697 |
| citationstartpage |
39 |
| citationendpage |
47 |
| url2_str_mv |
https://revistas.usb.edu.co/index.php/IngUSBmed/article/download/4697/3731 |
| _version_ |
1798192158837047296 |
| spelling |
Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software application/pdf Text http://purl.org/coar/access_right/c_abf2 info:eu-repo/semantics/openAccess http://purl.org/coar/version/c_970fb48d4fbd8a85 info:eu-repo/semantics/publishedVersion http://purl.org/coar/resource_type/c_6501 info:eu-repo/semantics/article Object Management Group. “Essence—Kernel and Language for Software Engineering Methods Version 1.2”. 2018, Recuperado de https://www.omg.org/spec/Essence/1.2/PDF [2] S. Kemmis, J. Wilkinson, Ch. Edwards-Groves, I. Hardy, P. Grootenboer, & I. Hardy. Changing practices, changing education. Singapur: Springer, 2014. [3] I. Sommerville. Software engineering 8th edition. Boston: Pearson Education, 2007. [4] W. Behutiye, P. Karhapää, D. Costal, M. Oivo, & X. Franch. “Non-functional requirements documentation in agile software development: challenges and solution proposal”. Lecture Notes in Computer Science, Vol. 10611, pp. 515-522, 2017. [5] D. Mairiza & D. Zowghi. “Constructing a catalogue of conflicts among non-functional requirements”. Evaluation of novel approaches to software engineering ENASE, pp. 31-44, 2010. [6] S. Kopczyńska, J. Nawrocki, & M. Ochodek. “An empirical study on catalog of non-functional requirement templates: usefulness and maintenance issues”. Information and software technology, Vol. 103, pp. 75-91, 2018. [7] M. Mirakhorli & J. Cleland-Huang. Tracing non-functional requirements. J. Cleland-Huang et al. (eds.), Software and systems traceability. Londres: Springer-Verlag, 2012. [8] Y. Montoya. Evaluation model for non-functional requirements of a software product. Director: Carlos Mario Zapata J. Tesis de Maestría, Universidad Nacional de Colombia, Medellín, 2016. [9] B. Barn. “Do you own a Volkswagen? Values as non-functional requirements”. Lecture Notes in Computer Science, Vol. 9856, pp. 151-162, 2016. [10] G. Robiolo, E. Scott, S. Matalonga, & M. Felderer. “Technical debt and waste in non-functional requirements documentation: an exploratory study”. Lecture Notes in Computer Science, Vol. 11915, pp. 220-235, 2019. [11] A. Barón. Modelo para la definición unificada de la práctica como constructo teórico en ingeniería de software. Director: Carlos Mario Zapata J. Tesis de Doctorado, Universidad Nacional de Colombia, Medellín, 2019. [12] F. Aburub, M. Odeh, & I. Beeson. “Modelling non-functional requirements of business processes”. Information and software technology, Vol. 103, pp. 75-91, 2018. [13] K. Adams. Non-functional requirements in systems analysis and design. New York: Springer, 2015. [14] D. Akoumianakis & C. Stephanidis. “Using non-functional requirements as design drivers for universal access”. Lecture Notes in Computer Science, Vol. 3041, pp. 141-155, 2005. [15] D. Ameller, X. Burgués, D. Costal, C. Farré, & X. Franch. “Non-functional requirements in model-driven development of service-oriented architectures”. Science of computer programming, Vol. 168, pp. 18-37, 2018. [16] D. Ameller & X. Franch. “How do software architects consider non-functional requirements: a survey”. Lecture Notes in Computer Science, Vol. 6182, pp. 276-277, 2010. [17] A. Berztiss. “Non-functional requirements in the design of software”. Lecture Notes in Computer Science, Vol. 750, pp. 375-386, 1994. [18] L. Buglione, O. Ormandjieva, & M. Daneva. “Using PSU for early prediction of COSMIC size of functional and non-functional requirements”. Lecture Notes in Computer Science, Vol. 5338, pp. 352-361, 2008. [19] R. Chopra, V. Gupta, & D. Chauhan. “Experimentation on accuracy of non functional requirement prioritization approaches for different complexity projects”. Perspectives in science, Vol. 8, pp. 79-82, 2016. [20] S. Chouali, A. Hammad, & H. Mountassir. “Assembling components using SysML with non-functional requirements”. Electronic notes in theoretical computer science, Vol. 295, pp. 31-47, 2013. [21] J. Cleland-Huang, R. Settimi, X. Zou, & P. Solc. “Automated classification of non-functional requirements”. Requirements engineering, Vol. 12, pp. 103-120, 2007. [22] M. Dabbagh, S. Lee, & R. Parizi. “Functional and non-functional requirements prioritization: empirical evaluation of IPA, AHP-based, and HAM-based approaches”. Soft computing, Vol. 20, pp. 4497-4520, 2016. [23] Ch. Gnaho, F. Semmak, & R. Laleau. “Modeling the impact of non-functional requirements on functional requirements”. Lecture Notes in Computer Science, Vol. 8697, pp. 59-67, 2014. [24] K. Gómez, C. Baron, P. Esteban, C. Gutiérrez, L. Laredo. “How to find non-functional requirements in system developments”. IFAC PapersOnLine, Vol. 51, N. 11, pp. 1573-1578, 2018. [25] I. Hussain, L. Kosseim, & O. Ormandjieva. “Using linguistic knowledge to classify non-functional requirements in SRS documents”. Lecture Notes in Computer Science, Vol. 5039, pp. 287-298, 2008. [26] S. Izukura, S. Hosono, H. Sakaki, E. Numata, K. Kimita, & Y. Shimomura. “Bridging non-functional requirements and IT service design”. Procedia CIRP, Vol. 30, pp. 24-29, 2015. [27] M. Kassab, O. Ormandjieva, M. Daneva, & A. Abran. “Non-functional requirements size measurement method (NFSM) with COSMIC-FFP”. Lecture Notes in Computer Science, Vol. 4895, pp. 168-182, 2008. [28] T. Marew, J. Lee, & D. Bae. “Tactics based approach for integrating non-functional requirements in object-oriented analysis and design”. The journal of systems and software, Vol. 82, pp. 1642-1656, 2009. [29] Y. Matsumoto, S. Shirai, & A. Ohnishi. “A method for verifying non-functional requirements”. Procedia computer science, Vol. 112, pp. 157-166, 2017. [30] E. Poort, N. Martens, I. Van de Weerd, & H. Van Vliet. “How architects see non-functional requirements: beware of modifiability”. Lecture Notes in Computer Science, Vol. 7195, pp. 37-51, 2012. [31] M. Riojas, S. Lysecky, & J. Rozenblit. Understanding non-functional requirements for precollege engineering technologies. R. Klempous & J. Nikodem (eds.), Innovative technologies in management and science. Londres: Springer-Verlag, 2015. [32] T. Shah, & S. Patel “A novel approach for specifying functional and non-functional requirements using RDS (Requirement Description Schema)”. Procedia computer science, Vol. 79, pp. 852-860, 2016. [33] S. Song, Y. Kim, S. Park, & S. Park. A non-functional requirements traceability management method based on architectural patterns. R. Lee (ed.), Computers, networks, systems, & industrial engineering. Berlin: Springer-Verlag, 2015. [34] C. Theaker & J. Whitworth. Designing with non-functional requirements. M. Lee et al. (eds.), Software quality and productivity. Dordrecht: Springer, 1995. [35] J. Zou, L. Xu, M. Yang, X. Zhang, & D. Yang. “Towards comprehending the non-functional requirements through developers’ eyes: an exploration of stack overflow using topic analysis”. Procedia computer science, Vol. 112, pp. 157-166, 2017. [36] E. Brockmann & W. Anthony. “The influence of tacit knowledge and collective mind on strategic planning”. Journal of managerial issues, Vol. 10, N. 2, pp. 204-222, 1998. Ingenierías USBMed - 2020 https://creativecommons.org/licenses/by-nc-sa/4.0/ Español https://revistas.usb.edu.co/index.php/IngUSBmed/article/view/4697 Ingenierías USBMed Universidad San Buenaventura - USB (Colombia) Publication 2 En ingeniería de software, es usual hablar de prácticas a diferentes niveles, como grupos de actividades que se repiten y que entregan buenos resultados con su uso. Los requisitos no funcionales (entendidos como restricciones en los servicios o funciones del sistema) también tienen prácticas asociadas. Sin embargo, existen formas de nombramiento que no permiten generar un consenso alrededor de dichas prácticas, pues se utilizan productos de trabajo, restricciones, descripciones y otros elementos que impiden reconocer la práctica y su uso. Por ello, en este artículo se nombra un conjunto de prácticas sobre requisitos no funcionales a partir de su descripción en la literatura y tomando en consideración los elementos que requiere el buen nombramiento. Se espera que este conjunto de prácticas de requisitos no funcionales sirva como punto de partida para la representación detallada en estándares gráficos que se definan para ese fin. Zapata Jaramillo, Carlos Mario Requisitos no funcionales Prácticas 11 Nombramiento de prácticas Núm. 2 , Año 2020 : Ingenierías USBMed Artículo de revista Practice naming In software engineering we can talk about practices at different levels. Practices are understood as sets of repeatable activities for achieving good results when they are used. Non-functional requirements—constraints on services/functions of a system—also have associated practices. However, naming forms are useless for generating consensus about such practices, since elements like work products, constraints, descriptions, and so on are used, and such elements interfere with practice recognition and usage. For this reason, in this paper we name a set of practices about non-functional requirements from their description in the state of the art. We also consider the elements required by good naming of practices. We hope this set of practices about non-functional requirements can be used as a starting point for detailed presentation by using graphical standards employed for practices. Journal article Non-functional requirements Practices Naming practices related to non-functional requirements in the software development process 10.21500/20275846.4697 2020-10-07 https://revistas.usb.edu.co/index.php/IngUSBmed/article/download/4697/3731 https://doi.org/10.21500/20275846.4697 47 39 2020-10-07T00:41:14Z 2027-5846 2020-10-07T00:41:14Z |