840 Aluminium Street, Westgate, Harare

Engineering Lab

Brikaishe Engineering Lab

Eight interactive demonstrations of how software, data, intelligent systems and engineering concepts work. Change the inputs and watch each system respond.

Educational demonstrations. Simplified for explanation; not certified engineering tools. All data is fictional. Everything runs in your browser: nothing you enter is sent or stored.

JavaScript is off, so each module shows a worked example. Turn JavaScript on to change the inputs.

Module A

System architecture explorer

Choose a component to see its responsibility, what it connects to and what happens if it fails.

Fig. 01 · System architecture explorerEducational demonstration

Application components: components and connections

  • User interface (browser or app)
    • connects to API layer: request
  • API layer (defined interface)
    • connects to Authentication: verify
    • connects to Business logic: process
  • Authentication (who is asking)
  • Business logic (rules and workflows)
    • connects to Database: read / write
    • connects to External service: integrate
  • Database (records)
  • External service (payments, messaging)

API layer

Responsibility
Receives every request, routes it and returns a consistent response.
Connects to
User interface, Authentication, Business logic
If it fails
Nothing reaches the rest of the system; the interface shows errors.

All components

User interface
Shows information and collects what the user enters. If it fails: Users cannot see or enter anything, even if every other part is healthy.
API layer
Receives every request, routes it and returns a consistent response. If it fails: Nothing reaches the rest of the system; the interface shows errors.
Authentication
Confirms who is making a request and what they are allowed to do. If it fails: Signed-in actions stop; a safe design refuses access rather than allowing it.
Business logic
Applies the organisation's rules: prices, approvals, eligibility, workflows. If it fails: Requests are received but cannot be processed.
Database
Stores records permanently and keeps them consistent. If it fails: Data cannot be read or saved; backups decide what can be recovered.
External service
Provides a capability from another provider, such as payments or messages. If it fails: Only the features that depend on it stop, if the integration is designed to degrade gracefully.
Simplified for explanation. Not a certified engineering tool.

Module B

Database visualiser

Three related tables. Run a query to see the SQL, the result and which rows it used.

Fig. 02 · Database visualiserFictional demonstration data
learners
learner_idnametown
L1AlexNorthfield
L2ChipoRiverside
L3FaraiNorthfield
courses
course_idtitlelevel
C1MathematicsForm 4
C2PhysicsForm 4
C3ProgrammingBeginner
enrolments
learner_idcourse_idstatus
L1C1active
L1C3active
L2C1completed
L2C2active
L3C3active

SQL

SELECT c.title, e.status
FROM enrolments e
JOIN courses c ON c.course_id = e.course_id
WHERE e.learner_id = 'L1';

Result

titlestatus
Mathematicsactive
Programmingactive

Highlighted rows in the tables above are the ones the query used.

All names and values are fictional. No real company or customer data is shown.

Module C

API flow explorer

Follow a request through each stage of a server and see where, and why, it can be refused.

Fig. 03 · API flow explorerEducational demonstration

Request

GET /api/courses
  1. ClientpassedThe browser sends the request.
  2. GatewaypassedWithin the rate limit; routed to the courses service.
  3. AuthenticationskippedPublic endpoint: no sign-in needed.
  4. ValidationpassedNo input to validate.
  5. HandlerpassedHandler asks for published courses.
  6. Databasepassed3 rows read.
  7. Responsepassed200 OK returned with the list.

Response 200 OK

[{ "id": "C1", "title": "Mathematics" }, { "id": "C2", "title": "Physics" }, { "id": "C3", "title": "Programming" }]
Simplified for explanation. Not a certified engineering tool.

Module D

AI workflow explorer

Ask a question of a small, fictional knowledge base and inspect every stage: processing, retrieval, response and validation.

Fig. 04 · AI workflow explorerFictional demonstration data

Scripted demonstration. This module uses keyword matching and fixed templates. It does not use a machine-learning model; it shows the stages a real AI application goes through.

  1. 1 · User inputWhich courses do you offer?
  2. 2 · Input processingKeywords: which, courses, offer
  3. 3 · Context retrievalCourses: 2 · Opening hours: 0 · Enrolment: 0
  4. 4 · Reasoning (scripted)Best match: Courses
  5. 5 · Response generationFrom "Courses": Example Academy offers Mathematics, Physics and Programming courses for Form 4 and beginner learners.
  6. 6 · Output validation
    • Pass: Answer is based only on retrieved information
    • Pass: No personal data in the answer
    • Pass: Within the length limit (300 characters)
  7. 7 · User responseFrom "Courses": Example Academy offers Mathematics, Physics and Programming courses for Form 4 and beginner learners.
The fictional knowledge base (5 entries)
Opening hours
Example Academy is open Monday to Friday from 08:00 to 17:00 and on Saturday from 08:00 to 12:00.
Courses
Example Academy offers Mathematics, Physics and Programming courses for Form 4 and beginner learners.
Enrolment
To enrol, a learner completes the online form and an administrator confirms the place within two working days.
Fees
Fees are charged per term; the office provides the current fee schedule on request.
Location
Example Academy is located at 1 Sample Road, Northfield.
All names and values are fictional. No real company or customer data is shown.

Module E

Algorithm visualiser

Step through how a computer sorts a list or finds a value, one comparison at a time.

Fig. 05 · Algorithm visualiserEducational demonstration

List 7, 3, 9, 1, 6, 4, 8, 2

Start: compare neighbours and swap them when they are out of order.

Step 1 · Comparisons 0 · Swaps 0

Simplified for explanation. Not a certified engineering tool.

Module F

Automation workflow builder

Connect a business event to a sequence of actions, then run a simulation. Actions need the right data from their trigger.

Fig. 06 · Automation workflow builderFictional demonstration data

Workflow

  1. New enquiry received
  2. Send confirmation email
  3. Create a CRM record
  4. Notify the team on WhatsApp
  5. Schedule a follow-up in 3 days

Simulation log

  1. +0s Trigger: New enquiry received.
  2. +2s Send confirmation email: Confirmation email queued to the customer.
  3. +3s Create a CRM record: Customer record created.
  4. +4s Notify the team on WhatsApp: Team notified in the sales group.
  5. +5s Schedule a follow-up in 3 days: Follow-up task scheduled for a team member.
  6. +5s Workflow finished.
All names and values are fictional. No real company or customer data is shown.

Module G

Engineering visualiser

Two classic ideas from aerospace and control engineering: the physics of a banked turn, and a feedback controller tracking a target.

Fig. 07 · Banked turnEducational demonstration
Load factor (n = 1 / cos φ)
1.15 g
Stall speed increases by (√n)
× 1.07
Turn radius (v² / g·tan φ)
441 m
Time for a full circle
55 s

A level, coordinated turn. Steeper banks need more lift, which raises the load and the stall speed.

Simplified for explanation. Not a certified engineering tool.
Fig. 08 · Feedback controlEducational demonstration
System output against the target over ten secondstarget10 s
Overshoot
0.0 %
Settling time (2 %)
6.9 s
Remaining error
0.6 %

A PI controller on a simple first-order system. Higher Kp responds faster; Ki removes the remaining error but can cause overshoot.

Simplified for explanation. Not a certified engineering tool.

Module H

Software development lifecycle

How an idea becomes working software, and the check that must pass before each next stage.

Fig. 09 · Software development lifecycleEducational demonstration
  1. 01 · Requirements

    Agree what problem is being solved, for whom, and how success will be measured. Outputs: User needs, scope, acceptance criteria. Quality gate: The owner confirms the requirements.

  2. 02 · Architecture

    Choose the main components, how they communicate and where data lives. Outputs: Architecture diagram, key decisions and their reasons. Quality gate: The design meets security, cost and performance needs.

  3. 03 · Design

    Specify screens, data structures and interfaces in detail. Outputs: Interface designs, data model, API definitions. Quality gate: Designs reviewed against the requirements and accessibility.

  4. 04 · Development

    Write the code in small, reviewable changes. Outputs: Source code under version control, with tests. Quality gate: Code review; automated tests pass.

  5. 05 · Testing

    Check behaviour, security, accessibility and performance. Outputs: Test results and fixed defects. Quality gate: Every acceptance criterion is met.

  6. 06 · Deployment

    Release the tested version to users safely. Outputs: A running release, with a way to roll back. Quality gate: The live system is verified after release.

  7. 07 · Monitoring

    Watch availability, errors and usage once people depend on it. Outputs: Alerts, logs and usage measurements. Quality gate: Problems are detected before users report them.

  8. 08 · Improvement

    Use what was measured and learned to plan the next change. Outputs: Prioritised improvements; the cycle begins again. Quality gate: The next requirements are agreed.

Simplified for explanation. Not a certified engineering tool.

Read how these ideas fit together on the Engineering page.

Request a quote (opens in a new tab)