.
Objectives of the Software
Development Plan
The main objectives of a Software Development Plan are:
Define the project scope and objectives.
Identify project activities and tasks.
Estimate time, cost, and required resources.
Assign responsibilities to team members.
Monitor and control project progress.
Ensure the project is completed on time, within budget, and with the required quality.
2. Closing Process Tasks
The Closing Process includes the following tasks:
Deliver the completed project to the customer.
Obtain customer acceptance.
Acknowledge project results.
Assess project success.
Prepare a written project evaluation.
Record lessons learned and formally close the project.
3. Work Breakdown Structure (WBS)
Definition:
A Work Breakdown Structure (WBS) is a hierarchical decomposition of the total
project work into smaller, manageable work packages that help in planning,
scheduling, assigning responsibilities, and controlling the project.
Purpose:
Break complex work into smaller tasks.
Improve planning and scheduling.
Assign responsibilities.
Monitor project progress effectively.
(If your examiner asks for the definition only, write the first paragraph.)
4. Difference between Change
Management and Risk Management
Change Management Risk Management
Deals with changes requested during Deals with uncertain events that may affect the
the project. project.
Focuses on controlling project Focuses on identifying, analyzing, and reducing
changes. risks.
Happens when a change request Starts from the beginning of the project and
occurs. continues throughout.
Objective is to manage approved Objective is to minimize threats and maximize
changes. opportunities.
5. Executing Process Tasks
The Executing Process includes:
Lead and manage the project team.
Perform project activities.
Solve project problems.
Coordinate resources.
Build the project product.
Achieve project goals according to the plan.
6. Responsibility for Contract Work
Breakdown
The responsibility includes:
Dividing the contracted work into manageable tasks.
Assigning responsibilities to team members or contractors.
Monitoring contract activities.
Ensuring contract deliverables meet project requirements.
Controlling contract performance according to the project plan.
7. Types (important for MCQs)
From the handouts:
Software Development Models
o Waterfall Model
o Rapid Prototyping Model
o Spiral Model
8. How many Project Characteristics?
The handouts describe these five main project characteristics:
1. Temporary
2. Unique Product/Service/Result
3. Aims/Tasks/Purpose
4. Limited Time Scale
5. Progressive Elaboration
9. How many Project Phases?
According to the handouts, a project has five phases:
1. Initiation
2. Planning
3. Executing
4. Controlling
5. Closing
10. How many Components (Four P's of Software
Project Management)?
There are four components (Four P's):
1. People
2. Product
3. Process
4. Project
1. Software Review Techniques
Software review techniques are:
1. Informal Review
2. Walkthrough
3. Technical Review
4. Inspection
These techniques are used to identify defects, improve software quality, and ensure
that the software meets its requirements.
2. RMMM Plan
RMMM stands for:
Risk Mitigation
Risk Monitoring
Risk Management
Components of an RMMM Plan
Identify project risks.
Analyze and prioritize risks.
Prepare mitigation strategies.
Monitor risks throughout the project.
Manage risks if they occur.
The purpose of an RMMM plan is to reduce the impact of risks on the software
project.
3. Software Maintenance
Steps and Percentage
Types of Software Maintenance
1. Corrective Maintenance
2. Adaptive Maintenance
3. Perfective Maintenance
4. Preventive Maintenance
Percentage of Total Software Project Effort
Development = 40%
Maintenance = 60%
Software maintenance generally requires about 60% of the total software project
effort.
4. Initial Effort Estimate
(Numerical)
If values are given, use:
Effort (Person-Months) = Size × Productivity Factor
or
Use the estimation formula given in the question (COCOMO or Function Point).
The question usually asks you to calculate the initial effort estimate using the
provided values.
5. Two Decomposition
Techniques
The two decomposition techniques are:
1. Problem-Based Decomposition
2. Process-Based Decomposition
These techniques are used for software cost and effort estimation.
6. Project Scheduling
Project scheduling includes:
Identify project activities.
Determine task dependencies.
Estimate task duration.
Assign resources.
Prepare the project schedule.
Monitor and update the schedule.
Common scheduling tools are:
Gantt Chart
PERT Chart
CPM (Critical Path Method)
SHORT QUESTIONS
1. What activities are involved in Risk
Management?
The activities involved in risk management are:
Risk Identification
Risk Analysis
Risk Prioritization
Risk Mitigation
Risk Monitoring
Risk Management
2. Objectives are one of many elements
of the Software Development Plan
(SDP). List any three objectives.
Any three:
Define project scope.
Define project goals and objectives.
Allocate resources.
Estimate cost and schedule.
Assign responsibilities.
Ensure project quality.
3. What are the outputs of the Initiating
Process?
Outputs of the Initiating Process include:
Project Charter
Project Objectives
Project Scope
Stakeholder Identification
Initial Project Team
4. Who is responsible for managing a
functional area's contribution within a
WBS element?
Answer:
The Functional Manager is responsible for managing a functional area's contribution
within a WBS element.
LONG QUESTIONS
1. What are the four steps to calculate
the Function Point estimates for a
project?
The four steps are:
1. Count Information Domain Values.
2. Calculate Unadjusted Function Points (UFP).
3. Determine the Value Adjustment Factor (VAF).
4. Calculate Adjusted Function Points (AFP).
2. List five key steps involved in the
Software Project Risk Management
Process.
1. Risk Identification
2. Risk Analysis
3. Risk Prioritization
4. Risk Mitigation Planning
5. Risk Monitoring and Management
3. Enlist the names of three most
common methods to represent the
schedule of a project.
1. Gantt Chart
2. PERT Chart
3. Critical Path Method (CPM)
These are the standard answers expected in CS615 Software Project Management
exams.
1. Maintenance Activities
Software maintenance activities include:
1. Corrective Maintenance – Fixes errors and defects found after software delivery.
2. Adaptive Maintenance – Modifies software to work in a changed environment.
3. Perfective Maintenance – Enhances software performance and adds new features.
4. Preventive Maintenance – Improves software to prevent future problems and increase
maintainability.
2. Software Quality Assurance
(SQA) Activities
The major SQA activities are:
Prepare the Software Quality Assurance (SQA) Plan.
Review software processes and work products.
Conduct formal technical reviews.
Ensure compliance with software standards and procedures.
Identify, report, and track defects.
Perform audits and quality assessments.
Maintain quality records and reports.
3. Project Initial Activities
(Initiating Process)
The main project initial activities are:
Identify the business need.
Define project objectives.
Develop the Project Charter.
Define the project scope.
Identify stakeholders.
Appoint the Project Manager.
Form the initial project team.
Obtain project authorization.
4. Risk Projection Activities
Risk projection (Risk Estimation) includes the following activities:
1. Estimate the probability of each risk.
2. Assess the impact of each risk on the project.
3. Determine the overall risk exposure.
4. Prioritize risks according to probability and impact.
5. Document the results in the Risk Table.
5. WBS Categories
A Work Breakdown Structure (WBS) is commonly divided into the following
categories:
1. Project
2. Major Deliverables
3. Sub-deliverables
4. Work Packages
5. Tasks/Activities
The WBS breaks the project into smaller, manageable components for planning,
scheduling, cost estimation, and control
1. Software Review Techniques
Software review techniques are:
Informal Review
Walkthrough
Technical Review
Inspection
These techniques help identify defects and improve software quality.
2. Three Basic Estimation
Processes
The three basic estimation processes are:
1. Size Estimation
2. Effort Estimation
3. Cost Estimation
3. Two System Components of
Design Decomposition
The two components are:
Data (Information)
Functional (Process)
4. What is an RMMM Plan?
RMMM stands for:
Risk Mitigation
Risk Monitoring
Risk Management
It is a document that identifies project risks, defines mitigation strategies, monitors
risks, and specifies actions if risks occur.
5. Difference between Cost-
Plus and Fixed-Price Contract
Cost-Plus Contract Fixed-Price Contract
Customer pays actual cost plus Customer pays a fixed agreed
profit. amount.
Risk is mainly on the customer. Risk is mainly on the contractor.
Suitable when requirements are Suitable when requirements are
uncertain. clear.
Cost is fixed unless scope
Cost may increase.
changes.
6. Cost and Effort Estimation
Approach
Estimate project size.
Select an estimation technique (COCOMO, Function Point, etc.).
Estimate effort.
Estimate cost.
Review and refine estimates.
Factors Considered
Project size
Complexity
Team experience
Technology
Project schedule
Resources
Risk level
Why Estimation is Critical
Helps prepare budget.
Helps create schedule.
Supports resource allocation.
Reduces project risk.
Improves project planning.
7. Five Reasons Why Software
Projects Get Delayed
Poor planning
Changing requirements
Inaccurate estimates
Lack of skilled staff
Poor communication
8. Primary Steps of Project
Planning
Define project scope.
Identify tasks.
Develop Work Breakdown Structure (WBS).
Estimate cost and effort.
Develop schedule.
Allocate resources.
Identify risks.
Prepare project plan.
9. Risk Components
The four risk components are:
Performance Risk
Cost Risk
Schedule Risk
Support Risk
10. Three Possibilities of Risk
Mitigation
Avoid the risk.
Reduce (Mitigate) the risk.
Accept the risk.
11. Activities Involved in Risk
Management
Risk Identification
Risk Analysis
Risk Projection
Risk Mitigation
Risk Monitoring
Risk Management
12. Types of Maintenance
Corrective Maintenance
Adaptive Maintenance
Perfective Maintenance
Preventive Maintenance
13. Types of Projects
Software projects can be classified as:
Concept Development Projects
New Application Development Projects
Application Enhancement Projects
Application Maintenance Projects
Reengineering Projects
14. Types/Categories of WBS
WBS generally consists of:
Project
Major Deliverables
Sub-deliverables
Work Packages
Tasks/Activities
15. Software Project
Management Steps
Initiation
Planning
Executing
Monitoring and Controlling
Closing
16. Objectives of Project
Planning
Define project scope.
Estimate cost and schedule.
Allocate resources.
Identify risks.
Achieve project objectives.
17. Estimation Techniques
Common estimation techniques are:
Function Point Analysis
Lines of Code (LOC)
COCOMO Model
Expert Judgment
Decomposition Techniques
18. Design Decomposition
Objectives (Any Three)
Reduce system complexity.
Improve modularity.
Make design easier to understand.
Improve maintainability.
Simplify testing.
19. Distinct Components of
Software Quality
Software quality includes:
Correctness
Reliability
Efficiency
Integrity
Usability
Maintainability
Flexibility
Testability
Portability
Reusability
Interoperability
20. Goal of WBS
The goal of WBS is to:
Divide the project into manageable tasks.
Improve planning.
Assign responsibilities.
Estimate cost and schedule.
Track project progress.
21. Wind-up (Closing)
Activities
Deliver the final product.
Obtain customer acceptance.
Prepare final documentation.
Record lessons learned.
Release project resources.
Close the project formally.
22. Risk Projection Activities
Estimate probability.
Estimate impact.
Determine risk exposure.
Prioritize risks.
Prepare the risk table.
23. Maintenance Activities
Corrective
Adaptive
Perfective
Preventive
24. SQA (Software Quality
Assurance) Activities
Prepare SQA Plan.
Conduct technical reviews.
Perform audits.
Ensure standards compliance.
Track defects.
Prepare quality reports.
25. Project Initial Activities
Identify business need.
Define objectives.
Develop Project Charter.
Define scope.
Identify stakeholders.
Assign Project Manager.
26. Tools and Techniques Used
for Team Development
Training
Team-building activities
Recognition and rewards
Ground rules
Co-location
Effective communication
27. Moderator and Recorder
Tasks (Technical Review)
Moderator
Plans and conducts the review meeting.
Keeps the discussion focused.
Ensures review procedures are followed.
Prepares the review report.
Recorder
Records all defects and issues.
Maintains review notes.
Documents action items.
Prepares the review summary.
28. Two Ways to Manage Risk
Risk Mitigation
Risk Monitoring
29. Factors that Can Damage a
Project
Poor planning
Unrealistic schedule
Budget problems
Poor communication
Changing requirements
Lack of skilled staff
Technical risks
30. How Do People Affect a
Project?
People affect a project through:
Skills and experience
Communication
Leadership
Teamwork
Motivation
Commitment
Coordination
These factors directly influence project quality, schedule, and success.
1. What activities are involved
in Risk Management?
The main activities involved in Risk Management are:
1. Risk Identification
2. Risk Analysis
3. Risk Projection (Risk Estimation)
4. Risk Mitigation
5. Risk Monitoring
6. Risk Management
2. Objectives is one of many
elements of Software
Development Plan (SDP). List
any three (3) points about
Objectives.
Any three objectives are:
Define the project scope and objectives.
Estimate project cost, effort, and schedule.
Allocate resources and assign responsibilities.
Other acceptable points include:
Ensure software quality.
Monitor and control project progress.
Complete the project within time and budget.
3. What are the outputs of
Initiating Process?
The outputs of the Initiating Process are:
Project Charter
Project Scope Statement
Project Objectives
Stakeholder Identification
Initial Project Team
4. Who is responsible for
managing a functional area's
contribution within a WBS
element?
Answer:
The Functional Manager is responsible for managing a functional area's contribution
within a Work Breakdown Structure (WBS) element.
Long Question 1
What are the four (4) steps to calculate
the Function Point estimates for a
project?
The four steps are:
1. Count the Information Domain Values.
2. Calculate the Unadjusted Function Points (UFP).
3. Determine the Value Adjustment Factor (VAF).
4. Calculate the Adjusted Function Points (AFP).
Long Question 2
List five key steps involved in the
Software Project Risk Management
Process.
The five key steps are:
1. Risk Identification
2. Risk Analysis
3. Risk Projection (Risk Estimation)
4. Risk Mitigation Planning
5. Risk Monitoring and Management
Long Question 3
Enlist the names of three (3) most
common methods to represent the
schedule representation of a project.
The three most common methods are:
1. Gantt Chart
2. PERT (Program Evaluation and Review Technique)
3. Critical Path Method (CPM)
These are the standard schedule representation techniques used for project planning
and tracking.
1. Software Project Risk
Management (Long Question)
Software Project Risk Management is the process of identifying, analyzing, planning,
monitoring, and controlling risks that may affect a software project.
Steps of Risk Management
1. Risk Identification
1. Identify all possible project risks.
2. Risk Analysis
1. Analyze the probability and impact of each risk.
3. Risk Projection (Risk Estimation)
1. Estimate the likelihood and consequences of each risk.
4. Risk Mitigation
1. Develop strategies to reduce or eliminate risks.
5. Risk Monitoring
1. Continuously monitor risks throughout the project.
6. Risk Management
1. Implement contingency plans if risks occur.
Objective: To minimize the impact of risks and improve the chances of project
success.
2. Intermediate COCOMO
Numerical (Long Question)
Intermediate COCOMO Formula
Effort (Person-Months) = a × (KLOC)^b × EAF
Where:
KLOC = Thousands of Lines of Code
EAF = Effort Adjustment Factor
a and b depend on the project type.
Constants
Project
a b
Type
1.0
Organic 3.2
5
Semi- 1.1
3.0
Detached 2
1.2
Embedded 2.8
0
Development Time Formula
TDEV = 2.5 × (Effort)^0.38
Exam Tip: If the paper gives values for KLOC and
EAF, substitute them directly into the formula to
calculate the effort.
3. Software Planning Tasks
(Long Question)
The major Software Project Planning tasks are:
1. Define project scope.
2. Estimate project size.
3. Estimate cost and effort.
4. Identify project risks.
5. Develop Work Breakdown Structure (WBS).
6. Prepare the project schedule.
7. Allocate resources.
8. Prepare the Software Development Plan (SDP).
4. Risk Projection (Short
Question)
Risk Projection is the process of estimating the probability and impact of each
identified risk so that risks can be prioritized.
Activities
Estimate risk probability.
Estimate risk impact.
Determine risk exposure.
Prioritize risks.
Prepare the Risk Table.
5. Closing Process (Short
Question)
If the question asks for two names from the Closing Process, you can write:
Customer Acceptance
Lessons Learned
Other valid closing activities include:
Final Project Evaluation
Project Closure
Final Documentation
Release of Project Resources
1. RMMM Plan (Handout)
The RMMM Plan
"A collection of risk information sheets developed for all
risks that lie above the cut off. A risk management
strategy can be included in the software project plan or
the risk management steps can be organized into a
separate Risk Mitigation, Monitoring and
Management Plan (RMMM). The RMMM plan
documents all work performed as part of risk analysis
and are used by the project manager as part of the
overall project plan."
ormal RMMM doc
"Once RMMM has been documented and the project
has begun, risk mitigation and monitoring steps
commence."
2. Software Development Plan
(SDP)
Software Development Plan (SDP) –
Information Needs
According to the handout, the Project Plan should contain:
1. Introduction and status of the plan
2. The authorization procedures
3. Statement of project objectives
4. Statement of requirement
5. Deliverables in the project
6. A Work Breakdown Structure (WBS)
7. The project milestones
8. The resource requirements
9. Interdependencies of work
10. The timetable of events
11. Staffing, organization and responsibilities
12. Development methods and toolsets to be used
13. Source documentation
14. Resource and financial summary
3. Function Point (FP)
The handout states:
"The FP technique is a direct indicator of the
functionality of a software application from the user's
perspective."
"The total size of a project is estimated as a single FP
value."
Four Steps to Calculate Function Point Estimates
1. Identify the Unadjusted Function Points (UFP).
2. Calculate total General System Characteristics (GSCs).
3. Calculate the Value Adjustment Factor (VAF).
4. Apply the formula to calculate Adjusted Function Points (AFP).
Advantages of Function Points
The handout lists these advantages:
Total size of the project is expressed in total Function Points.
FP is independent of programming language.
FP is independent of technology.
FP is independent of methodology.
FP can estimate any kind of software project.
FP can still be used when project requirements change during development.
4. Work Breakdown Structure
(WBS)
The handout defines WBS as:
"Work Breakdown Structure (WBS) is a technique to
decompose the project for the purpose of management
and control. It provides the framework for organizing
and managing the work."
It further explains:
A project may be divided into subprojects.
Subprojects are divided into work packages.
Work packages are further decomposed into project activities.
The handout also states:
WBS is commonly used at the beginning of a project.
It is used for defining project scope.
It helps organize Gantt schedules.
It helps estimate project costs.
WBS includes management, procurement, installation, software development, etc.
WBS is related to planning and scheduling.
It is a functional decomposition of project tasks.
5. Risk Management
The handout lists the Risk Management processes as:
1. Risk Management Planning
o Deciding how to approach and plan risk management activities.
2. Risk Identification
o Determining which risks might affect the project and documenting their
characteristics.
3. Qualitative Risk Analysis
o Prioritizing risks according to their effect on project objectives.
4. Quantitative Risk Analysis
o Measuring the probability and consequences of risks.
5. Risk Response Planning
o Developing procedures to enhance opportunities and reduce threats.
6. Risk Monitoring and Control
o Monitoring risks, identifying new risks, implementing risk reduction plans, and
evaluating their effectiveness throughout the project life cycle.