Recommendation : 5. Implement and develop functionalities to limit impacts
Don't the functionalities of the service go beyond user needs ?
development standards
A People
A Planet
A Prosperity
Difficulty
*
Priority
High
Récurrence
OnUpdate
Tests
Is each feature removed if it is not related to a defined use?
Precisions
The number of features available in a digital service directly impact the consumption of resources and the environmental footprint. By creating functions of little use, they are sources of creation of totally unnecessary environmental debt. The features also increase the volume of the service, which introduces additional loading times and storage space.
Use Case
Data are collected (analytics, probes, ...) to ensure real usefulness of features
Additional elements
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Number of features really used / Number of features
Life cycle
Conception
5 other criteria related to the recommendation: Implement and develop functionalities to limit impacts
development standards
Are the logs free of unprocessed errors ?
development standards
Are dead codes cleared ?
development standards
Is a compiled language used for performance and / or security aspects ?
user Experience
Are the reference elements known, kept up to date, and made available to the entire project team ?
user Experience
Is the inventory of the input data made available for reuse in other projects ?