Clik here to view.
Separating Business Rules From Requirements Increases Agility
We’ve written in the past about why it is important to gather and manage requirements. In short, you avoid some costly mistakes, and fix others before they become too expensive. We’ve also started...
View ArticleClik here to view.
Use Case Example With Business Rules
In our ongoing exploration of how to meld the worlds of business rules and requirements, we look at an example use case and see how to extract the business rules. Separating Business Rules From...
View ArticleClik here to view.
Business Rules Hidden in Use Cases
Business rules are not requirements. Yet they are often gathered at the same time as requirements, from the same sources, by the same business analysts. And unfortunately, often documented in the same...
View ArticleClik here to view.
10th International Business Rules Forum
The 10th International Business Rules Forum is coming up fast in October 2007. Scott Sehlhorst and James Taylor will be presenting Getting it Right. Rules and Requirements in Software on Thursday at...
View ArticleClik here to view.
Why Separate Rules from Requirements
Separation of business rules from requirements is a good thing. Not because of semantic distinctions, but because it allows you to write better software, write it faster, and change it more easily....
View ArticleClik here to view.
Elicitation Techniques for Processes, Rules, and Requirements
Each elicitation technique we have in our toolbox is a tool. But not every elicitation job is the same. If we have a hammer, we might be working with nails, or screws, or even an egg. In our analysis,...
View ArticleClik here to view.
Global Processes and Business Rules
We’ve written before about the importance of separating rules from requirements, particularly in use cases. We wrote that with the goal in mind of reducing the costs of system maintenance. Low-level...
View ArticleClik here to view.
Glossary of Terms
Some books on how to write and manage requirements mention using a glossary. Most books on requirements don’t go into enough detail about either the importance of a glossary of terms, or the precise...
View ArticleClik here to view.
Business Architecture, Rules, and Requirements
We know to treat business rules and business requirements differently. One example – treat external government regulations as rules (because they are less subject to change than requirements). When...
View ArticleClik here to view.
Hidden Business Rule Example
A business process is not just a sequence of steps. A business process is a series of decisions and actions. Some decisions are obvious and can be actively managed. Some decisions are hidden, and...
View ArticleClik here to view.
The Impact of a Hidden Decision
Business rules are often hidden in processes as hidden decisions. Once you discover that hidden decision, how do you communicate the impact of exposing and managing the decision? Hidden Decision In...
View ArticleClik here to view.
Simple Agile Model Example
A picture is worth a thousand words. Agile values working software over comprehensive documentation, and it values customer collaboration over contract negotiation. With that in mind, how much is a...
View ArticleClik here to view.
A Prototype is Worth a Thousand Lines of Code
A picture is worth a thousand words. A prototype is worth a thousand lines of code. Two key elements of product management – and of agile development are elicitation and feedback. Low fidelity...
View Article
