Professional Documents
Culture Documents
Project Management: ©ian Sommerville 2004 Software Engineering, 7th Edition. Chapter 5 Slide 1
Project Management: ©ian Sommerville 2004 Software Engineering, 7th Edition. Chapter 5 Slide 1
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide1
Objectives
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide2
Topics covered
Management activities
Project planning
Project scheduling
Risk management
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide3
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide4
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide5
Management activities
Proposal writing.
Project planning and scheduling.
Project costing.
Project monitoring and reviews.
Personnel selection and evaluation.
Report writing and presentations.
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide6
Management commonalities
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide7
Project staffing
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide8
Project planning
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide9
Description
Quality plan
Validation plan
Configuration
management plan
Maintenance plan
Staff
plan.
development Describes how the skills and experience of the project team
members will be developed. See Chapter 25.
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide10
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide11
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide12
Introduction.
Project organisation.
Risk analysis.
Hardware and software resource
requirements.
Work breakdown.
Project schedule.
Monitoring and reporting mechanisms.
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide13
Activity organization
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide14
Requirements
analy sis
Prototype
development
Design
study
Requirements
specifi ca
tion
Feasibility
report
User
requirements
Evaluation
report
Architectur
al
design
System
requirements
MILESTONES
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide15
Project scheduling
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide16
Identify
activities
Identify activity
dependencies
Estimate resources
for activities
Allocate people
to activities
Software
requirements
IanSommerville2004
Create project
charts
Activity char
ts
and bar char
ts
SoftwareEngineering,7thedition.Chapter5
Slide17
Scheduling problems
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide18
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide19
Duration (days)
T1
T2
15
T3
15
T4
10
T5
10
T2, T4 (M2)
T6
T1, T2 (M3)
T7
20
T1 (M1)
T8
25
T4 (M5)
T9
15
T3, T6 (M4)
T10
15
T5, T7 (M7)
T11
T9 (M6)
T12
10
T11 (M8)
IanSommerville2004
Dependencies
T1 (M1)
SoftwareEngineering,7thedition.Chapter5
Slide20
Activity network
14/7/03
15 days
M1
T3
8 days
T9
T1
25/7/03
4/7/03
start
15 days
5 days
4/8/03
T6
M4
M3
25/8/03
M6
7 days
20 days
15 days
T7
T2
25/7/03
10 days
M2
T4
T11
10 days
T5
5/9/03
11/8/03
M7
T10
18/7/03
M8
15 days
10 days
T12
M5
25 days
Finish
T8
19/9/03
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide21
Activity timeline
4/7
11/7
18/7
25/7
1/8
8/8
15/8
22/8
29/8
5/9
12/9
19/9
Start
T4
T1
T2
M1
T7
T3
M5
T8
M3
M2
T6
T5
M4
T9
M7
T10
M6
T11
M8
T12
Finish
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide22
Staff allocation
4/7
Fred
1/8
8/8
5/9
12/9 19/9
T4
T8
T11
T12
Jane
T1
T3
T9
Anne
T2
T6
Jim
Mary
IanSommerville2004
T10
T7
T5
SoftwareEngineering,7thedition.Chapter5
Slide23
Risk management
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide24
Software risks
Risk
Affects
Description
Staff turnover
Project
Management change
Project
Hardware unavailability
Project
Requirements change
Project and
product
Specification delays
Project and
product
Size underestimate
Project and
product
Product
Technology change
Business
Product competition
Business
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide25
Risk identification
Risk analysis
Risk planning
Risk monitoring
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide26
Risk
identifi cation
Risk analysis
Risk planning
Risk
monitoring
List of potential
risks
Prioritised risk
list
Risk avoidance
and contingency
plans
Risk
assessment
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide27
Risk identification
Technology risks.
People risks.
Organisational risks.
Requirements risks.
Estimation risks.
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide28
Possiblerisks
Technology
Thedatabaseusedinthesystemcannotprocessasmanytransactionspersecond
asexpected.
Softwarecomponentsthatshouldbereusedcontaindefectsthatlimittheir
functionality.
People
Itisimpossibletorecruitstaffwiththeskillsrequired.
Keystaffareillandunavailableatcriticaltimes.
Requiredtrainingforstaffisnotavailable.
Organisational
Theorganisationisrestructuredsothatdifferentmanagementareresponsiblefor
theproject.
Organisationalfinancialproblemsforcereductionsintheprojectbudget.
Tools
ThecodegeneratedbyCASEtoolsisinefficient.
CASEtoolscannotbeintegrated.
Requirements
Changestorequirementsthatrequiremajordesignreworkareproposed.
Customersfailtounderstandtheimpactofrequirementschanges.
Estimation
Thetimerequiredtodevelopthesoftwareisunderestimated.
Therateofdefectrepairisunderestimated.
Thesizeofthesoftwareisunderestimated.
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide29
Risk analysis
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide30
Probability
Effects
Organisationalfinancialproblemsforcereductionsin
theprojectbudget.
Low
Catastrophic
Itisimpossibletorecruitstaffwiththeskillsrequired
fortheproject.
High
Catastrophic
Keystaffareillatcriticaltimesintheproject.
Moderate
Serious
Softwarecomponentsthatshouldbereusedcontain
defectswhichlimittheirfunctionality.
Moderate
Serious
Changestorequirementsthatrequiremajordesign
reworkareproposed.
Moderate
Serious
Theorganisationisrestructuredsothatdifferent
managementareresponsiblefortheproject.
High
Serious
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide31
Probability
Effects
Thedatabaseusedinthesystemcannotprocessas
manytransactionspersecondasexpected.
Moderate
Serious
Thetimerequiredtodevelopthesoftwareis
underestimated.
High
Serious
CASEtoolscannotbeintegrated.
High
Tolerable
Customersfailtounderstandtheimpactof
requirementschanges.
Moderate
Tolerable
Requiredtrainingforstaffisnotavailable.
Moderate
Tolerable
Therateofdefectrepairisunderestimated.
Moderate
Tolerable
Thesizeofthesoftwareisunderestimated.
High
Tolerable
ThecodegeneratedbyCASEtoolsisinefficient.
Moderate
Insignificant
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide32
Risk planning
Minimisation strategies
Contingency plans
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide33
Strategy
Organisational
financialproblems
Prepareabriefingdocumentforseniormanagement
showinghowtheprojectismakingaveryimportant
contributiontothegoalsofthebusiness.
Recruitment
problems
Alertcustomerofpotentialdifficultiesandthe
possibilityofdelays,investigatebuyingin
components.
Staffillness
Reorganiseteamsothatthereismoreoverlapofwork
andpeoplethereforeunderstandeachothersjobs.
Defective
components
Replacepotentiallydefectivecomponentswithbought
incomponentsofknownreliability.
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide34
Strategy
Requirements
changes
Derivetraceabilityinformationtoassessrequirements
changeimpact,maximiseinformationhidinginthe
design.
Organisational
restructuring
Prepareabriefingdocumentforseniormanagement
showinghowtheprojectismakingaveryimportant
contributiontothegoalsofthebusiness.
Database
performance
Investigatethepossibilityofbuyingahigher
performancedatabase.
Underestimated
developmenttime
Investigatebuyingincomponents,investigateuseofa
programgenerator
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide35
Risk monitoring
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide36
Risk indicators
Risktype
Potentialindicators
Technology
Latedeliveryofhardwareorsupportsoftware,manyreported
technologyproblems
People
Poorstaffmorale,poorrelationshipsamongstteammember,
jobavailability
Organisational
Organisationalgossip,lackofactionbyseniormanagement
Tools
Reluctancebyteammemberstousetools,complaintsabout
CASEtools,demandsforhigherpoweredworkstations
Requirements
Manyrequirementschangerequests,customercomplaints
Estimation
Failuretomeetagreedschedule,failuretoclearreported
defects
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide37
Key points
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide38
Key points
IanSommerville2004
SoftwareEngineering,7thedition.Chapter5
Slide39