How to document use cases ARTICLE - Ideally use cases capture the functional requirements of a system in terms of identifiable and testable goals. The trick is writing and documenting them so that they offer value.
Threat modeling enhanced with misuse cases TIP - Misuse cases capture all the possible attacks on an application, as well as mitigation steps, helping architects, developers and testers incorporate security throughout the SDLC.
Software requirements analysis: Five use case traps to avoid TIP - Employing use cases during software requirements analysis helps you improve your chances of developing software that truly meets their needs. But there are traps you should avoid.
REFERENCE & LEARNING:1 - 1 of 1
Software requirements gathering techniques
SearchSoftwareQuality.com | 16 Feb 2007 LEARNING GUIDE - Requirements gathering can be a difficult, exhaustive process. We've assembled information on the best methods for requirements engineering in one guide.
Approaches to defining requirements within Agile teams
Submitted By: SearchSoftwareQuality.com | 24 Apr 2008 TIP - Agile development methods focus on defining "just enough" requirements detail for the next sprint. Martin Crisp explains three things to consider when eliciting those requirements.
Getting started with Web application misuse cases
Submitted By: SearchSoftwareQuality.com | 17 Apr 2008 TIP - When developing applications it isn't enough to think about how they will be used. You must also consider how they will be misused -- or abused -- so that you can prevent attacks.
Developing use cases that support business goals
02 Apr 2008 EXPERT ANSWER - Discovering use cases that account for the whole value of your project requires a meticulous approach. Expert Rob Apmann explains how to define use cases with business goals in mind.
From use case diagrams to context diagrams
SearchSoftwareQuality.com | 01 Nov 2007 ARTICLE - It's tempting to consider use case diagrams as context diagrams because they do show context. But having one diagram for both will result in an unreadable cloud of bubbles.
UML made Jacobson's use cases state of the art. What's next?
SearchSoftwareQuality.com | 08 Oct 2007 ARTICLE - Milan Kratochvil, author of UML Xtra Light, explores the future of classical system use cases, Ivar Jacobson's business use cases and user queries.
The pros and cons of use case diagrams
SearchSoftwareQuality.com | 24 Sep 2007 ARTICLE - Putting too much into a use case diagram can often render the otherwise useful technique of use cases almost useless. A more balanced and restrained approach is recommended.
That's not a user story. It's an epic!
All About Agile | 31 Jan 2008 BEST WEB LINK - When putting user stories onto a product backlog (or feature list), you shouldn't feel compelled to break everything down until the features are nearing development.
Example of a user story
All About Agile | 18 Jan 2008 BEST WEB LINK - Kelly Waters of "All About Agile" gives an example of a user story card explains what to include on it.
use case
01 Oct 2003 WORD - A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. The use case is made up of a set of possible sequences of interactions between systems and users in a particular ...
TechTarget provides enterprise IT professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective IT purchase decisions and managing their organizations' IT projects - with its network of technology-specific Web sites, events and magazines.