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 use of the glossary of terms. Or if they do, they under-emphasize the benefits of a well-defined glossary of terms. Walking a day in the moccasins of a business rules analyst helps us all appreciate the importance of a well-managed glossary of terms.
Archive of Data management Articles
(6 votes, average: 5 out of 5)
Loading ...October 29th, 2007
Glossary of Terms
(4 votes, average: 5 out of 5) Loading ...July 10th, 2007
Business Rules And Requirements - Early Thoughts
We had a great interview with James Taylor a couple weeks ago, where we talked about his new book, Smart (Enough) Systems.
James is an expert on decision management systems. I spent the late 1990s working on “rules-centric” software systems that allowed us to isolate rules and manage them seperately from other software requirements.
Traditional structured requirements approaches focus on the gathering and management of software requirements, but they gloss over the gathering and management of business rules.
James and I are exploring the best ways to bring these two points of view together.
Add Tyner Blain to Google Toolbar
