Getting started
Introduction to ADOM
Bring requirements, AI-assisted development, testing and delivery into a project your team can review and manage.
Everyone
What ADOM does
ADOM is AutoBridge Systems’ development platform for building and modernizing software. It coordinates work from a business need through planning, implementation, review and delivery. The result is more than generated code: a project needs an agreed scope, a working application, evidence that it meets its requirements, and people accountable for its release.
A business owner explains the outcome and reviews the result. Technical specialists configure the environment and assess implementation. Security and operational stakeholders review the controls and evidence relevant to their responsibilities. ADOM helps organize that work; people retain responsibility for decisions and acceptance.
Choose your starting point
| Your situation | Start here | What you will establish |
|---|---|---|
| A new application | Define the project | Users, workflows, data and measurable acceptance criteria |
| An existing application | Modernization with ADOM Refactor | What the system does, what must remain equivalent and what may change |
| A security or procurement review | Security and governance | The proposed environment, responsibilities and evidence needed for approval |
| A project already underway | Manage delivery | Owners, progress, review decisions, changes and release readiness |
How a project moves forward
The lifecycle is iterative. A finding during testing may return work to implementation; a new requirement may require a revised plan. Review each result against the agreed version of the scope.
- Define the outcome and approve the requirements.
- Review a plan and divide the work into reviewable tasks.
- Build and inspect the application in an agreed environment.
- Test expected behavior, permissions and failure cases.
- Review release evidence, deploy with approval and hand over operations.
A simple example
A facilities team needs an application for maintenance requests. The specification describes who may submit a request, who assigns work, which records each role can see, and how completion is reported. The team reviews the proposed workflow, tests sample requests and restricted access, then approves a release when the agreed checks pass. This is an illustrative workflow, not a performance benchmark.
Getting access
ADOM access is coordinated with AutoBridge and your organization. This documentation does not create an account or start a build. Begin with your project contact or send AutoBridge a description of the intended outcome. An existing customer should use the workspace and onboarding instructions supplied for their engagement.
Need guidance for your environment? Contact AutoBridge or use your existing project support channel.