deepsource.io Open in urlscan Pro
2606:4700:3108::ac42:2b2c  Public Scan

Form analysis
0 forms found in the DOM

Text Content

Product
Customers
Pricing
Resources
Company
Login
Sign up Request demo

Product
Static AnalysisAutofixSASTReportsIaC AnalysisCode coverageSelf-Hosting
Customers
Pricing
Resources
Blog Documentation Trust Report Community OWASP® Top 10 Whitepaper
Company
About Jobs We are hiringSecurity Roadmap Changelog
Login
Sign up Request demo
abcdefghijklmnopqrstuvwxyz
← All Entries
Glossary


INCREMENTAL DEVELOPMENT

   
 * Incremental Development
 * What are the advantages of Incremental Development?
 * Pitfalls


INCREMENTAL DEVELOPMENT

Incremental development is a method of building software products in which a
system is built piece-by-piece. The final requirement specification is clear
from the beginning, and everyone knows the end result clearly. The system is
broken down into small sub-systems which are designed, built and tested
independently. This allows partial utilization of the product, but the full
system isn't usable unless until the development is entirely done.

A good analogy to understand this model is looking at how a mason builds a wall.
How the final wall should look like is already clear in their mind, and starting
from zero they lay out the wall brick by brick. The wall becomes fully usable
only when the construction is entirely done.


WHAT ARE THE ADVANTAGES OF INCREMENTAL DEVELOPMENT?

 * Since sub-systems of a product are gradually built over time, if development
   takes longer than expected, what has been built so far can be released. This
   helps put part of the software in user's hands faster.
 * It is relatively easy to ensure the quality of sub-systems because
   development efforts are concentrated only on a small system at a time.
 * Users of the software can respond to features and provide feedback early.


PITFALLS

 * Since the entire scope is known and frozen at the outset and the development
   happens on sub-systems, it becomes very critical to design the overall system
   architecture and interface definitions between sun-systems well. Failure to
   do so results in delays due to re-work needed on already built systems.
 * The final cost of the entire system can well exceed the initial cost
   projected.

Write clean and secure code with DeepSource
Powerful static analysis that takes 5 minutes to set up and helps you fix code
health and security problems on every pull request.
Start for free
Request demo
Product Platform Pricing Static Analysis IaC Analysis SAST Reports Code Coverage
Self-Hosting

Resources Blog Documentation Trust Report Glossary Guide to OWASP® Top 10 Good
Code Podcast Good First Issue Spotlight State of Go OWASP Top 10 Whitepaper

Company About Security Roadmap Changelog Customers Jobs We are hiring Privacy
Policy Terms of Service Press Enquiries Brand Assets

Support FAQs System Status Contact Sales DeepSource Discuss


Product
Platform Pricing Static Analysis IaC Analysis SAST Reports Code Coverage
Self-Hosting


Resources
Blog Documentation Trust Report Glossary Guide to OWASP® Top 10 Good Code
Podcast Good First Issue Spotlight State of Go OWASP Top 10 Whitepaper


Company
About Security Roadmap Changelog Customers Jobs We are hiring Privacy Policy
Terms of Service Press Enquiries Brand Assets


Support
FAQs System Status Contact Sales DeepSource Discuss



© 2023, DeepSource Corp. All rights reserved.
We use cookies to enhance your experience. Learn more →
Accept