Email Alerts
-
Collaboration in Agile development: Requirements analysis is a team effort
SSQ Site Editor Yvette Francino talks to experts Sue Burk and Janet Gregory about tester involvement in requirements analysis. Feature
-
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
-
Forrester VP says enterprise mobile applications miss the mark
Building an enterprise mobile application may not be the right focus for today's enterprise application development teams. Tip
-
A five-step plan to capturing better application requirements
Defining software application requirements at a project's outset is still an issue. Learn how to build better application requirements. Tip
-
Health care applications: Is Agile compatible with FDA regulations?
Using the following strategies, FDA regulations can be assimilated into an Agile environment to meet the compliance needs of health care applications. Tip
-
Managing requirements as production applications scale
Learn how to go about managing requirements as production applications scale. Tip
-
Requirements review in Agile: Ensuring consistency and spotting defects
Agile testing teams can improve their requirements review process by ensuring consistency, carefully determining testability and spotting missing connections. Tip
-
Just-in-time requirements gathering with iterative development
Consultant Howard Deiner shows us how iterative development allows software teams to get just-in-time requirements, preventing wasted time on over-analysis and allowing for mid-course corrections along the way. Tip
-
Contextual inquiry techniques in requirements gathering
Software consultant Nari Kannan writes about typical problems with requirements gathering and provides an outline of contextual inquiry techniques. Tip
-
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
- See more Tips on Gathering Software Requirements Use Cases
-
Who should drive Agile planning and software requirements analysis?
Many application testers wonder who exactly is responsible for driving software requirements analysis and planning to ensure high-quality software. Answer
-
How do we define user experience design requirements for mobile apps?
User experience design is a huge part of building successful mobile applications. Gathering requirements for UX design is a must. Answer
-
Convince executives to be a part of writing business requirements
To get requirements gathering right, reluctant executives have to be convinced to take part in the process of writing business requirements. Answer
-
Managing requirements with multiple stakeholders: A balancing act
Managing requirements with multiple stakeholders requires product managers to resolve conflicts and carefully weigh priorities. Answer
-
How project sponsors can successfully manage changes to requirements
Expert Scott Sehlhorst explores the questions managers must ask and explains how project sponsors can keep projects on track following changes to requirements. Answer
-
Requirements gathering and ALM: How to improve the process
More and more organizations are looking for ways to improve their requirements gathering and management processes, according to expert Kevin Parker. Answer
-
What is the link between test cases and requirements?
Expert Pete Walen describes the intricacies of the relationship between requirements and test cases, explaining how the context and the realities of the requirements make a difference in how test cases are produced. Answer
-
The role of software testers in requirements gathering
Testers play an important role in determining requirements, according to expert Pete Walen. He explains how throughout the project lifecycle, testers must ask questions that can help generate the discussion needed to avoid problems down the line. Answer
-
New techniques for requirements gathering in an Agile environment
Agile development practices have changed requirements gathering into a more “continuous” process rather than a step that is completed prior to beginning a project, according to expert Scott Sehlhorst. Answer
-
Three forms of communication essential to requirements management
Teams can produce a higher quality product when goals are aligned around meeting requirements. Expert Scott Sehlhorst discusses the three forms of collaboration that facilitate the requirements gathering and management process within organizations to... Answer
- See more Expert Advice on Gathering Software Requirements Use Cases
-
use case diagram
A use case diagram is a graphic depiction of the interactions among the elements of a system. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. Definition
-
use case
A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. Definition
-
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
-
Who should drive Agile planning and software requirements analysis?
Many application testers wonder who exactly is responsible for driving software requirements analysis and planning to ensure high-quality software. Answer
-
Forrester VP says enterprise mobile applications miss the mark
Building an enterprise mobile application may not be the right focus for today's enterprise application development teams. Tip
-
use case diagram
A use case diagram is a graphic depiction of the interactions among the elements of a system. A use case is a methodology used in system analysis to identify, clarify, and organize system requirements. Definition
-
How do we define user experience design requirements for mobile apps?
User experience design is a huge part of building successful mobile applications. Gathering requirements for UX design is a must. Answer
-
Convince executives to be a part of writing business requirements
To get requirements gathering right, reluctant executives have to be convinced to take part in the process of writing business requirements. Answer
-
A five-step plan to capturing better application requirements
Defining software application requirements at a project's outset is still an issue. Learn how to build better application requirements. Tip
-
Health care applications: Is Agile compatible with FDA regulations?
Using the following strategies, FDA regulations can be assimilated into an Agile environment to meet the compliance needs of health care applications. Tip
-
Managing requirements as production applications scale
Learn how to go about managing requirements as production applications scale. Tip
-
Managing requirements with multiple stakeholders: A balancing act
Managing requirements with multiple stakeholders requires product managers to resolve conflicts and carefully weigh priorities. Answer
-
How project sponsors can successfully manage changes to requirements
Expert Scott Sehlhorst explores the questions managers must ask and explains how project sponsors can keep projects on track following changes to requirements. 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.