Documentation home
Reference and support
Plain-English glossary
A shared vocabulary for project and security conversations.
Everyone
Project and delivery terms
| Term | Meaning |
|---|---|
| Requirement | A statement of behavior or a constraint the solution must satisfy |
| Acceptance criterion | An observable condition used to decide whether a requirement is met |
| Baseline | The agreed version of the scope used to assess delivery |
| Artifact | A work product such as a specification, test result or release package |
| Integration | An agreed exchange of information or actions between systems |
| Release | An identified version prepared for an environment and purpose |
| Rollback | A planned way to return to an earlier operational state |
Security and review terms
| Term | Meaning |
|---|---|
| Least privilege | Granting only the access needed for the approved task |
| Deployment boundary | The systems, services and responsibilities included in a particular deployment |
| Evidence | A record that supports a claim and can be examined |
| Finding | A gap or concern that needs a decision or corrective action |
| Remediation | Work intended to correct a finding, followed by verification |
| ATO | Authority to Operate: an authorization decision by the responsible authority |
| Model endpoint | The service location used to process an AI request |
Modernization terms
| Term | Meaning |
|---|---|
| Legacy system | An existing system that the organization continues to depend on |
| Business rule | A condition or decision that determines how a process behaves |
| Dependency | Another component or service that a workflow relies on |
| Behavioral equivalence | Agreement that selected outcomes meet the defined comparison criteria |
| Source of truth | The authoritative system or owner for a particular fact or record |
Need guidance for your environment? Contact AutoBridge or use your existing project support channel.