Development through prototypes, testing and acceptance
Turn requirements into a working prototype, then develop in stages against features and acceptance criteria, with business users involved throughout.
Requirements and working prototypes
Confirm users, workflows and data sources, try key screens, and define first-phase features and exclusions.
Stage deliverablesWorkflows, prototypes and acceptance criteriaDevelopment and scenario testing
Implement features and test roles, validation and error handling. Check interfaces and licensing for external services.
Stage deliverablesTestable releases, test records and issue logsLaunch and maintenance handover
Confirm deployment, backups, administrator accounts and operational checks, then provide usage instructions, version handover and support responsibilities.
Stage deliverablesApproved release, deployment and administration documents
Checks before handover
- Main workflows and permissions for different roles have been tested.
- Error notifications, backups and rollback are arranged.
- Source code, data, third-party costs and maintenance responsibilities are specified.
Features, timelines, source code and intellectual-property arrangements follow the project agreement. Third-party interfaces, platform approvals and AI output quality require separate verification.
Describe your idea through everyday work
You do not need programming knowledge or a chosen technology. Bring an idea, a hand-drawn process, a form or a reference screen. Explain who will use it, how the work is done today and the desired result, then organise functions and priorities. The following uses can be considered within a project scope.
- Service and interactive features for corporate websites, online platforms or mobile apps.
- Customer or staff portals for submitting data, applications and checking progress.
- Bookings, registrations, forms, notifications and follow-up.
- Inventory, customer management, tasks and reporting.
- Retaining or connecting existing websites, forms and business systems.
Define the website, app or internal system scope
Use screen examples or an interactive prototype to confirm workflows and compare website, mobile app or internal system approaches. Separate the initial phase from future extensions. Plan data sources, content rights, storage and account permissions together; before connecting other systems, review third-party interfaces, licences and restrictions.
- Devices, platforms, pages, forms and the data to be processed.
- What staff, customers and administrators may view, change or approve.
- Scope of legacy data imports, uploads, notifications, search and reporting.
- Administrative accounts, backups, retention and third-party responsibilities.
From prototype to coding, testing and acceptance
Once requirements and the prototype are agreed, development proceeds in phases so the business owner can check functions against the workflow. Test on the selected devices and platforms, covering normal use, invalid input, duplicate submissions, account permissions and necessary data restoration. For a changeover from an existing system, plan backups, a cutover window and rollback before an authorised person approves deployment.
- Specify functions, revision scope and acceptance criteria for each phase.
- Use approved or non-sensitive content for demonstrations and testing.
- Record issues, revisions and confirmed results before scheduling release.
Deployment, handover and ongoing maintenance
Deployment, app distribution, domains and third-party platforms must follow the selected platforms and service terms. Assign clear responsibility for administrative access and software updates. Define the handover of source code, accounts, operating information and deployment documentation at the start, including third-party components and licences. Allocate responsibilities for subsequent feature changes, fault support, patching and backups separately.
- Bring your idea, current workflow, intended users and the issue you want to improve.
- Prepare non-sensitive form or screen examples and separate essential features from later enhancements.
- Explain your budget, target dates, data sources and who will confirm requirements.
Functions, integrations, acceptance and ongoing support are subject to the agreed proposal.
Information and references
Suitability and enquiry preparation
When is this service suitable?
Common needs
- You want to turn a service or work idea into a website, application or customer portal.
- Scattered customer, inventory, booking or internal records need workflow-based management.
- You need reports or dashboards with role-based accounts and data access.
Which service do I need?
- Business website design services
Coordinate existing website content, features and management.
- Workflow automation and system integration
Connect websites, applications and internal systems to everyday workflows.
- Cybersecurity solutions
Plan controls around platforms, accounts and data.
Prepare for an enquiry
- Your idea, main users and the first two or three tasks to deliver.
- Describe existing websites, systems and data sources, or provide samples with personal and confidential information removed.
- Preferred platform, target date, budget direction and future management responsibilities.
For an initial enquiry, describe the issue and equipment only. Do not submit passwords or verification codes. The team will arrange a secure channel for sensitive documents and incident records.
EnquireCustom websites, applications and internal systemsCybersecurity and AI useExplore security planning, responsibilities and acceptance considerations
Cybersecurity · Safe AI use
Software development and integration: security planning priorities
「Custom websites, apps and internal systems」 includes the following security priorities; measures, tests and deliverables are specified in the proposal.
- Data and sign-inArrange authentication, data access and approvals around users and workflows, with clear purposes for company, development and test data.
- Integration and recordsCheck external interfaces, accounts and licensing, protect credentials, and plan logs for important actions, errors and changes.
- Testing and recoveryTest normal operation, invalid input and permission boundaries. Confirm release, backup, shutdown and rollback arrangements before deployment and maintenance handover.
AI considerationsAI queries must follow authorised data and user permissions. Restrict tool read/write access and retain human approval for important operations. Test malicious instructions in external content, data leakage and incorrect results.
Planning and acceptance recordsRequirements and acceptance checklist, software version, function and permission tests, deployment documents, and administration and maintenance responsibilities.
You may also want to know
Can I enquire with an idea but no programming knowledge?
Yes. Start with the users, current process and desired result, using a hand-drawn workflow or reference screen if helpful. We can then discuss a suitable website, app or system approach, beginning with a prototype and essential functions. Each phase should specify its scope, charges and acceptance criteria.
Can a new website, app or system use existing data?
First review the existing technology, administrative control, data formats and usage rights to assess retention, import or restructuring options. Third-party integrations also require checks of interfaces, licensing and restrictions before the feasible scope is agreed.
Who is responsible for source code, accounts and maintenance after completion?
The proposal should specify handover and responsibilities, distinguishing custom code from third-party components and their licences. It should also set out administrative control, deployment, updates, backups and subsequent changes for the business and development support team.
