The IRMA Community
Newsletters
Research IRM
Click a keyword to search titles using our InfoSci-OnDemand powered search:
|
Tracing the Implementation of Non-Functional Requirements
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.
Related Content
|
Sureyya Yigit.
© 2025.
32 pages.
|
|
Özden Sevgi Akıncı.
© 2025.
28 pages.
|
|
Öznur Taşdöken.
© 2025.
38 pages.
|
|
Fatih Ceylan, Birol Erkan.
© 2025.
24 pages.
|
|
Ezgi Kopuk, Hasan Umutlu.
© 2025.
34 pages.
|
|
Ozlem Inanc.
© 2025.
28 pages.
|
|
Burcu Savaş Çelik.
© 2025.
22 pages.
|
|
|