The “ilities” of Software Quality
There are many factors to consider when determining the quality of software. Here are some “ilities” to consider when measuring / testing for quality. It is crucial for the team to determine which of these are important characteristics that should be engineered into the software, as there will be constraints (time, resources, skills, tools available) that can prevent SQE organizations to measure such “ilities”. However, these should be part of the discussion and considered for each software project.
Correctness
- Correctness is judged based on what the user wants
- Does the software comply with requirements?
- Are the rules and regulations reflect the user’s request?
- Are the standards being followed?
Efficiency
- How much resources is needed?
Expandability
- How easy is it to expand the software?
Flexibility
- How easy is it to change it?
Integrity
- How secure is it?
- Data integrity?
Interoperability
- Does it interface easily?
Maintainability
- How easy is it to repair?
Manageability
- Is it easliy managed?
Portability
- How easy is it to transport?
- Can it be moved from one server or environment to another?
Usability
- How easy is it to use?
- Is it user friendly?
Reliability
- How often will it fail?
- What is the mean time between failures?
Reusability
- Is it reusable in other systems?
- Can existing code / software be used to implement this solution?
Safety
- Does it prevent hazards?
- Will anyone get hurt?
Survivability
- Can it survive an outage?
- Has business continuity been considered?
- How does it handle a failure?
- Does it restart cleanly?
Feasibility
- Can it be implemented within budget?
- Is the time schedule realistic?
- Does it use the right technologies?
- Are the right resources available?
Security
- Is the software secure?
- Is personal data protected from theft or threat?
Verifiability
- This confirms that it is possible to test.
- Can this be tested? Either programmatically / visually / physically?
- Can verification be done easily?
Recent Comments