SlideShare a Scribd company logo
5
Most read
11
Most read
12
Most read
SOFTWARE 
MANAGEMENT 
BCA 5th Sem 
DEEPAK SHARMA 
12KSSB6031
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.
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.
Project management keys 
DELIVERY TIME 
HUMAN RESOURCES 
COMMUNICATION 
OUTSOURCING 
COST 
SCOPE OF PROJECT 
QUALITY 
TOOLS 
RISK MANAGEMENT 
PROCUREMENT 
INTEGRATION
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.
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
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.
Software Quality Management 
Activities 
Software Quality 
management activities 
Quality 
assurance Quality control 
Quality planning
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
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.
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.
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
THANK YOU

More Related Content

PDF
Project Planning in Software Engineering
PPTX
Software project management introduction
PPTX
Maintenance & Re-Engineering of Software
PPTX
Software engineering project management
PPTX
Project Scheduling
PPTX
4 p’s of management spectrum and the w5hh principle
PPTX
Unit 1 OOSE
PDF
5. ch 4-principles that guide practice
Project Planning in Software Engineering
Software project management introduction
Maintenance & Re-Engineering of Software
Software engineering project management
Project Scheduling
4 p’s of management spectrum and the w5hh principle
Unit 1 OOSE
5. ch 4-principles that guide practice

What's hot (20)

DOCX
Pharmacy management system Requirement Analysis and Elicitation Document
DOC
127801976 mobile-shop-management-system-documentation
PDF
Software engineering lecture notes
PDF
Library Management System
DOCX
Library Management system requirements
DOCX
Billing and Invoice Management System
PPTX
Mobile Phone Shop
DOCX
SRS for Hospital Management System
PPTX
Distributed Operating System
PPTX
Online Food Ordering System
PDF
Software Engineering - Basics
PPTX
Use case of hospital managment system
PPT
Software Metrics
PPTX
Hospital Management System.pptx
PPT
Requirement change management
PPTX
Prototype Model
PPT
Student feedback system
PPSX
Student feedback system
PPTX
Blood Bank Management System
Pharmacy management system Requirement Analysis and Elicitation Document
127801976 mobile-shop-management-system-documentation
Software engineering lecture notes
Library Management System
Library Management system requirements
Billing and Invoice Management System
Mobile Phone Shop
SRS for Hospital Management System
Distributed Operating System
Online Food Ordering System
Software Engineering - Basics
Use case of hospital managment system
Software Metrics
Hospital Management System.pptx
Requirement change management
Prototype Model
Student feedback system
Student feedback system
Blood Bank Management System
Ad

Similar to 4.software management (20)

PPTX
Soft mgmt
PPTX
Software management
PPT
Project planning
DOCX
What is software quality management
PPTX
Software quality assurance
PPTX
software project management
PPT
1 Quality Assurance Presentation
PDF
Software Quality Assurance- Introduction
PPT
unit-5-1.ppt
PPT
unit-5-1.ppt
PPT
Cba Ipi Cmm Intro Session 2 Level 2
PPTX
Unit 1 spm
PPTX
Unit 1 spm
PPT
PPTX
Software Engineering and Project Management - Introduction to Project Management
PPT
GATPO_Software.ppt
PPT
Quality Management in Software Engineering SE24
PDF
Chapter 1 - Intro to Software Project Management.pdf
PPT
unit-1.ppt
PPTX
Project management Scheduling software engineering.pptx
Soft mgmt
Software management
Project planning
What is software quality management
Software quality assurance
software project management
1 Quality Assurance Presentation
Software Quality Assurance- Introduction
unit-5-1.ppt
unit-5-1.ppt
Cba Ipi Cmm Intro Session 2 Level 2
Unit 1 spm
Unit 1 spm
Software Engineering and Project Management - Introduction to Project Management
GATPO_Software.ppt
Quality Management in Software Engineering SE24
Chapter 1 - Intro to Software Project Management.pdf
unit-1.ppt
Project management Scheduling software engineering.pptx
Ad

More from Deepak Sharma (9)

PPT
8.flip flops and registers
PPTX
2.software requirement specification
PPTX
PPTX
6.applet programming in java
PPTX
9.cs instrset
PPTX
5.interface and packages
PPTX
10.data transmission
PPTX
7.error management and exception handling
PPTX
3.software testing
8.flip flops and registers
2.software requirement specification
6.applet programming in java
9.cs instrset
5.interface and packages
10.data transmission
7.error management and exception handling
3.software testing

4.software management

  • 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