Specification
05 assemblies
Service / Access

Build the Interface Around the People Who Actually Use It.

Internal tools and controlled portals can be designed around agreed roles, permissions, information requirements and the work each user needs to complete.

01

Internal tools

Replace a patchwork of workarounds with one coherent flow.

Potential project capabilities include staff workflows, operational administration, approvals, records and reporting where agreed.

  • Staff workflow
  • Administration
  • Approvals
  • Records
  • Reporting
01 / Staff workflow
02 / Administration
03 / Approvals
04 / Records
05 / Reporting
Example workflow Illustrative / not client work
02

Portals

Give external users purposeful, controlled access.

A portal may support customer, client, supplier or member access to agreed information, actions, documents and workflows.

  • Customer
  • Client
  • Supplier
  • Member
Customer
Client
Supplier
Member
Conceptual software architecture Illustrative / not client work
03

Permissions

Match access to role and responsibility.

Roles and permissions must be defined against project requirements. No role or permission model should be assumed automatically.

Conceptual software architecture Illustrative / not client work
04

Information design

Show the right context at the right moment.

Interface hierarchy can distinguish action, status, history, supporting documents and exceptions without overwhelming the user.

05

Security & data

Confirm responsibility and controls explicitly.

Access, data handling, authentication, retention, audit needs and client responsibilities require project-specific assessment.

Next assembly / Project brief

What should the software actually do?

Tell us about the business problem, current workflow, users, systems and the outcome you are trying to achieve.

Discuss a Software Project