Baumgart Software Guide Send a brief

Custom software, traced from requirement to release.

Requirements analysis, software design and development & implementation for organisations in Singapore. Choose a demonstration project and follow one requirement through all three phases.

01 Analysestories.md

Select a requirement to trace it.

02 Designscreens.svg
S-1OfflinechecklistS-2Defect captureS-3Defect board

Wireframes of the example, not product screenshots.

03 Buildmodules.txt
  • M-1Local store and sync queueIncrement 1 · tests from the criteria of R-1
  • M-2Media upload serviceIncrement 2 · tests from the criteria of R-2
  • M-3Reporting API and exportIncrement 3 · tests from the criteria of R-3

Every module ships with automated tests.

R-1S-1 · Offline checklistM-1 · Local store and sync queueOpen the full example: Field inspection checklist app

Demonstration only: invented scenarios, not client projects and not results.

Three services, one continuous trail

Each phase starts from the artefacts of the one before. You can book a single phase or all three; the documents stay with you either way.

  1. 01

    Requirements analysis

    input
    Your idea, current process, documents and people
    artefacts
    Problem statement, Stakeholder map, User stories with acceptance criteria
    output
    Problem statement, user stories, constraints, backlog
  2. 02

    Software design

    input
    User stories and constraints
    artefacts
    Context and container diagrams, Data model, Wireframes and prototype
    output
    Architecture, data model, wireframes, decision records
  3. 03

    Development & implementation

    input
    Design artefacts and an ordered backlog
    artefacts
    Source code and history, Automated tests, Deployment pipeline
    output
    Tested software in production, runbook, handover

Demonstration projects

Four invented projects, each documented phase by phase: user stories, a container diagram, a design decision record and an increment plan. They show the shape of the work, not past clients.

demo/field-inspection
Example wireframe for Field inspection checklist app

Field inspection checklist app

Offline checklists, defect photos and a supervisor board for routine equipment inspections.

Demonstration project · not a client case

demo/stock-reorder
Example wireframe for Stock and reorder dashboard

Stock and reorder dashboard

A low-stock list, purchase order drafts and a movement ledger for one small warehouse.

Demonstration project · not a client case

demo/room-booking
Example wireframe for Meeting room booking portal

Meeting room booking portal

Live availability, check-in to keep a booking, and maintenance blocks for a shared office floor.

Demonstration project · not a client case

demo/service-desk
Example wireframe for Internal service request portal

Internal service request portal

One intake form, routing rules, an agent queue and status e-mails for IT and facilities requests.

Demonstration project · not a client case

How the demonstration projects are made

Before you write a brief

Short guides on questions buyers ask early. Every rule or figure links to its public source.

  1. G1How to prepare requirements before talking to a developer

    What to write down, what to leave open, and how to describe a feature so that everyone knows when it is done.

  2. G2Build, buy or configure: choosing how to get the software you need

    When custom development makes sense, when an off-the-shelf product is the better choice, and the risk of modifying products.

  3. G3What a discovery phase is for, and what it should not do

    Discovery explained using public guidance: its purpose, its outputs, and why stopping after discovery can be the right result.

  4. G4Fixed price or time and materials: choosing a way to work together

    How the two common contract models share risk, what public-sector guidance recommends for agile work, and what to ask for in either model.

  5. G5PDPA basics for software projects in Singapore

    The PDPA obligations that shape requirements and design: consent, purpose, retention, transfers, breach notification and data intermediaries.

What a useful first brief contains

  1. The problem in one paragraph, and who has it.
  2. The people who will use the software.
  3. What exists today: spreadsheets, forms, systems.
  4. Constraints you already know: data protection, hosting, deadlines set by others.
  5. Which phase you need, if you know.