-
Agile software development tutorial: Agile requirements gathering
In this section of our agile development tutorial, learn tips and techniques for defining and gathering requirements in an agile environment. Tutorial
-
Top 10 software requirements tips
Developing quality software starts with the requirements process. If you fail here, your project fails. You end up with software that isn't used -- not to mention wasted time, energy, and money. These software requirements tips -- written by experts ... Fast Guide
-
Software requirements gathering techniques
Requirements gathering can be a difficult, exhaustive process. We've assembled information on the best methods for requirements engineering -- prototypes, storyboards, models, state transition diagrams and use cases -- in one guide. Learning Guide
-
Business analysis and requirements elicitation: Interview with Ellen Gottesdiener -- Part one
In part one of this two-part interview with EBG Consulting's Ellen Gottesdiener, we learn about techniques used to elicit requirements and hear about the differences between Agile and traditional requirements elicitation. News | 03 Jun 2011
-
Trends in ALM: Requirements management tools
Requirements management continues to be a challenge to software development organizations, but tool vendors are working to address those challenges. In this interview with Forrester analyst Mary Gerush, we hear about five important ALM trends in requ... News | 22 Mar 2011
-
Requirements practices evolving, but organizations still struggle
Requirements elicitation is software development teams' toughest problem today, reveals a TechTarget survey. Most teams rely on use cases and requirements management tools to get requirements right. Agile and lean development practices are also helpi... Article | 16 Nov 2009
-
From use case diagrams to context diagrams
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. Article | 01 Nov 2007
-
UML made Jacobson's use cases state of the art. What's next?
Milan Kratochvil, author of UML Xtra Light, explores the future of classical system use cases, Ivar Jacobson's business use cases and user queries. Article | 08 Oct 2007
-
The pros and cons of use case diagrams
Putting too much into a use case diagram can often render the otherwise useful technique of use cases almost useless. Kevlin Henney recommends a more balanced and restrained approach in order to not lose readers in a myriad of bubbles and microscopic... Article | 24 Sep 2007
-
How to document use cases
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 not just for requirements gathering but also for software design and tes... Article | 18 Jul 2007
-
Product management: Using social media for requirements gathering
In this tip, requirements expert Scott Sehlhorst explores the many uses of social media and social networks for improving product management. Tip
-
Estimation approaches in Agile development
In Agile environments, estimating is done using "story points." In this tip, SSQ contributor Chris McMahon describes how story points are used on Agile teams and how story size, velocity and iterations can play a part in estimating Agile efforts. Tip
-
Getting on the same page: How testers can help clarify requirements
Gathering accurate requirements is one of the biggest challenges of software development. There can be a big disconnect between what the users want and the software that gets developed. In this tip, Agile expert Lisa Crispin gives some helpful advice... Tip
-
Requirements tips for data-centric projects
Gathering requirements for data-centric projects presents a challenge. Business users may have trouble articulating the type of data needed to build a proper system and asking for changes late in the game can cause major project delays. In this tip, ... Tip
-
The perfect storm: Multiple mishaps lead to disaster
A series of mistakes, due to a series of software errors and lapses in judgment, result in a situation that could mean the difference between life and death for customers. Find out lessons that test expert Chris McMahon learned from experiencing a di... Tip
-
Change management: Change in requirements
When requirements change late in software development project things have a tendency to go wrong. Learn methods one expert uses to avoid complication when adapting a project t to meet revised requirements. Tip
-
Reliably estimating the requirements effort - Part 2
In this second part of a two-part article describing techniques to estimate the requirements effort, bottom-up estimates and requirements definition tasks are described. Accurately estimating the requirements effort will help ensure overall project s... Tip
-
Reliably estimating the software requirements effort
Differences in how business analysts and project managers define "requirements estimation" frustrate the software requirements elicitation process. No matter what methodology is in use, without adequately defining requirements, software projects are ... Tip
-
Defining report requirements with use cases
This tip offers a new and interesting way to go about defining and reporting requirements for use cases. There are a number of details that need to be attended to in defining requirements such as taking a look at users and then constructing use cases... Tip
-
How requirements use cases facilitate the SDLC
Learn software use case processes and techniques that result in better application requirements in this tip. Takeaways include use case diagrams and user acceptance test case examples. Tip
- See More: Tips on Gathering Software Requirements Use Cases
-
Requirements gathering: Using social media and collaboration tools
In this response, requirements expert Scott Sehlhorst discusses the three main uses he has identified for social media tools in the realm of requirements. Answer
-
Gathering software requirements: The importance of sequence
Does sequence matter when you are not using use cases or process modeling techniques? Expert Sue Burk explains the importance of sequence by using a typical customer service scenario as an example. Answer
-
Requirements management in the world of mobile devices and cloud computing
Do new technologies affect the requirements gathering process? In this response, expert Sue Burk delves into this question, explaining the tenets of good requirements gathering in real and virtual worlds. Answer
-
Eliciting and analyzing embedded systems requirements
Read this expert response for Sue Burk's suggestions for what techniques developers can use in embedded systems requirements gathering and analysis. Answer
-
How to overcome challenges with eliciting requirements for embedded systems
In this response, expert Sue Burk describes the importance of the relationship between hardware and software in embedded systems, and how they must be able to communicate and collaborate with each other. Answer
-
What is needed to define and fulfill software security requirements?
There are important distinctions between security requirements and security controls, as well as the expertise needed to define and satisfy each. In this expert response, Sue Burk offers a clear definition of security requirements and explanations of... Answer
-
How to define security requirements and manage risk in software development
Defining business security requirements is a collaborative effort, involving the participation of architects, business analysts and regulatory bodies. There is no black-and-white answer about achieving the best possible security for your software app... Answer
-
How to overcome the top two challenges associated with getting requirements right
Expert Sue Burk identifies the top challenges in accurately defining requirements as the challenge of involving the appropriate decision makers and subject matter experts in requirements development, and the struggle to meet the needs of both technic... Answer
-
Understanding the dependencies between requirements in a Scrum environment
Prioritizing user stories for each iteration in a Scrum environment can be challenging if the project owner does not understand the dependencies between requirements. In this expert response, Lisa Crispin shares best practices for prioritizing user s... Answer
-
How user stories help to define software requirements
User stories play an important role when defining requirements and they also contribute to living documentation during the software development process. In this expert response, Lisa Crispin offers key practices for ensuring that requirements align w... Answer
- See More: Expert Advice on Gathering Software Requirements Use Cases
-
use case
A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. Word
-
Writing Great User Stories
Writing Great User Stories Video
-
Excelling in the art and science of requirements elicitation
Eliciting software requirements is a human-intensive activity, and any process requiring user input is never a walk in the park. Learn techniques that can help project leaders make the right choices in eliciting and then analyzing requirements needs.... Podcast
-
Product management: Using social media for requirements gathering
In this tip, requirements expert Scott Sehlhorst explores the many uses of social media and social networks for improving product management. Tip
-
Requirements gathering: Using social media and collaboration tools
In this response, requirements expert Scott Sehlhorst discusses the three main uses he has identified for social media tools in the realm of requirements. Answer
-
Gathering software requirements: The importance of sequence
Does sequence matter when you are not using use cases or process modeling techniques? Expert Sue Burk explains the importance of sequence by using a typical customer service scenario as an example. Answer
-
Requirements management in the world of mobile devices and cloud computing
Do new technologies affect the requirements gathering process? In this response, expert Sue Burk delves into this question, explaining the tenets of good requirements gathering in real and virtual worlds. Answer
-
Business analysis and requirements elicitation: Interview with Ellen Gottesdiener -- Part one
In part one of this two-part interview with EBG Consulting's Ellen Gottesdiener, we learn about techniques used to elicit requirements and hear about the differences between Agile and traditional requirements elicitation. News
-
Writing Great User Stories
Writing Great User Stories Video
-
Eliciting and analyzing embedded systems requirements
Read this expert response for Sue Burk's suggestions for what techniques developers can use in embedded systems requirements gathering and analysis. Answer
-
How to overcome challenges with eliciting requirements for embedded systems
In this response, expert Sue Burk describes the importance of the relationship between hardware and software in embedded systems, and how they must be able to communicate and collaborate with each other. Answer
-
Estimation approaches in Agile development
In Agile environments, estimating is done using "story points." In this tip, SSQ contributor Chris McMahon describes how story points are used on Agile teams and how story size, velocity and iterations can play a part in estimating Agile efforts. Tip
-
What is needed to define and fulfill software security requirements?
There are important distinctions between security requirements and security controls, as well as the expertise needed to define and satisfy each. In this expert response, Sue Burk offers a clear definition of security requirements and explanations of... Answer
- See More: All on Gathering Software Requirements Use Cases
About Gathering Software Requirements Use Cases
Use cases and misuse cases are modeling tools used to document software requirements. Use cases are structured in a way in which a user story or scenario is described as a user, defined by the role he plays, performs a scenario. The story would describe what should happen when the software product is used. A misuse case, in contrast, names something that should not happen, which may lead to additional requirements that can be expressed as use cases. Misuse cases help in identifying security risks to the system.