Presentation about a new approach to estimate IT projects that includes functional and non-functional requirements. The accompanying paper was presented at the IWSM Mensura conference in Gothenburg.

1. Frank Vogelezang
October 25, 2017nesma

2. The team
Cost engineers
Frank Vogelezang
Eric van der Vliet
René Nijland
Architects
Eltjo Poort
Harry Mols
Jelle de Vries
| A Shortcut to Estimating Non-Functional Requirements?

3. The customer requirements
| A Shortcut to Estimating Non-Functional Requirements?
=

4. The architects view
© Harvard University
| A Shortcut to Estimating Non-Functional Requirements?

5. The metrics view
| A Shortcut to Estimating Non-Functional Requirements?

6. But where is the money?
| A Shortcut to Estimating Non-Functional Requirements?
27 core modules
14 GUI portals
35 interfaces
2 frameworks
3.745 CFP
109 NFR

7. The solution is . . . ΣSolution
| A Shortcut to Estimating Non-Functional Requirements?
𝑐(𝑏) = ෍
𝑥 ∈ 𝑏
𝑐 𝑥 + 𝑂 𝑏

8. The ΣSolution
| A Shortcut to Estimating Non-Functional Requirements?
Most IT-projects are heterogeneous solutions
to fulfill functional and non-functional requirements

9. The cost engineer and the ΣSolution
| A Shortcut to Estimating Non-Functional Requirements?
Work with ‘size’ measures
for different types of
requirements
Estimate the cost of
each leaf in the solution to
estimate the total cost of the solution

10. The customer and the ΣSolution
Traceabilty from requirements to cost:
| A Shortcut to Estimating Non-Functional Requirements?
Requirement 1
Requirement 2
Requirement 3
Requirement n
. . .
Software
Hardware
Infrastructure
as a Services
Tools
. . .
Cost
Cost
Cost
Cost
Cost
. . .
TCO

11. nesma
𝑐(𝑏) = ෍
𝑥 ∈ 𝑏
𝑐 𝑥 + 𝑂 𝑏

12. The ΣSolution
For a given solution the cost estimate is described as:
| A Shortcut to Estimating Non-Functional Requirements?
𝑐(𝑏) = ෍
𝑥 ∈ 𝑏
𝑐 𝑥 + 𝑂 𝑏
Where:
c(b) is the cost of delivering branch b
c(x) is the cost of delivering leaf x
Ob is the integration overhead
𝑐 𝑥 = 𝑆 𝑥 ∙ 𝑅 𝑥
Where:
Sx is the size of leaf x
Rx is the unit cost

13. We need multiple ‘sizes’ to cover NFR
In the absence of a better word we use ‘size’ for each concept that can
act as a base for a cost function for a leaf of the Solution
Examples:
▪ Functional Size for software elements
▪ Square footing or power usage for hardware hosting
▪ Number of FTEs for organizational entities
▪ Bandwidth, storage and computing capacity for infrastructure
| A Shortcut to Estimating Non-Functional Requirements?

14. The ΣSolution and the COSMIC approach
The approach is similar
Is meant for homogeneous
software solutions
Does only offer definitions
of true NFR
| A Shortcut to Estimating Non-Functional Requirements?

15. The ΣSolution and the EPA approach
The approach has a
similar basis
Productivity drivers are
on total project level
Estimation model is more
complex
| A Shortcut to Estimating Non-Functional Requirements?

16. The ΣSolution and the SNAP approach
The SNAP approach only distinguishes between:
▪ Functional Size, measured in IFPUG FP
▪ Non-Functional Size, measured in SNAP points
All Non-Functional Requirements are captured in a single size measure
Project Requirements & Constraints are not covered
| A Shortcut to Estimating Non-Functional Requirements?

17. nesma

18. There is work to do
▪ Introduce Solution Based Estimation in the Architecture community
▪ Standardize Estimation methods for different types of components
▪ Introduce these methods in the Software Measurement community
▪ Set up a certification program to certify Software Cost Engineers
▪ Add the standardized components to a public repository
▪ Use these components in Proposal Requests, Tenders and Contracts
| A Shortcut to Estimating Non-Functional Requirements?

19. Your feedback is welcome
nesma