ABOUT THE AUTHOR

Arjen Spaans

During my time in the Technical University of Munich (TUM), I got in touch with Qualicen GmbH. My passion for high quality work, helping people and Software Engineering quickly aligned with the core values of the company. It was inevitable that after my graduation I would work for Qualicen. Now as a Consultant at Qualicen I work directly on those topics that are close to my heart, such as Software Engineering and Requirements Engineering. These are large - and often heavily debated - topics that capture my personal interest and passion. Currently I focus my research efforts on Model-Based System Engineering. My goal is to keep learning and exploring.

A Gentle Introduction Of A Requirement Syntax

Requirement documentation is mainly done in either Natural Language (NL) or in formal models like UML or SysML. NL offers the lowest learning curve and the most flexibility, which for many companies means: “Everyone can start writing requirements without formal training”.

In contrast, formal modelling languages require a considerable effort to learn and are very restrictive. But, the flexibility of NL comes with ambiguity and inconsistency. These are two major downsides that formal modeling languages aim to eliminate.

Our customers often ask: “Is there something in the middle, keeping the benefits of NL, but reducing the downsides?” our answer: “Yes, a requirement syntax”.

But what has that children’s puzzle to do with writing requirements?

 

Continue reading A Gentle Introduction Of A Requirement Syntax