Skip to content
FR EN

Handbook of Sustainable Design of Digital Services

MENU
← go back
Backend    ODD#12     ODD#13    

Are code quality metrics being tracked ?

Recommendation 

Quality

B People

C Planet

A Prosperity

Difficulty

***

Priority

High

Récurrence

Periodic

Tests

Are the faults traced and reviewed with their impact on Sustainable IT?

Precisions

The quality of the software produced has a direct impact on the Sustainable IT aspects. Defects lead to multiple deliveries of successive new versions, anomalies lead to the production of errors, and to functionalities that consume more resources, sometimes without achieving any result, so that in the end resources were used to no avail.

Use Case

Continous integration

Additional elements

Operational issues related to the project

Posts

Rule for assessing the level of compliance of the criterion

Formalized = 100 ; Planned = 75 ; Identified = 50 ; Ignored = 0 / 100

Life cycle

Déploiement

9 other criteria related to the recommendation: Use development principles that reduce impacts

Recommendation

Flux

Are user notifications necessary ?

Advice

IU

Is SSO implemented when possible ?

Advice

Life cycle

What would be my dev reflex, to take into account the life cycle ?

Advice

Life cycle

Does each stakeholder have the latitude to make decisions that may influence the environmental footprint ?

Recommendation

Quality

Is code analysis used in the continuous integration process ?

Advice

Quality

Are functionality test reports available and tracked ?

Advice

Life cycle

Have the tools for monitoring Sustainable IT performance been identified and made available to developers ?

Advice

Life cycle

Has an analysis of the application's consumption profile been performed ?

Advice

Life cycle

Does each version deployed follow the same process for qualifying for Sustainable IT performance ?