1. Logeshwari E (MCA12012)
Saranya T (MCA12027)
Kesavan S (MCA12040)
Santhanakumar P (MCA12049)
Venkadesh S (MCA12054)
Guided By,
Miss R.Indumathi MCA.,
AP/MCA
07/20/14 1
2. Project Management’s FIVE process
Software Project Management
Project Lifecycle and model
Requirements Analysis
Specification
Design and coding
Verification and validation
Implementation and installation
Maintenance and support
07/20/14 2
3. Initiating a project
Planning the project
Executing the project/plan
Controlling execution of the project/plan
Closing the project
07/20/14 3
4. A software project is considered as a software
application with specific elements.
The Lists of activities are:
Feasibility study
Planning phase
Project execution
07/20/14 4
6. Feasibility Study:
Investigation prospective project is worth
starting.
Information is gathered about requirements of
the proposed application.
Estimate:
(i)Developmental and Operational costs.
(ii)Value and benefits
07/20/14 6
7. The large project ,we would not a detailed
planning right at the beginning.
Whole project and a detailed one for the First
Stage.
Developing a realistic project plan is
essential to gain an understanding of the
resources required.
How these should be applied.
07/20/14 7
9. The execution of a project often Contains
design and implementation sub-phases.
Example:
Software product have five major components
=> groups of activities.
Individual projects are considerable classic
project life cycle.
07/20/14 9
10. A (Software/System) lifecycle model is a
description of the sequence of activities.
It provides a fixed Generic Framework.
Project specific Parameters will include:
(i)Size(person-years)
(ii)Budget
(iii)Duration
project plan=lifecycle model+ project
parameters
07/20/14 10
11. There are hundreds of different lifecycle
models.
Example:
Waterfall
Code-and-fix
Spiral Model
Rapid protoyping
Unified process(UP)
07/20/14 11
13. The users require of the system that the project
is to implement.
Several difficult approaches to the user
requirements explored.
Example:
A small system which satisfies some, but not
all, of the users needs at a low price.
Compared to a system with more functions
but a higher price.
07/20/14 13
14. Detailed documentation of what the proposed
system is to do.
Software Requirements Specification (SRS),
it is a Software system.
It is a description of the behavior of a system.
It developed by “usecase” that describe a
interactions with a system.
07/20/14 14
15. A design has to be drawn up which meets the
specification.
Design is a second phase of the Project Life
Cycle.
This design will be in 2 stages:
(i) External or User design.
(ii) Physical design.
07/20/14 15
16. 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.
It procedures are to be structured internally.
07/20/14 16
17. This may refer to writing code in a procedural
language C or Ada.
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.
07/20/14 17
18. Developed by the customer requirements.
Verification:
Analyze the quality of the project.
It verifies that the software being developed
implements all the requirements specified in
the SRS document.
Example:
Are We building the “product right”.
07/20/14 18
19. Validation:
Validation is done against the SRS(Software
Requirement Specification) document.
The correct input is given and expected result
is received.
Example:
Validation: ”Are we building the right
product”
07/20/14 19
21. In the software life cycle, the maintenance
phase is the last stage of the cycle.
Once the system has been implemented.
It is a Continuous process.
Maintenance the software.
Document and error correction.
07/20/14 21
22. They categorized maintenance activities into four
classes
Adaptive – modifying the system to cope with
changes in the software environment (DBMS, OS)
Perfective – implementing new or changed user
requirements which concern functional enhancements to
the software.
Corrective – diagnosing and fixing errors, possibly
ones found by users.
Preventive – increasing software maintainability or
reliability to prevent problems in the future.
07/20/14 22
23. Bob Hughes and MikeCotterall ”SOFTWARE
PROJECT MANAGEMENT”, Third Edition
Rames,Gopalasamy” MANAGING GLOBAL
PROJECTS”, Tata McgrawHill,2001.
Applied “Software Project Management”
Stellan &Greene SPD.
07/20/14 23