Software Quality Fundamentals

Software quality is far more than the absence of bugs. It describes how well a software solution meets user requirements and how efficiently it can be maintained throughout its lifecycle. This article covers the fundamentals of software quality and shows how you can measure and implement it in your daily development work.

In the era of rapid coding practices, developers often move so quickly that quality takes a backseat. Understanding software quality matters from the start of your career. You should become familiar with ISO 25010 early on, and once your project begins, you’ll need to know both functional and non-functional requirements. These concepts are learnable and straightforward to apply in practice. It’s also worth understanding the difference between ISO 9126 and ISO 25010—essentially old versus new—though ISO 25010 is really just an extension of its predecessor.

In a Nutshell: Software Quality in Application Development

• Software quality encompasses both functional and non-functional requirements.
• ISO 25010 defines eight key characteristics: Functional Suitability, Performance Efficiency, Compatibility, Usability, Reliability, Security, Maintainability, Portability.
• High quality reduces defect costs, accelerates development, and increases user satisfaction.
• Quality emerges through testing, clean code, clear architecture, peer reviews, and continuous metrics.

Software quality measures whether a program does what it should and how well it does it. It’s not a binary state but a balance of properties weighted differently depending on context. A medical application, for instance, demands high reliability and security, while a streaming platform prioritizes performance efficiency and scalability.

The key dimensions fall into three categories:

1. Functional Quality: Correctness, completeness, and appropriateness of features.
2. Non-Functional Quality: Performance, security, reliability, usability.
3. Structural Quality: Maintainability, testability, extensibility, code quality.

Core Components of Software Quality

1. Functional Correctness: The software fulfills specified requirements without errors.
2. Reliability: The system remains stable under load and when failures occur.
3. Performance: Response times, throughput, and resource efficiency meet target ranges.
4. Security: Protection against unauthorized access, data breaches, and tampering.
5. Maintainability: Code is readable, modular, and easy to change.
6. Testability: Components can be tested in isolation and automatically.
7. Usability: Users can operate the software intuitively and efficiently.
8. Compatibility: Integration with other systems, browsers, and devices.

Practical Example: Quality Goals for a Web API

Goal: An order API for an online shop

Functional Suitability:
- All use-case endpoints are present and correctly documented.
- Price, tax, and discount calculations are correct in 100% of cases.

Performance Efficiency:
- 95th percentile response time under 200 milliseconds at 100 concurrent users.
- Throughput of at least 500 requests per second without SLA violations.

Reliability:
- 99.9% availability per month.
- MTTR under 30 minutes for outages.

Security:
- Transport encryption with TLS 1.3.
- Authentication via OIDC with MFA for administrators.
- Immutable audit log for all critical changes.

Maintainability:
- Code coverage of at least 70% for unit tests.
- No circular dependencies between modules.
- Feature flags enable controlled rollouts.

Pros and Cons

Pros

• Lower Total Cost: Finding defects early is far cheaper than fixing them in production.
• Faster Development Velocity: Clean code and solid tests enable quicker iterations.
• Greater Customer Satisfaction: Stable, performant, and intuitive software is pleasant to use.
• Reduced Risk: Security vulnerabilities and outages can be minimized proactively.

Cons

• Higher Upfront Effort: Tests, reviews, and metrics consume time at the project’s start.
• Trade-offs: Maximum security can reduce performance; maximum flexibility can increase complexity.
• Measurement Overhead: Quality must be defined, measured, and monitored to be effective.

Exam-Relevant Key Points

• Definition of software quality according to ISO 25010.
• Distinction between functional and non-functional requirements.
• Eight main characteristics of ISO 25010 and their significance.
• Connection between quality, testing, and maintainability.
• Cost of defect fixes across different lifecycle phases.
• Importance of clean code, reviews, and static analysis.

Typical Exam Questions (with Short Answers)

1. What is software quality? The degree to which software meets specified and implied requirements.

2. Name three non-functional quality characteristics. Performance, security, reliability.

3. What does maintainability mean? The ability to modify, correct, or extend software with reasonable effort.

4. Why is testability important? It enables automated, repeatable tests and early detection of defects.

5. What is the difference between ISO 9126 and ISO 25010? ISO 25010 extends the six characteristics from ISO 9126 to eight and adds security and compatibility.

Next in the Software Quality Learning Path

The next article in the software quality learning path covers Software Quality and ISO 25010 — the eight quality characteristics according to the international standard.

Key References

1. https://iso25000.com
2. https://www.iso.org/standard/35733.html
3. https://en.wikipedia.org/wiki/ISO/IEC_25010