ISO/IEC 19510:2013(E) · BPMN + BPSS
Standards-based AI application building
I do not simply build applications. I convert business requirements into a standards-aligned Business Process System Specification, then transform that specification into a working software platform using AI-assisted engineering and local IT team enablement.
Core belief
A business application should not start with code. It should start with a clearly understood business process.
Before building any system, the organisation must understand who starts the process, who owns each step, which department is responsible, what information is required, what documents are submitted, what decisions are made, what approvals are needed, what system actions happen automatically, what exceptions may occur, what happens when something is rejected or delayed, what integrations are required, what audit trail must be maintained, what reports management needs, and how the process ends.
Only after this is understood should software development begin. That is the foundation of my approach.
What makes the approach different
Most projects fail because process and software design are not aligned.
The business explains the requirement one way, the analyst writes it another way, the developer understands it differently, and the final system behaves differently from how the business operates. My framework closes this gap.
I first convert business requirements into a Business Process System Specification (BPSS), aligned with ISO/IEC 19510:2013(E) BPMN principles — process flows, activities, events, gateways, participants, data objects, message flows, sub-processes, approvals, exception paths, and execution logic.
The BPSS
The bridge between business operation and software performance.
The Business Process System Specification is not just a requirement document, not just a process diagram, not just a workflow drawing. It is the business and technical bridge between what the organisation does and what the software must perform.
- System architecture
- Application modules
- User roles
- Workflow automation
- Approvals & business rules
- Screens
- APIs
- Database structure
- Integrations
- Reports
- Audit trails
- Testing & training
From requirement to platform
The flow.
- 01
Business requirement
Captured from users, management, operations, IT, compliance, and process owners.
- 02
Business process model
Real workflows, manual steps, documents, approvals, exceptions, informal workarounds.
- 03
ISO-aligned BPSS
Processes, activities, events, gateways, participants, data, messages, execution logic.
- 04
Application architecture
Modules, screens, APIs, entities, workflows, reports, integrations, access control.
- 05
AI-assisted development
AI agents and reusable components generate and assemble per the approved spec.
- 06
Validation & process matching
Every path, approval, exception, notification and integration tested against the BPSS.
- 07
Local IT enablement
Train the client's team to understand, extend, and own the platform.
AI agents in delivery
Guided by the spec, not the imagination of the model.
AI agents support requirement analysis, process extraction, BPMN-style structuring, module decomposition, user-story generation, database design, API specification, frontend planning, backend code generation, test cases, documentation, exception scenario identification, role mapping, training material, and validation of missing flows.
AI agents are guided by the BPSS. This means AI does not randomly generate an application. It builds according to a structured, process-driven blueprint.
Local IT empowerment
The client's team should own the platform — not me.
I involve local IT staff from requirement understanding through to maintenance planning and future enhancement. The goal is to transfer knowledge, not hide it. The local team should be able to modify basic workflows, add fields, create reports, adjust approval levels, manage users and master data, maintain documentation, support users, and work with AI tools to generate controlled improvements.
Many organisations spend heavily on software because every small change requires the original vendor. My approach reduces that long-term dependency.
The outcome
Not just software — a business platform.
- Aligned with the actual business process
- Built from a standards-based specification
- Mapped from requirement to workflow to code
- Documented for business and technical users
- Supported by AI-assisted delivery
- Maintainable by the client's local IT staff
- Flexible for future changes
- Ready for continuous improvement
Design the process before building the app.
Let's discuss how the BPMN + BPSS framework can fit your platform delivery.