There are many different activities that are a form of requirements gathering. So many that it can be difficult to determine which approach to use in what circumstance. By classifying requirements gathering into three different types of activities we can simplify the choices.
Flashback: A Year Ago This Week on Tyner Blain [2006-03-24]
A look back at the best from a year ago.
Don’t Make Your Products Too Simple
Joshua Ledwell wrote a short article expressing his perspective on designing software that is neither too simple nor too complex. He also links to some excellent other articles on the topic.
UML Statecharts and Documenting Business Rules
In yesterday’s article we compared use cases and UML statecharts as tools for discovering business rules. James Taylor asked a question about how we would document those rules, and then followed up my comment response with an article about business rules and RUP. In this article we move the conversation slightly forward – recognizing that we’re slowly entering the ocean of business process management.
Use Case vs. UML Statechart – Business Rules
What is the better requirements management model for capturing business rules? The use case, or the UML statechart? In this article, we explore how customer orders are submitted and processed, and contrast how use cases and statecharts expose and document business requirements and business rules.
Outside Reading: Mary and Tom Poppendieck on Lean Software Development
InfoQ has an outstanding interview with Mary and Tom Poppendieck about Lean Software Development. One of the longer interviews on the topic, and full of great content. You can watch streaming video of the interview, jump around to the answers of specific questions, or read the full transcript – great format for presenting a long form interview like this.
Use Case vs. Process Flow – Failure Handling
Should you use use cases or process flow diagrams to document business requirements? At some level, they both document the same thing, they just document it differently. The best requirements will come from doing both – but what if you are forced to choose one? What are the tradeoffs between use cases and process flows? In this article we look at the documentation of failure handling.
Flashback: A Year Ago This Week on Tyner Blain [2006-03-17]
A look back at the best from a year ago.
Explaining Agile Development…
…to your Brother-in-Law. A great article by Joe Little, on his new blog. Thanks Mishkin for telling us about it. Joe’s article serves as an excellent precursor to our comparison of agile software development methodologies. It would also be extremely effective advice for getting mindshare prior to rolling out agile […]