Nombramiento de prácticas relacionadas con requisitos no funcionales en el proceso de desarrollo de software

Abstract

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.