0% found this document useful (0 votes)
7 views22 pages

1.1

The document outlines the principles of software project management, defining software, projects, and the specific characteristics of software projects. It details the software project life cycle, including phases such as initiation, planning, execution, and monitoring, as well as the Waterfall model for software development. Additionally, it discusses the advantages and disadvantages of the Waterfall model and provides examples of successful projects using this approach.

Uploaded by

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

1.1

The document outlines the principles of software project management, defining software, projects, and the specific characteristics of software projects. It details the software project life cycle, including phases such as initiation, planning, execution, and monitoring, as well as the Waterfall model for software development. Additionally, it discusses the advantages and disadvantages of the Waterfall model and provides examples of successful projects using this approach.

Uploaded by

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

SOFTWARE PROJECT

MANAGEMENT
CSPE 318/ITPE318

Dr. Sweeti Sah


Assistant Professor
Department of Computer Engineering
Syllabus
Software
A set of programs which is designed for a specific operation is called software.
There two types of software:
◦ 1. System software: OS, Device drivers
◦ 2. Application software: MS-Word, Excel, VLC media player, MX player etc.
Project
A project is well-defined task, which is a collection of several operations done in order to achieve a
goal (for example, software development and delivery).
A Project can be characterized as:
1. Every project may has a unique and distinct goal.
2. Project is not routine activity or day-to-day operations.
3. Project comes with a start time and end time.
4. Project ends when its goal is achieved hence it is a temporary phase in the lifetime of an
organization.
5. Project needs adequate resources in terms of time, manpower, finance, material and knowledge-
bank.
Software Project
A Software Project is the complete procedure of software development from requirement
gathering to testing and maintenance, carried out according to the execution methodologies, in a
specified period of time to achieve intended software product.
Management
The process of dealing with or controlling things or people is called management. Management
is a set of principles relating to the functions of planning, organizing, directing and controlling a
process or job to complete successfully within the time period.
Software Project Management
Software project management is an art and discipline of planning and supervising software
projects.
It is a sub-discipline of software project management in which software projects planned,
implemented, monitored and controlled.
It is a procedure of managing, allocating and timing resources to develop computer software that
fulfills requirements.
There are three needs for software project management.
These are:
◦ 1. Time
◦ 2. Cost
◦ 3. Quality
The image above shows triple constraints for software projects.
It is an essential part of the software organization to deliver a quality product, keeping the cost within the client’s
budget and deliver the project as per schedule.
There are various factors, both external and internal, which may impact this triple factor.
Any of three-factor can severely affects the other two.
Product
A product is something that is deliverable to an internal or external customer.
Attributes of project
1. A project is a set of things that an organization decides to do to achieve its vision and goals as
well as to enhance revenues and profits. In other words, each project serves a definite purpose
that fits in with the big picture of the organization.
2. Each project has a definite beginning and a definite ending time.
3. Each project has to be executed under certain constraints. These constraints may change with
time and that is a part of the project dynamics. e.g. Availability of manpower, capital budget, drop
dead dates for project completion etc.
A product development life-cycle
It consists of the following phases:
◦ 1. Idea generation
◦ 2. Initial prototype development
◦ 3. Alpha testing
◦ 4. Beta testing
◦ 5. Production
◦ 6. Maintenance
Project Life Cycle
1. The Project Life Cycle is a series of activities which are essential for accomplishing project
objectives or targets.
2. Projects may have different dimensions and difficulty level, but, whatever the size: large or
small, may be all projects could be mapped to the given lifecycle structure.
3. This life cycle for the project includes four phases:
◦ 1. Initiation Phase
◦ 2. Planning Phase
◦ 3. Execution Phase
◦ 4. Monitoring, Controlling & Closing Phase
Project Lifecycle Models
Waterfall Model
1. Waterfall Model is a sequential model that divides software development into different phases.
2. Each phase is designed for performing specific activity during SDLC phase.
3. It was introduced in 1970 by Winston Royce.
Different Phases of Waterfall Model
1. Requirement Gathering stage: During this phase, detailed requirements of the software
system to be developed are gathered from the client.
2. Design Stage: Plan the programming language, for Example Java, PHP, .net Or database like
Oracle, MySQL, etc. Or other high-level technical details of the project.
3. Built/Implementation Stage: After design stage, it is built stage that is nothing but coding the
software. Here numbers of small programs are designed and go for their testing is called unit
testing.
4. Test Stage/Integration Testing: In this phase, you test the software to verify that it is built as
per the specifications given by the client.
5. Deployment stage: Deploy the application in the respective environment i.e. Customer
environment or market.
6. Maintenance stage: Once your system is ready to use, you may later require change the code
as per customer request.
When to use SDLC Waterfall Model?
• Requirements are not changing frequently.
• The application is not complicated and big.
• Project is short.
• Requirement is clear.
• Environment is stable.
• Technology and tools used are not dynamic and is stable.
• Resources are available and trained.
Advantages of the Waterfall Model
1. Before the next phase of development, each phase must be completed.
2. Suited for smaller projects where requirements are well defined.
3. They should perform quality assurance test (Verification and Validation) before completing
each stage.
4. Elaborate documentation is done at every phase of the software's development cycle.
5. Project is completely dependent on project team with minimum client intervention.
6. Any change in software is made during the process of the development.
Disadvantages of the Waterfall Model
1. Error can be fixed only during the phase.
2. It is not desirable for complex project where requirement changes frequently.
3. Testing period comes quite late in the developmental process.
4. Documentation occupies a lot of time of developers and testers.
5. Client’s valuable feedback cannot be included with ongoing development phase.
6. Small changes or errors that arise in the completed software may cause a lot of problems.
Some names of successful projects
using the waterfall model:
1. Energy management systems for electrical utilities
2. Rail traffic control systems for railways.
THANK YOU

You might also like