Analysis Of Non-functional Requirements Research Articles

The KlaperSuite framework for model-driven reliability analysis of component-based systems

Automatic prediction tools play a key role in enabling the application of non-functional requirements analysis, to simplify the selection and the assembly of components for component-based software systems, and in reducing the need for strong mathematical skills for software designers. By exploiting the paradigm of Model-Driven Engineering (MDE), it is possible to automatically transform design models into analytical models, thus enabling formal property verification. MDE is the core paradigm of the KlaperSuite framework presented in this paper, which exploits the KLAPER pivot language to fill the gap between design and analysis of component-based systems for reliability properties. KlaperSuite is a family of tools empowering designers with the ability to capture and analyze quality of service views of their systems, by building a one-click bridge towards a number of established verification instruments. In this article, we concentrate on the reliability-prediction capabilities of KlaperSuite and we evaluate them with respect to several case studies from literature and industry.

Sistema de evaluación cualitativa a través de dispositivos móviles

El Sistema PruebaL es un producto del proyecto Evaluación Cualitativa a Través de Dispositivos Móviles, cuyo objetivo es analizar e implementar un sistema para gestionar procesos de evaluación. La temática se enmarca dentro de los conceptos de mobile learnig y su desarrollo consistió en el análisis de requerimientos funcionales y no funcionales, la definición del sistema, el diseño para las relaciones modulares de profesor, estudiante, administrador y pruebas y la implementación utilizando tecnología de teléfonos celulares. Se alcanzaron dos logros fundamentales: un modelo de evaluación cualitativa automatizada con el sistema PruebaL y la notificación efectiva a los teléfonos celulares matriculados en las bases de datos de estudiantes, para la presentación de las evaluaciones y el acceso Web a estas.

A nonfunctional requirement tradeoff analysis approach for software product line architecture design

Software product line development paradigm allows the development of intensive products simultaneously. Nonfunctional requirement analysis for the paradigm is a challenge problem, mainly due to the massive products that are involved. Especially in the situation where some products' nonfunctional requirements are not met, how do architects keep the revision, and the impact caused by the revision both minimal? This paper investigates the issue of nonfunctional requirement tradeoff analysis for software product lines at the architecture design stage, and proposes an architectural approach to assist architects in making optimal revision decisions based on nonfunctional tradeoff analysis results. In particular, the nonfunctional requirement supported in the approach at this stage is performance. The little's law has been adopted to support performance analysis for software product line architecture design. A Unified Modeling Language profile is also developed to support performance modeling for software product line architecture design, thus to facilitate architectural performance analysis.

Modeling of Component Diagrams Using Petri Nets

With the growing use of UML diagrams for software architecture description and the importance of non-functional requirements evaluation at software architecture level, filling the scientific gap between architect and requirement analyst is considered to be significant. Software architects are not usually familiar with non-functional requirement analysis and are not able to analyze such requirements easily. On the other hand, non-functional requirements cannot be evaluated directly by UML diagrams. Therefore, the architect should annotate additional information of the nonfunctional requirements to software architecture description and then an executable model can be produced. These executable models can be petri nets, queuing networks, stochastic process algebra and etc. One kind of the UML diagrams that can be used to describe software architecture is component diagram. In this paper, we propose a new algorithm that enables an architect to transform a component diagram into an executable model based on different extensions of petri nets. Moreover, we show how to use this petri net model for performance evaluation and simulation and the implications of this transformation are described completely. Finally, to represent the usage of our proposed algorithm, we consider a case study as an example.

Feature-Oriented Nonfunctional Requirement Analysis for Software Product Line

Domain analysis in software product line (SPL) development provides a basis for core assets design and implementation by a systematic and comprehensive commonality/variability analysis. In feature-oriented SPL methods, products of the domain analysis are domain feature models and corresponding feature decision models to facilitate application-oriented customization. As in requirement analysis for a single system, the domain analysis in the SPL development should consider both functional and nonfunctional domain requirements. However, the nonfunctional requirements (NFRs) are often neglected in the existing domain analysis methods. In this paper, we propose a context-based method of the NFR analysis for the SPL development. In the method, NFRs are materialized by connecting nonfunctional goals with real-world context, thus NFR dicitation and variability analysis can be performed by context analysis for the whole domain with the assistance of NFR templates and NFR graphs. After the variability analysis, our method integrates both functional and nonfunctional perspectives by incorporating the nonfunctional goals and operationalizations into an initial functional feature model. NFR-related constraints are also elicited and integrated. Finally, a decision model with both functional and nonfunctional perspectives is constructed to facilitate application-oriented feature model customization. A computer-aided grading system (CAGS) product line is employed to demonstrate the method throughout the paper.

Non-functional requirements analysis: deficiencies in structured methods

This paper examines some deficiencies in structured systems development methods that have the effect of overlooking non-functional requirements. Evidence from four case studies shows that non-functional requirements are often overlooked, questioning users is insufficient, methodologies do not help in the elicitation of non-functional requirements and there is a lack of consensus about the meaning and utility of non-functional requirements. Some lessons are drawn from the domain of real time systems development. Finally a framework is advanced for taking a stakeholder approach to the conflict and organisational change issues associated with the elicitation stage of requirements analysis.