top of page

The case for Semantic Alignment with Requirements

Updated: Apr 11, 2019

Business analysts might want to become more familiar with the need for semantic alignment around requirements since to ensure their perspectives around requirements are not isolated from knowledge.   Folks who are starting to map out the future direction around knowledge management will embrace the the outcome driven data captured from customer focus studies. Needs, wants and desires are not easily aligned or mapped into requirements engineering frameworks, which results in redundant and often conflicting priorities, designs and sub-optimal products and services.  The outcome driven approach (promoted by Strategyn) for capturing cu

stomer needs helps ensure the requirements address the 4 Cs for modeling customer needs properly:

  • Clarity                   =  Clear and unambiguous

  • Completeness    =  No missing pieces

  • Correctness        =  Accurate capture of information

  • Centered         

    =  Focused information (“around a job”)

Once needs are captured using consistent semantics, they can be mined for patterns, reused and repurposed for new and/or existing products and services.

Recent Posts

See All


bottom of page