Presentation about how to be a great software developer and consider quality as first class requirements

1. Software Quality for
Programmersversion 1.0
Paweł Klimczyk
Gemotial 2016

2. About me
• Software engineer
• Running Gemotial Software Studio
• Co-organizer ofWrocNET
• Blog: http://blog.klimczyk.pl
• Contact:
• Twitter @pwlklm
• Mail: pawel@klimczyk.pl

3. Software quality definition
"capability of a software product to conform to
requirements." (ISO/IEC 9001)
Deming:”The problem inherent in attempts to define the quality of a product, almost
any product……….”
Feigenbaum:”Quality is a customer determination, not an engineer's determination,
not a marketing determination, nor a general management determination”
Juran:”Two of these meanings dominate the use of the word: 1. Quality consists of
those product features which meet the need of customers and thereby provide product
satisfaction. 2. Quality consists of freedom from deficiencies. ”
@pwlklm blog.klimczyk.pl
Wikipedia

4. Quality in construction
@pwlklm blog.klimczyk.pl
http://www.leica-geosystems.es/images/new/product_solution/app_eng_siterunner.jpg
https://s-media-cache-
ak0.pinimg.com/originals/97/ea/a4/97eaa4fb3555decb132dc12064072e8c.jpg

5. „Quality” in code
@pwlklm blog.klimczyk.pl

6. Quality check
@pwlklm blog.klimczyk.pl
http://www.e-architect.co.uk/images/jpgs/singapore/uob_plaza_one_two_tr010709_1.jpg
https://i.kinja-img.com/gawker-media/image/upload/18mllspae8l8tjpg.jpg

7. „Great refactor”
@pwlklm blog.klimczyk.pl
https://assets.bwbx.io/images/users/iqjWHBFdfxIU/i0dwq8cFhDmE/v1/-1x-1.jpg

8. How do it in IT ?
@pwlklm blog.klimczyk.pl
How check quality in software ?

9. Measurement - WTF per minute measurement
aka Code Review
@pwlklm blog.klimczyk.pl

10. Measurement – Code Review
@pwlklm blog.klimczyk.pl
https://www.jetbrains.com/upsource/features/screenshots/Features-team-collaboration.png

11. Measurement - It’s not a bug, it’s a feature
@pwlklm blog.klimczyk.pl

12. Measurement - ROI
@pwlklm blog.klimczyk.pl

13. Quality and Quantity- what do you choose?
@pwlklm blog.klimczyk.pl

14. Technical debt and maintenace
@pwlklm blog.klimczyk.pl
Producing more
code leads to
technical debt

15. Effective QualityTriangle
@pwlklm blog.klimczyk.pl

16. Bad Quality Examples
https://pl.wikipedia.org/wiki/ExoMars
@pwlklm blog.klimczyk.pl

17. Code Quality Core
@pwlklm blog.klimczyk.pl
Correctness
Readability
Performance

18. Formal Software Quality Measurement Models
@pwlklm blog.klimczyk.pl
Dromey (1992)
McCall (1977)
Ghezzi (1991)
FURPS+ (1992) IEEE 1061 (1993)
ISO/IEC 9126-1 (1991)
Boehm (1978)
ISO/IEC 25010:2011 (2011)
ISO/IEC 9126:2001 (2001)
SATC (1995)
Kazman (2003)
CMM (1991)

19. Formal Software Quality Measurement Metrics
@pwlklm blog.klimczyk.pl
Integrity Usability
Reliability
Correctness
Efficiency
Testability
Maintanability
Flexibility
Portability
Reusability
Interoperability
Performance
Supportability
Compability
Configurability
Security
Operability
Stability
Safety
Analizability
Changeability
Maturity
Accuracy

20. Formal Code Quality Measurement Methods
@pwlklm blog.klimczyk.pl
Cyclomatic Complexity
Lines of code
Cohesion
Code Coupling Circular Dependency
Temporal Coupling

21. SOLID, Design Patterns,TDD, XP.
@pwlklm blog.klimczyk.pl
SOLID
Design Patterns
Extreme programming
Test driver development
Domain driven development
Best practicesContinuous Integration
Continuous deployment

22. Tooling
@pwlklm blog.klimczyk.pl
Jira
TeamCity
Jenkins
SonarQube
UpSource
NDepend/JDepend
JUnit/NUnit
FindBugs
JarAnalyzer
UCDetector
Cobertura
Checkstyle
FxCop
StyleCop Bamboo

23. Developer skills
@pwlklm blog.klimczyk.pl
http://manifesto.softwarecraftsmanship.org/
Not only working software,
but also well-crafted software
Not only responding to change,
but also steadily adding value
Not only individuals and interactions,
but also a community of professionals
Not only customer collaboration,
but also productive partnerships

24. The Software Craftsman
@pwlklm blog.klimczyk.pl
Sandro Mancuso

25. Specifications
@pwlklm blog.klimczyk.pl

26. Organization quality triangle
@pwlklm blog.klimczyk.pl

27. Conclusions (I)
Whole organization contributes in
delivering quality
What quality do we deliver?
@pwlklm blog.klimczyk.pl

28. Conclusions (II)
What developers can do to improve quality?
@pwlklm blog.klimczyk.pl
•Craftmanship
•SOLID + Design Patterns + tooling
•XP,TDD, BDD, DDD
•Change organization or change
organization

29. Conclusions (III)
Maintenance costs is ~75% of total
costs in application life-cycle
@pwlklm blog.klimczyk.pl

30. Thank you!
Contact
• Blog: http://blog.klimczyk.pl
• Twitter: @pwlklm
• E-mail: pawel@klimczyk.pl
Q&A