Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Similar a How to ensure your code is maintainable
Similar a How to ensure your code is maintainable (20)
Último
Último (20)
How to ensure your code is maintainable
- 1. Sogeti Java Meetup Quality Engineering How to ensure your code is maintainable Peter Rombouts Senior Technology Consultant Sogeti
- 2. Security Classification © 2019 Sogeti. All rights reserved. 2 Presentation title | Date 2 Who am I https://peterrombouts.nl https://www.twitter.com/prombouts https://www.github.com/prombouts https://labs.sogeti.com Senior Technology Consultant Peter Rombouts Cloud Software Architect Over 18 years of experience in IT Passionate about Software Development, Architecture and Cloud SogetiLabs Fellow Azure Cloud Cognitive Services Software Development Multi Cloud QSD
- 3. Security Classification © 2019 Sogeti. All rights reserved. 3 Presentation title | Date Systems and software engineering — Systems and software Quality Requirements and Evaluation (SQuaRE) — System and software quality models ISO 25010 for short What is Software Quality?
- 4. Security Classification © 2019 Sogeti. All rights reserved. 4 Presentation title | Date The International Standard defines: Quality in Use Model Product Quality Model
- 5. Security Classification © 2019 Sogeti. All rights reserved. 5 Presentation title | Date The International Standard defines: Quality in Use Model Product Quality Model
- 6. Security Classification © 2019 Sogeti. All rights reserved. 6 Presentation title | Date The International Standard defines: Quality in Use Model Product Quality Model
- 7. Security Classification © 2019 Sogeti. All rights reserved. 7 Presentation title | Date Guidelines (SIG) 1. Write Short Units of Code 2. Write Simple Units of Code 3. Write Code Once 4. Keep Unit Interfaces Small 5. Separate Concerns in Modules 6. Couple Architecture Components Loosely 7. Keep Architecture Components Balanced 8. Keep Your Codebase Small 9. Automate Tests 10.Write Clean Code SIG was established in 2000. Its roots can be traced back to the Dutch National Research Institute for Mathematics and Computer Science (Centrum voor Wiskunde en Informatica [CWI]).
- 8. Security Classification © 2019 Sogeti. All rights reserved. 8 Presentation title | Date Guidelines (SIG) 1. Write Short Units of Code 2. Write Simple Units of Code 3. Write Code Once 4. Keep Unit Interfaces Small 5. Separate Concerns in Modules 6. Couple Architecture Components Loosely 7. Keep Architecture Components Balanced 8. Keep Your Codebase Small 9. Automate Tests 10.Write Clean Code SIG was established in 2000. Its roots can be traced back to the Dutch National Research Institute for Mathematics and Computer Science (Centrum voor Wiskunde en Informatica [CWI]).
- 9. Security Classification © 2019 Sogeti. All rights reserved. 9 Presentation title | Date Tools How to choose? Static Code Analysis? Software Composition Analysis?
- 10. Security Classification © 2019 Sogeti. All rights reserved. 10 Presentation title | Date What tooling is available? Analyses the(lines of) code. Normally used in automated pipelines. Examples: • SonarQube • PMD • NDepend • BinSkim Analyses the dependencies Mostly stand-alone products with notification capabilities. Also often used for checking licenses in open-source packages and if they comply with company policies.. Examples: • WhiteSource • WhiteSource Bolt • Snyk • Fossa • npm-audit • David (Node.JS) Static Code Analysis Software Composition Analysis
- 11. Security Classification © 2019 Sogeti. All rights reserved. 11 Presentation title | Date What tooling is available? Analyses the(lines of) code. Normally used in automated pipelines. Examples: • SonarQube • PMD • NDepend • BinSkim Analyses the dependencies Mostly stand-alone products with notification capabilities. Also often used for checking licenses in open-source packages and if they comply with company policies.. Examples: • WhiteSource • WhiteSource Bolt • Snyk • Fossa • npm-audit • David (Node.JS) Static Code Analysis Software Composition Analysis
- 12. Security Classification © 2019 Sogeti. All rights reserved. 12 Presentation title | Date Static Code Analysis: SonarQube
- 13. Security Classification © 2019 Sogeti. All rights reserved. 13 Presentation title | Date
- 14. Security Classification © 2019 Sogeti. All rights reserved. 14 Presentation title | Date Software Composition Analysis: WhiteSource Bolt
- 15. Security Classification © 2019 Sogeti. All rights reserved. 15 Presentation title | Date Software Composition Analysis: WhiteSource Bolt
- 16. Security Classification © 2019 Sogeti. All rights reserved. 16 Presentation title | Date Software Composition Analysis: WhiteSource Bolt
- 17. 17 Sogeti Global Overview | © 2019 Sogeti. All rights reserved. Sogeti Global Overview | © 2019 Sogeti. All rights reserved. Mind The (Tool) Gap!
- 18. Security Classification © 2019 Sogeti. All rights reserved. 18 Presentation title | Date How to proceed?
- 19. Security Classification © 2019 Sogeti. All rights reserved. 19 Presentation title | Date Hoe nu verder?
- 20. Sogeti Java Meetup Quality Engineering Questions? peter.rombouts@sogeti.com https://peterrombouts.nl https://labs.sogeti.com Twitter @prombouts GitHub @prombouts
Notas del editor
- Quality in Use -> 5 characteristics related to outcomes of interaction with a system (including users) Product Quality Model -> Focuses on target computer system that includes the target software product.
- Quality in Use -> 5 characteristics related to outcomes of interaction with a system (including users) Product Quality Model -> Focuses on target computer system that includes the target software product.
- 1. Modularity 2. Reusability 3. Analyzability 4. Modifiability 5. Testability
- At the time of writing, in total SIG has analyzed 7.1 billion lines of code, and 72.7 million new lines of code are uploaded to SIG weekly. SIG is the only organization in the world certified by TÜViT for Trusted Product Maintainability. we have selected metrics that: • Are contained in a set as small as possible • Are technology-independent • Are easy to measure • Enable a meaningful comparison of real-world enterprise software systems
- At the time of writing, in total SIG has analyzed 7.1 billion lines of code, and 72.7 million new lines of code are uploaded to SIG weekly. SIG is the only organization in the world certified by TÜViT for Trusted Product Maintainability. we have selected metrics that: • Are contained in a set as small as possible • Are technology-independent • Are easy to measure • Enable a meaningful comparison of real-world enterprise software systems
- Many tools, what is the ‘golden record’ Another time, another session! C? XML? T-SQL, PL-SQL NIET gratis?
- RDP Session
- RDP Session
- Edge: https://dev.azure.com/sogetiazurefundamentals/sogetiazurefundamentals/_build/results?buildId=258&view=whitesource.ws-bolt.build-tab.wss
- Edge: https://dev.azure.com/sogetiazurefundamentals/sogetiazurefundamentals/_build/results?buildId=258&view=whitesource.ws-bolt.build-tab.wss
- Edge: https://dev.azure.com/sogetiazurefundamentals/sogetiazurefundamentals/_build/results?buildId=258&view=whitesource.ws-bolt.build-tab.wss
- Tool gap! Hard to interpret Will never replace pair programming. Peer review, Expert review.
- Turning the Guidelines into Practice Ensuring that your code is easy to maintain depends on two behaviors in your daily routine: discipline and setting priorities. Discipline Lower-Level (Unit) Guidelines Take Precedence Over Higher-Level (Component) Guidelines\ Remember That Every Commit Counts
- Turning the Guidelines into Practice Ensuring that your code is easy to maintain depends on two behaviors in your daily routine: discipline and setting priorities. Discipline Lower-Level (Unit) Guidelines Take Precedence Over Higher-Level (Component) Guidelines\ Remember That Every Commit Counts 15 -> SKIP INDIEN NO TIME