-
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
-
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
-
Get to know your business analysts
How well do you know the business analysts in your organization? Business analysts, or BAs, fill varied roles at companies of all sizes. This career field has been expanding steadily for the past few years, as indicated by this and past Forrester res... News | 07 Mar 2011
-
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... News | 17 Dec 2010
-
ALM boundaries are expanding in application development
ALM vendor trends and customer needs have led to an expansion in what constitutes Application Lifecycle Management. Vendors like HP, IBM and Microsoft continue to offer their customers more ALM solutions, broadening the scope beyond the software deve... Article | 08 Feb 2010
-
IBM strengthens ALM line, as Micro Focus buys competitors Borland, part of Compuware
Application lifecycle management (ALM) heated up with announcements of IBM's new ALM product and enhancements and the acquisition of Borland and some Compuware assets this week. Article | 07 May 2009
-
Software development lifecycle (SDLC) trends 2009: Requirements, agile
Read expert predictions on what's in store this year for software development lifecycle practices and who will best weather the economic storm. Article | 05 Jan 2009
-
Business requirements drive Compuware's new application delivery management tools
With its new Compuware Optimal and Optimal Delivery Manager, Compuware makes business requirements the basis of software development and gives IT managers a clear view into the development and delivery of applications. Article | 06 Jun 2007
-
Effective prototyping for quality software
The authors of "Effective Prototyping for Software Makers" discuss the benefits of prototyping, how anyone can create a helpful prototype, and how the software development process is affected by the use of prototypes. Article | 21 Mar 2007
-
Strategies for scaling Agile beyond simple code-and-deploy environments
In this tip, consultant Michael Kelly shares some models and strategies that will help teams stay Agile as projects grow. Tip
-
Adopting Agile: Eight traction tips to make Agile development stick
Agile transition isn't easy. The tendency may be to revert back to traditional methods once the going gets tough, though experts encourage organizations to stick with it. In this tip, we learn eight tips for Agile traction recommended by Howard Deine... 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
-
Optimizing your mobile website for all devices
When your Web application goes mobile, your users may see some strange results if you’re not careful. In this tip, consultant Judith Myerson discusses four strategies that will help you make sure your Web application is optimized for use on mobile de... Tip
-
Extending ALM to deployment
Application lifecycle management is not done with code complete. ALM now includes involving the operations team with release management processes and tools. ALM is more than automating the software development process; it’s also about delivering the ... Tip
-
Eleven steps to kickoff application lifecycle management
Regardless of the methodology or process that your organization uses, it's important that you define your application lifecycle. Director of QA John Scarpino shares 11 important steps you can follow to ensure you carry out application lifecycle manag... 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
-
Five crucial steps for software leaders to establish vision
Projects led by unorganized project managers are easily stranded and rarely meet a timely completion. This tip will teach you five crucial steps to establishing project direction. Competent project managers always keep end-results in mind and drive p... Tip
-
How to improve software project requirements estimates tutorial
Overcoming management constraints on softgware projects is often thought be impossible. Expert Robin Goldsmith shows ways to more efficiently estimate projects in this multiple step tip. Tip
-
Expert shows seven ways to improve your project management abilities
Project management offices can benefit when the team has a diverse portfolio of skills. Learn how to become a better project manager by reading these seven suggestions, which range from developing talents and group leaders to better assessing softwar... Tip
- See More: Tips on Software Requirements Management
-
Contract negotiation: Agile development and defining requirements up front
In this response, expert Lisa Crispin explains how experienced Agile teams can negotiate contracts that satisfy customers while also ensuring all necessary development and testing activities are completed. Answer
-
Wikis and software requirements specification: Tracking changes in Agile development
There are several methods for tracking changes so that all team members understand what has taken place. Read this expert response for Lisa Crispin's take on requirements change tracking. 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 app... 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
-
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 expl... Answer
-
How to select your ALM requirements management tool
Choosing an appropriate ALM requirements management tool comes with many challenges. Sometimes defining requirements may be close to impossible. For situations when requirements can be defined, expert Mike Jones has several tips on how to find the to... Answer
-
Integrated ALM tools vs. best-of-breed lifecycle management tools
Everyone wants to select the highest quality tools available, and depending on whether you are working in a professional development shop or in an enterprise IT shop, your ALM tooling needs will vary. Expert Mike Jones offers some insight into whethe... Answer
-
How to begin the software requirements gathering process: Elicitation and analysis techniques
The software requirements gathering process for a new agile development project can seem daunting at first. In this expert response, Sue Burk offers advice on how to begin using elicitation techniques and choosing analysis models that fit your busine... Answer
-
Understanding functional and non-functional requirements in the software development lifecycle
The premise that functional and non-functional requirements exist separately is a misconception. In this expert response, Robin Goldsmith explains the how these two types of specifications are inter-related and correlate with particular functionaliti... Answer
-
Types of software requirements: Business, functional, stakeholder, and "real"
Expert Robin Goldsmith explains the different ways that requirements are categorized, explaining the difference between "whats" and "hows." Goldmith recommends what he refers to as "real" business requirements driven down to detail and are always bus... Ask the Expert
- See More: Expert Advice on Software Requirements Management
-
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
-
Continuous Delivery with a Rapid Deployment Pipeline
Continuous Delivery with a Rapid Deployment Pipeline Video
-
Strategies for scaling Agile beyond simple code-and-deploy environments
In this tip, consultant Michael Kelly shares some models and strategies that will help teams stay Agile as projects grow. Tip
-
Contract negotiation: Agile development and defining requirements up front
In this response, expert Lisa Crispin explains how experienced Agile teams can negotiate contracts that satisfy customers while also ensuring all necessary development and testing activities are completed. Answer
-
Wikis and software requirements specification: Tracking changes in Agile development
There are several methods for tracking changes so that all team members understand what has taken place. Read this expert response for Lisa Crispin's take on requirements change tracking. Answer
-
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
-
Continuous Delivery with a Rapid Deployment Pipeline
Continuous Delivery with a Rapid Deployment Pipeline Video
-
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 app... Answer
-
Adopting Agile: Eight traction tips to make Agile development stick
Agile transition isn't easy. The tendency may be to revert back to traditional methods once the going gets tough, though experts encourage organizations to stick with it. In this tip, we learn eight tips for Agile traction recommended by Howard Deine... Tip
-
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
-
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 expl... Answer
-
How to select your ALM requirements management tool
Choosing an appropriate ALM requirements management tool comes with many challenges. Sometimes defining requirements may be close to impossible. For situations when requirements can be defined, expert Mike Jones has several tips on how to find the to... Answer
- See More: All on Software Requirements Management
About Software Requirements Management
Software requirements management is one of the most important activities in application lifecycle management (ALM.) Requirements are gathered at the beginning of the software project and are used as crucial inputs throughout the lifecycle. Traceability to requirements are used throughout the lifecycle to ensure that each of the activities in the follow-on phases can be tied to specific requirements. Software requirements are used as input when doing acceptance test. The importance of gathering and documenting requirements cannot be underestimated.