Software Requirements Gathering Techniques
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
-
Answer
05 Jan 2021
How to elicit performance requirements
Eliciting performance requirements from business end users necessitates a clearly defined scope and the right set of questions. Expert Mary Gorman explains how to effectively gather information. Continue Reading
-
Answer
09 Dec 2020
What are the types of requirements in software engineering?
Requirements fall into three categories: business, user and software. See examples of each one, as well as what constitutes functional and nonfunctional kinds of software requirements. Continue Reading
-
Answer
30 Sep 2020
Functional vs. nonfunctional requirements in software engineering
Learn the meaning of functional vs. nonfunctional requirements in software engineering, with helpful examples. Then, see how to write both and build a product that users will love. Continue Reading
-
Answer
06 May 2020
The risks and effects of spyware
Spyware can steal mundane information, track a user's every move and everything in between. Read up on the types of spyware and how to best fix infected devices. Continue Reading
-
Feature
12 Dec 2019
How software prototyping beats requirements gathering
How do you know which features to code into the software you're developing? Application teams share tips on how to deliver ROI with prototyping, UX research and a design week. Continue Reading
-
Tip
23 Oct 2019
10 tips for effective change management in Agile
Agile development encourages product owners to address customer needs through change. Follow these 10 tips for change requests and management practices that keep projects on track. 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
-
Answer
17 Jan 2018
What skills do Agile testers need?
The Agile team collaborates closely and makes a lot of changes. What does the ideal Agile tester possess in technical and people skills? Continue Reading
-
Feature
02 Nov 2016
Use elicitation techniques to discover software requirements
Discovering project requirements can be challenging. An expert offers elicitation techniques you can use to discover business and software requirements. 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
15 Jan 2015
How QA testers participate in the requirements definition process
Learn how QA testers should participate in the requirements definition process in this expert response. Continue Reading
-
Answer
29 Mar 2013
A well-developed software requirements specification is easy to test
SearchSoftwareQuality expert Scott Sehlhorst discusses how to avoid writing a software requirements specification that is too vague to be tested. 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
12 Oct 2010
What is a test case? What is a requirement?
After exploring the definition of a test case by surveying test experts, authors and students, consultant Robin Goldsmith learns that interpretations remain ambiguous and varied. Similarly, the level of detail thought to be needed to define requirements can vary and can often drive the level of detail of the test efforts. Continue Reading
-
Tip
22 Sep 2010
Inadequate requirements and what to do about them
Software requirements are often subjective and poorly written resulting in inadequate requirements documentation. In this tip, QA Director John Scarpino describes some of the reasons behind poor requirements and ways that this can be addressed. 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
20 Aug 2009
How to deliver software with an SDLC iterative model
The phases of iterative SDLCs come together to build better software applications faster, as long as the team avoids some common development and planning mistakes. 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
-
Tip
21 Jan 2009
Making requirements walkthroughs more effective (and fun)
Do you have to twist arms to get people to attend your requirements review sessions? It doesn't have to be this way. Learn how to use a simulation model to get everyone engaged in the walkthrough. 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
-
Tip
22 Dec 2008
Using proactive test design methods to catch requirements issues early
Proactive test design allows QA testers to identify requirements and design problems at an earlier stage than with traditional test cases. Continue Reading
-
Answer
16 Dec 2008
Is a requirements freeze in a software project a bad idea?
Learn why imposing a requirements freeze in an application project is usually a misguided idea. Continue Reading
-
Answer
21 Oct 2008
Elicit software requirements using a variety of techniques
Software requirements elicitation can be challenging, but you can achieve success if you have strong personal skills and use a variety of techniques, says expert Ken Willett. 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
27 Aug 2008
How to estimate change requests in requirements
Software requirements are often subject to change; using a sound estimation process helps greatly to manage change. Requirements expert Betty Luedke explains, in detail, how to implement good estimation techniques. 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
-
Answer
25 Mar 2008
Testability requirements and verification work
Testability and verifiability are a category of nonfunctional requirements. Expert Roxanne Miller explains how these concepts fit into software requirements engineering. Continue Reading
-
Answer
21 Jan 2008
Requirements gathering for payroll application
Engineering requirements for a payroll or similar application demands careful consideration. Expert Rob Apmann explains how to approach this complicated task. Continue Reading
-
Tip
21 Jan 2008
Testers' involvement in requirements gathering important
In this increasingly complex software development era, it is important to include testing as early in the project as possible. And that means starting with requirements gathering. 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
-
Answer
06 Aug 2007
Software requirements specification and IEEE standards
What does the IEEE outline for requirements specifications, and how strictly should you abide by that standard? Expert Karl E. Wiegers digs into the details of an SRS. 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
-
Tip
27 Feb 2007
Software requirements: Using models to understand users' needs
Successful software projects involve users early and often to explore and reach closure on requirements. Using analysis models you can depict user needs with a combination of diagrams and structure text such as tables or templated text. 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
-
News
23 Feb 2006
HTTP response splitting is [still] mostly harmful
Recently, several anti- HTTP response splitting strategies has been suggested and/or put to use by various individuals and vendors. Unfortunately, they don't follow recommended guidelines. Amit Klein sets the record straight and details what techniques and methodologies should be used in this paper. Continue Reading
-
News
13 Feb 2006
Effects of domain hijacking can linger
Malicious hackers who are able to hijack an organization's Web domain may be able to steal traffic from the legitimate Web site long after the domain has been restored to its owner, according to a recent report from the Web Application Security Consortium. Continue Reading