Software development lifecycle
The software development lifecycle encompasses every step from the initial idea and requirements, to live applications and beyond. Learn about the latest ALM and CI/CD tools for the SDLC, as well as top methodologies and processes in use.
Top Stories
-
Tip
19 Nov 2024
Top 10 Jenkins alternatives
Tired of the overhead of hosting your own Jenkins installation and looking for some alternatives? Here are 10 of the best. Continue Reading
-
Tip
23 Oct 2024
Continuous delivery vs. continuous deployment: Which to choose?
Continuous delivery and continuous deployment both compress and de-risk the final stages of production rollout. Learn how to choose the proper path for your organization. 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
-
Tip
08 Mar 2018
Jenkins basics: The DevOps and build platform for dev teams
Software expert Walker Rowe discusses how Jenkins goes beyond a DevOps tool. Get a better understanding of how and why your enterprise should install Jenkins. Continue Reading
-
Answer
21 Feb 2018
What are the QA risks in automated software release management?
Beware the QA threats of software release management automation, warns Brian Kirsch. Application release automation enables fast deployment, but be sure to catch bugs first. Continue Reading
-
News
15 Jan 2018
Atomist extends CI/CD to automate the entire DevOps toolchain
The Atomist DevOps automation platform extends beyond CI/CD to fully cover DevOps processes end to end, enabling developers to avoid mundane tasks and focus on productivity. Continue Reading
-
Answer
09 Nov 2017
How do I understand runtime environments?
Whether it's C, Java or Adobe, it's important to understand the differences among runtime environments. Expert Stephen J. Bigelow outlines the various choices. 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
-
Feature
28 Sep 2015
Rally Software the go-to ALM tool for Agile developers
Rally Software gives Agile developers an ALM tool that, along with customizable dashboards, offers SAFe training and certification. Continue Reading
-
Feature
25 Sep 2015
Polarion Software offers compliance-focused ALM
Polarion Software is a browser-based, ALM platform that offers high traceability functions for enterprises with a regulation focus. Continue Reading
-
Feature
23 Sep 2015
Breaking down the Altassian ALM software suite
With JIRA, Confluence, HipChat, Bitbucket and Stash, the Atlassian ALM software suite is for enterprises of all sizes that use Agile methodologies. Continue Reading
-
Feature
23 Sep 2015
HP application lifecycle management: What you need to know
The HP application lifecycle management suite, HP ALM, offers on-premises or SaaS ALM tools to enterprises small and large. Continue Reading
-
Feature
01 Jul 2015
What you need to know about the ALM methodology
Gerie Owen provides an overview of ALM methodology, covering its requirements, development and maintenance phases and its core components. Continue Reading
-
Answer
21 May 2015
The good and the bad of online discussion forums
What is the value of online discussion forums? This expert sees the good and the bad in online forums. Continue Reading
-
Answer
20 Mar 2015
Define project scope in terms of time, money and quality
We all want our projects to be on budget, on time and of high quality, but not necessarily in that order. What is your advice for balancing these needs? Continue Reading
-
Opinion
27 Feb 2015
Three traits of continuous software development
What is 'continuous' in software development? Combining iterative development with automation produces code so quickly it is now thought of as continuous. 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
22 Dec 2014
How do requirements relate to acceptance criteria?
Requirements and acceptance criteria often seem to be essentially the same thing, but that's not quite true. Continue Reading
-
Answer
23 May 2014
How Amazon CloudWatch provides automated APM tools
Amazon CloudWatch provides AWS customers with automated APM tools that they can use to keep applications and businesses running smoothly. Continue Reading
-
Tip
24 Mar 2014
Agile application lifecycle management is not an oxymoron
Learn how Agile application lifecycle management supports the development process for better software and business needs. Continue Reading
-
Quiz
06 Mar 2014
ALM and the Agile development methodology: What do you know?
Test your knowledge of application lifecycle management when it's merged with the Agile development methodology. 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
-
Tutorial
07 Mar 2013
Mobile ALM guide
This guide outlines common mobile ALM challenges and explores the various ways software professionals can meet and solve them. Continue Reading
-
Tip
13 Jul 2012
Agile project management using the Cynefin framework
Learn how the Cynefin framework facilitates problem solving, Agile project management and teamwork. 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
-
Tip
26 Jan 2011
Agile ALM tools: How they differ from traditional lifecycle management tools
Software consultant Nari Kannan describes the differences between agile application lifecycle management (ALM) tools and traditional lifecycle management software. Agile ALM tools are more tightly integrated, easier to use, supportive to distributed teams and seamlessly integrated into many of the traditional lifecycle management functions. 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
28 Dec 2010
Eight steps for a successful software release
Have you done everything to prepare for a successful software release? Software project manager Kay Diller describes eight things you can do to ensure your deployment will go smoothly. From creating your team to being prepared with a back-out plan, Diller steps you through important considerations covering all aspects of the project. 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
-
News
15 Jun 2010
IBM chief methodologist speaks on scaling Agile projects at Innovate 2010
Agile expert, Scott Ambler, states that scalability should be a primary focus for agile development initiatives. To be effective in agile, teams must tailor efforts, tools and processes to reflect development situations, says Ambler Continue Reading
-
News
14 Jun 2010
Through numerous acquistions, IBM has beefed up security test coverage in Rational
Jack Danahy, CEO and founder of Ounce Labs, a static analysis testing tool provider acquired by IBM last summer, explains how application security practices and tooling have evolved. At IBM Innovate 2010, Danahy explained customer desire in knowing their systems are configured properly. Continue Reading
-
Answer
01 Feb 2010
Who determines the appropriate severity or priority for a defect?
There are often differences of opinion on the definition of severity or priority of a defect. The bottom line is determining when and if the defect will be fixed. Factors that need to be considered are customer urgency and time required to fix and test. This strategy takes into account needs of the customer, the developer and the tester. Continue Reading
-
Answer
05 Oct 2009
Problems caused by skipping analysis stage of SDLC
A requirements expert explains the possible pitfalls of skipping the analysis phase in the software life cycle development (SDLC). 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
23 Jun 2009
Differentiating between Functional and Nonfunctional Requirements
Many of the difficulties encountered in defining requirements relate to the functional-nonfunctional distinction. As so often happens, some of those difficulties are things of which people are aware, largely realizing after-the-fact that nonfunctional requirements were missed. Continue Reading
-
Tip
17 Mar 2009
Defining requirements during software project feasibility analysis
There are at least two key points in a software project when requirements should be defined. One point people often miss is during feasibility analysis, and failure to define requirements at this stage can doom a project. 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
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
-
Definition
27 Sep 2007
cruft
Cruft is the elements of a program, system or product that are either useless, poorly designed or both. In computing, cruft describes areas of redundant, improper or simply badly written code, as well as old or inferior hardware and electronics. Cruft may also be used to describe a group of hackers, like a pod of whales, exultation of larks or murder of crows. (Continued...) 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
19 Sep 2007
How to structure a software requirements document
Effective requirements documentation is essential for any good software project. Expert Karl E. Wiegers explains how to structure your software requirements documents. 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
-
Answer
08 May 2007
Estimating project costs, writing project reports
Estimating the cost of a software development project and writing a suitable project report are not necessarily difficult tasks. Bas de Baar breaks down project reporting and cost estimation for beginners. 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