1 of 1

Prototype

Develop, test, and iterate a functional prototype.

Once the wireframe and/or voice command flow is approved, we are ready to start developing and orchestrating a functional prototype of the service. The prototype is iteratively developed. Each successive iteration adds new functionalities and refines the prototype based on user feedback. This results in a service that meets the desired level of functionality and usability.

What are the benefits of protoyping?

Prototyping an e-service allows:

Pre-procurement testing of software solutions
Technical feasibility check
Requirement gathering (e.g.BPMs) for procurement
Transparency of the inner functioning of the Building Block approach
Reference set-up for development, deployment, and operating life cycle
Testing the Frontend with Users/Citizens

Develop Product and Technical specifications for the service.
Develop the front end and back end of the service according to the Product and Technical specifications and approved wireframes and/or voice command flow.
Develop a test script considering all the branches of "To-Be" user journey.
Prepare
- test scripts
- security and quality assurance checklist
- digital service release plan
- stabilization and maintenance routine
Refer GovStack sandbox documentation and prototype service using rapid prototyping tools. Learn more about the use of prototyping tools by reading the Do It Yourself (DIY) Full Stack Sction of GovStack Sandbox documentation.
Launch α, β versions to a limited set of citizens/business users, admins, and public officials.
Collect their feedback on the functional prototype and identify concrete steps to improve it.
Iteratively developed and deliver the launch version that meets the requirements and needs of citizens/business users, admins, and public officials.
Prepare the plan for migration of the prototype to the production environment.
Prepare the launch of the service.

Who does what

Service designer – Lead the service co-design journey
– Lead software product development according to the service blueprint
Front-end developer – Develops front-end applications following UX/UI style guide
Solution architect – Architects the service according to the BB integration plan
Back-end developer – Adjust BB, connects legacy systems, and test the application
Digital security manager - validates compliance with digital security policy
Cloud architect - Designs cloud strategy and microservices architecture that supports the digitalization of government services

Deliver a functional prototype of the service which:

Complies with the approved 'To-be user journey' and wireframe and/or voice command flow
Complies to Country digital service design standards. This includes standards for:
Complies with Country enterprise architecture, including digital security protocols approved by the country technical team

Iterative prototyping

Following are the stages of prototyping a digital government service, from α version to the Launch version:

α version prototype: α version is a rough functional prototype used to test the initial concept and get feedback from a limited number of users and stakeholders. The duration for the α version must be agreed upon between service owners and stakeholders. It usually lasts between a few weeks and months. α version can be hosted in a testing environment that may or may not be the GovStack Sandbox.
β version prototype: Once the α version is tested and feedback is collected, the β version is developed. This prototype is more refined and is closer to the final digital service. It includes more features and functionalities and is tested by a larger group of users or stakeholders to identify any final issues before launching the next iteration.
In case the β version is hosted on GovStack Sandbox, preparations must be made to deploy it on the country's cloud infrastructure/ production environment.
Launch version: The launch version is the first version of the service that is released to the public. It includes the core features and functionalities that meet the needs of the users and are further iterated based on future user feedback.