INTERLUDE SOFTWARE LTD
The work betweenSoftware / infrastructure / information

Software, data and infrastructure—planned as one working system.

For organisations connecting applications, preparing records or planning a service environment, the useful starting point is the same: understand what needs to happen between the parts.

A connected system cross-sectionFive compartments connect requirements, systems, infrastructure, processing and retrieval along a common information path.REQUIREMENTSSYSTEMSINFRASTRUCTUREPROCESSINGRETRIEVALdefine the needconnect the partssupport operationprepare the recordsfind the material
An information path, viewed in section. Each connection needs a defined purpose.
01 / System design

Define what the
system has to do.

Requirements connect people, applications and recordsPEOPLE + TASKSOperational needAPPLICATION BOUNDARYInputs → decisions → outputsEXISTING RECORDSSources + ownershipReviewable result
Illustrative architecture: define the boundary before choosing the implementation.

Computer systems design connects an operational need with a technical structure.

Begin with users, tasks, information sources and the points where work changes hands. Identify existing applications and the constraints any new component must respect.

A design brief can establish functional requirements, application boundaries, integration points and component responsibilities. Depending on scope, useful outputs include requirements documents, architecture diagrams, interface specifications and acceptance criteria.

A decision worth making early

When applications exchange records, which system holds the authoritative field? Define ownership and recovery behaviour before relying on the connection.

02 / Infrastructure + hosting

Give software an
operating environment.

Hosting is a set of operating decisions: resources, dependencies, access and responsibility.

Establish what needs to run, expected usage patterns, platform constraints and deployment responsibilities. A useful brief also addresses backup, recovery, monitoring and maintenance requirements.

Application

The service people use

Identify websites, applications and connected services, including their deployment requirements.

Runtime

The conditions it depends on

Record configuration, service dependencies and access arrangements for each environment.

Storage

The information it holds

Define storage needs and agree responsibilities for backup, restoration and ongoing operation.

Possible outputs: an environment inventory, configuration plan, deployment procedure and operational handover notes.

03 / Data preparation

Turn incoming records
into usable inputs.

Source files and destination systems rarely describe everything in the same way. Preparation makes the differences explicit: field names, date formats, identifiers and missing values all need agreed rules.

Illustrative transformation / fictional records
Received

Different conventions

item_ref A-017
recorded14/03/2026
category—
Agreed rules

Make meaning explicit

  • Trim surrounding spaces.
  • Convert dates to ISO format.
  • Flag required values for review.
Prepared

A defined schema

referenceA-017
recorded_date2026-03-14
categoryReview required

A brief may cover field mapping, format conversion, validation, duplicate identification or import-file preparation. Specify the required output alongside the rules for records that cannot be processed automatically.

Mapping specifications, transformation procedures, validation reports and exception files make the result inspectable. Preserve a relationship to source records so corrections can be traced.

04 / Information retrieval

Make information
easier to locate.

A useful search starts with how a collection is described.

Information retrieval concerns finding relevant material within a defined collection. A portal provides the interface for queries, filters and access to underlying information.

Establish what belongs in the collection, which attributes describe it, who needs access and what a useful result contains. Library and archive information also calls for attention to catalogue structure and links between records and source material.

A retrieval brief can define indexing rules, searchable fields, filters, result layouts and example queries for assessing relevance.

From collection metadata to search resultsThree offset planes show a descriptive field passing from a source record into an index and a visible result.METADATA / title + subjectINDEX / searchable fieldsRESULT / title + source link
Illustrative cutaway: the same descriptive field supports three different layers.
Across the boundaries

One requirement.
Several connected decisions.

These illustrative project patterns show how the disciplines can meet within a single brief.

Connect two applications

A connection may need an interface specification, a shared record format and an environment for the connecting process. Agree ownership and failure handling across the handoff.

Systems
Processing
Infrastructure

Open a collection to search

Records may need preparation before indexing. Define descriptive fields and result behaviour together so that the interface exposes information the collection can support.

Preparation
Retrieval
Portal

Move a website environment

A hosting decision begins with an inventory of dependencies. Identify configuration, connected services and deployment responsibilities before agreeing the move.

Hosting
Dependencies
Handover
A reviewable scope

Make the next
decision clear.

Understand

Start with the operational task.

Review the existing environment, information sources and constraints. Establish what people need to accomplish before selecting an implementation approach.

Define

Write down the boundary.

Describe outputs, dependencies, responsibilities and exclusions. Agree which examples and acceptance criteria will demonstrate a usable result.

Review

Make progress inspectable.

Where implementation is included, review points should connect the developing work to the agreed scope. Validate against representative cases and record unresolved exceptions.

Hand over

Clarify what happens afterwards.

Agree documentation, account control and continuing responsibilities. Exact stages and any ongoing services belong in the project agreement.

Before commissioning

Questions that
shape the brief.

Can the work involve existing systems?
Identify applications, interfaces, documentation and access restrictions first. These determine what can be assessed.
What if source records are inconsistent?
A representative, appropriately redacted sample helps establish transformation rules and the exceptions that need review.
Does hosting include maintenance?
The scope should distinguish infrastructure provision from application updates, monitoring and support responsibilities.
What determines cost and timing?
Requirements, dependencies, access, output complexity and acceptance criteria shape a proposal. Agree scope before committing to delivery terms.
Who controls accounts and documentation?
Record ownership, permissions and handover requirements explicitly, including any responsibilities retained by the commissioning organisation.
Company imprint

About Interlude.

INTERLUDE SOFTWARE LTD works across computer systems design and related services, computing infrastructure, data processing, web hosting, web search portals and information retrieval.

The activity range also encompasses library, archive and other information services. The common thread is how information is structured, moved and found.

Company addressFlat 20 Collingwood Court, The Strand, Brighton Marina Village BRIGHTON, BN2 5WH United Kingdom
Begin with the task

Describe what
needs to work.

Outline the operational task, the systems or information involved and the output you need. Include known constraints and any target date. An initial overview is enough; keep credentials and confidential datasets out of the enquiry.