Se Mod 5 PDF
Se Mod 5 PDF
Se Mod 5 PDF
MODULE-5
Project Planning:
Software pricing, Plan-driven development, Project scheduling, Estimation techniques.
Quality management:
Software quality,Reviews and inspections, Software measurement and metrics ,Software
standards.
➢ Project Planning
Project planning involves breaking down the work into parts and assign these to
project team members, anticipate problems that might arise and prepare tentative
solutions to those problems.
The project plan, which is created at the start of a project, is used to communicate how the
work will be done to the project team and customers, and to help assess progress on the
project.
➢ Proposal planning
The aim of planning at this stage is to provide information that will be used in setting a
price for the system to customers.
Estimates are made to discover the cost, to the developer, of producing a software system.
There is not a simple relationship between the development cost and the price charged to
the customer.
Broader organisational, economic, political and business considerations influence the price
charged.
A project plan is created that records the work to be done, who will do it, the development
schedule and the work products.
Managers use the plan to support project decision making and as a way of measuring
progress.
4.2.1 ProjectPlans
In a plan-driven development project, a project plan sets out the resources available to the project,
the work breakdown and a schedule for carrying out the work. Plans normally includes the
following sections,
1 Introduction This briefly describes the objectives of the project and sets out the
constraints (e.g., budget, time, etc.) that affect the management of the
project
2 Project This describes the way in which the development team is
organization organized, the people involved, and their roles in the team
3 Risk analysis This describes possible project risks, the likelihood of these risksarising,
and the risk reduction strategies that are proposed
4 Hardware and This specifies the hardware and
software support software required to carry out the development. If hardware has to
resource be
requirements bought, estimates of the prices and the delivery schedule may be included
5 Work This sets out the breakdown of the project into activities and
breakdown identifies the milestones and deliverables associated with each activity
Milestones are key stages in the project where progress can be assessed;
deliverables
are work products that are delivered to the customer.
Project planning is an iterative process that starts when you create an initial project plan
during the project startup phase.
▪ As more information about the system and the project team becomes available
during the project, you should regularly revise the plan to reflect requirements,
schedule and risk changes.
Procedure:
Step 1: At the beginning of planning process, identify the constraints that aere affecting the project.
The constraints are may be resources like budget, time skilled staffs. At the same time identify the
possible risks, define milestones and deliverables.
Step 2: Prepare estimated schedule and after some time review the progress identify the problems
or minor problems, minor modifications in the plan might be required at this stage.
Step 3: If serious problem, may cause delay in project, then replan the project.
Step 4: Perform the work , repeat step2, and step 3 until project is finished.
Advantages:
You estimate the calendar time needed to complete each task, the effort required and who
will work on the tasks that have been identified.
Milestones are points in the schedule against which you can assess progress, for example,
the handover of the system for testing.
Deliverables are work products that are delivered to the customer, e.g. a requirements
document for the system.
• Scheduling problems
Estimating the difficulty of problems and hence the cost of developing a solution is hard.
• Schedule representation
Graphical notations are normally used to illustrate the project schedule.( gantt charts,
barcharts.)
These show the project breakdown into tasks. Tasks should not be too small. They should
take about a week or two.
Bar charts are the most commonly used representation for project schedules. They
show the schedule as activities or resources against time.
• Project activities are the basic planning elements, each activity has,
1. A duration in calendar days or months.
2. An effort estimate, which reflects the number of person-days or person-months to
complete the work.
3. A deadline by which the activity should be completed.
4. A defined endpoint.
Solution:
1. Scheduling barchart/ gantt chart. T1, t2,… represents various tasks, the milestones
of various tasks is shown by m1,m2…starting from week 0, and every week is having
5 days of working days. Barchart is represented as,
2. Diamond symbol indicates milestone
1. The longest possible path to reach from beginning to end is referred as critical path in the
project. And activities along this path are referred as critical activities.
2. Draw the activity diagram.
3. Find the possible path from start to end
4. Find the critical path.( having max costs)
5. Highlight the critical path