RSSAll Entries Tagged With: "books"

“Cascade”: Q&A with David Wright

“Cascade”: Q&A with David Wright

Cascade: Better practices for effective delivery of information systems in a multi-project environment.

Business Analyst “Blueprint for Success”

Business Analyst “Blueprint for Success”

Alex Papworth has released a free e-book for new and prospective business analysts, entitled Blueprint for Success as a New Business Analyst.

Structured Analysis & Big, Thick Documents

Structured Analysis & Big, Thick Documents

Great book on modeling & systems analysis and yet another critique of “big, thick documents.”

Does Your Paperwork Add Value?

Does Your Paperwork Add Value?

That it’s required doesn’t mean that it adds value.

Quick Tip to Help Identify Use Case Actors

Quick Tip to Help Identify Use Case Actors

A few thoughts on identifying use case actors and a job-aid that may help simplify the effort.

A Couple Tips on Keeping Use Cases Simple

A Couple Tips on Keeping Use Cases Simple

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.