Paper information
Title
Requirements and Architecture: a marriage for Quality Assurance
Requirements and Architecture: a marriage for Quality Assurance
Published in
VIII Jornadas de Ingeniería del Software y Bases de Datos, Alicante, Novembre 12-14, 2003, ISBN 84-688-3836-5, pp. 69-78 - 2003
VIII Jornadas de Ingeniería del Software y Bases de Datos, Alicante, Novembre 12-14, 2003, ISBN 84-688-3836-5, pp. 69-78 - 2003
Abstract
Nowadays, software has quality as a goal over its lifecycle, from its inception to its completion. Several factors, methods and/or processes can be used to cope with this issue. Some of them assessed the quality in terms of customer satisfaction. Such approach highlights how needed the elaboration of high quality requirements specifications is. They should in turn produce systems that are more likely to perform as the stakeholders expectation. Architectural specifications act like a bridge between requirements and implementation. They provide systems models with a high abstraction level. Moreover, they allow to reason whether a system satisfies its requirements and therefore to determine the quality shown by the system. But a problem appears when the system is built because new and changed requirements may arise and the system needs to evolve. This paper sketches our work-in-progress in this field in which we are concerned about a methodology to guide the reflexive architecture development from the software requirements. This methodology also allows one to identify and define the involved aspects in the final software architecture. The intermediate software artefacts are formalized in order to validate them and achieve a highly automatic process. Additionally, software updates are easily achieved because architectures can be directly derived from the requirements, with a more expectations-centric view.
Nowadays, software has quality as a goal over its lifecycle, from its inception to its completion. Several factors, methods and/or processes can be used to cope with this issue. Some of them assessed the quality in terms of customer satisfaction. Such approach highlights how needed the elaboration of high quality requirements specifications is. They should in turn produce systems that are more likely to perform as the stakeholders expectation. Architectural specifications act like a bridge between requirements and implementation. They provide systems models with a high abstraction level. Moreover, they allow to reason whether a system satisfies its requirements and therefore to determine the quality shown by the system. But a problem appears when the system is built because new and changed requirements may arise and the system needs to evolve. This paper sketches our work-in-progress in this field in which we are concerned about a methodology to guide the reflexive architecture development from the software requirements. This methodology also allows one to identify and define the involved aspects in the final software architecture. The intermediate software artefacts are formalized in order to validate them and achieve a highly automatic process. Additionally, software updates are easily achieved because architectures can be directly derived from the requirements, with a more expectations-centric view.
BibTeX
@misc{issi_web:id:125,
title = "Requirements and Architecture: a marriage for Quality Assurance",
author = "Elena Navarro Martínez and Isidro Ramos Salavert",
booktitle = "VIII Jornadas de Ingeniería del Software y Bases de Datos, Alicante, Novembre 12-14, 2003, ISBN 84-688-3836-5, pp. 69-78",
year = "2003",
eprint = "http://issi.dsic.upv.es/publications/archives/",
url = "",
abstract = "Nowadays, software has quality as a goal over its lifecycle, from its inception to its completion. Several factors, methods and/or processes can be used to cope with this issue. Some of them assessed the quality in terms of customer satisfaction. Such approach highlights how needed the elaboration of high quality requirements specifications is. They should in turn produce systems that are more likely to perform as the stakeholders expectation.
Architectural specifications act like a bridge between requirements and implementation. They provide systems models with a high abstraction level. Moreover, they allow to reason whether a system satisfies its requirements and therefore to determine the quality shown by the system. But a problem appears when the system is built because new and changed requirements may arise and the system needs to evolve.
This paper sketches our work-in-progress in this field in which we are concerned about a methodology to guide the reflexive architecture development from the software requirements. This methodology also allows one to identify and define the involved aspects in the final software architecture. The intermediate software artefacts are formalized in order to validate them and achieve a highly automatic process. Additionally, software updates are easily achieved because architectures can be directly derived from the requirements, with a more expectations-centric view.
"
}