Why do we write use cases? We write use cases for the same reasons that people use our software – to achieve goals. In our case, we want to assure that we are creating the right software. By looking at this high level goal in
In our article, The 8 Goals of Use Cases, the first goal is that our use cases must support requirement-completeness validation. In this article, we explore how to address this goal and how use cases can help. There are many pieces to this puzzle, and
One of the ten big rules of writing a good MRD is writing complete requirements. We identify problems and opportunities in the market. We determine that one of these problems is valuable enough and practical to implement. Then we have to write the requirements, and
Pragmatic Marketing has a training seminar called Requirements That Work. In support of that, they provide a list of 8 characteristics of good requirements. We change one and add two more to round it out to The Big Ten Rules. Combine this with Michael’s ten
Introduction Alistair Cockburn opened my eyes to the essence, elegance and effectiveness of use case preconditions. In [1], he discusses preconditions in just a dozen paragraphs, but these contain two statements that revolutionized my understanding of preconditions and their counterpart, postconditions. This article starts with
Agile teams typically differentiate between “epics” and “user stories.” In most cases epics are just really large stories that sit far down on your product backlog until the team is ready to flesh them out into more detail. The logical question is how to scope
I’ve been getting more and more emails lately from people confused about the difference between “user stories”, “epics” and “themes.” So I thought this month we’d return and cover some basic–but very helpful–territory by explaining those terms. moreFirst, the terms don’t matter that much. These
Are you working on your first project as a business analyst? Have you ever wondered exactly what requirements documents a business analyst creates for review by the business and technical teams? While the requirements documents created for any specific project will heavily depend on the
Facilitation and Elicitation Techniques Introduction Requirements elicitation and facilitation skills are the cornerstone of the business analysis practice. Having accurate requirements is critical to effectively manage application development, business improvements or responses to current (changing) business conditions. As described in Section X of the guidebook,
An Overview of Requirements Elicitation Featured 60219 Views 8 Comments 27 Likes What is Elicitation? A thorough discovery of business requirements is almost never readily available at an analyst’s fingertips—rarely can requirements be quickly looked up as one would gather information for a
