VOGO · Agent Design
The agent for solution architecture
Architecture, components, integrations, the data model and security — designed and documented by the agent, following the recognised standards of the profession.
For the organisation's implementation projects and for the architecture chapter of bids. The architect approves and is accountable.
- Every requirement has its design element
- Security and quality by design
- The architect decides
Design, documented as it happens; the decision, the architect's
The agent starts from the approved analysis and carries each requirement through to the design element that realises it. The architecture, the interface contracts, the data model and the security measures carry the same requirement codes, so the design report reads directly against the requirements register.
Every architecture decision has its own record: the context, the alternatives weighed and the consequences. Quality requirements get a measurable target and the way they are ensured.
What it states about a standard rests on that standard's sources, kept locally; what it cannot find there, it says openly.
Fewer lost decisions. Fewer surprises during implementation. The same accountability, the architect's.
Solution architecture
The context, containers and components of the system, drawn level by level, from the overview to the detail.
Components and integrations
The responsibility of each component and the interface contracts, defined before implementation.
The data model
The logical and physical models, the data dictionary, data classification and personal data.
Security by design
Authentication, authorisation, encryption and logging decided at design time, verifiable against a standard.
Product quality
Performance, availability, maintainability and usability, each with its requirement and how it is ensured.
Accessibility
Screens designed for every user, following the international web accessibility guidelines.
Architecture decisions
Every important decision with its context, the alternatives considered and the consequences, in a record of its own.
The architect decides
The agent proposes, documents and checks; approving the architecture remains the architect's call.
What the client receives at the end of design
The design report
The logical and technical architecture, components, integrations, security and sizing, on the requirements of the analysis.
The integration specification
For each integration: the systems involved, the data exchanged, the interface contract and error handling.
Architecture decisions (ADR)
One record per decision: the context, the alternatives considered, the decision and the consequences.
The data dictionary
The entities and fields of the data model, with the type, rules and classification of each.
Their templates are in the project folder in VOGO ECM, in the design folder, created in one click from the software implementation project template.
The frameworks it works by
TOGAF and ArchiMate
Enterprise architecture: the phases, the deliverables and the modelling language.
C4, arc42, ISO/IEC/IEEE 42010 and 12207
How an architecture is described and documented, by levels and by sections, across the software life cycle.
UML, iSAQB, AWS and Azure
Modelling structure and behaviour; the software architect certification and the AWS and Azure cloud architect guides.
ISO/IEC 25010, OWASP ASVS, WCAG
Product quality, application security verification and accessibility.
Service-oriented architecture, interfaces defined by contract before implementation and security verified progressively — the same approach we use in our projects and our bids.
Frequently asked questions
Does it replace the architect?
No. The agent prepares the options, draws the diagrams, writes the design report and checks requirement coverage; the architect chooses and is accountable.
Does it start from the analysis?
Yes. It works on the requirements and models of the analysis, with the same codes, so every requirement has the design element that realises it.
What does it rely on when it cites a standard?
On the sources kept locally for each framework. What is not in its sources, it says so; it does not fill gaps from memory.
Does it help with bids?
Yes. It prepares the architecture chapter of a bid: the logical and physical architecture, the integrations, security and sizing.
Where is project data kept?
In the organisation's folder. Processing is based on the agreement between the organisation, VOGO and the provider of the artificial intelligence service.
See how VOGO Agent Design works
A 15-minute demo, on an example or on one of your organisation's projects.