Separation of data presentation, processing and storage

A tiered architecture for the web systems to allow for integration and future change

All Local Authority systems that provide web based user interfaces (to any users, whether customers or staff) must allow for those interfaces to be redesigned, changed and managed using suitable mechanisms.

The ability for changes to be made to the presentation of interfaces (including static information pages) should not be limited to specific parts of the interface and should not be implemented solely through point and click editing tools.

It should be possible to replace the presentation elements (usually HTML and CSS) of a web interface or page via an API or through editing files.

Service oriented architecture

Adopt a service oriented architecture that allows a number of interdependent systems to work together now and in the future.

In order to connect the various web systems that are provided by the Local Authority, its partners and other organisations and individuals, a flexible and accessible mechanism must be implemented. A service oriented architecture (SOA) should be adopted to allow interconnection between the numerous systems without requiring direct and tight coupling of the systems.

A messaging system to communicate events and data such as a lightweight enterprise service bus (ESB) should be used to connect the systems (via the necessary security devices and mechanisms) using the standard protocols that are most convenient and appropriate to each system e.g. REST, WSDL, JSON, SOAP, etc.