Improve Estimation maturity using Functional Size Measurement and Historical ...Harold van Heeringen
Many software projects still fail in recent years, also agile projects. Improving estimation maturity in order to start with a realistic estimate instead of an optimistic one can really save billions of dollars in most local software industries. The Chinese government may now be moving towards an active software estimation maturity improvement strategy in its new 5-year plan. Functional size measurement and relevant historical data as well as parametric estimation tools are key to such a strategy. This presentation was the key-note speech at the China System and Software Process Improvement Association conference on software estimation, Beijing China, May 27 2016.
The importance of benchmarking software projects - Van Heeringen and OgilvieHarold van Heeringen
Benchmarking is a crucial management activity that enables organizations to understand how competitive they are. Using functional size measurement methods and historical data enables organizations to improve their processes and become more succesful.
This presentation shows why it is important to benchmark the performance of software projects and organizations. Measurement of performance and comparing this to relevant peer groups provides the knowledge and understanding for managemenr to make informed decisions on where the organization stands and where it should go. This presentation was given at the Italian GUFPI-ISMA conference (December 2013) and addressed also the way the Italian industry is performing according to the ISBSG Country Analysis report.
The Use of Functional Size in the Industry.pdfNesma
In this webinar, the emphasis is on the use of Functional Size in the Industry, and we focus on several use cases where functional size helps organizations to make impactful decisions based on objective metrics and data.
While traditional performance metrics often measure individual output or adherence to pre-defined plans, measuring performance in agile teams requires a different approach. Agile teams operate in iterative cycles, prioritizing adaptability and learning over rigid goals. So, why do organizations still measure their performance?
By using the right metrics in the right way, organizations can empower their agile teams to thrive and deliver exceptional results.
Software Cost Estimation webinar January 2024.pdfNesma
In this webinar you will learn why Software Cost Estimation is important, what is the Software Cost Estimation Body of Knowledge for Software and the ways you can become a professional certified software cost estimator SCEC!
Improve Estimation maturity using Functional Size Measurement and Historical ...Harold van Heeringen
Many software projects still fail in recent years, also agile projects. Improving estimation maturity in order to start with a realistic estimate instead of an optimistic one can really save billions of dollars in most local software industries. The Chinese government may now be moving towards an active software estimation maturity improvement strategy in its new 5-year plan. Functional size measurement and relevant historical data as well as parametric estimation tools are key to such a strategy. This presentation was the key-note speech at the China System and Software Process Improvement Association conference on software estimation, Beijing China, May 27 2016.
The importance of benchmarking software projects - Van Heeringen and OgilvieHarold van Heeringen
Benchmarking is a crucial management activity that enables organizations to understand how competitive they are. Using functional size measurement methods and historical data enables organizations to improve their processes and become more succesful.
This presentation shows why it is important to benchmark the performance of software projects and organizations. Measurement of performance and comparing this to relevant peer groups provides the knowledge and understanding for managemenr to make informed decisions on where the organization stands and where it should go. This presentation was given at the Italian GUFPI-ISMA conference (December 2013) and addressed also the way the Italian industry is performing according to the ISBSG Country Analysis report.
The Use of Functional Size in the Industry.pdfNesma
In this webinar, the emphasis is on the use of Functional Size in the Industry, and we focus on several use cases where functional size helps organizations to make impactful decisions based on objective metrics and data.
While traditional performance metrics often measure individual output or adherence to pre-defined plans, measuring performance in agile teams requires a different approach. Agile teams operate in iterative cycles, prioritizing adaptability and learning over rigid goals. So, why do organizations still measure their performance?
By using the right metrics in the right way, organizations can empower their agile teams to thrive and deliver exceptional results.
Software Cost Estimation webinar January 2024.pdfNesma
In this webinar you will learn why Software Cost Estimation is important, what is the Software Cost Estimation Body of Knowledge for Software and the ways you can become a professional certified software cost estimator SCEC!
Nesma event June '23 - How to use objective metrics as a basis for agile cost...Nesma
This document discusses using objective metrics for agile cost estimation and monitoring. It notes that while agile development is challenging to estimate and measure, sizing software using functional points allows for estimation and benchmarking using data. Story points alone do not provide enough information to manage value creation over time. Key metrics like productivity, defects, and where teams spend their effort need to be measured to understand performance. Effort registration is crucial for project control to understand functionality delivered and productivity. Functional size measurement creates reference points to help manage projects.
Nesma event June '23 - Easy Function Sizing - Introduction.pdfNesma
The document introduces a new method called Easy Functional Sizing (EFS) that aims to provide a simpler alternative to the more complex High Level Function Point Analysis method. EFS is designed to be aligned with modern development methods, have fewer debates around function point types, and be easy to learn. It maintains the same level of assessment as High Level FPA but only has 4 pages of definitions and rules organized into 3 components. Initial analysis shows EFS results are comparable to High Level FPA with less than a 2% difference on average. Feedback is requested from reviewers knowledgeable and not knowledgeable in FPA to test if EFS provides enough depth.
The journey of UNISON Cost Engineering in the field of automotive software cost estimation started in 2018. The expectation is that in 2030 the cost of software will be 50% of the total production cost of a car. To help the OEM get a proper understanding of the software development cost they need to use some form of size measurement to compare, challenge and control the cost of software development by the software vendors.
The COSMIC battle between David and Goliath - Paul HusseinNesma
No more exhaustive and emotional discussions on price and deliverables. Predictable prices for projects and changes. No escalating maintenance costs. This can only be done by specifying exactly what you want and outsource it to the right service providers that have the required platform already in place.
Succesful Estimating - It's how you tell the story - Amritpal Singh AgarNesma
Estimating the Cost of something is a profession. But then you have to tell the story about the estimate to whoever needs to hear that story. The success of how you tell the story is determining the success of the cost estimate.
(Increasing) Predictability of large Government ICT Projects - Koos VeefkindNesma
1) The document discusses using Function Point Analysis (FPA) to increase the predictability of large government IT projects.
2) FPA is used to estimate the total development capacity needed and provide periodic estimates of the expected lead time to completion based on measuring function points completed and productivity.
3) Tracking actual function points completed against the initial goal and expected progress allows projects to identify risks and make adjustments to the planning and estimates.
CEBoK for Software Past Present Future - Megan JonesNesma
The Cost Estimation Body of Knowledge for Software is in development for a number of years within ICEAA. First as a section of the general CEBoK, but it will be established as a separate CEBoK-S for Software, since software is becoming very prominent within the cost estimation community.
Agile Development and Agile Cost Estimation - A return to basic principles - ...Nesma
Is there a natural tension between agile development and traditional cost management or do we need to return to basic principles? Even when you are flexible, you still need to make a plan, build an estimate and measure what you have achieved.
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...Nesma
Agile software development does not always live up to the promises. Especially in the field of IT Cost Management. Without proper estimation and tracking the value cannot be made clear.
Project Succes is a Choice - Joop SchefferlieNesma
Project success is a choice. Don't stop thinking about the best way to do a project, agile or not. Select the best competencies to ensure that the project will be successful.
Deze presentatie beschrijft een praktische implementatie van het gebruik van Nesma functiepunten in Agile deliveries. Deze presentatie is gepresenteerd door Richard Sweer van Infinity tijdens de webinar Afrekenen met functiepunten. Voor meer info: www.nesma.org; conference@nesma.org.
Software sizing as an essential measure past present and future - Dan Galorat...Nesma
The document discusses different methods for software sizing, both historically and currently. It covers lines of code, functional sizes, story points, and more. It also discusses sizing commercial off-the-shelf (COTS) software by considering features, objects, and the required cognition. COTS cognition involves understanding features, referenced and configured tables, and input/output/inquiry services or classes. The percentage of COTS functionality required is also a factor. Overall, the document advocates that there are many viable sizing methods and standards are important, while not dismissing lines of code when appropriate.
Rick Collins presented on the importance of software size in cost estimating for defense programs. Recent studies by the GAO and others found that many defense programs experienced significant software size growth compared to initial estimates, with actual sizes being 20-60% larger than estimated. This consistent size growth across programs emphasizes the need for cost estimates to be based on actual size data from completed projects in order to establish credible and defensible estimates. Failing to account for likely size growth can lead to unrealistic budgets and schedules for new programs.
The document discusses a software estimation challenge hosted at the Nesma Conference 2020. It provides context about the conference and challenge, describes the inputs, tasks, and deliverables of the challenge. It then details Metri's approach to completing the tasks, which included estimating the functional size using various methods, estimating the impact of non-functional requirements, and using historical project data to estimate the effort required to develop the software.
Estimation of a micro services based estimation application bhawna thakur -...Nesma
The document discusses estimating the cost of developing a microservices-based estimation application. It describes how initial cost estimates were 34% lower than actual costs due to not properly accounting for the independent nature of microservices. By resizing the application to treat each microservice independently and adjust complexity factors, estimates were brought within 2% of actual costs. The conclusion is that accurately estimating microservices applications requires a different sizing approach that considers how microservices impact functions like data and transactions compared to monolithic architectures.
Nesma event June '23 - How to use objective metrics as a basis for agile cost...Nesma
This document discusses using objective metrics for agile cost estimation and monitoring. It notes that while agile development is challenging to estimate and measure, sizing software using functional points allows for estimation and benchmarking using data. Story points alone do not provide enough information to manage value creation over time. Key metrics like productivity, defects, and where teams spend their effort need to be measured to understand performance. Effort registration is crucial for project control to understand functionality delivered and productivity. Functional size measurement creates reference points to help manage projects.
Nesma event June '23 - Easy Function Sizing - Introduction.pdfNesma
The document introduces a new method called Easy Functional Sizing (EFS) that aims to provide a simpler alternative to the more complex High Level Function Point Analysis method. EFS is designed to be aligned with modern development methods, have fewer debates around function point types, and be easy to learn. It maintains the same level of assessment as High Level FPA but only has 4 pages of definitions and rules organized into 3 components. Initial analysis shows EFS results are comparable to High Level FPA with less than a 2% difference on average. Feedback is requested from reviewers knowledgeable and not knowledgeable in FPA to test if EFS provides enough depth.
The journey of UNISON Cost Engineering in the field of automotive software cost estimation started in 2018. The expectation is that in 2030 the cost of software will be 50% of the total production cost of a car. To help the OEM get a proper understanding of the software development cost they need to use some form of size measurement to compare, challenge and control the cost of software development by the software vendors.
The COSMIC battle between David and Goliath - Paul HusseinNesma
No more exhaustive and emotional discussions on price and deliverables. Predictable prices for projects and changes. No escalating maintenance costs. This can only be done by specifying exactly what you want and outsource it to the right service providers that have the required platform already in place.
Succesful Estimating - It's how you tell the story - Amritpal Singh AgarNesma
Estimating the Cost of something is a profession. But then you have to tell the story about the estimate to whoever needs to hear that story. The success of how you tell the story is determining the success of the cost estimate.
(Increasing) Predictability of large Government ICT Projects - Koos VeefkindNesma
1) The document discusses using Function Point Analysis (FPA) to increase the predictability of large government IT projects.
2) FPA is used to estimate the total development capacity needed and provide periodic estimates of the expected lead time to completion based on measuring function points completed and productivity.
3) Tracking actual function points completed against the initial goal and expected progress allows projects to identify risks and make adjustments to the planning and estimates.
CEBoK for Software Past Present Future - Megan JonesNesma
The Cost Estimation Body of Knowledge for Software is in development for a number of years within ICEAA. First as a section of the general CEBoK, but it will be established as a separate CEBoK-S for Software, since software is becoming very prominent within the cost estimation community.
Agile Development and Agile Cost Estimation - A return to basic principles - ...Nesma
Is there a natural tension between agile development and traditional cost management or do we need to return to basic principles? Even when you are flexible, you still need to make a plan, build an estimate and measure what you have achieved.
Resolving Cost Management and Key Pitfalls of Agile Software Development - Da...Nesma
Agile software development does not always live up to the promises. Especially in the field of IT Cost Management. Without proper estimation and tracking the value cannot be made clear.
Project Succes is a Choice - Joop SchefferlieNesma
Project success is a choice. Don't stop thinking about the best way to do a project, agile or not. Select the best competencies to ensure that the project will be successful.
Deze presentatie beschrijft een praktische implementatie van het gebruik van Nesma functiepunten in Agile deliveries. Deze presentatie is gepresenteerd door Richard Sweer van Infinity tijdens de webinar Afrekenen met functiepunten. Voor meer info: www.nesma.org; conference@nesma.org.
Software sizing as an essential measure past present and future - Dan Galorat...Nesma
The document discusses different methods for software sizing, both historically and currently. It covers lines of code, functional sizes, story points, and more. It also discusses sizing commercial off-the-shelf (COTS) software by considering features, objects, and the required cognition. COTS cognition involves understanding features, referenced and configured tables, and input/output/inquiry services or classes. The percentage of COTS functionality required is also a factor. Overall, the document advocates that there are many viable sizing methods and standards are important, while not dismissing lines of code when appropriate.
Rick Collins presented on the importance of software size in cost estimating for defense programs. Recent studies by the GAO and others found that many defense programs experienced significant software size growth compared to initial estimates, with actual sizes being 20-60% larger than estimated. This consistent size growth across programs emphasizes the need for cost estimates to be based on actual size data from completed projects in order to establish credible and defensible estimates. Failing to account for likely size growth can lead to unrealistic budgets and schedules for new programs.
The document discusses a software estimation challenge hosted at the Nesma Conference 2020. It provides context about the conference and challenge, describes the inputs, tasks, and deliverables of the challenge. It then details Metri's approach to completing the tasks, which included estimating the functional size using various methods, estimating the impact of non-functional requirements, and using historical project data to estimate the effort required to develop the software.
Estimation of a micro services based estimation application bhawna thakur -...Nesma
The document discusses estimating the cost of developing a microservices-based estimation application. It describes how initial cost estimates were 34% lower than actual costs due to not properly accounting for the independent nature of microservices. By resizing the application to treat each microservice independently and adjust complexity factors, estimates were brought within 2% of actual costs. The conclusion is that accurately estimating microservices applications requires a different sizing approach that considers how microservices impact functions like data and transactions compared to monolithic architectures.
2. FPA termen en DWH termen
Interne
Logische
Gegevens-
Verzameling
Invoer- Uitvoer-
Functie functie
IF ILGV UF
Te tellen systeem
Grens te
tellen
systeem
Presentatie ALV Nesma 2006 FPA voor DWH projecten
2 van 29
3. Agenda
• Wat doet een DWH voor een organisatie?
– Welke architectuur volgt daaruit
• Wat staat er in een Globaal Ontwerp aan DWH
termen?
– Feiten, Dimensies, Data Marts, Sterren, ...
• Hoe tellen we?
– Waar op letten?
Presentatie ALV Nesma 2006 FPA voor DWH projecten
3 van 29
4. Nu
Informatie?
Y=A
Dus...? Y=B
C=A
Presentatie ALV Nesma 2006 FPA voor DWH projecten
4 van 29
5. Wens
Eenduidigheid!
Y=A
Juist! C=(A+B)/2
C=(A+B)/2
Presentatie ALV Nesma 2006 FPA voor DWH projecten
5 van 29
6. Informatie Analyse
1/2
Y=A
De omzet van de afdeling <W> in maand <Y> is <A>
Presentatie ALV Nesma 2006 FPA voor DWH projecten
6 van 29
7. Informatie Analyse
2/2
Y=B
Y=A
C=(A+B)/2
De omzet van de afdeling <W> in maand <Y> is <A>
De omzet van de afdeling <Z> in maand <Y> is <B>
De omzet van het bedrijf in de maand <Y> is het gemiddelde van de afdeling <X> en <Z>
Presentatie ALV Nesma 2006 FPA voor DWH projecten
7 van 29
8. Herkomst Analyse
Gegevensbronnen
W,Y,A
Z,Y,B
Presentatie ALV Nesma 2006 FPA voor DWH projecten
8 van 29
9. Architectuur – SPOTT
Definities
C, Y, (A+B)/2 W,Y,A
C, Y, (A+B)/2
C, Y, (A+B)/2
Z,Y,B
Presentatie ALV Nesma 2006 FPA voor DWH projecten
9 van 29
10. Architectuur – SPOTT
Gegevens
C, Y, (A+B)/2 W,Y,A
Hoofdafdeling Jaar
Afdeling Maand
C, Y, (A+B)/2
Omzet
Z,Y,B
Presentatie ALV Nesma 2006 FPA voor DWH projecten
10 van 29
11. Architectuur – Performance
C, Y+1, (A+B)/2
Veel van alles W,Y,A!
C, Y, (A+B)/2 W,Y+1,A1
C, Y+2, (A+B)/2 W,Y+2,A2
Hoofdafdeling Jaar
C, Y+1, (A+B)/2 Afdeling Maand
C, Y, (A+B)/2
C, Y+2, (A+B)/2
Omzet
Z,Y,B
Z,Y+1,B1
Z,Y+2,B2
Presentatie ALV Nesma 2006 FPA voor DWH projecten
11 van 29
13. Architectuur –
Systeemonderdelen
Data
Marts
Data
Staging
Warehouse
Data Area
Marts
Presentatie ALV Nesma 2006 FPA voor DWH projecten
13 van 29
14. DWH - Architectuur
Back Room Front Room
Source Data Application Presentation
Layer Layer Layer Layer
Source Data
Data Staging Area Data M arts Reports End-user
Internal/E xternal Warehouse
(ETL) (ETL) Win Gui
ODS
(ETL)
Data
Extraction, (ETL) Brow ser
Transformation
?? & Load (ETL)
Data
(ETL)
W arehouse
Extern
Operational Inform ational
Presentatie ALV Nesma 2006 FPA voor DWH projecten
14 van 29
15. Agenda 2/3
• Wat doet een DWH voor een organisatie?
– Welke architectuur volgt daaruit
• Wat staat er in een Globaal Ontwerp aan DWH
termen?
– Feiten, Dimensies, Data Marts, Sterren, ...
• Hoe tellen we?
– Waar op letten?
Presentatie ALV Nesma 2006 FPA voor DWH projecten
15 van 29
16. FPA-tellingen per projectfase
(1) Indicatief – Projectvoorstel - Ordegrootte +/- 50%
• Input: Gegevensmodel
(2) Globaal – Globaal ontwerp
• Input: Logische gegevensverzamelingen en relaties
• Input: De systeemfuncties met hun ...
• Input: In- en uitgaande informatiestromen
(3) Gedetailleerd – Specificaties gereed
• Input: als globaal maar tot op niveau van elk
betrokken “attribuut”.
Presentatie ALV Nesma 2006 FPA voor DWH projecten
16 van 29
17. Globaal ontwerp
– Dimensies? Feiten?
Dimensies? Ordeningen! Feiten: #calls, afhandelings-
• Geografie tijd, #medew. per ... :
• Afdelingen 1. Uur, dag, week, maand,
• Productgroepen kwartaal, jaar, totaal
• Processen 2. Afdeling, vestiging, regio,
land, totaal
• Klantsegment
3. Servicelijn, type lijn
• Tijd
4. Skilllevel, skill, alles
5. E-mail of telefoon of ?
Dimensies? Samenvoegingen
6. IVR of agent of ?
• Serviceproduct
– service + wijze van
verstrekking + vestiging + 1 feit met 6 dimensies!
vestigingstype + regio
Presentatie ALV Nesma 2006 FPA voor DWH projecten
17 van 29
18. DWH <> Data Mart
Customer Contact Center
Feiten DWH: Call Feiten Data Mart: Call
• Tijdstippen IVR-in en -uit • # calls
• IVR-menu (uit) • Totale gesprekstijd
• Medewerker • # binnen norm
• Tijdstip einde gesprek • # medewerkers
• Normtijd
Dimensies Data Mart
Dimensies DWH
• Tijd
• Tijd
• Organisatie
• Medewerker
Organisatie • Service of Verkoop
Service • Skilllevel, skill, alles
Skill
• E-mail of telefoon of ?
• of IVR-menu
Service • IVR, IVR/CCC of CCC !!
Presentatie ALV Nesma 2006 FPA voor DWH projecten
18 van 29
19. Data Mart <> Rapport
Customer Contact Center
Feiten Data Mart: Call Feiten Rapport: Call
• # calls • # calls
• Totale gesprekstijd • Gemiddelde tijd
• # binnen norm • % binnen norm
• # medewerkers actief • % actief: # medewerkers
Dimensies Data Mart actief / # medewerkers
• Tijd aanwezig
• Organisatie Rapporten
• Dag x team [teamleiders]
• Service of Verkoop • Week x afdeling [CCC-mgt]
• Skilllevel, skill, alles • Verkoop x team sales [acc.mgt]
• E-mail of telefoon of ? • ...
• IVR, IVR/CCC of CCC !! DM organisatie!!
• # medewerkers aanwezig
Presentatie ALV Nesma 2006 FPA voor DWH projecten
19 van 29
20. Agenda 3/3
• Wat doet een DWH voor een organisatie?
– Welke architectuur volgt daaruit
• Wat staat er in een Globaal Ontwerp aan DWH
termen?
– Feiten, Dimensies, Data Marts, Sterren, ...
• Hoe tellen we?
– Waar op letten?
Presentatie ALV Nesma 2006 FPA voor DWH projecten
20 van 29
21. Functies aan de rand
Gegevens Systeemgrens
verzameling IF DWH
3 IFs
KGV
IF
Ster
Dimensie Dimensie Data Mart
Upload Staging
Feit Dimensie
bestand gegevens UFs
ILGV Dimensie Dimensie Feit
Staging 5 ILGVs Dimensie
gegevens 1 ILGV
ILGV Data Mart
Upload Staging Relationeel DWH Dimensie
bestand gegevens
ILGV Entiteit Entiteit Feit
Upload Staging Entiteit Dimensie UFs
bestand gegevens Entiteit 3 ILGVs
ILGV
Technische
kopie
IFs
IFs
Data Data Data Data
Reports
Sources Staging Area Ware House Mart
Presentatie ALV Nesma 2006 FPA voor DWH projecten
21 van 29
22. DWH – DSA
DSA: zero points
Technisch hulpmiddel Niet tellen
• Vertaling broncode naar DWH-codes
• Bufferfunctie i.v.m. Verschillende frequenties van
dataleveringen
• Toevoegen tijdvak levering / geldigheidsperiode
• Toevoegen metagegevens over proces
• Handhaven juiste volgorde verwerking
• Archiveren gegevens
Rapportages aan gebruikers? Wel tellen
Presentatie ALV Nesma 2006 FPA voor DWH projecten
22 van 29
23. DWH – DSA
DSA: zero points
GV Systeemgrens
in bron DWH
(IF)
KGV
Upload
bestand Staging
gegevens
ILGV
DWH
Upload Staging
bestand gegevens
ILGV
Upload Staging
bestand gegevens
ILGV
Technisch
kopie, niet tellen
(IF)
Data Data Data Data
Reports
Sources Staging Area Ware House Mart
Presentatie ALV Nesma 2006 FPA voor DWH projecten
23 van 29
24. DWH – DWH
Dimensie:1 ILGV,1 IF/recordtype & Feit:1 ILGV,1 IF/bron
“Vertaling van de brongegevens naar een corporate
structuur / visie (SPOTT)”
Zelfstandige ILGV’s
• Dimensies
Worden door gebruikers als één geheel gezien
1 ILGV
• Dimensielagen (-levels, -hierachie)
Als de “lagen” van een dimensie anders worden
gevuld is er sprake van meerdere functies
1 IF per andere afhandeling (Nesma : recordtype)
• Feiten
Vaak meerdere bronnen voor feiten
1 ILGV en 1 IF per bron
Presentatie ALV Nesma 2006 FPA voor DWH projecten
24 van 29
25. DWH – DWH
Dimensie:1 ILGV,1 IF/recordtype & Feit:1 ILGV,1 IF/bron
Gegevens Systeemgrens
verzameling DWH
IF
3 IFs
KGV
Ster
Dimensie Dimensie
Upload Staging
bestand gegevens Feit
ILGV Dimensie Dimensie
Staging 5 ILGVs
gegevens
ILGV
Upload Staging Relationeel DWH
bestand gegevens
Entiteit Entiteit
ILGV
Upload Staging Entiteit
bestand gegevens Entiteit
ILGV
Technische
kopie
IFs
Data Data Data Data
Reports
Sources Staging Area Ware House Mart
Presentatie ALV Nesma 2006 FPA voor DWH projecten
25 van 29
26. DWH – DM
DM:1 ILGV,1 IF
“Vertaling van de corporate structuur / visie (SPOTT)
naar toepassing, bedrijfsafdeling of staffunctie”
Zelfstandige ILGV’s
• Datamarts
1 ILGV
mits: anders dan aggregatie alleen en combinatie van
feiten uit DWH.
• Vulling DM
1 IF
• Dimensies
Aanname: Verwijzing c.q. Technische kopie van
dimensies in DWH
Anders tellen als bij DWH
Presentatie ALV Nesma 2006 FPA voor DWH projecten
26 van 29
27. DWH – Rapportages
R:1 UF per rapportgroep
Vertaling van techniek naar functionaliteit: groepeer
gelijkende rapporten (BO vs Cognos)
- zelfde inhoud en opmaak maar andere selectie of
ander aggregatieniveau in dimensie => Zelfde UF
(Cognos: uren, naar invalshoeken tijd, organisatie en
product
vs.
BO: uren per dag per team, uren per week per afdeling,
uren per maand per productlijn)
• Punten voor rapportage apart houden: andere
hulpmiddelen, ander aantal uren/FP.
Presentatie ALV Nesma 2006 FPA voor DWH projecten
27 van 29
28. Samenvatting / Vragen
Gegevens Systeemgrens
verzameling IF DWH
3 IFs
KGV
IF
Ster
Dimensie Dimensie Data Mart
Upload Staging
Feit Dimensie
bestand gegevens UFs
ILGV Dimensie Dimensie Feit
Staging 5 ILGVs Dimensie
gegevens 1 ILGV
ILGV Data Mart
Upload Staging Relationeel DWH Dimensie
bestand gegevens
ILGV Entiteit Entiteit Feit
Upload Staging Entiteit Dimensie UFs
bestand gegevens Entiteit 3 ILGVs
ILGV
Technische
kopie
IFs
IFs
Data Data Data Data
Reports
Sources Staging Area Ware House Mart
Presentatie ALV Nesma 2006 FPA voor DWH projecten
28 van 29
29. Auteurs
Sinds eind 2004
• Jolijn Onvlee
– NESMA
• Rob Eveleens
– Atos Origin DWH-expert
FP/FD-projecten
• Theo Kersten
– Atos Origin, FPA, DWH KPN
• Nico Mak
– Projectoffice AAB
Presentatie ALV Nesma 2006 FPA voor DWH projecten
29 van 29