Welcome to the InfoSci Platform
Reference Hub1
Tracing the Implementation of Non-Functional Requirements

Tracing the Implementation of Non-Functional Requirements

Stephan Bode, Matthias Riebisch
Copyright: © 2011 |Pages: 23
ISBN13: 9781605667942|ISBN10: 1605667943|EISBN13: 9781605667959
DOI: 10.4018/978-1-60566-794-2.ch001
Cite Chapter Cite Chapter

MLA

Bode, Stephan, and Matthias Riebisch. "Tracing the Implementation of Non-Functional Requirements." Non-Functional Properties in Service Oriented Architecture: Requirements, Models and Methods, edited by Nikola Milanovic, IGI Global, 2011, pp. 1-23. https://doi.org/10.4018/978-1-60566-794-2.ch001

APA

Bode, S. & Riebisch, M. (2011). Tracing the Implementation of Non-Functional Requirements. In N. Milanovic (Ed.), Non-Functional Properties in Service Oriented Architecture: Requirements, Models and Methods (pp. 1-23). IGI Global. https://doi.org/10.4018/978-1-60566-794-2.ch001

Chicago

Bode, Stephan, and Matthias Riebisch. "Tracing the Implementation of Non-Functional Requirements." In Non-Functional Properties in Service Oriented Architecture: Requirements, Models and Methods, edited by Nikola Milanovic, 1-23. Hershey, PA: IGI Global, 2011. https://doi.org/10.4018/978-1-60566-794-2.ch001

Export Reference

Mendeley
Favorite

Abstract

A software architecture has to enable the non-functional properties, such as flexibility, scalability, or security, because they constitute the decisive factors for its design. Unfortunately, the methodical support for the implementation of non-functional requirements into software architectures is still weak; solutions are not generally established. Recently, there are only few approaches that actually deal with non-functional requirements during design; even fewer take advantage of traceability, which supports a mapping of requirements to solutions through the development process. Therefore, in this chapter the new architectural design method TraGoSoMa is presented, which supports these issues. The method uses a so-called Goal Solution Scheme, which guides the design activities, supports conflict resolution, decision-making, and the classification of solutions. For illustration purposes the chapter uses a case study from a reengineering project for a Manufacturing Execution System (MES) that is restructured according to the SOA principles and integrated with an Enterprise Resource Planning (ERP) system.

Request Access

You do not own this content. Please login to recommend this title to your institution's librarian or purchase it from the IGI Global bookstore.