The document discusses ensuring code maintainability. It defines software quality according to ISO 25010 as having quality in use and product quality models. It presents 10 guidelines for writing maintainable code from SIG. It also discusses tools for static code analysis (e.g. SonarQube) and software composition analysis (e.g. WhiteSource Bolt) to help ensure code quality. The presentation aims to help developers choose the right tools to analyze their code and dependencies.
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.
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?
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
