About this previous year paper
KIT071 – SOFTWARE PROJECT MANAGEMENT
B.Tech (SEM VII) – Theory Examination
Time: 3 Hours | Max Marks: 100
SECTION A
(Attempt all questions in brief – 2 marks each)
a. Define S.M.A.R.T.
S.M.A.R.T. stands for Specific, Measurable, Achievable, Relevant, and Time-bound. It is used to define clear and effective project goals.
b. What do you mean by Software Project Estimation?
Software project estimation is the process of predicting effort, cost, duration, and resources required to complete a software project successfully.
c. Write different approaches used in identifying activities.
Different approaches are: Top-down approach
Bottom-up approach Analogy-based approach
Expert judgment
d. Define organization.
An organization is a structured group of people working together with defined roles, responsibilities, and authority to achieve common objectives.
e. Write different types of cost related to project development.
Types of costs include: Personnel cost
Hardware and software cost Training cost
Maintenance cost
f. Define Walkthroughs.
A walkthrough is an informal review technique where developers present their work to peers to identify errors and improve quality.
g. Differentiate between verification and validation.
Verification checks whether the product is built correctly, while validation checks whether the right
product is built according to user requirements.
h. How is change control process handled in software project?
Change control is handled by formally evaluating change requests, analyzing impact, getting approval, and updating project documents and baselines.
i. State the uses of Software Project Management tools.
SPM tools are used for: Project planning and scheduling
Resource allocation Cost tracking
Risk management
j. Define risk management.
Risk management is the process of identifying, analyzing, and controlling potential risks that may affect project success.
SECTION B
(Attempt any three – answers provided for ALL)
2(a). Software Project Management and its Need. Structure of SPM Plan
Software Project Management (SPM) involves planning, organizing, monitoring, and controlling software projects to ensure they are completed on time, within budget, and with required quality.
Need for SPM: Manages complexity
Controls cost and schedule Ensures quality
Handles risks
Structure of Software Project Management Plan (SPMP):
Project overview Scope and objectives
Schedule and milestones Resource plan
Risk management plan Quality assurance plan
2(b). Work Breakdown Structure (WBS), types, and role of WBS dictionary
WBS is a hierarchical decomposition of a project into smaller, manageable components.
Types of WBS: Deliverable-based WBS
Phase-based WBS Task-based WBS
Role of WBS Dictionary:
It provides detailed descriptions of each WBS element including scope, cost, schedule, and responsibility.
2(c). Project Monitoring and Control & its Dimensions
Project monitoring and control ensure that project performance matches the plan.
Dimensions include: Schedule control
Cost control Quality control
Risk control Scope control
Monitoring helps detect deviations early and apply corrective actions.
2(d). Various types of Testing Strategies
Testing strategies include: Unit testing
Integration testing System testing
Acceptance testing Regression testing
Each strategy ensures defect detection at different development stages.
2(e). Risk identification in software development and categories
Risk identification points: Unclear requirements
Technical complexity Resource shortage
Schedule pressure
Risk categories: Project risks
Technical risks Business risks
SECTION C
3(a). SPM framework and objectives
SPM Framework includes: Planning
Scheduling Risk management
Quality management Monitoring and control
Objectives: Deliver software on time
Maintain quality Minimize risk
Optimize resources
3(b). Project Plan and types
A project plan is a formal document defining project execution.
Types of project plans: Quality plan
Risk management plan Schedule plan
Cost plan
4(a). Project scheduling techniques
Scheduling techniques include: Gantt Chart
PERT CPM
PERT (Program Evaluation and Review Technique):
PERT uses probabilistic time estimates to handle uncertainty and identify critical activities.
4(b). Importance of critical path and PERT/CPM
Even with one person, the critical path helps identify the minimum project duration.
PERT/CPM helps: Identify dependencies
Optimize schedule Reduce delays
5(a). Software review and types
Software reviews evaluate work products to detect defects early.
Types: Walkthroughs
Inspections Technical reviews
Management reviews
5(b). Earned Value Indicators and short notes
Earned Value Indicators: Planned Value (PV)
Earned Value (EV) Actual Cost (AC)
Error Tracking:
Process of logging, monitoring, and fixing defects.
Cost Variance (CV):
Difference between EV and AC.
Pair Programming:
Two developers work together to improve code quality.
6(a). Software quality factors and SEI CMM vs ISO 9000
Quality factors: Reliability
Usability Efficiency
Maintainability
Difference:
SEI CMM focuses on process maturity levels, while ISO 9000 focuses on quality standards and documentation.
6(b). Types, levels, and strategies of testing
Levels: Unit
Integration System
Acceptance
Strategies: Black-box testing
White-box testing Grey-box testing
7(a). Risk identification and categories
Important points: Early identification
Risk prioritization Risk mitigation planning
Categories:
Schedule risk Cost risk
Technical risk Organizational risk
7(b). Software Configuration Management (SCM)
SCM manages changes to software artifacts.
Configuration items: Source code
Design documents Test cases
SCM tasks: Version control
Change control Configuration auditing
Example: Git managing different versions of code.