Suitable might be the most generic term within the Q42 properties.
Being right or appropriate for a particular person, purpose, or situation.
Note: In previous versions of Q42, the term “testable” was used instead of suitable. Users found that to be overly specific, see the discussion here.
Definition
(Functional) Suitability:
…provides functions that meet stated and implied needs when used under specified conditions.
The ISO restricts Suitability to functional aspects. In our opinion, it is useful in a broader sense: For example, seen from a testing perspective, suitable can mean “easy to test”.
“Responsibility” as an alternative term
Bass et al., 2021 propose to use the term “responsibility” instead of (functional) suitability. That is, from our perspective, a matter of taste.
Typical Acceptance Criteria
(todo)
What Stakeholders mean by suitable
Stakeholder | (potential) Expectation for suitable |
---|---|
User | * offers the required (suitable) functions in appropriate quality * adequate performance * adequate robustness * adequate accessibility and useability |
Product-Owner | * providing appropriate (suitable) functions in suitable quality * easy to enhance with new functions or features |
Management | * appropriate cost/benefit ratio * appropriate effort required to add new features or functions |
Developer | * appropriate effort required to understand internals * good code readability * appropriate effort required to locate and fix bugs * appropriate technologies used * appropriate technical documentation |
Tester | * appropriate effort required for testing |
Admin | * easy to perform required administration tasks (like deploy, install, configure etc) |
Domain-Expert | - |
Others | - |
Qualities tagged with #suitable
- Affordability
- Autonomy
- Budget constraint
- Cohesion
- Compliance
- Correctness
- Cost
- Cycle time
- Deployability
- Deployment frequency
- Expected physical environment
- Functional appropriateness
- Functional completeness
- Functional correctness
- Functional suitability
- Functionality
- Loose Coupling
- Mean time to recovery
- Standard Compliance
- Suitability
- Test Coverage
- Testability
- Versatility
Requirements tagged with #suitable
- Access control is enforced
- Access Control
- Auditability
- Accurate estimate of insurance contract rate
- Accuracy
- Functional correctness
- Preciseness
- Precision
- Reliability
- Add new product
- Affordable CRM (customer relationship management)
- Affordability
- Budget constraint
- Cost
- Time to Market
- Assess impact of proposed change
- Analysability
- Reliability
- Authenticity of a digital document
- Authenticity
- Budget constrained library update
- Affordability
- Budget constraint
- Cost
- Time to Market
- Detailed audit log
- Accountability
- Easily understandable acceptance test cases
- Consistency
- Efficiency
- Maintainability
- Suitability
- Easily understandable generated code
- Code Readability
- Legibility
- Maintainability
- Readability
- Understandability
- Efficient generation of test data
- Capacity
- Efficiency
- Time behaviour
- Test with path coverage in 30min
- Cycle time
- Risk identification
- Testability
- Up to date API
- Accuracy
- Correctness
- Reliability