Quality Policy

01Our quality policy

At VexCore Teknoloji A.Ş., we regard quality as the precondition for the reliability of our products and services. Our quality policy in a single sentence:

Every change passes through defined quality gates; every process has a measurable objective; results are recorded; deviations from objectives or rules are managed through the corrective action mechanism; and closure requires not only the completion of the corrective action but the verification of its effectiveness.

02Basis

Our software development, project and risk management, quality assurance, verification, configuration, problem resolution, change and release management processes are defined within the scope of TS ISO/IEC 15504-7 (SPICE) Staged Level 2 and have been assessed and certified by an independent certification body. Certificate details and the verification link are available on our Credentials page.

03Operating principles

Traceability

Every change is based on a work item and implemented through a change request. Traceability between requirements, changes and releases is maintained.

Independent review

Every change is reviewed by someone other than its author. Automated build, test, formatting and security checks are mandatory quality gates.

Segregation of duties

Quality assurance and testing roles are independent of development roles; quality assurance verifies evidence rather than producing the product.

Evidence-based conformity

A work product with failed, missing or unevidenced test results is not considered conforming. Conformity is never demonstrated by deleting a failed result.

Measurable objectives

Every process has a measurable objective; process performance is evaluated periodically and presented at management review.

Corrective action

Nonconformities are recorded, root-cause analysed and tracked as corrective actions with an owner and a deadline. Closure is independently verified once the effectiveness criterion is met.

Controlled releases

Releases are numbered using semantic versioning; a changelog, test results and release approval are recorded for each release. A backup and rollback plan is prepared before production deployment.

Configuration integrity

Configuration items are kept under version control; the version running in production always corresponds to a defined tag. Manual changes are not considered permanent.

04Customer focus and continual improvement

Customer requirements are collected, analysed and validated in writing, and deliverables are tested against them. Feedback from customers and audits is treated as input for improvement. Our quality objectives and this policy are reviewed by management at least once a year.