From Requirements to Release: A Practical Software Development Lifecycle
Most software problems that reach customers were decided long before the code was written: a requirement nobody pinned down, a build that only worked on one laptop, or a release nobody could reproduce six months later. A practical lifecycle is the smallest set of habits that keeps requirements, code, tests and releases connected, so every shipped version can be explained and rebuilt.
At a glance
- Testable
- A requirement is only useful if someone can write a test that shows it has been met.
- CI
- Continuous integration builds and tests every change, so breakage is found soon after the commit.
- SemVer
- Semantic Versioning uses MAJOR.MINOR.PATCH to signal breaking changes, new features and fixes.
- One build
- The binary that passed testing is the one that ships. It is never rebuilt for release.
The problem
Requirements written as wishes, such as fast, intuitive or reliable, cannot be tested, so they are never verified. The gap shows up at acceptance, when the customer and the team discover they meant different things.
Releases cause the second set of problems. If the build depends on one machine, or the release is rebuilt from a branch that has since moved on, nobody can say exactly what the customer is running or reproduce the fault they report.
Every shipped version should trace back to its requirements, its source and its test results. If one of those links is missing, the release is a guess.
Software alongside hardware
When an application runs with firmware and a physical device, the lifecycle has to track compatibility as well as features. Keep a matrix of which application versions work with which firmware and hardware revisions, and test the combinations you actually ship.
Define what done means before work starts: code reviewed, tests written and passing in CI, documentation updated and the change linked to the requirement it serves. A shared definition stops work being declared finished when it is only written.
What good looks like
Write requirements that are specific and testable, give each one an identifier, and agree them with the people who will accept the product.
Set up version control, code review and a CI pipeline that builds from a clean environment and runs the automated tests on every change.
Tag each release in version control, archive the exact binaries and test results, and publish release notes stating what changed and what is known.
The lifecycle at a glance
- Requirements: Testable, numbered, agreed
- Architecture: Components, interfaces, risks
- Implementation: Reviewed changes in version control
- Verification: Automated and manual tests
- Release: Tagged, signed, archived
- Maintenance: Fixes, updates, field feedback
| Stage | Artefact | Why it matters |
|---|---|---|
| Requirements | Numbered requirement list | Gives tests something to verify |
| Architecture | Interface and design notes | Lets work proceed in parallel |
| Implementation | Reviewed commits | Records why each change was made |
| Verification | Test reports from CI | Shows what was proven and when |
| Release | Tag, binaries and release notes | Makes the version reproducible |
What it changes
Traceability
Each feature links to a requirement, a change and a test, which makes audits and customer questions quick to answer.
Predictability
Small, continuously tested changes give a realistic view of progress instead of a late integration crunch.
Reproducibility
Any released version can be rebuilt and debugged, even years later.
Supportability
Knowing exactly what each customer runs turns field reports into problems that can be fixed.
Where to go next
Scale the process to the risk. A regulated medical or industrial product needs formal design controls; an internal tool needs the same habits with less paperwork.
Automate the release steps themselves. Signing, packaging and publishing done by a script are repeatable; done by hand they drift.
Problems this prevents
- Requirements nobody can test
- Builds that only work on one machine
- Releases that cannot be reproduced
- Application and firmware versions that do not match
Discuss your project
Email support@aavico.com or use Get in Touch when the website finishes loading.