Cascade: Q&A with David Wright
Cascade: Better practices for effective delivery of information systems in a multi-project environment.
Read Moreby JB | Oct 1, 2009 | Books & Literature | 2 |
Cascade: Better practices for effective delivery of information systems in a multi-project environment.
Read Moreby JB | Aug 18, 2009 | Link Share | 1 |
Alex Papworth has released a free e-book for new and prospective business analysts, entitled Blueprint for Success as a New Business Analyst.
Read Moreby JB | Jun 29, 2009 | Requirements | 4 |
Great book on modeling & systems analysis and yet another critique of “big, thick documents.”
Read Moreby JB | Sep 10, 2008 | Methodology | 2 |
That it’s required doesn’t mean that it adds value.
Read Moreby JB | May 21, 2008 | Requirements | 1 |
A few thoughts on identifying use case actors and a job-aid that may help simplify the effort.
Read Moreby JB | Jan 22, 2008 | Requirements | 3 |
Use cases are atomic functions that are portable and not dependent upon a certain situation. They are requirement “objects” in the “object oriented” sense. I think that modularity and “reusability” are among the most valuable aspects of using use cases to express requirements.
This modularity can be undermined, though, if we allow our use cases to get too far into specifics and implementation detail.
The book “Use Cases: Requirements in Context”, by Kulak and Guiney, provides us with a couple simple ways to self-check our use cases to ensure that they include the appropriate level of detail, but aren’t reaching too far into design.
Read More