Developing future-proof software starts today The QSD Qualification: Maintainability Foundation Level

Transcription

1 Developing future-proof software starts today The QSD Qualification: Maintainability Foundation Level Yiannis Kanellopoulos, Gijs Wijnholds 8 th of March 2016 GETTING SOFTWARE RIGHT

2 About SIG Getting Software Right We are an international consultancy firm with HQs in Amsterdam, and we aim at improving software. Started in 2000 as a spin-off of CWI. We operate as an independent, impartial mediator between IT customers and suppliers. We deliver insight to management on IT projects and systems. We do this based on validated facts and measurements. We actively support scientific research in the field of software engineering. Page 2 of 25

3 Our Analysis Lab in numbers Sole "Trusted Lab in Europe being accredited with the ISO standard 1, supported technologies 50 monitored 22,000 sourcecode- inspections snapshots per week Software Improvement Group PEOPLECERT systems / PUBLIC 227 clients >7,400,000,000 lines of code in software analysis warehouse Page 3 of 25

4 How do we help our clients? The SIG Capabilities Cost Estimation Functional Suitability QSD Architecture Review Performance Efficiency Security Development Process Assessment Early Effort Estimation Compatibility Maintainability Benchmarking Transferability Usability Portability Function point analysis > SIG Capabilities Reliability > SIG ISO IEC Certified Capabilities Page 4 of 25

5 About PEOPLECERT Global leader in assessment & certification of professional skills. ü 4,000,000+ exams delivered to date ü Web & Paper based exams in 25 languages ü Award-winning assessment technology Online Proctoring & Instant Scan and Mark ü e-certificates Speedy hard copy and e-certificate delivery ü 10,000 exam locations worldwide ü Any time, any place exams and customer service, 24/7/365 ü 150 countries every year of exam delivery peoplecert.org Page 5 of 25

6 About PEOPLECERT State-of-the-art, A-to-Z assessment solutions ü Certification Scheme & Test creation test testing & test validation ü Internet-Based / Computer-Based / Paper-Based Exams ü 30 types of Questions - Multiple Choice, Essay, Audio, Video etc. ü Award-winning marking solutions - Automated, Remote, Manual ü Certificate Printing and Delivery - e-certificate, hard copy certificate ü Certificate Validation - online on PEOPLECERT website ü Maintenance of Candidates Records and Database - All Data, Reports peoplecert.org [email protected] Page 6 of 25

7 About PEOPLECERT Commitment to Quality ü Accredited by the National Hellenic Accreditation System (NHAS) as Certification Body according to: ü ISO for Certification of Persons (2006) ü ISO for Certification of Products, Processes & Services (2015) ü Certified by Lloyds Register (UK) according to: ü ISO 9001 Quality Management (2003) ü ISO Customer Satisfaction and Complaints Handling (2006) ü ISO Environmental Management (2006) ü ISO Information & Data Security (2008) ü ISO Use of IT in the delivery of assessments (2013) ü ISO Business Continuity (2015) peoplecert.org Page 7 of 25

8 The global challenge Global IT debt is $500 Billion and rapidly growing* The amount of change requires more developers than are available 52% of debugging effort is spent on 8% of the defects** High-risk parts of software systems consume developers time, no room left for innovation Better code is cheaper 66% of debugging time can be saved with software of high quality *Source: Andy Kyte, Measure and manage your IT debt, Gartner, Inc., August 9, 2010 (last reviewed June 19, 2013) **Source: Deloitte University Press, Tech Trends 2014 Inspiring Disruption ***Source: Dennis Bijlsma, Miguel Alexandre Ferreira, Bart Luijten, Joost Visser: Faster issue resolution with higher technical quality of software. Software Quality Journal, 2012 Page 8 of 25

9 The QSD approach 1) Distilled metrics-based standard A small number of guidelines that are clear, easy-to-follow, meaningful, high-impact 2) Training material for developers to use these standards effectively (Foundation) Thorough explanation, examples, exercises, immediately applicable in daily programming practice 3) Training material for teams to organize around these standards (Advanced) Tools, techniques, practices to be shared by a team to produce quality code consistently Page 9 of 25

10 The QSD Stack Body of Knowledge and videos Online content SIG Vanilla training material Education Exam items Examination and certification Page 10 of 25

11 Body of Knowledge Response of developers who reviewed our book Just finished reading the book this morning. I got a lot more out of the book than I had expected and would recommend it to others. - Vincent O Sullivan, VHI Ireland It contains many good ideas about how to write better code. I must say that my first reaction to some of the ideas is, No way! That's unnecessarily restrictive. But, I often find myself mellowing towards such ideas as I continue reading. - Roger House, Sebastopol CA These guidelines are spot on. They provide a crisp and actionable explanation of what the working programmer needs to know to deliver quality code in a consistent manner. - George Marinos, National Bank of Greece Page 11 of 25

12 Video Material Maintainability Foundation > Complementary material to the body of knowledge > Including many practical examples of building futureproof code > Available online at Page 12 of 25

13 The QSD Qualification Maintainability Foundation > Expected background: 2 years of working experience in object-oriented programming, or BSc in computer science or software engineering > Exam currently available for Java and C# > 75 questions, 2h duration > Closed book > Physical or web proctoring > Certificate of perpetual validity > To date, 170 certificates awarded since its launch early 2016 Page 13 of 25

14 Quality Software Development Trainer Prerequisites > Hold the Quality Software Development Certification. > At least 3 years of experience as a Software Engineer in Object Oriented programming. > Good knowledge of the Object Oriented paradigm and knowledge on how to apply it. > More than 10 hours of Training Experience. Page 14 of 25

15 Quality Software Development Available vanilla material > Trainer s manual > Syllabus > Lesson plans > Code snippets from open source systems > Example exam questions > Slide decks 1 Introduction slide deck 1 Code smells slide deck 8 Guideline slide decks 3 Refactoring slide decks 1 Automated testing slide deck 1 Code hygiene slide deck 1 Example exam questions slide deck 1 Next steps slide deck Page 15 of 25

16 Vanilla Material Samples Two versions of the slide decks 1. Slide decks in PDF, SIG style 1. Slide decks in PPTX, Vanilla style Chapter 2: Code Smells A famous example: Apple s SSL/TLS bug Background details CVE ID: CVE Apple ios 6.x (< 6.1.6) Apple ios 7.x (< 7.0.6) Apple TV 6.x (< 6.0.2) Apple OS X 10.9.x (< ) Impact: millions of devices? Chapter 2: Code Smells A famous example: Apple s SSL/TLS bug Background details CVE ID: CVE Apple ios 6.x (< 6.1.6) Apple ios 7.x (< 7.0.6) Apple TV 6.x (< 6.0.2) Apple OS X 10.9.x (< ) Impact: millions of devices? Unit: SSLVerifySignedServerKeyExchange( ) LOC: 64 McCabe: 14 Nr. of parameters: 5 Unit: SSLVerifySignedServerKeyExchange( ) LOC: 64 McCabe: 14 Nr. of parameters: 5 *Read more: *Read more: Software Improvement Group Page 3 of 4 Page 3 of 4 Page 16 of 25

17 Chapter 4: Write Simple Units of Code (Day 1, Part 3) The guideline Do: > Limit the number of branch points to 4 By: > Splitting complex units into simpler ones > Avoiding complex units Because simple units are: > Easy to test > Easy to understand > Easy to modify Positive effects on other guidelines: > Unit Size > Unit Interfacing Page 17 of 25

18 Chapter 4: Write Simple Units of Code (Day 1, Part 3) How you can measure it Count the cyclomatic complexity: > Every branch point (if, case, for, &&, ) is counted, and we add 1 to the total 2 branch points + 1 = cyclomatic complexity of 3 Page 18 of 25

19 Chapter 4: Write Simple Units of Code (Day 1, Part 3) Examples from the Jenkins CI source code ( This unit has 3 branch points This unit has 4 branch points Page 19 of 25

20 Chapter 4: Write Simple Units of Code (Day 1, Part 3) An example of non-compliant code This unit has 5 branch points

21 Chapter 11: Extract Method (Day 2, Part 2) Applying Extract Method (1/2): Apache Tomcat on * > The init() method contains 69 lines of code and has a McCabe complexity of 19 > The Extract Method has been applied to extract the configuration check to a separate method *Source of snapshot: Page 21 of 25

22 Chapter 11: Extract Method (Day 2, Part 2) Applying Extract Method (2/2): Apache Tomcat on * > After refactoring, the init() method now contains 50 lines of code and has a McCabe complexity of 15 *Source of snapshot: Page 22 of 25

23 Chapter 16: Exam Preparation (Day 3, Part 2) Example questions 7 & 11 > Question: Which statement is true? The complexity of a unit of code is measured by A. The number of lines of code in the unit B. The number of parameters C. The number of branch points D. The number of calls to other units > Question: What is the unit complexity of this unit? A. 13 B. 15 C. 17 D. 20 * Slice.intersects() method from Apache Cassandra on Jan. 18 th 2016 Page 23 of 25

24 Tips & Tricks Focus of the training should be on the Maintainability Mindset : The guidelines; how to interpret them, how to apply them Refactoring techniques to turn non-compliant code into compliant code Maintainable software is a matter of discipline and practice: Show real-time refactorings, or let students do so themselves Bring your/their own source code Building maintainable software is technology-independent, training is language-specific The book and snippets are available in Java and C# Snippets in the slide decks and at Page 24 of 25

25 Q & A Page 25 of 25

26 Contact @sig_eu GETTING SOFTWARE RIGHT