Single Page Application (SPA)

Everything should be in one page with refreshable areas of the page based on a Domain Object Model (DOM).

Most of the product based on a series of tasks visible in a “workflow container”. These can be added, manipulated, updated and removed by a user. They should be visual and will be in task boxes. See wireframes for an idea of this.

Modular Design Structure

Expect this to be abstracted into layers into an object-oriented model in both design and implementation as far as possible with reusability as an important aspect.

APIs

APIs for CRUD. Basic input/output with potentially quite complex signatures containing multiple nested data structures and with returned messages for success and failure. JSON implementation required using REST APIs. Examples of APIs

• Client

  • Seko clients, eg. “Room” who design and supply rooms within a building, eg. meeting rooms

• Indigina/Seko Integration hub to existing Seko products

  • Warehouse Management (Seko 360 WMS)

    • Arrive, put away, pick, pack, release

  • Voyager (transport)

  • Notification (notification, eg. SMS, email etc)

• URLs from emails to accept/reject requests for work to be undertaken

Notifications

Email, SMS etc.

Instant Notifications

Notifications based on instant messaging for refreshes, data updates, messages etc.

Asynchronous Processes

Reporting and other longer term processes may need to go into an asynchronous process queue with appropriate load balancing

Client Login / Authorisation

• Different logins based on either:

  • Different URLs with an inherent set of permissions based on URL design

  • Same URL with permission based entirely on permission/entitlement records

  • Hybrid approach