Knowledge
Software Requirements Management Articles, Blog Posts, Books and Quotes
UML versus Domain-Specific Languages
UML versus Domain-Specific Languages considers the two most popular starting points for code generation: * UML for program modeling, part of the OMG’s Model Driven Architecture (MDA) approach, and * Domain-Specific Languages (DSLs), little languages that are created specifically to model some problem domain.
Read More
Unstated Requirements
In every requirement document, there is at least one if not many unstated requirements. This blog post discusses that “good” or “better” solutions solve not just the stated requirements but also the “unstated requirements.”
Read More
UML or DSL: Which Bear Is Best?
This article describes the scenarios in which UML or DSLs should be used, and how each can be effectively integrated with the other.
Read More
Requirements aren’t evil, we are.
As he is responsible to create the requirements, we set the customer as the sole owner of the definition of success. Therefore, we force the burden of success onto the shoulders of the very person who has come to us, the software developer, for help. If that isn’t evil incarnate? This post is about the […]
Read More
Writing User Stories for Web Applications
This post introduces user stories as the substitute of formal requirements documents in an agile environment.
Read More
User Stories are a Reminder to Collaborate
User stories are not a highly documented series of requirements but rather a reminder to collaborate about the topic of the user story—in other words, in agile development (good agile at least), the documentation is secondary to the collaboration. Source: “New to User Stories?“, William F. Nazzaro and Charles Suscheck, ScrumAlliance.org
Read More