Technical Feasibility
Technical Feasibility lists the hardware and software needed to run the proposed system. Specifications must be realistic for the client.
Technical Feasibility (Hardware + Software)
What this section does
Lists the minimum hardware and software needed to develop AND run the proposed system. The panel will check that the client can actually obtain these resources.
Table 3.1 - Deployment hardware
| Component | Minimum specification |
|---|---|
| Server | Intel i3 or AMD Ryzen 3 equivalent |
| RAM | 4 GB |
| Storage | 256 GB SSD |
| Network | 10 Mbps wired LAN |
| UPS | 600 VA (60 min runtime) |
| Client tablet | Android 11+ or iPad 9th gen+ |
| Printer | Thermal receipt (optional) |
Table 3.2 - Deployment software
| Component | Version / notes |
|---|---|
| Operating System | Ubuntu Server 22.04 LTS |
| Web server | Apache 2.4 |
| Runtime | PHP 8.2 |
| Database | MySQL 8.0 |
| Browser (client) | Chrome 110+ / Safari 16+ |
| SMS gateway | Third-party HTTP API |
| Backup | mysqldump via cron |
Development software adds
| Tool | Purpose |
|---|---|
| Visual Studio Code | IDE |
| Git 2.40+ | Version control |
| draw.io | Diagrams |
| PHPUnit 10 | Unit tests |
| Postman | API testing |
Mentor's tip
The deployment hardware MUST be affordable for the client. A bakery cannot buy a 32-core server. If the client cannot afford the specs, your project is operationally infeasible.
Panel defense checklist
- [ ] Development hardware listed in a table.
- [ ] Deployment hardware listed in a table.
- [ ] Development software listed (IDE, build tools, version control).
- [ ] Deployment software listed with versions.
- [ ] Specifications justified against expected load (rough estimate).
- [ ] Backup and recovery hardware included.
- [ ] Specs consistent with Operational Feasibility section.
Common mistakes
- Listing aspirational specs the client cannot afford.
- Forgetting backup hardware (UPS, external drive).
- Omitting browser version for client devices.
- Listing only operating system and forgetting middleware.
Mentor’s tip: Two tables for hardware (dev + deployment), two for software. Specs must be realistic for the client to buy. Match the operational feasibility section exactly.
Discussion
Loading…