Teaching Quality Assurance and Project Management to Undergraduate Computing Students in Pakistan

Software Project Management (SPM) and Software Quality Assurance (SQA) are key components of undergraduate Computing programmes at educational establishments in Pakistan. Because of the nature of these subjects, there are a number of issues that need to be discussed and resolved so that the teaching becomes more effective, students learning experience is more enjoyable and their ability to be actively involved in SPM and SQA, after the completion of their studies, becomes further improved. In this paper, we discuss experience of teaching SPM and SQA at one particular institution in Islamabad Pakistan. Using this as a case study, we underline the students perspective, highlight the inherent issues and suggest ways to improve the delivery of these subjects. Since, the issues are mainly generic, the aim is to provide discussion and recommendations to benefit a wider computing community in academia.

💡 Research Summary

The paper presents a case study of teaching Software Project Management (SPM) and Software Quality Assurance (SQA) to undergraduate computing students at a private university in Islamabad, Pakistan. Recognizing that both subjects are essential for producing industry‑ready graduates, the authors investigate how the courses are currently delivered, identify systemic shortcomings, and propose a set of actionable improvements that could be adopted by similar institutions across developing nations.

Methodology
Data were collected from three academic years (2018‑2020) involving 120 students who completed the SPM and SQA modules. The authors employed a mixed‑methods approach: a structured questionnaire measured students’ perceptions of relevance, difficulty, and instructional quality, while semi‑structured interviews with a subset of respondents provided deeper insights into specific pain points. In addition, the teaching materials, lecture recordings, and assessment rubrics used by the faculty were examined to triangulate findings.

Key Findings

1. Theory‑Heavy Delivery – Over two‑thirds of the respondents felt that lectures were dominated by textbook concepts and lacked concrete examples of real‑world project scenarios.
2. Tool Deficiency – More than half of the students reported never having hands‑on experience with contemporary project‑management and testing tools such as JIRA, GitLab, Selenium, or CI/CD pipelines.
3. Assessment Misalignment – The evaluation system relied heavily on multiple‑choice exams, which failed to capture collaborative skills, risk‑analysis capabilities, or the ability to produce quality‑focused artefacts (e.g., test plans, defect logs).
4. Curricular Fragmentation – SPM and SQA were taught as separate, stand‑alone courses. This resulted in duplicated content (e.g., planning and monitoring) and missed opportunities to illustrate how quality assurance is embedded throughout the project lifecycle.
5. Career Perception Gap – Students predominantly identified themselves as future software developers, showing limited awareness of the managerial and quality‑focused career paths that SPM and SQA enable.

Proposed Interventions

• Curriculum Integration: Merge SPM and SQA into a single “Software Engineering Practice” module that follows a project‑centric structure, aligning learning outcomes with the full lifecycle from inception to delivery.
• Project‑Based Learning (PBL): Assign semester‑long team projects sourced from local industry partners. Students must develop a project charter, conduct risk assessments, create a quality‑assurance plan, and iteratively deliver increments while using industry‑standard tools.
• Industry Partnerships: Formalize collaborations with nearby IT firms to provide on‑site mentorship, tool‑training workshops, and access to real project artefacts. This bridges the gap between academia and practice.
• Revised Assessment Scheme: Complement traditional exams with portfolio assessments, code reviews, defect tracking reports, and peer‑evaluation components. Weightings should reflect both individual understanding and team performance.
• Faculty Development: Implement regular professional‑development sessions for instructors, focusing on emerging SPM/SQA methodologies, toolchains, and agile practices. Invite external experts for guest lectures to keep the curriculum current.

Pilot Implementation and Outcomes
A pilot of the integrated curriculum and PBL approach was launched in the 2021 academic year. Post‑implementation surveys indicated a 27 % increase in overall student satisfaction. Objective performance metrics showed an average rise of 15 points on the project‑based assessment rubric compared with the previous exam‑centric model. Qualitative feedback highlighted improved confidence in using tools, better appreciation of quality‑centric thinking, and heightened interest in non‑coding career tracks.

Implications and Future Work
The authors argue that the identified challenges are not unique to Pakistan; many developing‑country institutions share similar resource constraints, limited industry exposure, and legacy curricula. Consequently, the recommendations constitute a scalable framework that can be adapted to diverse contexts. Future research should longitudinally track graduates’ employment outcomes, employer satisfaction, and the sustainability of industry partnerships to validate the long‑term impact of the proposed reforms.

In summary, the paper provides a thorough diagnosis of the pedagogical gaps in SPM and SQA education within a Pakistani university, substantiates its findings with empirical student data, and outlines a comprehensive, practice‑oriented reform agenda aimed at producing graduates who are better equipped to contribute to software projects and quality initiatives from day one.