| Week | Labs (Monday) | Monday lecture | Wednesday lecture |
| 1: Jan 2-4 | No lab (VIU closed) | No lecture (VIU closed) | Course overview, project expectations, role of the system analyst |
| 2: Jan 9-11 | Lab 1/2: Team formation, project administrivia, project ideas/discussion | Identifying opportunities for change, JAD techniques | Project proposals, feasibility analysis, cost benefit analysis, scope refinement |
| 3: Jan 16-18 | Running reviews and meetings, presenting ideas, extracting feedback and acting on it | Project life cycles, team members and roles | |
| 4: Jan 23-25 | Lab 3: team proposals, feasibility analysis, recommendations | Project management, the project plan | Project tasks, metrics, and scheduling |
| 5: Jan 30-1 | Lab 4: project plan | Risk analysis and management | Requirements types, gathering, and documentation |
| 6: Feb 6-8 | CANCELLED | CANCELLED | Optional project working session |
| 7: Feb 13-15 | no lab (VIU closed) | no lecture (VIU closed) | risk analysis and management plan
Requirements, use cases, viewpoints, scenarios |
| Study days Feb 20-24 | |||
| 8: Feb 27-1 | Project working session - teams are to conduct user interviews/walkthroughs to obtain feedback on their project ideas/features/interfaces | Process and sequence modeling | |
| 9: Mar 6-8 | Lab 7: Presentation dry run, revision | Data design and modeling, architectural design | Team project presentations |
| 10: Mar 13-15 | Lab 8: process model | Transactional data systems and data integrity | Inspections and reviews, prep for in-class inspection |
| 11: Mar 20-22 | Lab 9: data model | In-class inspection exercise | User guidance and education |
| 12: Mar 27-29 | Lab 10: architectural design | System rollout, changeover | System maintenance and support, patches and updates |
| 13: Apr 3-5 | Lab 11: project working session | Privacy and security | Final exam review |
| 14: Apr 10-12 | Lab 12: project demos | Final presentations | No lecture (VIU study days) |