Why this matters
The most expensive mistakes in a software project do not happen at the keyboard. They happen when nobody states out loud what should actually be built, or when the architecture is never written down. Software is a core asset for your business. Its value rises with every extension and falls with every unclear decision, every vendor lock-in, and every legacy patch. We put the requirements on the table before the money flows, and we capture the architecture decisions so the value compounds over years rather than being eaten by its own complexity.
Two standards we work to
We anchor every engagement to two international frameworks - one for the question “what should we build?”, one for the question “how will it fit, today and in five years?”.
TOGAF ADM (Architecture)
The TOGAF Architecture Development Method keeps the four architectures aligned:
- Business architecture: capability map, value streams, stakeholder requirements.
- Data architecture: domain model, data ownership, privacy classification.
- Application architecture: components, interfaces, API-first principles.
- Technology architecture: platforms, hosting, run model.
Architecture decisions are captured as ADRs (Architecture Decision Records) - context, options, trade-offs, consequences. Anyone who looks at the code today or in five years understands why.
IREB CPRE (Requirements)
We work to the IREB requirements engineering body of knowledge - the same one CPRE-certified practitioners are tested on. In practice that means:
- Structured elicitation - interviews, workshops, observation, document analysis.
- Clean separation between functional and non-functional requirements.
- Specification in a form every stakeholder can read - use cases, user stories with acceptance criteria, an NFR catalogue.
- Validation and verification against business goals and architecture.
- Requirements management throughout the project, with traceability into the tests.
What you get
- Requirements vision: business goals, personas, scope diagram, out-of-scope list.
- Story map with prioritised user stories and concrete acceptance criteria.
- NFR catalogue: performance, availability, security, compliance, usability.
- Glossary of domain terms agreed with stakeholders.
- Capability map and target-state architecture.
- Build-vs-buy scoring matrix for every major component.
- Modernisation roadmap in sprints rather than a big-bang.
- Vendor and standards selection (OAuth, OIDC, ISO 27001, plus sector-specific standards when relevant).
- Architecture risks with mitigations.
- Traceability matrix: requirement -> architecture decision -> test.
When we fit
- You are launching a new product and need clarity before development starts.
- You are planning a major investment and want to know whether the architecture will carry it.
- An ongoing project is derailing because requirements are unclear or conflicting.
- A grown system has become slow and expensive - you need a modernisation plan without a full stop.
- You are choosing between vendors or platforms and need an objective assessment.
- You need an independent eye before a tender or an audit.
Why Luzid
- Requirements anchored to IREB; architecture to TOGAF ADM. Two disciplines, same team - and quality you can put in front of an auditor.
- Experience across regulated sectors and SaaS platforms.
- We deliver architecture as software, not slideware - every decision is traceable into the code and into the tests.
- We write so that leadership, compliance, and engineering all read the same thing.
- No lock-in - what we build is yours.