J.E.D.I
7.4.2 Work Breakdown Schedule Format
There are two common formats that can be used to represent the WBS, namely, graphical or hierarchy chart and outline format.
Graphical or Hierarchy Chart
An example of a hierarchy chart of Pre-joint Meeting Task of Requirements Engineering is shown Figure 7.3.
Outline Format
A sample outline format is shown in below. 1.
Pre-joint Meeting Task 1.1
Write product request. 1.2
Set pre-joint meeting. 1.2.1 Set time and date.
1.2.2 Set place. 1.2.3 Identify facilitator and participants
1.3 Invite participants
1.4 Distribute product request to all participants.
Software Engineering 314
Figure 7.3 Hierarchy Chart Pre-joint Meeting
Write the product request.
Set pre-joint Meeting.
Invite participants. Distribute product
request to all participants.
Set Time and Date Set Place.
Identify Facilitator and Participants.
J.E.D.I
GANTT Chart
It is an easy way of scheduling tasks. It is a chart that consists of bars that indicates the length of the tasks. The horizontal dimension indicates the time while the vertical
dimension indicates the task. Table 35 shows an example of a GANTT Chart.
1 2
3 4
5 6
1. Pre-joint Meeting Task 1.1 Write product request.
1.2 Set pre-joint meeting. 1.2.1 Set time and date.
1.2.2 Set place. 1.2.3
Identify facilitator and participants.
1.3 Invite participants. 1.4 Distribute product request.
Table 35: Sample GANTT Chart
Software Engineering 315
J.E.D.I
7.5 Project Resource Allocation
The project resource allocation is the process of allocating or assigning money, people, equipment, tools, facilities, information, skills etc to the tasks identified in the
project. They are needed in order to achieve software goals and objectives. There are three major project constraints that are always considered in a software development
project. They are:
• Time Constraints
• Resource Constraints
• Performance Constraints
7.5.1 Resource Availability Data Base
The project manager must use the resource availability database to manage resources allocated for each task set. The Resource Availability Database specifies what resources
are required against the resources that are available. Table 36 shows an example.
Resource Type
Resource ID Skills
Date Needed
Duration Number of
Resources
Type 1 Project
Manager Planning
Managing 11XX
10 months
1 Type 2
Analyst Developing
Analysis Model 1225XX
Indefinite 2
Type 3 Designer
Developing Software
Architecture and
Components Now
36 Months
2
… …
… …
… …
… …
… …
… …
… …
… …
… …
Type n-1 Operator
Machining Immediate
Indefinite 4
Type n Programmer
Software Tools 92XX
12 months
5
Table 36: Resource Availability Database
There are some factors to be considered when allocating resources. Some of them are listed below.
• Limitations on resource availability
• Precedence restrictions
• Activity-splitting restrictions
• Non-pre-emption of activities
• Project Deadlines
• Resource Substitutes
• Partial Resource Assignments
Software Engineering 316
J.E.D.I
• Mutually exclusive activities
• Variable resource availability
• Variable activity durations
Allocating Resources to the Project Task Set.
Project Task Set Resources
1 1. Pre-joint Meeting Task 1.1 Write product request.
End-user who will write the product request.
Computer Office Supplies
1.2 Set pre-joint meeting. 1.2.1 Set time and date.
Project Leader 1.2.2 Set place.
Project Leader 1.2.3 Identify facilitator and participants.
Project Leader 1.3 Invite participants.
Administrative staff E-mail
Office supplies 1.4 Distribute product request.
Project Leader Computer
Office supplies
Software Engineering 317
J.E.D.I
7.6 Software Metrics
Kategori