Non-functional grl goals considering software quality standards

Abstract

A goal represents high-level objectives of an organization, a software system (SS) and/or the participants in a software project. The goal-oriented approach, expressed by the Goal-oriented Requirements Language (GRL), reduces the gap between the business
model and the SS, considering also non-functional goals (MNF), in addition to the functional ones (MF), which are not explicitly considered in the business model. There are several levels of abstraction regarding goals: business goals derived from business requirements, SS goals that aim to automate business processes, and SS requirements derived from business goals. . In the literature there is no clear description of how to move from business goals to SS goals; this makes it difficult to automate business processes. On the other hand, the early consideration of aspects, or “Early- Aspects” approach, is important to identify non functional requirements (NFRs) that intersect with functional requirements (RFs); NFRs are largely responsible for building the architecture of an evolving SS. This paper proposes the identification of NFMs that intersect several MFs (cross-cutting NFMs) in a
process that integrates both goal and aspect approaches. NFMs are specified by the ISO/IEC 25010 standard quality model. The process proposed as a result of the work is important to derive initial architectural models; it is applied to an industrial software system. The work is framed in the project PG-03-7310- 2008/2 ADIRE, recently concluded, from CDCH, UCV.