Use Cases can be built up by combining other use cases. When a use case is made up of other use cases, the component use cases are known as subordinate use cases. The “parent” use case is referred to as the superordinate use case. This is known as composition. See an example of how composition works for use cases.
Administrivia
Posted on:
Happy Birthday Tyner Blain!
The Tyner Blain blog is a year old today! Look back at some of our stats, including most popular posts, and a little bragging (not too much, we hope)!
Design / Interaction design / Prioritization / Requirements / Software development / Software requirements specification / UX
Posted on:
Fifteen Ways to Shut Down
There are 15 ways for someone to shutdown a laptop running Windows Vista. This adds unwarranted complexity to our software. How can we avoid the same problem in our software?
Slightly off-topic
Posted on:
Gifts for Geeks: Pre-Black Friday
Many of us who are part of the Tyner Blain community are geeks, gadget hounds, and people who read books that make you think. All of us know someone like this. Tyner Blain is a mostly-for-free site – we just ask that you remember our name, join in on the […]
Business Analysis / IIBA / Lists / Organizations / Requirements / Requirements gathering
Posted on:
Ten Requirements Gathering Techniques
The BABoK (Business Analyst Body of Knowledge) lists 10 techniques for gathering requirements. Here’s an overview of each one. For more details, check out the latest Guide to the BABoK.
Business Analysis / Requirements / Writing
Posted on:
Pairing Business Analysts
Pair programming is a bit of a foreign concept for many people in business. A few years ago, it was foreign to most programmers too. Pair programming is a powerful technique for software development because it allows two people to look at the same problem/solution from two different perspectives at the same time. Would that same approach work for business analysis?
Interaction design / Product Management / Requirements / Requirements gathering / ROI / UX
Posted on:
Gathering Implicit Requirements
Johanna Rothman just wrote an article titled Implicit Requirements are Still Requirements. She points out that her expectations were not met, even though her needs might have been. Johanna also implicitly begs the question – how do we gather implicit requirement?
Business Analysis / IIBA / Organizations
Posted on:
First IIBA Certification Exam And More
This is a bit of a potpourri post. Found some good stuff out there today, check it out. The first IIBA Exam just finished in Orlando Florida. Barbara was one of the 16 business analysts who took it. Read about her experience! Her post has inspired me to crack open […]
Interaction design / Prioritization / Product Management / Requirements / UX
Posted on:
How To Not Suck At Design
Michael Shrivathsan just wrote an article presenting five tips for creating products with great design. Michael’s List Start with the user interface. [Roger Cauvin adds, start with a working first iteration] Work closely with UI designers. Pay attention to details. Simpler is better. Be brave. Our Thoughts User centric design […]