We continue our exploration of UML Class Diagrams with this article that explores how to represent basic business relationships in a class diagram. Drawing these relationships can dramatically clarify requirements documents. Using a class diagram to supplement other requirements documents provides for a centralized reference that enables a shared understanding […]
Requirements / Requirements gathering / Requirements Models / UML Modeling
Posted on:
Uncovering Requirements With UML Class Diagrams Part 1
UML Class Diagrams can be used not only for documenting software design, but for documenting software requirements. One of the challenges in writing clear, unambiguous requirements is being precise about what a particular word means. This is especially true with symbolic terms like “quote” or “customer” – where everyone knows […]
Business Analysis / Prioritization / Product Management / Requirements
Posted on:
Is Your Product Improving?
Do you recognize this early logo from Amazon.com? Future Now has a great article detailing how Amazon evolved their “add to shopping cart” implementation. From reviewing this summary of the evolution of one feature, we can see that Amazon decided there was value in reinvention. The improved the way their […]
Business Analysis / Requirements / Requirements gathering
Posted on:
C.R.A.C.K. Users Are Addictive
Barry Boehm, inventor of the spiral model of software development, may also be the originator of the CRACK acronym for the type of users we want on our projects. When defining (and executing on) projects, we don’t just want CRACK users, we want CRACK stakeholders. And we want them to […]
Agile / Business Analysis / Product Management / Requirements / Requirements Models / Software development / Use Cases
Posted on:
Cockburn Affirms: Use Cases Rule for Agile!
We’ve been promoting use cases as the right way to approach agile requirements, and in a recent article, Alistair Cockburn stresses the importance of use cases. Over the last three years, he has found that teams that avoid use cases consistently run into the same three problems. We defer, of […]
Business Analysis / Product Management / Requirements / Requirements Models
Posted on:
The NICE Way To Think About Requirements
Too much information about requirements or too little? Too much documentation or too little? Use the NICE framework to get it just right.
Business Analysis / Product Management / Requirements / Requirements gathering / Requirements Models / Software requirements specification
Posted on:
SRS Plan of Attack
How do you approach starting a small requirements project as part of a large initiative within a massive enterprise? Do you boil the ocean? Your customer knows she needs “requirements” to give to her development team. She asks you – what will you deliver, and how long will it take? […]
Business Analysis / Interaction design / Prioritization / Product Management / Requirements / Requirements Models / ROI / Software development / Use Cases / UX
Posted on:
Use Case Management is a Tough Balancing Act
Learning how to write use cases can be tough, but it is simple compared to the balancing act of determining which use cases to write and how to manage the expectations of all the stakeholders that are involved. It can be a difficult balancing act to prioritize use cases to […]
Business Analysis / Product Management / Requirements gathering
Posted on:
Requirements: Knowledge and Understanding
[photo by Henkster] Writing good requirements is more than just about following a set of rules. You can capture knowledge about your goals and your product with a set of well crafted requirements. But to truly write good requirements, you have to gain a level of understanding that surpasses knowledge. […]