TABFlux
HomeCoursesUniversitiesProgramsForum
Contact Us

© 2026 TABFlux. All rights reserved. Built for students, by students.

ForumPrivacy PolicyTerms of ServiceContact UsContributors

Software Project Management

This course familiarizes students with different concepts of software project management mainly focusing on project analysis, scheduling, resource allocation, risk analysis, monitoring, control and software configuration management.

Select University

TU

Select Program

BSC-CSITBCA-OLDBITBCT-NEWBCT-OLDBEI-NEW

TabFlux . Software Project Management . TU . BCA-OLD

Software Project Management

0%

Course Title: Software Project Management

Course No: CAC5407

Nature of the Course: Theory + Lab

Semester: 7

Full Marks: 20 + 20 + 60

Pass Marks: 8 + 8 + 24

Credit Hours: 3

Course Description

Course Objectives

Course Contents

1. Software Project Management Concepts
8 hrs
1.1. Introduction
1.2. Project and Software project
1.3. Software project vs other project
1.4. Importance and Problems in software project management
1.5. Process of SPM
1.6. Characteristics of good project manager
1.7. Successful Software Project Manager
1.8. Overview of Software Project Planning
2. Software Project Scheduling
8 hrs
2.1. Objectives of activity planning
2.2. Work breakdown structure
2.3. Network planning model
2.4. Critical path method (CPM)
2.5. Program evaluation and review technique (PERT)
2.6. Precedence diagramming method (PDM)
2.7. Shortening project duration
2.8. Identifying critical activities
2.9. Forward pass and Backward pass
3. Software Estimation Techniques
7 hrs
3.1. Software Effort Estimation
  • Problems with over and under estimations
  • Basis of software Estimating
  • Software effort estimation techniques
  • Expert Judgment
  • Estimating by analogy
  • Bottoms-up estimating
  • Top-down approach and parametric models
4. Software Evaluation and Costing
8 hrs
4.1. Project Evaluation
  • Strategic Assessment
  • Technical Assessment
  • Cost-benefit analysis
  • Cash flow forecasting
  • Cost-benefit evaluation techniques
  • Risk Evaluation
4.2. Selection of Appropriate Report
  • Project approach: Choosing technologies
  • Choice of process models
  • Structured methods
5. Risk Management
5 hrs
5.1. Risk Identification
5.2. Planning
5.3. Evaluation and Management
5.4. Categories of Risk
5.5. Framework for dealing with risk
5.6. Evaluating Risks to the schedule
6. Software Quality Management
5 hrs
6.1. TQM
6.2. Six Sigma
6.3. Software Quality: defining and importance software quality
6.4. ISO 9126
6.5. Place of software quality in software planning
7. Software Configuration Management
7 hrs
7.1. Concept
7.2. Requirement and Elements of SCM
7.3. Baseline
7.4. SCM Repository
7.5. Versioning and version control
7.6. SCM Process
7.7. Change Control Process
7.8. Configuration Audit and Status Reporting
7.9. Case Study: Version Control Software Tools
  • Git
  • CVS
  • SVN

Laboratory Works

  1. 1.Project Management Tool Practice

Reference Books

  1. 1.Cotterell, B. H. (2018). Software Project Management. McGraw-Hill.
  2. 2.Dutt, S. C. (n.d.). Software Project Management. Pearson Education India.
  3. 3.A.S. Kelkar (n.d.). Software Project Management. PHI Learning.

Notes:

Source:

This course provides the comprehensive knowledge about Software Project Management, which encompasses with Software Project Planning, Scheduling, Cost Estimation, Risk management, Quality management and Configuration management.

The general objective of this course is to provide fundamental knowledge of software project management and corresponding software tool.

Laboratory works should be done covering all the topics listed above and a small work should be carried out using the concept learnt in each unit in the group. Work should be assigned on individual basis. Student may choose project Management tools like (MS Project, OpenProj, dot Project, Trello, Asana, ClickUp).
This syllabus follows the official BSC-CSIT curriculum of Tribhuvan University. In case of any doubt or revision, the university's published syllabus shall be considered authoritative.