Related Systems
Related Systems is where you analyse other implementations that solve a similar problem. The standard write-up covers what each system does, how it differs from yours, and what feature you will retain or improve.
What Counts As A Related System
| Type | Examples |
|---|---|
| Commercial product | Sprout HR, Microsoft Dynamics 365 |
| Academic prototype | Thesis projects from prior years in your library |
| Open-source project | LimeSurvey, OpenEMR, Moodle |
| In-house tool | An Excel macro currently used by the beneficiary |
Standard Write-Up Structure
For each related system, cover these in two paragraphs:
- Name, developer, year, deployment context.
- Key features and target users.
- Strengths relevant to your problem.
- Limitations or gaps.
- Implication for your design.
Comparison Table (Template)
| System | Year | Platform | Key Features | Strengths | Limitations | Implication |
|---|---|---|---|---|---|---|
| System A | 2022 | Web | Login, attendance, leave | Mature, multi-tenant | Costly, foreign | Adopt the leave UX |
| System B | 2023 | Mobile | Biometric, payslip | Local context | Bank-only | Borrow biometric flow |
| System C | 2024 | Desktop | Simple, offline | Lightweight | No reporting | Avoid the offline model |
| Proposed | 2026 | Web + Mobile | Same scope plus dashboards | PH-localised | Single-tenant | - |
Why Panels Love This Section
Panels grade this section on **what you chose not to copy**. Stating limitations explicitly shows critical thinking and justifies your design decisions later.
Discussion
Loading…