A QoS ontology cooperated with feature models for non-functional requirements elicitation

Quality requirements elicitation based on inquiry of quality-impact relationships

“…Such models allow identification of needs for improving, increasing, or keeping the level of the quality characteristics of a software. To support systematic identification of goals and qualities within a given domain, ontologies have been developed and used to support requirements elicitation [16,17]. The means-ends relationships that are an inherent part of a goal model make the impact of such a quality requirements explicit [18,19].…”

“…For a telecommunication system, Quality of Service (QoS) requirements are stated that concern system performance, availability, and capacity [17]. Often these requirements are agreed in a service level agreements (SLA) between the system customers and the supplier [28].…”

Classification and Qualitative Analysis of Non-Functional Requirements Approaches

“…Goal-oriented Aspect-oriented Pattern-based • Use-case Questioner [14] • MOQARE [15] • NFRs elicitation model [16] • Actor-based model [17] • Usability catalogue [18] • NFRs Layered Framework [19] • Goal-based requirement extraction [20] • Usability Elicitation Framework [21] • NFR Classifier [22] • Semi supervised text Analysis [23] • QA-Miner [24] • NFR Incorporation Framework [25] • Speech recognition [26] • Experience-based Method [27] • NFRs elicitation Framework [28] • ElicitO [29] • Efficiency usecases [30] • NFR recommendation [31] In goal-oriented elicitation approach, goal-based questionnaire is proposed to extract NFRs by questioning stakeholders [14,15], business process model [16], usecase of domain model [17], and taxonomy [18] in the system development. Goal decomposing [19] and goal analysis [20] methods are proposed to identify stakeholder, generate their expected goals based on developer's knowledge and experience, then decompose the goals into sub-goals and identify NFRs for each sub-goals.…”

“…meeting minutes, interview notes, and memos). In pattern-based approach, experience-based elicitation [27], domain ontology [28][29][30] are proposed to assist requirements analysts in NFRs elicitation process. Recommendation system [31] is also proposed to understand expected realistic NFRs in the system development.…”

Experience of pragmatically combining RE methods for performance requirements in industry

“…PROPRE does not rely on the availability of all stakeholders or up-to-date documentation, is applicable in a globalized environment, and goes along with a moderate and feasible time effort. To achieve this goal, it solely relies on abstract feature models [6] of the system under study. Furthermore, we provide performance requirements specification templates to ensure that all relevant attributes of the gathered performance requirements are recorded.…”