Email Alerts
-
Software requirements development: FAQ
This FAQ tells how to get business execs engaged in software requirements development -- and how to avoid vague requirements and unnecessary features. FAQ
-
Writing requirements: Common sense measures for success
Experts offer simple, common sense measures for writing requirements that deliver software that's better for the business. Feature
-
Release manager on software rollout: Let business goals drive code changes
An experienced release manager offers advice on software rollouts: Let business goals and tight controls drive code changes. Feature
-
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
-
Requirements gathering: Collaborative approaches for software teams
Agile expert Lisa Crispin shares real-world examples of ways teams can collaborate, creating a shared understanding between business and customers and IT development teams. 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
-
Web application security and the PCI DSS
Software security should be integrated into the software development lifecycle at every phase. While the PCI DSS doesn't account for all of this, here are some tips to get you started on a holistic approach toward security. Learning Guide
-
How to capture performance requirements -- Expert Webcast
In this webcast Paul R. Reed explains how to elicit specific and measurable performance requirements and how to get stakeholders to agree on them. Webcast
-
Where do requirements models fit in the project lifecycle?
Modeling should not be considered something that's done only after requirements have been gathered. Use them throughout the requirements process to elicit and clarify requirements. Special Report
- 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
-
Agile process: Structured conversations build business-ready software
Teams committed to the Agile process are good at delivering working software. But what good is that if the software doesn't meet business needs? Tip
-
Software lifecycle: Defining just-in-time requirements
SearchSoftwareQuality expert Matt Heusser explains how to increase software lifecycle efficiency by defining the right requirements just in time. 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
-
Acceptance test-driven development explained
Acceptance test driven development brings developers, testers and business together to sort out bugs before coding starts, according to a new book. Tip
-
Requirements shifting with enterprization of mobile apps
The enterprization of mobile apps is affecting design, performance and security requirements. Find out how to manage these requirement changes. 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
-
Optimizing requirements management: Working with Agile and Waterfall
Learn what can teams do to optimize requirements management when working within both Agile and Waterfall. 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
- See more Tips on Software Requirements Gathering Techniques
-
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
-
Mobile apps: Devising software requirement specifications
Expert Scott Sehlhorst identifies three mobile app types and explains the unique challenges each poses around software requirement specifications. Answer
-
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. 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
-
Social media surveys: A tool for better requirements?
Social media surveys make it easier to conduct conversations with experts to help define requirements for software development projects. Answer
-
Requirements definition: Get developers involved early
It pays for business analysts to engage developers early in the requirements definition process -- better communication means better requirements. Answer
-
Requirements management process: Security and application performance
Organizations need to explicitly address security and application performance during the requirements management process according to expert Dan Cornell. Answer
-
Do business stakeholders lose requirements ownership in Agile?
The iterative nature of Agile means that requirements must be revisited frequently, which changes the dynamic amongst business stakeholders. Answer
-
Gathering project requirements up front in Agile
While many people believe Agile development eliminates the need for gathering project requirements up front, that idea is misleading. Answer
- See more Expert Advice on Software Requirements Gathering Techniques
-
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
-
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) Definition
-
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) Definition
-
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
-
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
-
Agile process: Structured conversations build business-ready software
Teams committed to the Agile process are good at delivering working software. But what good is that if the software doesn't meet business needs? Tip
-
Software lifecycle: Defining just-in-time requirements
SearchSoftwareQuality expert Matt Heusser explains how to increase software lifecycle efficiency by defining the right requirements just in time. Tip
-
Mobile apps: Devising software requirement specifications
Expert Scott Sehlhorst identifies three mobile app types and explains the unique challenges each poses around software requirement specifications. Answer
-
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. Answer
-
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
-
Software requirements development: FAQ
This FAQ tells how to get business execs engaged in software requirements development -- and how to avoid vague requirements and unnecessary features. FAQ
-
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
-
Writing requirements: Common sense measures for success
Experts offer simple, common sense measures for writing requirements that deliver software that's better for the business. Feature
- 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.