Requirements analysts often play the role of translator. They listen to, understand, and document the needs of system users in the users’ natural language and
Use cases are an indispensible tool for capturing the behavioral requirements of a software product and many analysts employ them exclusively for that purpose. But
We often spend the majority of our modeling time on use cases, process flow diagrams, and other tools that model behavior. These behavior models are
One of the most common mistakes made by software development teams and others in thinking about software is the confusion between the concept of software
As requirements consultants we sometimes find ourselves working with people who have learned through painful experience that requirements are not fun. We like to think
For Agile development teams, there are three key modeling concepts that are critical for successful requirements modeling. First, create model artifacts “just in time” and
Last month I wrote about Agile Requirements and a concept called GRIT or Great Requirements in Total. The idea behind GRIT is that it is
One of the quickest ways to improve your requirements documentation is to have someone else review your work and provide feedback. Of course, the flip
Any sizeable collection of use cases will have relationships between use cases that can be modeled using the UML includes and extends stereotypes. Used properly
The first principal of agile software development is that the highest priority is to satisfy the customer through early and continuous delivery of valuable software.
Reliability is an important non-functional requirement for most software products so a software requirements specification (SRS) should contain a reliability requirement, and most do. But,
One of the challenges faced by requirements analysts is the need to communicate the complex behavior of systems in an understandable yet rigorous and verifiable
Generate and convert leads, increase revenue through ecommerce, and cut costs by automating operations.