cs-413 1 techniques supporting project management (part 4) bilgisayar mühendisliği bölümü –...

1CS-413

Techniques Supporting Project Management (Part 4)

Bilgisayar Mühendisliği Bölümü – Bilkent Üniversitesi – Fall 2009

Dr.Çağatay ÜNDEĞER

InstructorBilkent University, Computer Engineering

Middle East Technical University, Game Technologies

General ManagerSimBT Inc.

e-mail : cagatay@undeger.com

2CS-413

Techniques Supporting Project Management

• Task related:– Work breakdown structures – Gantt Charts– Network Diagrams– Program Evaluation Review Technique (PERT)– Calender View– Task usage View

• Resource related:– Resource Sheet– Resource Calenders– Resource Graph View– Resource Usage View

3CS-413

Work Breakdown Structures

• A hierarchical listing of the activities (e.g. tasks, sub-tasks) necessary for the completion of the project.

• Split activities into sub-activities as much as you can;– Until leaf activities become clear and easily

manageable.

4CS-413

A Sample Project

• Generating a multimedia database with;– Word, excell, power point documents– Image files– Video files– Sound files

• Viewing and editing – Source files & database content

• Exporting/Importing database content to/from individual files.

5CS-413

A Sample Work Breakdown Structure

• Software Project Development Life Cycle (Spiral Model)– Cycle 1

• System Planning• System Analysis

– Cycle 2• System Planning• System Anaylsis• System Design• System Implementation (Prototype)• System Deployment

– Cycle 3• System Planning• System Anaylsis• System Design• System Implementation (Release 1.0)• System Deployment

• System Maintenance

6CS-413

Cycle 1 (System Planning)

• System Planning– Identify project needs– Determine project scope– Prepare project definition document– Prepare project management plans

• Prepare Software Project Management Plan• Prepare Software Quality Assurance Plan• Prepare Software Risk Management Plan

– Prepare software engineering plans• Prepare Software Configuration Management Plan• Prepare Software Verification and Validation Plan

– Evaluate and approve project plans– Sign project contract

• System Analysis ...

7CS-413

Cycle 1 (System Analysis)• System Planning ...• System Analysis

– Perform software requirements analysis• Determine software requirements• Structure software requirements• Prepare Software Requirements Specification • Evaluate and approve Software Requirements

Specification– Perform literature survey

• ???

8CS-413

– Perform software requirements analysis• Determine software requirements• Structure software requirements• Prepare Software Requirements Specification • Evaluate and approve Software Requirements

• Loading and visualising office files (doc, xls, ppt, etc.)

• Loading and visualising image files (bmp, jpg, tif, etc.)

• Loading and playing video files (avi, mpg, dat, etc.)• Loading and playing sound files (wav, mp3)• Generating multimedia databases with above

sources

9CS-413

• System Planning– Update project management plans

• Update Software Project Management Plan• Update Software Risk Management Plan

– Evaluate and approve project plans• System Analysis ...• System Design ...• System Implementation (prototype) ...• System Deployment...

10CS-413

– Refine software requirements analysis• Update software requirements• Restructure software requirements• Prepare Software Requirements Specification • Evaluate and approve Software Requirements

• ???– Generate alternative designs

• Determine and select alternative designs• Evaluate and approve selected design

• System Design ...• System Implementation (prototype) ...• System Deployment...

11CS-413

• Editing and saving office files (doc, xls, ppt, etc.)• Editing and saving image files (bmp, jpg, tif, etc.)• Editing and saving video files (avi, mpg, dat, etc.)• Editing and saving sound files (wav, mp3)

– Generate alternative designs• Determine and select alternative designs• Evaluate and approve selected design

• System Design ...• System Implementation (prototype) ...• System Deployment...

12CS-413

Cycle 2 (System Design)• System Planning ...• System Analysis ...• System Design

– Prepare logical system description– Prepare physical system description

• Determine details of implementation environment– Select hardware platforms and operating systems– Select programming languages– Select database systems and file structures– Select network environment

• Design details of system– Design user interfaces

» ???– Design reports

» ???– Design databases

» ???– Design algorithms

» ???– Design computer process

» ???• Design system integration

– Prepare Software Design Description– Evaluate and approve Software Design Description

• System Implementation (prototype) ...• System Deployment...

13CS-413

Cycle 2 (System Design)• System Planning ...• System Analysis ...• System Design

– Prepare logical system description– Prepare physical system description

• Determine details of implementation environment– Select hardware platforms and operating systems– Select programming languages– Select database systems and file structures– Select network environment

• Design details of system– Design user interfaces

» Main window» Windows for file import, visualise, edit and save» Windows for database content generation» Windows for database content browser, visualise, edit and save to file» Windows for database backup and restore» Windows for user accounts management

– Design reports» ...

– Design databases– Design algorithms– Design computer process

• Design system integration– Prepare Software Design Description– Evaluate and approve Software Design Description

• System Implementation (prototype) ...• System Deployment...

14CS-413

Cycle 2 (System Implementation)

• System Planning ...• System Analysis ...• System Design ...• System Implementation (prototype)

– Coding• Implement software components

– ???• Integrate software components• Correct reported bugs

– Testing & Correction• Prepare Software Test Document• Evaluate and approve Software Test Document• Perform unit tests• Perform integration tests• Report test results and update Software Test Document

– Demonstrate, evaluate and approve system software• System Deployment...

15CS-413

• System Planning ...• System Analysis ...• System Design ...• System Implementation (prototype)

– Coding• Implement software components

– Implement user interfaces» Main window» Windows for file import, visualise, edit and save» Windows for database content generation» Windows for database content browser, visualise, edit and save to file» Windows for database backup and restore» Windows for user accounts management

– Implement reports» ...

– Implement databases– Implement algorithms– Implement computer process

• Integrate software components• Correct reported bugs

– Demonstrate, evaluate and approve system software• System Deployment...

16CS-413

Cycle 2 (System Deployment)

• System Planning ...• System Analysis ...• System Design ...• System Implementation (prototype) ...• System Deployment

– Install system software– Enter baseline data

• ???– Train users

• 1 weeks administrator training• 1 week user training

17CS-413

• System Planning ...• System Analysis ...• System Design ...• System Implementation (prototype) ...• System Deployment

• Import office documents from previous archives• Import image files from previous archives• Import video files from previous archives• Import sound files from previous archives

– Train users• 1 weeks administrator training• 1 week user training

18CS-413

• System Planning– Update project management plans

• Update Software Project Management Plan

– Evaluate and approve project plans• System Analysis ...• System Design ...• System Implementation (release 1.0) ...• System Deployment ...

19CS-413

Cycle 3 (System Analysis)

• System Planning ...• System Analysis

Specification• System Design ...• System Implementation (release 1.0) ...• System Deployment ...

20CS-413

Cycle 3 (System Design)

• System Planning ...• System Analysis ...• System Design

– Refine logical system description– Refine physical system description

• Refine details of system– Update user interfaces– Update reports– ...

• Refine system integration– Prepare Software Design Description– Evaluate and approve Software Design Description

• System Implementation (release 1.0) ...• System Deployment ...

21CS-413

• System Planning ...• System Analysis ...• System Design ...• System Implementation (release 1)

– Coding• Refine software components• Integrate software components• Correct reported bugs

– Prepare Software Deliverables• Prepare user manuals• Prepare system setup application

– Demonstrate, evaluate and approve system software• System Deployment ...

22CS-413

• System Planning ...• System Analysis ...• System Design ...• System Implementation (release 1) ...• System Deployment

• ...– Train users

• 3 weeks administrator training• 2 week user training

23CS-413

Afterwards (System Maintenance)

• System Maintenance– Fix system software bugs– Improve system software

24CS-413

25CS-413

Gantt Charts

• A bar chart showing start and end dates for the activities (WBS) of a project.

• Not intended to indicate how tasks must be ordered, – But simply show when a task should begin

and end.• Very helpful for seeing date-time relations of

activities.

26CS-413

Gantt Charts• On the left, a work breakdown structure is located;• On the right, the time bars are located.

summary tasks

leaf tasks

Start: 20.02.2008End: 28.02.2008Duration: 7 days

From Microsoft Office

27CS-413

Information on Gantt Charts• Many information can be seen on gantt charts

duration oftask

percent oftask completed

28CS-413

Information on Gantt Charts• Precedence relations can be seen on gantt charts.

Predecessor of Task A

Task A

Successorof Task A

Starts at theSame time

29CS-413

Information on Gantt Charts• Resource assignments can be seen on gantt charts• Resource usage can be seen on gantt charts

With two full-time personnel

With onepart-time personnel

With one Full-time personnel

With twopart-time personnel

Many tasks in parallel

30CS-413

Information on Gantt Charts• Critical paths can be seen on gantt charts

Red colored tasks are on critical path.Therefore they can not be delayed.

Blue colored tasks are not on critical path.Therefore they can be delayed.

Critical path is the longestpath through the projectillustrating the shortest amount of time in whicha project can be completed.

Tasks on critical path cannot be delayed without delaying project.

31CS-413

32CS-413

Network Diagrams

• A schematic display;– That illustrates various tasks in a project

• As well as their sequential relationship.• A scheduling technique used for controlling

resources.• Show which tasks can be done in parallel.

33CS-413

Network Diagrams

• Used to identify critical paths.• Critical path is the longest path through the

project – Illustrating the shortest amount of time

• In which a project can be completed.• Tasks on critical path cannot be delayed

without delaying project.

34CS-413

Network Diagrams (Sample: Summary & Leaf Tasks)

35CS-413

Network Diagrams (Sample: Leaf Tasks)

ID Task Name Duration Predecessors

3 Implement visualiser 2 -

4 Implement database 4 -

5 Integrate components 2 3, 4

6 Correct bugs 4 8

8 Prepare test document 1 5

9 Perform unit tests 1 5, 8

10 Perform integration tests 1 5, 9

11 Report test results 1 5, 10

12 Prepare sample data 7 4

13 Prepare deliverables 1 6, 12

• With the information below, – You can be able to draw a network diagram.

36CS-413

Network Diagrams (Sample: Visualisation)

• Tasks are shown by either– Circles or– Rectangles.

• Work flows are shown by arrows.

Task 1 Task 2Task 2 follows Task 1

Task 1 is the predecessor of Task 2

37CS-413

Network Diagrams (Sample: Network Diagram)

6 Correct bugs 4 8

38CS-413

6 Correct bugs 4 8

39CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

40CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = Earliest completion time Compute ET of left mosts first. Compute ET of each forward task by summing ET for each task from left to right.

LT = Latest completion time Compute LT of right mosts first. Compute LT of each backward task by subtracting duration for each task from right to left.

41CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

42CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = max(2,4)+2

ET = 4+7

43CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 6+1

44CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 7+4

ET = 7+1

45CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 8+1

ET = max(11,11)+1

46CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 9+1

ET = 12

47CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12

48CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12

Assign project end date, max(ET)

49CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12

LT = 12-1

50CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 11-1

LT = 11

51CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = min ( 11-4 , 10-1 )

52CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = min(7,9)

53CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = 7LT = 7-1

54CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = 7LT = 6LT = 6-2

LT = min ( 6-2 , 11-7 )

55CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = 7LT = 6LT = 4

LT = min(4,4)

56CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = 7LT = 6LT = 4

LT = 4

57CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = 7LT = 6LT = 4

LT = 4

Red tasks are on critical path, so should not be delayed.

58CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = 7LT = 6LT = 4

LT = 4

Orange tasks are not on critical path, so can be delayed up to some point.

59CS-413

6 Correct bugs 4 8

D = 2 D = 2

D = 1 D = 4

D = 1 D = 1 D = 1

Slack time is the amount of time a task can be delayed without delaying the project.

Slack-time = LT-ET

ET = 2

ET = 4

ET = 6

ET = 11

ET = 7 ET = 11

ET = 8 ET = 9 ET = 10

ET = 12LT = 12

LT = 12LT = 11LT = 10

LT = 11

LT = 7LT = 6LT = 4

LT = 4

Tasks not on the critical path contain some slack time (st).

st = 2

st = 2 st = 2 st = 2

60CS-413

61CS-413

Program Evaluation Review Technique (PERT)

• A technique used for determining the duration of tasks in work breakdown structures.

• It is difficult to estimate a tasks duration – When it involves a high degree of

complexity and uncertainty.• PERT uses;

– Optimistic, – Most likely, and– Pessimistic time estimates

• To calculate expected time.

62CS-413

Program Evaluation Review Technique (PERT)

• PERT uses a weighted average method.

• PERT duration is equal to:

Woptimistic x optimistic t. + Wmostlikely x most likely t. + Wpessimistic x pessimistic t.Woptimistic + Wmostlikely + Wpessimistic

• Sample Duration = 1 x 9 workdays + 4 x 12 workdays + 2 x 24 workdays

• Sample Duration = 105/7 = 15

63CS-413

64CS-413

Calender View

65CS-413

Task Usage View

66CS-413

67CS-413

Resources

• Resources are: – Any person,– A group of people,– A piece of

• Equipment, • Hardware • Software or • Material

used in accomplishing a task.

68CS-413

Resource Sheet

69CS-413

Resource Calenders

70CS-413

71CS-413

Resource Graph View

72CS-413

Resource Usage View

cs-413 1 techniques supporting project management (part 4) bilgisayar mühendisliği bölümü –...

Documents

dergi bilkent say› : 14 issn 1305-5178 aral›k 2010...

cs-413 1/42 introduction to software engineering project...

lecture notes - bilkent

esn bilkent genel sunum 2010

bilkent university bilkent university, department of...

bilkent university bcc bilkent computer center. bcc brief...

İdv Özel bilkent İlköğretim okulu

esn bilkent esn tanitim 2009

cs-413 1 integration management (part 6) bilgisayar...

haluk ÜndeĞer lİsesİ

bilkent unv Öğrenci projeleri 2006

bilkent university lost its founder, prof. Ýhsan...

cs-413 1 introduction to project life cycle (part 2)...

bİlkent Ünİversİtesİ ope

cs-413 1 a detailed look to initiation phase of scope...

saat bilkent tiyatro günleri yer bilkent tiyatro günleri...

bİlkent genÇlİk senfonİ orkestrasi bİlkent youth...

bilkent senfoni orkestrası

bilkent ieee tanışma toplantısı '11

bilkent esn sunum_tanıtım