jabrena/plinth / skills/814-regulations-iso-25010
814-regulations-iso-25010
VerifiedUse when reviewing, designing, or modifying Java enterprise systems and need a structured, repeatable ISO/IEC 25010:2023 quality-attribute review covering Functional Suitability, Performance Efficiency, Compatibility, Interaction Capability, Reliability, Security, Maintainability, Flexibility, and Safety, producing an engineering review report rather than an interactive ADR discovery. Part of Plinth Toolkit
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 10.8 KB |
| assets/questions/814-iso-25010-engineering-review-questionnaire.md | markdown | 8.4 KB |
| assets/reports/814-iso-25010-engineering-review-report-template.md | markdown | 6.1 KB |
| references/814-regulations-iso-25010-chapters-summary.md | markdown | 6.4 KB |
| references/814-regulations-iso-25010-engineering-examples.md | markdown | 14.7 KB |
assets/reports/814-iso-25010-engineering-review-report-template.md
View on GitHub# ISO/IEC 25010:2023 Engineering Review Report
Use this template after reviewing `references/814-regulations-iso-25010-chapters-summary.md`, asking the needed questions from `assets/questions/814-iso-25010-engineering-review-questionnaire.md`, and matching the relevant examples from `references/814-regulations-iso-25010-engineering-examples.md` for each of the nine ISO/IEC 25010:2023 quality characteristics.
This report is not certification advice, compliance advice, conformity advice, or an audit conclusion. Use it as engineering evidence for architecture, product, security, platform, operations, and accountable business-owner review.
The purpose of this report is to increase awareness of potential quality-attribute gaps in a Java enterprise system and create engineering evidence for qualified review. The response produced from this template does not represent ISO/IEC 25010:2023 certification readiness, compliance approval, audit pass/fail status, or final conformity with ISO/IEC 25010:2023.
Official public source references:
- ISO/IEC 25010:2023 standard page: `https://www.iso.org/standard/78176.html`
- ISO/IEC 25000 SQuaRE series overview: `https://iso25000.com/index.php/en/iso-25000-standards/iso-25010`
## 1. Review Context
- Java system, service, repository, module, or delivery pipeline reviewed:
- Repository or implementation path:
- Review date:
- Reviewers:
- Architecture owner:
- Product or business owner:
- Security owner:
- Platform or release owner:
- Operations owner:
- Source materials reviewed:
## 2. Review Scope
- Java modules, services, or pipeline stages in scope:
- Environments in scope:
- Users, consumers, or operators affected:
- Lifecycle stage:
- Open scope questions:
## 3. Engineering Evidence Reviewed
- Java applications, libraries, APIs, jobs, or services:
- Build files, Maven dependencies, and dependency-scan evidence:
- Test suites: unit, integration, contract, load/soak, and acceptance evidence:
- Static-analysis, complexity, and code-review evidence:
- Configuration, infrastructure-as-code, and deployment evidence:
- Monitoring, health/readiness probes, and operational runbooks:
- Owner handoffs and qualified review records:
## 4. Findings By Quality Characteristic
This section is not a certification or audit finding. Use it to list concrete engineering evidence, gaps, and findings for each of the nine ISO/IEC 25010:2023 quality characteristics and route each item to a qualified owner. When no concern is confirmed, say so explicitly and keep open items as potential evidence gaps.
| Quality characteristic | Sub-characteristics reviewed | Evidence from reviewed system | Finding | Required owner review | Engineering action |
| ----------------------- | ----------------------------- | ------------------------------ | -------------------------------------------------- | ---------------------- | ------------------- |
| Functional Suitability | Completeness, correctness, appropriateness | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
| Performance Efficiency | Time behaviour, resource utilization, capacity | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
| Compatibility | Co-existence, interoperability | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
| Interaction Capability | Recognizability, learnability, operability, user error protection, engagement, inclusivity, assistance, self-descriptiveness | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
| Reliability | Faultlessness, availability, fault tolerance, recoverability | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
| Security | Confidentiality, integrity, non-repudiation, accountability, authenticity, resistance | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
| Maintainability | Modularity, reusability, analysability, modifiability, testability | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
| Flexibility | Adaptability, scalability, installability, replaceability | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
| Safety | Operational constraint, risk identification, fail safe, hazard warning, safe integration | TBD | No identified concern / Potential gap / Confirmed gap | TBD | TBD |
## 5. Engineering Controls
- Functional-suitability traceability and edge-case tests:
- Performance capacity evidence and load/soak test results:
- Compatibility and API versioning strategy:
- Interaction-capability and self-descriptive error handling:
- Reliability and resilience patterns:
- Security, authorization, and secrets management:
- Maintainability and module-boundary review:
- Flexibility and configuration externalization:
- Safety guardrails and fail-safe defaults:
- Release readiness and owner approvals:
## 6. Evidence Inventory
- Acceptance-criteria traceability records:
- Load/soak test reports:
- API contract and versioning documentation:
- Static-analysis and complexity reports:
- Security scan and dependency-vulnerability reports:
- Test-pyramid and coverage reports:
- Configuration and infrastructure-as-code evidence:
- Monitoring dashboards or alerts:
- Owner review records:
## 7. Residual Risks
- Residual risk:
- Impact:
- Likelihood:
- Mitigation:
- Owner:
- Acceptance decision:
- Review date:
## 8. Release Decision
- Decision:
- Conditions:
- Blockers:
- Required approvals:
- Expiry or review date:
- Environments or versions approved:
- Next monitoring checkpoint:
## 9. Action Plan
| Priority | Action | Owner | Due date | Evidence expected | Status |
| -------- | ------ | ----- | -------- | ----------------- | ------ |
| High | | | | | Open |
| Medium | | | | | Open |
| Low | | | | | Open |
## 10. Final Notes
- Items requiring architecture decision:
- Items requiring product or business acceptance:
- Items requiring security review:
- Items requiring platform or operations review:
- Items requiring certification, compliance, or conformity determination (qualified owners only):
- Next review trigger:
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |