Changelog
This appendix defines the version-specific change history, change type classification, and revision principles for the TQS specification. All revisions are reflected after approval by the TQS Committee.
35.3.1. Version-Specific Change History
This section chronologically records the complete revision history of the TQS specification.
| Version | Date | Change Description | Author | Affected Scope |
|---|---|---|---|---|
| v1.0.0 | 2026-02-28 | Initial release | Technical Standards Committee | All |
| v1.1.0 | 2026-02-28 | Added PostgreSQL, jOOQ, Flyway, and file upload standards. Removed JPA-related content | Technical Standards Committee | Backend (Chapters 5-9) |
| v2.0.0 | 2026-03-01 | Large-scale frontend standard expansion (3 to 51 pages). Added TypeScript, Vue Router, Pinia, Axios, Tailwind CSS, accessibility, Vitest, performance, and vue-i18n standards. Chapter number reassignment (Chapters 10-29) | Technical Standards Committee | Frontend (Chapters 10-22), Operations/Verification/Certification (Chapters 23-29) |
| v3.0.0 | 2026-03-01 | Large-scale certification system expansion (2 to 30 pages). Separated certification overview, purpose and necessity, external certification comparison (ISO 27001, ISMS-P, ISO 9001, CMMI, SOC 2), certification procedures, checklist, audit preparation guide, post-certification management, and appendix. Chapter number reassignment (Chapters 28-35) | Technical Standards Committee | Certification (Chapters 28-35) |
35.3.1.1. v1.0.0 Details
This is the initial release version. The basic framework of the TQS specification was established.
- Development environment configuration standards defined
- Configuration management and branch strategy established
- Code conventions and formatters designated
- CI/CD pipeline standards defined
- Testing, security, and API standard foundations defined
- 5-stage certification procedure defined
- Appendix (glossary, references, changelog) created
35.3.1.2. v1.1.0 Details
This version strengthened the backend data layer standards.
- PostgreSQL database standard added
- jOOQ-based query writing standard added
- Flyway-based schema migration standard added
- File upload and storage management standard added
- Existing JPA-related content removed (transitioned to jOOQ)
35.3.1.3. v2.0.0 Details
This is a major version that significantly expanded frontend standards.
- TypeScript type system standard added
- Vue Router routing standard added
- Pinia state management standard added
- Axios HTTP communication standard added
- Tailwind CSS styling standard added
- WCAG accessibility standard added
- Vitest unit testing standard added
- Core Web Vitals performance standard added
- vue-i18n internationalization standard added
- Chapter number reassignment (existing operations/verification/certification chapter numbers changed)
35.3.1.4. v3.0.0 Details
This is a major version that significantly expanded the certification system.
- Certification overview chapter established (certification definition, system, TQS Mark, grades)
- Certification purpose and necessity chapter established (purpose, necessity, expected benefits, maturity model)
- External certification comparison chapter established (ISO 27001, ISMS-P, ISO 9001, CMMI, SOC 2 comparison)
- Certification procedure chapter expanded (5-stage procedure detailed, RACI matrix, audit types)
- Certification checklist chapter established (backend, frontend, operations, security checklists)
- Audit preparation guide chapter established (preparation roadmap, self-assessment tools, failure cases)
- Post-certification management chapter established (maintenance, re-audit, certification revocation and restoration)
- Appendix separated into independent chapters (glossary, references and regulations, changelog)
35.3.2. Change Type Classification
Changes to the TQS specification are classified into the following types. Version number increment rules and chapter number impacts vary by change type.
| Type | Description | Chapter Number Impact |
|---|---|---|
| New addition | New chapter or section added | Subsequent chapter numbers may change |
| Content expansion | Content enhancement of existing chapters | No chapter number changes |
| Structural change | Chapter separation, merger, or rearrangement | Chapter number changes occur |
| Technical change | Technology stack or tool change | Only the affected chapter is impacted |
| Error correction | Typo fixes, broken link repairs, etc. | No impact |
35.3.2.1. Examples by Change Type
Specific examples for each change type are as follows.
- New addition: In v3.0.0, 8 new chapters were added including certification overview, purpose and necessity, and external certification comparison
- Content expansion: In v2.0.0, frontend standards were expanded from 3 pages to 51 pages
- Structural change: In v2.0.0, chapter numbers were reassigned to Chapters 10-29
- Technical change: In v1.1.0, JPA was removed and replaced with jOOQ
- Error correction: Typo fixes, broken link repairs, table formatting cleanup, etc.
35.3.3. Revision Principles
Revisions to the TQS specification follow the following principles.
35.3.3.1. Version Number System
The TQS specification follows the SemVer (Semantic Versioning) system.
| Version Type | Format | Change Criteria | Example |
|---|---|---|---|
| Major version | X.0.0 | Large-scale structural changes or new chapter additions | v1.0.0 to v2.0.0 |
| Minor version | x.Y.0 | Content expansion or technical changes in existing chapters | v1.0.0 to v1.1.0 |
| Patch version | x.y.Z | Typo fixes, link repairs, minor wording changes | v1.0.0 to v1.0.1 |
35.3.3.2. Revision Procedure
All specification changes must follow the following procedure.
- Change proposal: A TQS Committee member or project team proposes the change.
- Impact analysis: The impact of the change on existing certifications is analyzed.
- Committee resolution: The TQS Committee reviews and resolves on the change.
- Application and announcement: The resolved change is applied to the specification and announced company-wide.
- Transitional measures: Transitional measures for projects with existing certifications are communicated.
35.3.3.3. Revision Compliance Requirements
- All changes must be reflected only after TQS Committee resolution.
- The change description, author, and affected scope must be recorded in the changelog table.
- For major version changes, a transitional period (minimum 3 months) must be granted to projects with existing certifications.
- For minor version changes, the changes are applied from the next renewal audit.
- Patch version changes take immediate effect and do not affect existing certifications.
- When chapter numbers change, all links referencing those chapters in existing documents must be updated.