0% found this document useful (0 votes)
8 views

SPM Introduction

Uploaded by

manjulanistala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
8 views

SPM Introduction

Uploaded by

manjulanistala
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 23

Software Project Management

(SPM)
Need Of Computerization :
Computer based system have become an integral
part of every field like educational, economical &
social.

Computer based systems must be developed &


maintained to satisfy the requirements &
expectations of the user’s of the concerned
organization.

Modernization of an organization is the increased


need today’s world.

1
Saving Of Manpower And Time :
Accuracy And Efficiency :
Early And Correct Decision Making
:
Immediate Response To Queries :
The computerization has many benefits. Primarily,
a computer is helpful in four major aspects of any
kind of organization:
•Time Efficiency
•Cost Effectiveness
•Huge data storage capacity and
•Simple operation
2
Project :

The dictionary definitions put a clear


emphasis on the project being a planned activity.

A project is a sequence of unique, complex, and


connected activities that have one goal or purpose
and that must be completed by a specific time,
within budget, and according to specification.

3
Software projects :

Many of the techniques of general project


management are applicable to software project
management.

But the products of software projects have certain


characteristics which make them different.

One way of perceiving software project


management is as the process of making visible that
which is invisible.

4
Invisibility:

When a physical artifact such as a bridge or road is


being constructed the progress being made can
actually be seen.

With software progress is not immediately visible.

5
Complexity:

Software products contain more complexity than


other engineered artifacts.

6
Conformity:
Software developers have to conform to the
requirements of human clients.

7
Flexibility:
The ease with which software can be changed.

However, this means that where the software


system interfaces with a physical or organizational
system, it is expected that, where necessary, the
software will change to accommodate the other
components.

This means the software systems are likely to be


subject to a high degree of change.

8
What is Project management ?
For any systems development, effective project
management is necessary to ensure that the project
meets the deadline, is developed within an
acceptable budget, and fulfills customer expectations
and specifications.

Project management is the process of


scooping, planning, staffing, organizing, directing, and
controlling the development of an acceptable system
at a minimum cost within a specified time frame.

9
Project Manager is the person responsible for
supervising a system project from initiation to
conclusion. Successful project managers possess a
wide range of technical, management, leadership,
and communication skills.

10
Process management is concerned with the
activities, deliverables, and quality standards to be
applied to all projects.

The scope of process management is all projects,


whereas the scope of project management is a
single project.

Process management is the activity of


documenting, managing, and continually improving
the process of system development.

11
Management :
Software Project Management module suggested that
management involves the following activities:

Planning – deciding what is to be done;


Organizing – making arrangements;
Staffing – selecting the right people for the job. Etc;
Directing – giving instructions;
Monitoring – checking on progress;
Controlling – taking actions;
Innovating – coming up with new solutions;
Representing – Liaising with users, etc.

12
Activities Covered By SPM

Feasibility study
How do we
do it?

o rth
Is i t w
g? Plan
doin
Do it!

Project execution

13
The Feasibility Study:
This is an investigation into whether a prospective
project is worth starting. Information is gathered
about the requirements of the proposed application.

The probable developmental and operational costs,


along with the value of the benefits of the new system
are estimated.

14
Planning:
If the feasibility study produces results which
indicate that the prospective project appears
viable, planning of the project can take place.

15
Project Execution:
The Project can now be executed.

The execution of a project often contains design


and implementation sub-phases. Essentially, design
is thinking and making decisions about the precise
form of the products that the project is to create.

In the case of software, this could relate to the


external appearance of the software, that is, the
user interface, or the internal architecture.

16
SDLC
Requirements
analysis

Specification

Design

Coding

Verification &
Validation

Implementation
installation

Maintenance &
support 17
Requirements analysis :
 This is finding out in detail what the user
require of the system that the project is to
implement.

 Some work along with these lines will


almost certainly have been carried out when the
project was evaluated, but now the original
information obtained needs to be updated and
supplemented.

 Several different approaches to the user


requirements may be explored. For example, a small
system which satisfies some, but not all of the users
needs at a low price might be compared to a system
with more functions but a higher price. 18
Specification :
Detailed documentation of what the proposed system
is to do.

Design :
A design has to be drawn up which meets the
specification.
As noted earlier, this design will be in two stages.
One will be the external or user design concerned
with the external appearance of the application.
The other produces the physical design which tackles
the way that the data and software procedures are to
be structured internally.
19
Coding :

This may refer to writing code in a procedural


language such as C or Object oriented languages
such as VB, C++, Java or new technology such
as .NET etc.

Even where software is not being built from scratch,


some modification to the base package could be
required to meet the needs of the new application.

20
Implementation/Installation :
Some system development practitioners refer to the
whole of the project after design as ‘implementation’
(that is, the implementation of the design) while others
insist that the term refers to the installation of the
system after the software has been developed.

In this latter case it includes setting up operational


data files and system parameters, writing user
manuals and training users of the new system.

21
Maintenance and support :
Once the system has been implemented there is a
continuing need for the correction of any errors that
may have crept into the system and for extensions
and improvements to the system.

Maintenance and support activities may be seen as a


series of minor software projects.

22
Plans, Methods and
Methodologies:
Analyze the requirements for the software.
Derive and write test cases that will check that
each Requirement has been satisfied.
Create test scripts and expected results for each
test case.
Compare the actual results and the expected
results and
Identify discrepancies.
23

You might also like