System Results
Chapter IV opens with the System Results - what the prototype actually does, with screenshots and feature walkthroughs.
Chapter IV - System Results
What this section does
Reports what the prototype actually does. Walks the reader through the delivered system module by module, with screenshots and short descriptions.
Module walkthrough format
For each module include:
| Element | Content |
|---|---|
| Module name | Ordering, Inventory, SMS, Reporting |
| Screenshot | At least one, captioned as Figure 4.x |
| Key actions | What the user clicks; expected outcome |
| Objective mapped | Which Specific Objective from Chapter I |
Feature-to-objective mapping (Table 4.0)
| Specific Objective | Delivered feature |
|---|---|
| 1. Identify requirements | SRS in Appendix A |
| 2. Design architecture + DB + UI | ERD, mockups, architecture |
| 3. Develop the proposed system | All five modules |
| 4. Integrate SMS notification | SMS module |
| 5. Evaluate usability and acceptance | Section 4.4 below |
Module summary
| Module | Purpose | Figure |
|---|---|---|
| Ordering | Place + cancel orders | 4.1 |
| Inventory | Track stock; auto-decrement | 4.2 |
| SMS | Notify customer on order-ready | 4.3 |
| Customer | Customer record + history | 4.4 |
| Reporting | Daily sales + low-stock alerts | 4.5 |
Worked example - Ordering module paragraph
Figure 4.1 shows the order placement screen used by counter staff to create new orders. The interface follows the workflow observed during requirements gathering: staff search for products by name or category, add them to a draft order, set the customer's contact number, and submit. Confirmation appears with a unique order ID and an SMS notification queued for the customer.
This module satisfies Specific Objective 3 (develop the proposed system using PHP, MySQL, responsive HTML/CSS) and Specific Objective 4 (SMS notification integration).
Mentor's tip
Every Specific Objective from Chapter I must appear here as 'delivered.' If you cannot map an objective to a feature, the panel will catch the gap.
Panel defense checklist
- [ ] Every module described with at least one screenshot.
- [ ] Screenshots are clear and labelled with figure numbers.
- [ ] Feature-to-objective mapping table is present.
- [ ] No screenshots from the design phase (only the actual delivered UI).
- [ ] No screenshots that show fake or test data presented as real.
- [ ] Captions consistent across all figures.
Mentor’s tip: Walk through every module with at least one screenshot. Map every Specific Objective to a delivered feature in a table. If you cannot point to it on screen, the panel will assume it was never built.
Discussion
Loading…