DFP5033

SOFTWARE REQUIREMENT
& DESIGN

Chapter 3:
SOFTWARE MANAGEMENT AND DEVELOPMENT

LAILATUL AIMI
Chapter 3 :
© Oscar Nierstrasz LECTURE TITLE 1
 Roadmap
Course Overview
3.1 Elaborates software management process
3.1.1 Explain the importance of software management
3.1.2 Discuss step by steps on project planning process
3.1.3 Describe and elaborate four risk management process
◦ a. risk identification
◦ b. risk analysis
◦ c. risk planning
◦ d. risk monitoring
3.1.4 Discuss the importance of managing people and working in a teamwork
3.1.5 Elaborate the impact of having a a good project planning and scheduling

DFP5033 SOFTWARE REQUIREMENT & DESIGN

 Roadmap
Course Overview
Software Management Process
Software Development Models

DFP5033 SOFTWARE REQUIREMENT & DESIGN

© Oscar Nierstrasz LECTURE TITLE 4
 Need of software project
management

DFP5033 SOFTWARE REQUIREMENT & DESIGN

© Oscar Nierstrasz LECTURE TITLE 6
© Oscar Nierstrasz LECTURE TITLE 7
© Oscar Nierstrasz LECTURE TITLE 8
© Oscar Nierstrasz LECTURE TITLE 9
© Oscar Nierstrasz LECTURE TITLE 10
Importance of software
management . Discussion

© Oscar Nierstrasz LECTURE TITLE 11

Steps by step on project planning
process

© Oscar Nierstrasz LECTURE TITLE 12

© Oscar Nierstrasz LECTURE TITLE 13
© Oscar Nierstrasz LECTURE TITLE 14
Project planning process

© Oscar Nierstrasz LECTURE TITLE 15

Steps project planning

© Oscar Nierstrasz LECTURE TITLE 16

© Oscar Nierstrasz LECTURE TITLE 17
Initiating
This basic process includes only one detail process:

• Concept development—describing the product of the project,

documenting initial project objectives, and assigning a project manager.

© Oscar Nierstrasz LECTURE TITLE 18

Planning
Some detail planning processes have clear dependencies that require
them to be performed in sequence. For example, tasks must be defined
before they can be scheduled or costed. The dependent planning
processes include:

• Scope definition-developing a written scope statement that includes

the project justification, the major deliverables, and the project
objectives

• Project definition—decomposing the major deliverables into more

granular deliverables to provide better control (the top levels of the
Work Breakdown Structure)

© Oscar Nierstrasz LECTURE TITLE 19

Planning
• Task definition—identifying the tasks that will be performed in order to
produce the project's deliverables (the lower levels of the WBS)
• Task sequencing—identifying dependencies among tasks
• Duration estimating—estimating the probable duration of individually
scheduleable tasks and activities
• Schedule development—determining and documenting specific dates for
tasks
• Cost estimating—developing initial estimates of the overall project cost
• Cost budgeting—developing detail estimates of the cost of individual
tasks
• Plan integration—creating and documenting a coherent project plan from
the outputs of the other planning processes

© Oscar Nierstrasz LECTURE TITLE 20

Executing
Project progress must be measured regularly to identify variances from
the plan as well as to determine when the project is finished. Variances
are fed into the control processes in the various knowledge areas.
For example, a missed task finish date may require adjustments to the
current staffing plan, reliance on overtime, or trade-offs between
budget and schedule objectives.
• Progress measurement and reporting—collecting and disseminating
progress information
• Scope change management—documenting and controlling changes to
project scope

© Oscar Nierstrasz LECTURE TITLE 21

Executing
• Quality control—measuring project deliverables and activities to
assess whether quality objectives are being met
• Quality improvement—evaluating project performance on a regular
basis to determine how to improve project quality
• Time/schedule control—controlling and responding to schedule
changes
• Cost control—controlling and responding to cost changes
• Risk control—responding to changes in risk over the course of the
project

© Oscar Nierstrasz LECTURE TITLE 22

Closing
This basic process includes the following detail processes:

• Scope verification-ensuring that the project deliverables have been

completed satisfactorily

• Contract close-out—resolution of any outstanding administrative

matters and archiving of contract documentation

• Project closure—gathering and disseminating information to

formalize project completion

© Oscar Nierstrasz LECTURE TITLE 23

Activities involve in project
planning

© Oscar Nierstrasz LECTURE TITLE 24

Risk Management

© Oscar Nierstrasz LECTURE TITLE 25

© Oscar Nierstrasz LECTURE TITLE 26
© Oscar Nierstrasz LECTURE TITLE 27
© Oscar Nierstrasz LECTURE TITLE 28
© Oscar Nierstrasz LECTURE TITLE 29
© Oscar Nierstrasz LECTURE TITLE 30
© Oscar Nierstrasz LECTURE TITLE 31
© Oscar Nierstrasz LECTURE TITLE 32
© Oscar Nierstrasz LECTURE TITLE 33
© Oscar Nierstrasz LECTURE TITLE 34
© Oscar Nierstrasz LECTURE TITLE 35
© Oscar Nierstrasz LECTURE TITLE 36
© Oscar Nierstrasz LECTURE TITLE 37
© Oscar Nierstrasz LECTURE TITLE 38
© Oscar Nierstrasz LECTURE TITLE 39
Roadmap
Managing people and working in
Teamwork

© Oscar Nierstrasz LECTURE TITLE 40

© Oscar Nierstrasz LECTURE TITLE 41
© Oscar Nierstrasz LECTURE TITLE 42
© Oscar Nierstrasz LECTURE TITLE 43
© Oscar Nierstrasz LECTURE TITLE 44
© Oscar Nierstrasz LECTURE TITLE 45
© Oscar Nierstrasz LECTURE TITLE 46
© Oscar Nierstrasz LECTURE TITLE 47
© Oscar Nierstrasz LECTURE TITLE 48
© Oscar Nierstrasz LECTURE TITLE 49
© Oscar Nierstrasz LECTURE TITLE 50
© Oscar Nierstrasz LECTURE TITLE 51
© Oscar Nierstrasz LECTURE TITLE 52
© Oscar Nierstrasz LECTURE TITLE 53
© Oscar Nierstrasz LECTURE TITLE 54
© Oscar Nierstrasz LECTURE TITLE 55
© Oscar Nierstrasz LECTURE TITLE 56
© Oscar Nierstrasz LECTURE TITLE 57
© Oscar Nierstrasz LECTURE TITLE 58
© Oscar Nierstrasz LECTURE TITLE 59
© Oscar Nierstrasz LECTURE TITLE 60