1 / 13

Metrics-Driven Development

Metrics-Driven Development. By Mantas Klasavičius CS654 Software Architecture. Summary. I) What is MDD II) Interests III) How to creates metrics IV) Example V) Layered approch VI) Take decisions with metrics VII) Difficulties & Advices VIII) Conclusion. What is MDD ?.

ilana
Télécharger la présentation

Metrics-Driven Development

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Metrics-DrivenDevelopment By Mantas Klasavičius CS654 Software Architecture

  2. Summary I) What is MDD II) Interests III) How to creates metrics IV) Example V) Layered approch VI) Take decisions with metrics VII) Difficulties & Advices VIII) Conclusion

  3. What is MDD ? « Use the metrics to drive the application developmentprocess. » • Principes : • Everythingismeasured • Assignmetrics to metricsowners • Createlayeredmetrics and correlate trends • Everydecisiontakenisbased on metrics

  4. Interests ? • Only 40% of IT projects meet schedule, budget and quality goals (source : IBM) • MDD bring : • Visibility on development process • Problems are immediately detected • “Everything that can be measured can be optimized”

  5. How to creates metrics ? • Eachmetric has an owner • No only the operational teams, but also : • Development teams • Business teams « Companies do not earn money because their servers run smoothly, but because of the functionality their applications and services provide and because they run smoothly »

  6. Example of success: RTB • Adform wanted to create a Real Time Bidding service, able to manage 40.000 queries per second, each transactions taking less than 100ms. (Requirements) • First launch : No more than 5000 QPS and 30% fail the time requirements • After using MDD : 70000 QPS ( 14X more), and below half per cent fail time requirements (around 50X less)

  7. Layered approch • Give structure to the data with 3 layers : • Business metrics • Application metrics • Infrastructure metrics Makeitunderstandable for everyone

  8. Take decisions with metrics • It appends that teams take decisions without knowing how their application really behaves • MDD permits to : • Detect problems and react immediately • Take decision based on metrics • Keep misunderstandings to the minimum • Improve the communication between teams

  9. Take decisions with metrics • Each developers team should be able to answer these questions : • “How do you know that your application is working correctly? (lack of open bugs is not enough, further evidence (e. g. simulations) must be provided) • How does your application performance evolve over time? (E.g. Does it get faster or slower compared to last release? Does it keep performing well under high load?) • How often is your application used? (E.g. How many users are generating reports at the same time? How many banners are published into the system during day? How many transactions do we receive?)”

  10. Difficulties & Advices • Get a MDD organization takes time • Some developers can be affected in their egos • Not only a technical change, but a cultural change • The changes have to be as smooth as possible • Spending too much time choosing a metrics tool is a waste • Choose the metrics that fits with the company vision • Unused metrics have to be deleted

  11. Conclusion • Everything that can be measured can be optimazed • The communication becomes data-driven and less emotional • MDD helps to improve relations within and between teams. • MDD is a kindof leanmanagement • Incorporating MDD canbeverydifficult, but benefits are potentiallyhuge

  12. References • http://www.infoq.com/articles/metrics-driven-development • http://devopsangle.com/2012/12/19/metrics-driven-development-lets-know-a-bit-more/ • http://faethconsulting.com/it-project-failure-rates-facts-and-reasons/ • http://java.dzone.com/articles/metrics-driven-development • http://fr.slideshare.net/mikebrittain/metrics-driven-engineering-at-etsy

  13. Thank you

More Related