⚠Not open for registration. This program is currently unavailable. Please check back soon.

Advanced

AI Systems & App Development

Specify. Build. Test. Deploy. Maintain.

Every graduate can put an SRS on the table and prove they understand, built, tested and can maintain their system. Problem → Requirements → SRS → Architecture → Build → Test → Secure → Deploy → Improve.

Duration

3 Levels · 62 Practical Modules · 90% Practical

Schedule

TBA

Start date

5 December 2026

Status

Registration closed

Curriculum

Weekly breakdown

Session 1

B1 — Systems Thinking Before Software

●Students take a real manual or paper-based process from their own community (school, business, clinic, church, association) and map the current process, pain points, people, information, decisions, bottlenecks and risks.
●You walk away with: System Problem Map.

Session 2

B2 — Problem Discovery

●Students investigate how complaints are currently handled by a real organisation (school, business, landlord, public-facing service) through stakeholder interviews, user interviews and observation, using Claude only to organise findings — never to invent them.
●You walk away with: Problem Discovery Report.

Session 3

B3 — From Problem To Product

●Students define the problem statement, user need, business need, solution hypothesis, success criteria, constraints and assumptions for their chosen system.
●You walk away with: Product Vision Document.

Session 4

B4 — Requirements Engineering

●Students write business, user, functional, non-functional, data, security, reporting, integration, compliance, accessibility, performance and audit requirements for their system.
●You walk away with: Requirements Catalogue.

Session 5

B5 — User Stories & Acceptance Criteria

●Students write epics, features, user stories and numbered acceptance criteria (AC01, AC02...), using the Given / When / Then structure where appropriate.
●You walk away with: User Story Backlog.

Session 6

B6 — The Software Requirements Specification

●Students write a full SRS against the 46-section Nyande SRS Standard, from document control and problem statement through to data model, UI requirements and glossary.
●You walk away with: A complete, professional SRS.

Session 7

B7 — AI-Assisted SRS Engineering

●Students run their discovery information through problem analysis, stakeholder analysis, requirements elicitation, classification, missing-requirements analysis, conflict analysis and edge-case analysis with Claude before drafting — with the student remaining the product owner throughout.
●You walk away with: An SRS built through the full AI-assisted engineering chain, with human review recorded.

Session 8

B8 — SRS Quality Assurance

●Students stress-test their SRS against a list of failure questions — missing data, no permission, page refresh, simultaneous users, oversized files, dropped connections, mobile use — and log every gap found.
●You walk away with: SRS Review Report.

Session 9

B9 — System Architecture For Non-Engineers

●Students map their system's frontend, backend, database, authentication, storage, API and hosting, and can explain the full path from user click through server, database, response and screen update.
●You walk away with: System Architecture Map.

Session 10

B10 — Database Thinking

●Students design tables, columns, primary/foreign keys and relationships for entities like Users, Complaints, Categories, Messages, Attachments, Status History and Audit Logs.
●You walk away with: Data Model.

Session 11

B11 — User Roles & Permissions

●Students define roles — public user, registered customer, complaint officer, investigator, manager, system administrator — and specify exactly who can view, create, edit, assign, close, reopen, delete and export.
●You walk away with: Role-Permission Matrix.

Session 12

B12 — Workflow Engineering

●Students design the complaint lifecycle from Submitted through Acknowledged, Under Review, Assigned, Investigating, Awaiting Customer, Resolved, Closed and Reopened, defining who changes status, under what conditions, and what happens automatically.
●You walk away with: Complaint Workflow Specification.

Session 13

B13 — UI/UX Before Building

●Students inventory every required screen — landing page through audit log — and plan navigation, forms, validation, empty/error/loading states, mobile responsiveness and accessibility for each.
●You walk away with: Screen Inventory + Wireframe Plan.

Session 14

B14 — Turning An SRS Into A Build Plan

●Students decompose their SRS into system, modules, features, user stories, dependencies and ordered build phases (Foundation, Authentication, Submission, Tracking, Staff Management, Workflow, Notifications, Reporting, Audit, Security & Release).
●You walk away with: Implementation Roadmap.

Session 15

B15 — Prompt Engineering For Software Building

●Students write build prompts using the Nyande Build Prompt structure — context, current state, requirement reference, objective, users, functional behaviour, business rules, data, permissions, UI, validation, error handling, security, acceptance criteria, test expectation, do-not-change list and definition of done.
●You walk away with: Build Prompt Library.

Session 16

B16 — Controlled AI Development

●Students run every change through Build → Inspect → Test → Fix → Verify → Record → Next Feature, maintaining a build log, decision log, defect log and change log throughout.
●You walk away with: Build Log, Decision Log, Defect Log and Change Log.

Session 17

B17 — Building With Lovable

●Students build frontend, authentication, database, forms, workflows, dashboards, file handling and role-based functionality directly against their SRS.
●You walk away with: A working application module, built strictly to specification.

Session 18

B18 — Building Complaint Management System V1

●Students build the complete customer, staff, management, administration and system-level functionality defined in the minimum functional scope — registration, submission, tracking, assignment, dashboards, user/role management and audit.
●You walk away with: Working Complaint Management System V1.

Session 19

B19 — Software Testing Fundamentals

●Students write and execute functional, negative, boundary, UI, responsive, permission, workflow, data, integration and regression test cases, recording precondition, steps, expected and actual results.
●You walk away with: Test Scenario & Test Case Set.

Session 20

B20 — Requirements Traceability

●Students link every functional requirement to its user story, acceptance criteria, build and test cases — for example FR-CMP-001 → US-CMP-001 → TC-CMP-001 to 004.
●You walk away with: Requirements Traceability Matrix.

Session 21

B21 — Defect Management

●Students log defects with ID, title, environment, precondition, steps, expected/actual result, evidence, severity and priority, then reproduce, fix, retest and regression-test each one.
●You walk away with: Defect Log with resolved and retested entries.

Session 22

B22 — Security Fundamentals

●Students review authentication, authorisation, passwords, secrets, input validation, database permissions, file uploads, session management and access control across their own application.
●You walk away with: Security Review Checklist, applied to their own system.

Session 23

B23 — Accessibility & Mobile-First Development

●Students test their application on mobile, tablet and desktop, checking keyboard navigation, labels, error messages, contrast, focus and touch targets.
●You walk away with: Accessibility & Mobile Review Report.

Session 24

B24 — Release Readiness

●Students run SRS, functional, regression, security, permission, mobile, accessibility, data, error and backup/recovery reviews, then make a documented Go / No-Go call.
●You walk away with: Release Readiness Checklist with a Go/No-Go decision.

Practical exercises

→ Capstone: Complaint Management System V1 — Every Beginner graduate submits a complete, 25-part capstone package: Problem Discovery Report, Product Vision, Stakeholder Map, Process Map, full SRS, Requirements Catalogue, User Stories, Acceptance Criteria, Role-Permission Matrix, Data Model, Workflow Specification, Screen Inventory, Architecture Map, Implementation Roadmap, Build Prompt Library, working Lovable application, Test Scenarios, Test Cases, Requirements Traceability Matrix, Defect Log, Security Review, UAT Evidence, Release Checklist, User Guide and a Live Demonstration.

Important

Graduate title: AI Application Builder