-
White Papers: How to protect against SQL injection and other application attacks
SQL injection is just one exploit that can be used against Web applications -- there are many lurking out there. Fortunately, there are steps you can take now to prevent SQL injection and other attacks on your applications. These two white papers des... Resource Guide
-
Top 10 Web application security vulnerabilities
Based on the Open Web Application Security Project's top 10 project, this guide covers the 10 most critical Web application security vulnerabilities and how to protect your applications. Learning Guide
-
Special Report: Securing applications -- The new frontier in security
It isn't enough to secure the physical network. Today, criminals are focusing on exploiting vulnerabilities in applications. This report, written by Jim Zimmerman from Techra LLC, looks at the top application security vulnerabilities and how to deal ... Research Report
-
Gaining access using application and operating system attacks
In this excerpt from Chapter 7 of Counter Hack Reloaded: A Step-by-Step Guide to Computer Attacks and Effective Defenses, Second Edition, authors Ed Skoudis and Tom Liston explain how security professionals can use exploit frameworks to their advanta... Book Chapter
- See More: Essential Knowledge on Software Requirements Gathering Techniques
-
Business analysis in Agile development: Q&A with Mary Gorman
How do you effectively get business requirements from the customer in Agile environments? Read this interview between Agile experts Lisa Crispin and Mary Gorman for tips. News | 18 Jul 2011
-
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
-
Business requirements and software tester collaboration with Ellen Gottesdiener -- Part two
In part two of this two-part interview, we hear more about tools and techniques in requirements elicitation and further explore the roles of tester collaboration in requirements processes. 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 in Scrum environments: Q&A with Dean Leffingwell, part 2
Dean Leffingwell, author of Agile Software Requirements – Lean Requirements Practices for Teams, Programs, and the Enterprise, believes that Scrum will continue to grow in popularity and become the organizational Agile methodology of choice. In this ... Q&A | 14 Mar 2011
-
Agile requirements: A conversation with author Dean Leffingwell, part 1
Requirements management has been said to be the most challenging part of software development. In Agile environments, changes in requirements are expected and embraced. But doesn't this wreak havoc with a schedule? Dean Leffingwell, author of Agile S... Q&A | 14 Mar 2011
-
Requirements definition getting more visual
Visualization software can make requirements easier to establish and aid developers in explaining features, but some analysts say the technology isn't quite there yet and needs some more improvements before it can become a standard. Article | 14 Jul 2010
-
Are visualizations the answer to gathering requirements?
Requirements elicitation is one of the most challenging parts of software developments. By using visualization software, business analysts are able to create working simulations to gather customer requirements. Vendors, analysts and users give their ... Article | 30 Jun 2010
-
Waters Corp. meets rigorous compliance demands with requirements management
Pharmaceutical, food industry service provider Waters Corp, boasts admiration on recent requirements additions to IBM's Rational software, which has allowed them to go paperless. Article | 23 Dec 2009
-
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
- See More: News on Software Requirements Gathering Techniques
-
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
-
Software requirements: Taking development efforts into account
In this tip, SSQ contributor Matt Heusser talks about using "desirements dialogues," which include development estimates, to help the team get the best bang for their development buck. Tip
-
Agile requirements management: Six advantages of using the cloud
The Agile Manifesto states that individuals and interactions are preferred over processes and tools. Exploring how cloud-based environments facilitate this aspect, software consultant Nari Kannan explains six advantages of using such environments for... Tip
-
Six tips for successful change management in an Agile environment
Since the idea of Agile development is to enable and encourage product or application owners to change their minds, change management in an Agile context should be smooth and natural. Here are six observations that will help an Agile practitioner alo... 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
-
Seven steps for tracking business requirements throughout a software release
In traditional software development, it can be easy for the business folks to think that their role is to define the requirements and their involvement is not needed again until UAT. However, in order to ensure requirements are implemented as expecte... Tip
-
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 requireme... Tip
-
The distinction between functional versus performance requirements
Senior test architect David Johnson describes the distinction between functional and performance requirements and the benefits from keeping these two test efforts separate. Examining differences in test investment, test ROI and risk, Johnson makes cl... Tip
-
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. Tip
- See More: Tips on Software Requirements Gathering Techniques
-
Managing requirements for cloud-based applications
In this expert response, Scott Sehlhorst examines the needs of cloud-based applications, explaining the details about updating, security and other considerations. Answer
-
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 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 Software Requirements Gathering Techniques
-
user story
A user story is a tool used in Agile development to capture a description of a software feature from an end-user perspective. Definition
-
requirements analysis (requirements engineering)
Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product... (Continued) Word
-
Wirth's Law
Wirth's Law states that computer software increases in complexity faster than does the ability of available hardware to run it... (Continued) Word
-
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
-
What are the best practices in agile
Requirements consultant Robin Goldsmith describes what the best practices in gathering requirements criteria in agile are, his answer might surprise you. Video
-
Mastering key requirements phases
Consultant Robin F. Goldsmith describes the key phases in a successful software requirements process in this audiocast interview. Podcast
-
Software requirements: Moving beyond use cases
In this podcast, software development and requirements definition expert Ellen Gottesdiener describes when use cases are a good fit for software projects, when they are not, and what alternative approaches should be used. Podcast
-
Reporter's Notebook: Jack Vaughan on agile methodology
Jack Vaughan, editor in chief of SearchSOA.com, gives his take on the evolution of agile, goals of agile, requirements gathering in agile, and the intersection of agile and service-oriented architecture. Video
-
Injection attacks -- Knowledge and prevention
SQL injection is recognized as a major threat to application security, but what about other injection attacks? SPI Dynamics' Caleb Sima dissects these exploits and offers straightforward prevention techniques in this podcast. Podcasts
-
Managing requirements for cloud-based applications
In this expert response, Scott Sehlhorst examines the needs of cloud-based applications, explaining the details about updating, security and other considerations. Answer
-
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
-
user story
A user story is a tool used in Agile development to capture a description of a software feature from an end-user perspective. Definition
-
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
-
Software requirements: Taking development efforts into account
In this tip, SSQ contributor Matt Heusser talks about using "desirements dialogues," which include development estimates, to help the team get the best bang for their development buck. Tip
-
Agile requirements management: Six advantages of using the cloud
The Agile Manifesto states that individuals and interactions are preferred over processes and tools. Exploring how cloud-based environments facilitate this aspect, software consultant Nari Kannan explains six advantages of using such environments for... Tip
-
Business analysis in Agile development: Q&A with Mary Gorman
How do you effectively get business requirements from the customer in Agile environments? Read this interview between Agile experts Lisa Crispin and Mary Gorman for tips. News
-
Six tips for successful change management in an Agile environment
Since the idea of Agile development is to enable and encourage product or application owners to change their minds, change management in an Agile context should be smooth and natural. Here are six observations that will help an Agile practitioner alo... Tip
- See More: All on Software Requirements Gathering Techniques
About Software Requirements Gathering Techniques
Software requirements engineering techniques and best practices would cover the different methods used in gathering, analyzing and documenting requirements. Business analysts may hold interviews or requirements workshops with customers to determine system requirements. Other techniques include prototyping, storyboarding, modeling and state transitions, use cases or documenting user stories. Some traditional methodologies, such as the waterfall model, promote the gathering, analysis, and documentation of all requirements before moving to the next phase of the software development cycle. In agile methodologies, requirements are considered dynamic and are reassessed with each short iteration of the development cycle.