Past exam question: 2082 Kartik (Back), Q6(a)
Open in the Padhaiko appCreate a bar graph to show the work schedule of any proposed work.
Solution
Concept and Role of Bar Graphs in Project Work Schedules: In engineering proposals and project management, work schedules are illustrated using horizontal bar graphs, commonly referred to as Gantt Charts. A work schedule bar graph plots scheduled activities along the vertical axis (Y-axis) and project timeline increments (weeks or months) along the horizontal axis (X-axis). The length of each horizontal bar depicts the planned duration of that activity, immediately displaying task sequences, overlapping phases, and milestone dependencies.
Proposed Project Case: Software Engineering Project (Campus ERP Development): Consider a 16-week software engineering project entitled "Development and Deployment of an Integrated Campus Management Information System (MIS)", segmented into six sequential and concurrent tasks:
- Requirements Analysis & Feasibility Study (Weeks 1–3)
- System Architecture & UI/UX Design (Weeks 3–6)
- Backend & Database Module Development (Weeks 5–11)
- Frontend Interface Integration (Weeks 8–13)
- Quality Assurance, Security & Load Testing (Weeks 11–15)
- User Acceptance Testing (UAT) & Cloud Deployment (Weeks 14–16)
Horizontal Bar Graph (Gantt Chart Work Schedule):
| Task Activity | Planned Duration | W01 | W02 | W03 | W04 | W05 | W06 | W07 | W08 | W09 | W10 | W11 | W12 | W13 | W14 | W15 | W16 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1. Requirements & Feasibility | Wk 1–3 | [=== | === | ===] | |||||||||||||
| 2. Architecture & UI Design | Wk 3–6 | [=== | === | === | ===] | ||||||||||||
| 3. Backend & DB Development | Wk 5–11 | [=== | === | === | === | === | === | ===] | |||||||||
| 4. Frontend Integration | Wk 8–13 | [=== | === | === | === | === | ===] | ||||||||||
| 5. QA & Security Testing | Wk 11–15 | [=== | === | === | === | ===] | |||||||||||
| 6. UAT & Final Deployment | Wk 14–16 | [=== | === | ===] |
Legend: [=== ===] indicates active execution period of the scheduled task. Overlapping bars illustrate concurrent task execution (e.g., frontend integration progressing alongside backend development).
Key Elements Illustrated by the Bar Graph:
- Task Dependencies: Phase 2 begins toward the conclusion of Phase 1, demonstrating that design relies on finalized system requirements.
- Concurrent Execution: Phase 3 and Phase 4 overlap between Weeks 8 and 11, indicating simultaneous backend API creation and frontend UI design to shorten overall project delivery time.
- Critical Path Monitoring: Any slippage in Backend Development (Task 3) directly postpones QA Testing (Task 5) and final Deployment (Task 6), allowing project managers to monitor and manage project risk.
The horizontal bar graph (Gantt chart) maps a 16-week software engineering project schedule across six sequential and concurrent tasks (Requirements, Architecture/UI Design, Backend Development, Frontend Integration, QA Testing, and Final Deployment). The horizontal bars visually denote task start dates, active durations, parallel execution phases, and project delivery milestones.