- Software Requirements Use Cases
- Software Requirements Techniques
- Software Requirements Tools
- Building security into the SDLC
Email Alerts
-
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 today.Answer
-
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
-
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
-
Facilitating requirements gathering with Agile development expertise
Agile expert Lisa Crispin offers tips for companies to avoid “analysis paralysis” and discusses how an Agile approach changes requirements gathering and management.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
-
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
-
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
- VIEW MORE ON : Software Requirements Use Cases
-
Integrating portfolio management and requirements management tools
Scott Sehlhorst explains how requirements management tools can aid in meeting business goals and discusses what actions to take to integrate portfolio management and requirements management tools.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
-
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
-
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 today.Answer
-
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
-
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
-
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
-
Increase IT and business communication for better requirements management
Communication between business and IT is important, yet building alliances can be challenging. Agile expert Lisa Crispin offers tips and strategies.Answer
- VIEW MORE ON : Software Requirements Techniques
-
Integrating portfolio management and requirements management tools
Scott Sehlhorst explains how requirements management tools can aid in meeting business goals and discusses what actions to take to integrate portfolio management and requirements management tools.Answer
-
Critical elements of the latest requirements management tools
As requirements management becomes more of a focus, teams must examine available tools and how to make the most of them. In this expert response, Kevin Parker offers several important factors to consider when it comes to requirements management tools, including process-centricity and collaboration.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
-
worst-case execution time (WCET)
Worst-case execution time (WCET) is a software development metric that determines the maximum length of time a task or set of tasks requires on a specific hardware platform... (Continued)Definition
-
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
-
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
-
Increase IT and business communication for better requirements management
Communication between business and IT is important, yet building alliances can be challenging. Agile expert Lisa Crispin offers tips and strategies.Answer
-
Requirements management collaboration with ALM tools
Software consultant Nari Kannan writes about features needed in software tools for requirements management and provides brief summaries of software tools available, both commercial and open source.Tip
-
Generating code from software requirements: Is it possible?
Software requirements, descriptions of features that will solve a problem, are not necessarily transferable into coding languages. Requirements management expert Scott Sehlhorst explains the nature of requirements and availability of tools that generate code in this response.Answer
-
The role of the software testing manager in gathering requirements
What are the responsibilities of the product manager, business analyst, and software testing manager in requirements gathering? Learn how the roles are distributed here.Answer
- VIEW MORE ON : Software Requirements Tools
-
How traceability benefits the software development lifecycle
Read expert Scott Sehlhorst’s explanation to learn how traceability of requirements improves visibility into building the right product as well as building the product right.Answer
-
How to define security requirements and manage risk in software development
Defining business security requirements is a collaborative effort, involving the participation of architects, business analysts and regulatory bodies. There is no black-and-white answer about achieving the best possible security for your software applications. Costs and benefits must be weighed. Read this response from expert Sue Burk for more insight into how security requirements are defined and prioritized.Answer
-
Debunking myths of application lifecycle management
In this tip, we expose three myths of Application Lifecycle Management (ALM) which continue to quietly impede successful software development and delivery across industries. Understanding that best-in-class isn’t always the best option, that there is no such thing in application development as one-size-fits-all and that point-to-point integrations are not a panacea will empower DevOps and large enterprise organizations to improve the speed, quality and collaborative nature of their application delivery process.Tip
-
Requirements management with embedded software: Interview with IntraPace
What are the important considerations of a requirements management tool when developing embedded software for a medical device? In this Q&A with IntraPace software development manager Mace Volzing, SSQ asks about managing requirements for the abiliti product -- a device that is implanted in the stomach to control hunger in obese patients.News | 17 Dec 2010
-
Glitch author seeks mandated software quality controls
In Part 2 of this SSQ interview with Glitch author Jeff Papows, we learn more about Papows' proposal for an IT Governance Manifesto which would mandate higher standards of quality for life-threatening software. Papows warns of the dangers of not taking quality seriously, saying we could be on the precipice of a digital Pearl Harbor.Interview | 03 Nov 2010
-
Test design focused on expediting functional test automation
Senior test architect David Johnson describes test design paradigms such as keyword-based test design, which can be leveraged for functional test automation. Johnson addresses both commercial and open source solutions in both agile and predictive environments.Tip
-
Requirements rethinking tutorial: Improving pre-development software analysis - Part 2
An expert shows how reimagining the software requirements elicitation process can lead to improving business requirements and add value to applications. In this tip, learn how to better evaluate your requirements upfront and throughout the SDLC.Tip
-
Reliably estimating the software requirements effort
Differences in how business analysts and project managers define "requirements estimation" frustrate the software requirements elicitation process. No matter what methodology is in use, without adequately defining requirements, software projects are destined for failure says an expert.Tip
-
SQL injection
SQL injection is a type of security exploit in which the attacker adds Structured Query Language (SQL) code to a Web form input box to gain access to resources or make changes to data.Definition
-
Top software testing and quality assurance news stories from 2009
This is a collection of news coverage from 2009 on software quality and testing trends. 2009 saw more agile adoption, changes in project manager roles and new software tools.Misc
- VIEW MORE ON : Building security into the SDLC