Non-Functional Requirements in the Context of SOA

Requirements Management Articles

This article presents new concepts to formalize and apply non-functional requirements (NFR) for business processes in the context of Service-Oriented Architectures (SOA). Today, popular languages for modeling business processes do not support the specification of NFRs in a systematic manner. However, there is a strong demand to explicitly address such requirements when designing and deploying software systems.

This articles presents an extension for BPMN (Business Process Model and Notation) towards the modeling of NFRs. A key feature is the tool independent representation of NFRs, which will be achieved by applying the widely used WS-Policy standard. Our approach also covers the mapping of the specified NFRs to the technical level represented by BPEL (Business Process Execution Language). For the monitoring of NFRs we exploit techniques from Complex Event Processing (CEP). A key characteristic of our solution is its coherence: from NFRs modeling at design level to their technical enforcement and dynamic validation during execution. The feasibility of our approach has been demonstrated by a proof of concept implementation based on NetBeans, Glassfish ESB, IEP as CEP implementation, and the BPEL Service Engine.

Requirements Management Blogs
Blogs Knowledge

Find Missing Requirements

This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.

Read More
Requirements Management Blogs
Blogs Knowledge

Perfect Requirements

In this blog post, James Christie starts from the fact that perfect requirements don’t exist to discuss the idea that the quality of requirements is directly influenced by the time and money you invest in crafting them.

Read More
Requirements Management Blogs
Blogs Knowledge

Why Should You Write Requirements

In this blog post, By Scott Sehlhorst starts with a simple fact: if there is a lot of discussions on how to write requirements, there is not so much material on why to write requirements. His advice is that you should start by thinking about why you write requirements before you decide how to write […]

Read More

Copyright © 2009-2022 Martinig & Associates