Monitoring Code Quality and Monitoring Code Quality and Development - - PowerPoint PPT Presentation

monitoring code quality and monitoring code quality and
SMART_READER_LITE
LIVE PREVIEW

Monitoring Code Quality and Monitoring Code Quality and Development - - PowerPoint PPT Presentation

Monitoring Code Quality and Monitoring Code Quality and Development Activity by Software Maps by Software Maps J h Johannes Bohnet and Jrgen Dllner B h t d J Dll Hasso-Plattner-Institute for IT Systems Engineering University of


slide-1
SLIDE 1

Monitoring Code Quality and Monitoring Code Quality and Development Activity by Software Maps by Software Maps

J h B h t d Jü Döll Johannes Bohnet and Jürgen Döllner

Hasso-Plattner-Institute for IT Systems Engineering University of Potsdam, Germany Spin-off Company – www.softwarediagnostics.com

slide-2
SLIDE 2

Challenges in

  • Challenging to find the balance.

SW-Development & Maintenance

Challenging to find the balance.

  • Internal quality:

▫ “Less visible“ aspects, e.g., modularity and clearly y y defined interfaces, and code complexity.

  • External quality:

“Vi ibl ” t e g ▫ “Visible” aspects, e.g., features per iteration and post-delivery defects.

  • Reasons for difficulties in finding the balance

▫ Increasing internal quality – no short-term revenue. ▫ Design short-cuts – give impression of quick development success. Design short cuts give impression of quick development success. ▫ Internal quality is largely invisible/non-understandable to managers and customers.

23.05.2011 Slide 2 MTD2011 @ ICSE | Dr. Johannes Bohnet |

slide-3
SLIDE 3

The Concept of Software Maps (1) The Concept of Software Maps (1)

  • Integrating information on code, runtime behavior, evolution

23.05.2011 Slide 3 MTD2011 @ ICSE | Dr. Johannes Bohnet |

slide-4
SLIDE 4

The Concept of Software Maps (2)

Goals

  • Making internal quality better visible and realizable to managers

The Concept of Software Maps (2)

Making internal quality better visible and realizable to managers.

  • Providing an effective communication means between managers

and developers. Development Development File File p Timeline Timeline File File Team Team Application Application Example: Application Application Module Module JBoss Red Hat Inc. 800.000 LoC

23.05.2011 Slide 4 MTD2011 @ ICSE | Dr. Johannes Bohnet |

Java

slide-5
SLIDE 5

“Early-warning system”

  • 5.Oct. 2010 – 5.Jan. 2011: Developers operate on large, complex files

detecting Costs and Risks

5.Oc . 0 0 5.Ja . : e e ope s ope a e o a ge, co p e es in the tomcat module.  Refactoring these files now?

23.05.2011 Slide 5 MTD2011 @ ICSE | Dr. Johannes Bohnet |

slide-6
SLIDE 6

Files containing Bugs

  • Complex files being changed in the context of bug fixes

Files containing Bugs

Complex files being changed in the context of bug fixes.

23.05.2011 Slide 6 MTD2011 @ ICSE | Dr. Johannes Bohnet |

slide-7
SLIDE 7

Conclusions & Future Work

  • Software Maps aim at making internal quality visible.

Conclusions & Future Work

So a e aps a a a g e a qua y s b e.

  • They provide a communication means between developers and

management.

  • Software Maps (www.softwarediagnostics.com)

i d il i l d l t i are in daily use in large development companies.

▫ Medical Systems (Embedded C/C++) ▫ Postage Systems (Embedded C/C++, C#) ▫ Laser Scanning Systems (C++, C#) g y ( ) ▫ Web portals (Java, C#/.Net, VB/.Net, PHP) ▫ Windows Desktop applications (C++) ▫ CAD Systems (C++) ▫ Multimedia Consoles in Automobiles (C++, C#) Multimedia Consoles in Automobiles (C , C#) ▫ Financing & Insurance Systems (Cobol, ABAP) ▫ …

  • Future work:

L t t di ith i ▫ Long-term case studies with companies. ▫ Field Studies. ▫ Visualization techniques to support highest-level management.

23.05.2011 Slide 7 MTD2011 @ ICSE | Dr. Johannes Bohnet |

slide-8
SLIDE 8

Thank You Thank You. Questions or Remarks?

23.05.2011 Slide 8 MTD2011 @ ICSE | Dr. Johannes Bohnet |