This document discusses software project management. It states that managing software projects through their entire life cycle, from initial planning through monitoring and termination, is necessary to deliver high-quality products on time. The document outlines the key aspects of software project management, including project planning, monitoring and control, quality management, maintenance, and the overall processes involved. It provides details on planning, monitoring, quality assurance, quality control, maintenance activities and models.

1. SOFTWARE
MANAGEMENT
BCA 5th Sem
DEEPAK SHARMA
12KSSB6031

2. Introduction
• To produce high-quality product, it is necessary to
manage the software project in a way that will lead to
timely delivery of a product.
• Software engineering is to manage his/her software daily
by daily.

3. Project Management
 Project is defined as a set of activities that has a definite
start and a definite end.
 Project management requires the application of
professional knowledge skills.
Project management tools and techniques to manage the
resource to deliver customer needs.
Project management activities must meet the user and
stakeholders needs and expectations from the project.
Effective project management team requires knowledge
of operating and supporting function.

4. Project management keys
DELIVERY TIME
HUMAN RESOURCES
COMMUNICATION
OUTSOURCING
COST
SCOPE OF PROJECT
QUALITY
TOOLS
RISK MANAGEMENT
PROCUREMENT
INTEGRATION

5. Project Management Process
Project management process is a complex process involving
several activities. They can be grouped under different phases.
Project planning
project management begins with a project plan before starting
of any technical activities. Project plan provides a framework or
blueprint for project management
.
Project monitoring and control
this phases concentrate on monitoring software developing
right from the scratch.
Project termination
this phase concludes the software development process. It
keeps track of project enhancement for further improvement of the
software package.

6. Project Planning
Project management begins with a project plan before starting
of any technical activities. Project plan provides a framework or
blueprint for project management
 Project schedule
 Cost estimation
 Milestone
 Project output Identification
 Risk Assessment Plans
 Risk Reduction Strategies
 Quality Control Plans
 Monitoring the overall project

7. Project Monitoring, Control And
Terminate
 Project monitoring and Control phase activities process continues
for the entire duration of the project.
 It takes care of project schedule and verifies whether software
development process activities are taking place as per project
plan.
 Project Termination phase concludes the software development
process
 It keeps track of project enhancement for further Improvement of
the software package.

8. Software Quality Management
Activities
Software Quality
management activities
Quality
assurance Quality control
Quality planning

9. Quality Management Activities
 Quality Assurance activities define a framework for achieving software quality.
This process defines standards that should be applied to the software
development process. The standards are embedded in the processes which are
applied during development.
 Quality Planning defines “What high-quality software actually means. Quality
plan is “ Project Quality Plan”. Standards refers to
1) Product Standards
2) Process Standards
 Quality Control process has its own set of procedures And reports that must
be used during software Development. Quality Control approaches
1) Quality Reviews
2) Automated software assessment

10. Software Maintenance
Software maintenance is the process of modifying
software process after it is delivered to customer.
1. Corrective maintenance: It is necessary to rectify some
errors in the system or increase the performance of the
system.
2. Adoptive maintenance: Running on new platform and it is
applied when the system has to interface with new
hardware or software.
3. Perfective maintenance: Helps to support new system
features. The users can change different functions of the
system.

11. Software Maintenance Model
 Starts with gathering required changes which needs to
be incorporated into the software.
 Analyze the changes for feasibility by applying the
different parameters.
 Draw out plan to introduce changes within the system.
 Apply the changes to the old code suitably.
 Perform integration and interface testing.

12. Software Maintenance Model
1.Gather requirements
need to be changed
2.Analyze changed
requirements
3.Plan changed
strategies
4.Apply changes to
old code
5.Integrate and test
6.Update document
with changes

13. THANK YOU