Search:

ProjectConnections Print View


Got a Question?
Drop us an email, or call us toll free:
888-722-5235
7am-5pm Pacific
Monday - Friday
We'd love to talk to you.


Learn more about ProjectConnections and who writes our content. Want to learn more? Take a site tour and compare our membership levels.


Are there times when a use case just isn't the right answer?

I've been asked to help capture the requirements for our project, and I'm thinking about using use cases. It seems like the best strategy for us, but are there times when use cases aren't the best way to capture requirements?
Use cases are a wonderfully practical way to present high-level contextual information. They're also one of the best ways to document the requirements when you want to capture functionality related to the details about user/system interactions. They're easy to create and use, they're versatile, and they blend visual and narrative elements in a way that most audiences will enjoy and understand. But use cases aren't necessarily the be-all end-all of requirements capture.…

Log in or Subscribe now to read the full answer...

This resource requires a Premium Subscription
Please log in. Don't have a log-in? Sign up now. Already a Member? Log in to upgrade immediately and get the full answer! A Premium subscription is only $14.95/month or $149/year and gets you over 200 templates, guidelines, and checklists.
15-day free trial period for new Premium subscribers! Learn more
Username:

Password:












©Copyright 2000-2012 Emprend, Inc. All Rights Reserved.
About us   Site Map   View current sponsorship opportunities (PDF)
Contact us for more information or e-mail info@projectconnections.com
Terms of Service and Privacy Policy