Page 8 - Helixion-swisscom-tapit-case-study

this in mind, what was delivered in the pilot could be considered as just one of many services
within a wallet container.

When it came to designing the full Tapit implementation, an initial “kick-off” workshop with all
the stakeholders present was held. The objective of the workshop was to draft the high level
design. It would have been easy to do this in isolation (either by Swisscom themselves or by
tasking Helixion with it) but by having all the stakeholders present and contributing, it
allowed a design to be put in place that all the parties understood and agreed with both
technically and commercially.

This initial step ensured that everyone was working to a common goal. There is a commonly
held belief amongst some people that “design by committee does not work” but when
structured correctly and well controlled, it can give real benefits to a project; and in this
instance it certainly worked as this case study clearly demonstrates.

Tapit: The Technical Architecture

Tapit’s architecture has been designed to address the
short, medium and long term vision. Consisting of two

core parts, the server and the client (the latter explained in
more detail below), each was designed to be service

agnostic. Careful assumptions have been made about the
types and implementation of services that might be made

available through the application so as not to limit the
implementation to only the immediate scope. Taking this

approach allows other services to be offered in the future
through Tapit without the need for expensive recoding and

testing.

8 A Helixion Case Study