UNIT 1

FUNDAMENTALS OF SOFTWARE PROJECT PLANNING

DEFINE
OBJECTIVE
STEPS
5 MAJOR FUNDAMENTALS

DEFINE: basically it is an management process which focuses on activities jisse

hamara project successfully complete ho. It prevent obstacles that arise in projects,
non availability of resources and so on…… obstacles means problems…
OBJECTIVE: To provide a framework that enables the manager to make estimates
of resources, cost and schedules and ye estimates tab milte hai jab hum clients ke saath
project discuss krte hai….
5 MAJOR FUNDAMENTALS:
1. PROJECT INITIATIONS
2. DETERMINING PROJECT FEASIBILTY (Feasibilty means kitna easy or difficult
hai)
3. ACTIVITY PLANNING AND CONTROLLING
4. PROJECT SCHEDULING
5. MANAGING SYSTEM ANALYSIS SYSTEM
STEPS:

1.Create and analyze business case

2.Define project scope
3.Set goals and objectives
4.Create project schedule
5.Given link is for explanation of software project.

https://www.youtube.com/watch?v=V-4yE4PmJ90
 CONVNETIONAL SOFTWARE MANAGEMENT

• Three analyses of the state of the software

engineering industry as of mid 1990s yielded:
• Software Development is still highly unpredictable
• Only about 10% of software projects are delivered successfully
on time, within initial budget, and meets user requirements
• The management discipline is more of a discriminator in success
or failure than are technology advances
• The level of software scrap and rework is indicative of an
immature process.
The waterfall model:
•In software engineering the waterfall model
is conventional software development
process and it treated as benchmark of that
process.
Waterfall in theory: The waterfall model
made three primary points.
a) There are two essential steps common to
the development of computer programs:
Analysis and coding.
b) To control intellectual freedom associated
with software development, we introdu ce
system requirements, software
requirements, program design and testing.
c) The basic framework in the waterfall
model is risky and invites failure.
The following diagram shows waterfall model
profile and the basic steps.
•The following are five improvements to the
basic waterfall process to eliminate the
development risks.

• 1)Program design comes first

• 2)Document the design
• 3) Do it twice
• 4) Plan, control, and monitor testing
• 5) Involve the customer
 Software Economics
Most software cost models can be described
five parameters: Size, Process, Personnel,
Environment, and required Quality
1. The size of the end product is typically
measured in terms of number of source lines
or the number of functional points developed
to achieve the required functionality.
2. The process used to produce the end
product, the ability of the process is to avoid
non value adding activities. (rework,
bu reaucratic delays, communications
overhead)
3.The capability of software engineering
personnel, and particularly their experience
with the computer science issues and the
applications domain issues of the project.
4.The environment which is made up of the
tools and techniques available to support
efficient software development and to
automate the process.
5. The required quality of the product,
including its features, performance,
reliability and adaptability.
IMPROVEMENT OF SOFTWARE
ECONOMICS
Improving Software Economics:
Reducing Software product size, improving
software processes, improving team
effectiveness, improving automation, Achieving
required quality, peer inspections.
https://www.youtube.com/watch?v=6LC1V-AAarA

This is for modern vs traditional software mgmt……..