resource requirement and allocation

7/29/2019 Resource Requirement and Allocation

1/26

1

RESOURCE REQUIREMENT

&ALLOCATION


2/26

2

Requirements Analysis

Software engineering task bridging the gap betweensystem requirements engineering and softwaredesign.

Provides software designer with a model of: system information

function

behavior

Model can be translated to data, architectural, andcomponent-level designs.

Expect to do a little bit of design during analysis anda little bit of analysis during design.


3/26

3

Analysis Objectives

Identify customers needs.

Evaluate system for feasibility.

Perform economic and technical

analysis.

Allocate functions to system elements.

Establish schedule and constraints.

Create system definitions.


4/26

4

Software Requirements Analysis

Phases Problem recognition

Evaluation and synthesis

focus is on what not how

Modeling

Specification

Review


5/26

5

Management Questions

How much effort put towards analysis?

Who does the analysis?

Why is it so difficult?

Bottom line - who pays for it?


6/26

6

Feasibility Study

Economic feasibility

cost/benefit analysis

Technical feasibility

hardware/software/people, etc.

Legal feasibility

Alternatives

there is always more than one way to do it


7/26

7

System Specification

Introduction.

Functional data description.

Subsystem description.

System modeling and simulation

results.

Products.

Appendices.


8/26

8

Requirements

Requirement

features of system or system function used

to fulfill system purpose. Focus on customers needs and

problem, not on solutions:

Requirements definition document(written for customer).

Requirements specification document(written for programmer; technical staff).


9/26

9

Types of Requirements - 1

Functional requirements: input/output

processing.

error handling.

Non-functional requirements: Physical environment (equipment locations,

multiple sites, etc.).

Interfaces (data medium etc.).

User & human factors (who are the users, theirskill level etc.).


10/26

10

Types of Requirements - 2

Non-functional requirements (continued):

Performance (how well is system functioning).

Documentation. Data (qualitative stuff).

Resources (finding, physical space).

Security (backup, firewall).

Quality assurance (max. down time, MTBF, etc.).


11/26

RESOURCE ALLOCATION

11


12/26

12

Schedules

Activity schedule - indicating start and

completion dates for each activity

Resource schedule - indicating dateswhen resources needed + level of

resources

Cost schedule showing accumulativeexpenditure


13/26

13

Resources

These include labour

equipment (e.g. workstations)

materials space

services

Time: elapsed time can often be reducedby adding more staff

Money: used to buy the other resources


14/26

14

Resource allocation

Identify the resources needed for each

activity

Identify resource types - individuals areinterchangeable within the group (e.g.

VB programmers as opposed to

software developers) Allocate resource types to activities and

examine the resource histogram


15/26

15

Resource histogram:

systems analysts

WEEK

1 2 3 4 5 6 7

1

2

3

4

5


16/26

16

Resource clashes

can be resolved by:

delaying one of the activities

taking advantage of float to change start date

delaying start of one activity until finish of theother activity that resource is being used on -puts

back project completion

moving resource from a non-critical activity

bringing in additional resource - increases

costs


17/26

17

Prioritizing activities

There are two main ways of doing this:

Total float prioritythose with the

smallest float have the highest priority

Ordered list priority this takes account

of the duration of the activity as well as

the float see next overhead


18/26

18

Burmans priority list

Give priority to:

Shortest critical activities Other critical activities

Shortest non-critical activities

Non-critical activities with least float Non-critical activities


19/26

19

Resource usage

Need to maximise %usage of resources

i.e. reduce idle periods between tasks

Need to balance costs against early

completion date

Need to allow for contingency


20/26

20

Critical path

Scheduling resources can create newdependencies between activities recallcritical chains

It is best not to add dependencies to theactivity network to reflect resource constraints Makes network very messy

A resource constraint may disappear during the

project, but link remains on network

Amend dates on schedule to reflect resourceconstraints


21/26

21

Allocating individuals to activities

The initial resource types for a task haveto be replaced by actual individuals.

Factors to be considered:

Availability

Criticality

Risk

Training

Team building and motivation


22/26

22

Cost schedules

Cost schedules can now be produced:

Costs include:

Staff costs

Overheads

Usage charges


23/26

23

Cost profile


24/26

24

Accumulative costs


25/26

25

Balancing concerns


26/26

THANK YOU

26

resource requirement and allocation

Documents