00-019Requirements Estimation Tool

Summary Page

00-029Page 1 of 9

Yellow cell values should be entered specific to this project

Light gray cells are either N/A or reference yellow cells and usually do not need to be edited
Dark gray cells are calculated, but can be overriden
Important summations
Input
Quantity Items
100
Existing pages of documentation for review
1
Existing systems being updated or replaced
52
Stakeholders
25
Interfacing Systems - small systems
2
Interfacing Systems - medium systems
1
Interfacing Systems - large systems
15
Process Flows
2
BDDs
20
Screens
20
Reports
Summary Total Effort Comparison
% of total
project
Number of BAs
BA budget for requirements work
BA budget for project duration

$
$

2
300,000
600,000

Quantity
$ 2,000,000
$125
Standard
8
No
56
28

Items
Total project budget
BA blended hourly cost
Type of project
Number of developers
Is your team remote?
Project duration? (weeks)
Requirements work duration? (weeks)

Ratio of
dev to BAs

Activity
based

$
$

1.3
187,000
373,000

$
$

1.1
*Excludes time of
155,000
309,000

Estimates
Category

Activity

Hours by
Category

Project Start and Management

Requirements plans
Status reporting
Requirements architecture
Project kick-of
Functions/Features organization
Traceability Links
Existing documentation review
Existing systems review

207

Model Requirements - People

Process Flows

393

Hours

Minutes per
unit

Units

Minutes

19
119
15
20
16
11
3
4

1140
255
910
1200
960
1.00
2.00
240

N/A
28
N/A
N/A
N/A
630
100
1

1140
7140
910
1200
960
630
200
240

164

656

15

9840

00-032Copyright Seilevel, Inc. All rights reserved.

Notes

Uses requirements project duration above

00-008www.seilevel.com/resources

00-019Requirements Estimation Tool

Summary Page
Category

Hours by
Category

Activity
Org Charts
User Stories
Decision Trees

Model Requirements - System

System Context Diagrams
System Interface Models - small systems
System Interface Models - medium systems
System Interface Models - large systems
Display-Action-Response Tables

311

Model Requirements - Data

Business Data Diagrams
Data Flow Diagrams
Data Dictionaries
State Tables
State Diagrams
Report Tables

326

Total Effort
Requirements Work
Remote Team Bufer add-on

00-029Page 2 of 9

8
216
6

Minutes per
unit
450
216
230

13
125
33
40
100

750
300
1000
2400
300

1
25
2
1
20

750
7500
2000
2400
6000

7
50
60
5
5
200

210
495
180
270
270
600

2
6
20
1
1
20

420
2970
3600
270
270
12000

Hours

Units

Minutes

1
60
1.5

450
12960
345

Uses number of screens, above

1237
0

BA estimate based on activities

Hours of work with bufer
Number of BAs for the Requirements Work
BA cost for requirements work
BA cost for entire project

1237
1.1
$154,573
$309,146

Assumes input requirements duration, excludes time of

Assumes input cost
Assumes input project duration and cost

BA estimate as ratio of Developers to BAs

Developers per BA Standard
Developers per BA COTS
Number of BAs for entire project
BA cost for requirements work
BA cost for entire project

6
3
1.3
$186,667
$373,333

Assumes input requirements duration and cost

Assumes input project duration and cost

BA estimate as % of total budget

Total budget
Percent of budget allocated to requirements
BA budget for requirements work
Number of BAs for the Requirements Work
BA budget for project duration

Notes

$
$
$

2,000,000
15%
15% is industry standard
300,000
2
Assumes input requirements duration and cost
600,000 Assumes input project duration and cost

00-032Copyright Seilevel, Inc. All rights reserved.

00-008www.seilevel.com/resources

00-044Requirements Estimation Tool

Assumptions Page
Yellow cell values should be entered specific to this project
Light gray cells are either N/A or reference yellow cells and usually do not need to be edited
Dark gray cells are calculated, but can be overriden
Estimated Model counts and Assumptions
Model
Quantity Estimate based on
User Stories
Decision Trees
DFDs
Data Dictionaries
State Tables
State Diagrams
Requirements
Business Rules
Number of traces

60
1.5
6
20
1
1
210
630
630

Process
Process
BDDs
BDDs
BDDs
BDDs
Process
Process
Process

00-044Page 3 of 9

Assumptions (* indicates assumption varies based on

project size-- Small, Medium, or Large)

Flow
Flow

Flow
Flow
Flow

Steps in a Process Flow

User Stories per Process Flow
Decision Trees per Process Flow
Decision points in a Decision Tree
Data objects in a BDD
Total objects in a DFD
State objects to define per BDD
States in a state model
DFDs per BDD
People in an Org Chart (S:10, M:30, L:50)*
Systems in a System Context Diagram (S:10, M:30, L:50)*

20
4
0.1
10
10
15
0.5
10
3
50
50

Elements in a Screen
Elements in a Report
Requirements per step in a Process Flow
Business rules per requirement
Requirements per Process Flow
Business rules per Process Flow
Unique requirements per User Story
Traces per requirement (to Process Flow, Screen, User Story)

15
20
0.7
3
14
42
4
3

Detailed Calculations for each activity

Category

Activity

Project Start and Management

Requirements plans
Create detailed requirements plans
Create burndowns
Complete the methodolgy checklist
Status reporting
Create a weekly status report
Weekly status meeting
Core Team meetings
Defect review meetings

Section
Subtotal
(minutes)

Total
Minutes

Estimate per
Number of
Element
Elements
(minutes)

Notes

Suggested Suggested
Time - Low Time - High
(minutes)
(minutes)

1140
720
180
240

720
180
240

N/A
N/A
N/A

Burndowns for budget and activities

Burndowns for budget and activities
Use checklists to build plan

60
60
75
60

60
60
75
60

N/A
N/A
N/A
N/A

Time
Time
Time
Time

480
120
120

960
240
360

15
15
30
30

90
120
90
120

255
per
per
per
per

week
week
week
week

00-033Copyright Seilevel, Inc. All rights reserved.

for
for
for
for

status reporting
status meetings
core team meetings
defect review meetings

www.seilevel.com/resources

00-044Requirements Estimation Tool

Assumptions Page
Category

Activity
Requirements architecture
Define Requirements Architecture
Setup team repository (SP and RM tools)
Kicking off project
Project kickof meetings
Project familiarization
Complete Business Problems and Objectives
Organizing Functions/Features
Identify all major buckets of functionality
Determine how to organize work
Existing documentation
Review existing documentation
Existing systems
Get trained in existing or new systems
Traceability Matrix
Traceability Matrix creation
Traceability Matrix analysis

Model Requirements - People

Org Charts
Org Chart elicitation
Org Chart creation
Org Chart internal review
Org Chart customer review
Evaluate org charts against stakeholder lists
Process Flows
Elicitation prep, meet, follow-up
Process Flow creation
Process Flow internal review
Process Flow customer review
Derive Requirements and business rules
Review and Update derived requirements

Section
Subtotal
(minutes)

Total
Minutes

Estimate per
Number of
Element
Elements
(minutes)

00-044Page 4 of 9

Notes

Suggested Suggested
Time - Low Time - High
(minutes)
(minutes)

910
700

700

N/A

Setup architecture objects and where the artifacts live

400

1000

210

210

N/A

Setup sharepoint, requirements tools, etc.

180

240

360
240
600

360
240
600

N/A
N/A
N/A

Prep and have meeting

Basic project introduction
Elicit and document business objectives

240
90
120

480
360
1200

480
480

480
480

N/A
N/A

Identify features, functions, modules, etc.

Make decisions about how to organize all of the work

240
120

1000
1200

N/A

Review a page in a document

0.5

240

240

N/A

Get up to speed on existing system

30

480

0.5
0.5

0.50
0.50

N/A
N/A

Time to link
Time per link to find issues or gaps

0.25
0.5

3
3

50
100
50
100
150

1
2
1
2
3

50
50
50
50
50

People within an org chart

0
1
1
1
1

5
5
3
3
5

120
60
60
80
112
224

120
3
3
4
2
4

N/A
20
20
20
56
56

Sessions breakdown (30 prep, 60 meet, 30 follow-up)

Steps within a process flow

60
1
1
1
1
1

180
6
6
10
6
10

1200

960

2
240
1

450

656

Requirements and business rules per process flow

00-033Copyright Seilevel, Inc. All rights reserved.

www.seilevel.com/resources

00-044Requirements Estimation Tool

Assumptions Page
Category

Activity
User Stories
User Story elicitation
User Story creation
User Story internal review
User Story customer review
Derive Requirements and business rules
Review and Update derived requirements
Decision Trees
Decision Tree creation
Decision Tree internal review
Decision Tree customer review
Derive Requirements and business rules
Review and Update derived requirements

Model Requirements - System

System Context Diagram
System Context Diagram elicitation
System Context Diagram creation
System Context Diagram internal review
System Context Diagram customer review
Small System Interface Models
Medium System Interface Models
Large System Interface Models
DAR models
Wireframe creation
Wireframe internal review
Wireframe customer review
Display-Action-Response creation
Display-Action-Response internal review
Display-Action-Response customer review
Model Requirements - Data
Business Data Diagrams
Business Data Diagram elicitation
Business Data Diagram creation
Business Data Diagram internal review
Business Data Diagram customer review

Section
Subtotal
(minutes)

Total
Minutes

Estimate per
Number of
Element
Elements
(minutes)

00-044Page 5 of 9

Notes

Suggested Suggested
Time - Low Time - High
(minutes)
(minutes)

216
60
20
10
30
32
64

60
20
10
30
2
4

N/A
N/A
N/A
N/A
16
16

Session breakdown (20 prep, 30 meet, 10 follow-up)

10
10
30
60
120

1
1
3
2
4

10
10
10
30
30

Decision points within a decision tree

150
150
150
300
300
1000
2400

3
3
3
6
300
1000
2400

50
50
50
50
N/A
N/A
N/A

60
30
60
60
30
60

4
2
4
4
2
4

15
15
15
15
15
15

Elements within a screen

60
60
30
60

60
6
3
6

N/A
10
10
10

Session breakdown (20 prep, 30 meet, 10 follow-up)

Objects within a business data diagram

Requirements and business rules per user story

30
10
5
10
1
1

120
45
30
60
6
10

1
1
1
1
1

10
5
10
6
10

0
1
1
1
40
400
2000

6
10
6
10
400
2000
4000

0
1
1
2
1
2

10
10
20
10
5
10

30
3
1
3

120
10
6
10

230

Business rules per decision tree

750
Systems within a context diagram

Small custom system, few data pieces

Lots of data is passed, lots of interface points

300

Elements within a screen

210

00-033Copyright Seilevel, Inc. All rights reserved.

www.seilevel.com/resources

00-044Requirements Estimation Tool

Assumptions Page
Category

Activity
Data Flow Diagrams
Data Flow Diagram creation
Data Flow Diagram internal review
Data Flow Diagram customer review
Derive Requirements and business rules
Review and Update derived requirements
Data Dictionaries
Data Dictionary creation
Data Dictionary internal review
Data Dictionary customer review
State Tables
State Table creation
State Table internal review
State Table customer review
Derive Requirements and business rules
Review and Update derived requirements
State Diagrams
State Diagram creation
State Diagram internal review
State Diagram customer review
Derive Requirements and business rules
Review and Update derived requirements
Report Tables
Report Table elicitation
Report Table creation
Report Table internal review
Report Table customer review

Section
Subtotal
(minutes)

Total
Minutes

Estimate per
Number of
Element
Elements
(minutes)

00-044Page 6 of 9

Notes

Suggested Suggested
Time - Low Time - High
(minutes)
(minutes)

495
90
45
90
90
180

6
3
6
2
4

15
15
15
45
45

Objects within a data flow diagram

3
1
3
1
1

10
6
10
6
10

60
60
60

6
6
6

10
10
10

Elements within a data dictionary

3
1
1

9
10
10

60
30
30
60
90

6
3
3
2
3

10
10
10
30
30

States in a state table

3
1
1
1
1

9
5
5
6
10

60
30
30
60
90

6
3
3
2
3

10
10
10
30
30

States in a state diagram

3
1
1
1
1

9
5
5
6
10

120
120
120
240

120
6
6
12

N/A
20
20
20

Sessions breakdown (30 prep, 60 meet, 30 follow-up)

Elements in a report

60
3
1
3

180
10
5
20

Business rules per DFD

180

270

Business rules per state table

270

Business rules per state diagram

600

00-033Copyright Seilevel, Inc. All rights reserved.

www.seilevel.com/resources

00-045Requirements Estimation Tool

Instructions Page

00-045Page 7 of 9

Quick Start
1 Access the Summary worksheet. Fill in the yellow cells with relevant numbers.
2 Access the Assumptions worksheet. Review the standards in the yellow cells. Change them if necessary.
3 Return to the summary worksheet and review your totals.

Detailed Information
Color Coding Key
Yellow cell values should be entered specific to this project
Light gray cells are either N/A or reference yellow cells and usually do not need to be edited
Dark gray cells are calculated, but can be overriden
Important summations

Summary Worksheet
The Summary worksheet contains project assumptions, efort on a model-by model basis, and total efort.
Input Section

You must fill in the left column of yellow cells. Filling in the the column of yellow cells to the right is optional.

00-030Copyright Seilevel, Inc. All rights reserved.

00-008www.seilevel.com/resources

00-045Requirements Estimation Tool

Instructions Page

00-045Page 8 of 9

Project duration is the total expected length of the project. It is used to estimate how many weeks beyond the
requirements efort are needed, and is used in calculating BA support needed for that timeframe. It does not have to be
entered.
Requirements Work Duration is the total expected length of time spent on requirements in a project. It is used to estimate
time for status reporting (since it is throughout this period). And it is used for estimating how many BAs are needed based
on the total work and desired duration.
Total project budget is only used as another means of estimating how much should be spent on the requirements efort.
Number of developers and type of project are used to estimate how many BAs are needed on the project in general.
Estimates Section
This section provides estimates on a model-by-model basis, based on the Inputs section and the Assumptions worksheet.
Total Effort Section
The calculations tell you the total work under "Total Efort" based on pre-set formulas.
The total BA count is calculated based on the duration of requirements work input at the top.
If you specified in the inputs that the team is remote, then a 10% bufer is added to the hours for inefective time use.

The number of BAs you can estimate needing based on number of developers is at the bottom of the summary tab.

00-030Copyright Seilevel, Inc. All rights reserved.

00-008www.seilevel.com/resources

00-045Requirements Estimation Tool

Instructions Page

00-045Page 9 of 9

The budget for BAs can be estimated as a percent of the total project.

The estimated BA cost based on the requirements work total is calculated as well.
The BA support cost through the rest of the project is calculated based on number of BAs needed per number of
developers.

Assumptions Worksheet
The Assumption worksheet contains the assumptions which are used determine the average efort to complete each model
or requirements artifact.
You do not have to change any of the assumption, but you may.
The yellow cells are all standards, but can be altered.
Estimated Model counts and Assumptions Section
At the top left, the number of models produced is calculated.
Detailed Calculations for each activity Section
Details below are the estimates to create each individual model or element.
Suggested Time - Low and - High are numbers you can use to decide on the value used in column E.
Element is any object or sub object used in the estimate. Element could be a use case, a step in a use case, a process flow,
a button in a screen, or a link in a screen.

00-030Copyright Seilevel, Inc. All rights reserved.

00-008www.seilevel.com/resources