
This paper investigates the suitability of UML as a semiformal requirements specification language. It identifies and demonstrates various problems and deficiencies of UML, particularly concerning use case models and system decomposition.
This paper investigates the suitability of UML as a semiformal requirements specification language. It identifies and demonstrates various problems and deficiencies of UML, particularly concerning use case models and system decomposition.
Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]
Read MoreThis blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.
Read MoreIn 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 MoreCopyright © 2009-2022 Martinig & Associates