Scientific Papers
ISSI Research PapersPaper information
Title
Incorporating the Model-Driven Techniques in the Requirements Engineering for Service-Oriented Development Process
Incorporating the Model-Driven Techniques in the Requirements Engineering for Service-Oriented Development Process
Grzogorz Loniewski
Published in
IFIP WG8.1 Working Conference on Method Engineering (ME 2011), Volume 351/2011, pp. 102-107, Paris, France, 20-22, 2011, DOI: 10.1007/978-3-642-19997-4_11 - 2011
IFIP WG8.1 Working Conference on Method Engineering (ME 2011), Volume 351/2011, pp. 102-107, Paris, France, 20-22, 2011, DOI: 10.1007/978-3-642-19997-4_11 - 2011
Abstract
Modern information systems, which are the result of the interconnection of systems of many organizations, run in variable contexts, and require both a lightweight approach to interoperability and the capability to actively react to changing requirements and failures. Model-Driven Development (MDD) and Service-Oriented Architecture (SOA) are software development approaches that deal with this complexity, reducing time and cost development and augmenting flexibility and interoperability. Although, requirements engineering is accepted as a critical activity in these approaches, there is a need to appropriately integrate and automate the requirements modeling and transformation tasks as part of MDD and SOA development approaches. Our proposal is a Rational Unified Process (RUP) extension, in which the requirements discipline is placed in a model-driven context in order to derive SOAs. This paper includes the definition of a model-driven requirements process including activities, roles, and work products.
Modern information systems, which are the result of the interconnection of systems of many organizations, run in variable contexts, and require both a lightweight approach to interoperability and the capability to actively react to changing requirements and failures. Model-Driven Development (MDD) and Service-Oriented Architecture (SOA) are software development approaches that deal with this complexity, reducing time and cost development and augmenting flexibility and interoperability. Although, requirements engineering is accepted as a critical activity in these approaches, there is a need to appropriately integrate and automate the requirements modeling and transformation tasks as part of MDD and SOA development approaches. Our proposal is a Rational Unified Process (RUP) extension, in which the requirements discipline is placed in a model-driven context in order to derive SOAs. This paper includes the definition of a model-driven requirements process including activities, roles, and work products.
BibTeX
@misc{issi_web:id:388,
title = "Incorporating the Model-Driven Techniques in the Requirements Engineering for Service-Oriented Development Process",
author = "Grzogorz Loniewski and Ausias Armesto and Emilio Insfrán Pelozo",
booktitle = "IFIP WG8.1 Working Conference on Method Engineering (ME 2011), Volume 351/2011, pp. 102-107, Paris, France, 20-22, 2011, DOI: 10.1007/978-3-642-19997-4_11",
year = "2011",
eprint = "http://issi.dsic.upv.es/publications/archives/",
url = "http://www.springerlink.com/content/c765qm44p44767l2/",
abstract = "Modern information systems, which are the result of the interconnection of systems of many organizations, run in variable contexts, and require both a lightweight approach to interoperability and the capability to actively react to changing requirements and failures. Model-Driven Development (MDD) and Service-Oriented Architecture (SOA) are software development approaches that deal with this complexity, reducing time and cost development and augmenting flexibility and interoperability. Although, requirements engineering is accepted as a critical activity in these approaches, there is a need to appropriately integrate and automate the requirements modeling and transformation tasks as part of MDD and SOA development approaches. Our proposal is a Rational Unified Process (RUP) extension, in which the requirements discipline is placed in a model-driven context in order to derive SOAs. This paper includes the definition of a model-driven requirements process including activities, roles, and work products."
}