Gathering Software Requirements Use Cases
Top Stories
-
Answer
13 Apr 2023
How to write a business requirements document in Agile
An Agile software team shouldn't rely on rigid processes or a control board to get the job done, but it still needs to make business requirements a central focus. Enter the BRD. Continue Reading
-
Tip
25 Feb 2022
Where requirements-based tests fit in software testing
Requirements-based testing has its upsides and downsides, and it's not right for every software project. But certain dev teams should still adopt the method. Learn which ones. Continue Reading
-
Feature
12 Mar 2018
Enterprise AR apps call for strong use cases, requirements
Developers, hone your AR app pitches with these tips on building use cases and requirements. Get ready, because augmented tools are ready for enterprise prime time. Continue Reading
-
Guide
08 Jun 2016
Want satisfaction guaranteed? Add user experience to the design process
UI and UX are set to change nearly everything about application design, development and testing. Get expert advice on this new user experience design process. Continue Reading
-
Answer
16 Jan 2015
Test software with persona-based requirements
Do persona-based requirements make it easier to test software? Learn if there are tools designed to make testing software easier. Continue Reading
-
Answer
06 Oct 2014
Is Agile requirement gathering that different from waterfall?
Does moving to Agile development eliminate up-front requirements gathering? Does it mean the development team takes responsibility for requirements instead of the business side? Continue Reading
-
Tip
18 Jul 2014
CI success depends on quality acceptance criteria
Successful continuous integration requires testable acceptance criteria that help to guide developers. Continue Reading
-
Answer
30 Mar 2011
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 stories based on requirement dependencies. Continue Reading
-
Answer
28 Mar 2011
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 with user stories and that user stories are accurate. Continue Reading
-
Answer
28 Mar 2011
Mapping software requirements to test cases
Even though you must have at least one test case per requirement, it's possible not to have a one-to-one mapping between each requirement and test case. In this response, expert Sue Burk explains how it is important to trace the relationship between requirements and the tests that verify them whether the relationship is one-to-one, one-to-many or many-to-many. Continue Reading
-
Answer
23 Mar 2011
Tracking changes to requirements in Agile development
All development teams need to track requirements changes, but depending on the software development lifecycle and overall ALM process, the best approach to change tracking may not be the same across the board. In this response, expert Mike Jones explains how Agile teams can best integrate change tracking into their development process. Continue Reading
-
Answer
29 Dec 2010
Functional requirements and nonfunctional requirements in software engineering explained
Clearly defining both functional and nonfunctional requirements in software engineering projects is important from both a business perspective and a performance perspective. In this expert response, Sue Burk offers definitions and examples for both functional requirements and nonfunctional requirements. Continue Reading
-
Tip
10 Sep 2009
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. Continue Reading
-
Tip
09 Sep 2009
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. Continue Reading
-
Answer
23 Jun 2009
Differentiating between Functional and Nonfunctional Requirements
Many of the difficulties encountered in defining requirements relate to the functional-nonfunctional distinction. As so often happens, some of those difficulties are things of which people are aware, largely realizing after-the-fact that nonfunctional requirements were missed. Continue Reading
-
Tip
22 Jan 2009
How to avoid requirements creep
Despite all the attention placed on defining requirements, creep continues to plague software projects. Learn how a different approach to requirements can curtail that creep. Continue Reading
-
Answer
21 Jan 2009
Template for requirements use cases
A user is looking for a template for writing requirements use cases. Robin Goldsmith walks through a few interpretations of this question. Continue Reading
-
Tutorial
14 Oct 2008
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 such as Karl E. Wiegers, Ellen Gottesdiener, Roxanne Miller, and Martin Crisp -- can help you prevent that. Continue Reading
-
Answer
06 Oct 2008
Use cases and SRS for requirements gathering
Before comparing use cases and software requirements specifications, you should know what each is. Requirements expert Robin Goldsmith explains how use cases and SRS work and how to use them for requirements engineering. Continue Reading
-
Answer
26 Aug 2008
Use cases: Who writes them, what data do you include?
Typically a business analyst writes the use cases for a software project. But who writes them doesn't matter as much as what is included in them, says expert Robin Goldsmith. Continue Reading
-
News
24 Sep 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 text. Continue Reading
-
Tip
24 Apr 2007
How to document system, software requirements
There are various formats you can use to document system and software requirements. However, no single one is sufficient to represent all requirements. You need to follow an integrated approach. Continue Reading
-
Answer
09 Apr 2007
Clarifying software requirements
Software requirements engineering is impeded by unclear, indeterminate requirements. Expert Karl E. Wiegers explains how analysts can clarify requirements with users. Continue Reading
-
Tutorial
15 Feb 2007
A template for 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. Continue Reading