Is the documentation of the functionality available to enable its reuse ?
What design information is being documented for reuse in other projects?
In an organisation, projects have many similarities, and the Sustainable IT aspects addressed in the projects are often of the same order. In order to capitalise on these elements and benefit from the efforts made, it is necessary to rely on a stable knowledge base. However, the maturity of an organisation from a Sustainable IT point of view is bound to progress, so the documented steps must also be able to follow these developments and actively participate in increasing this maturity.
Tecnical documentation contain sust. IT information
Operational issues related to the project
Rule for assessing the level of compliance of the criterion
Formalized = 100 ; Planned = 75 ; Identified = 50 ; Ignored = 0 / 100
16 other criteria related to the recommendation: Use the technical components that improve the sustainable IT aspects, security and performance
Is the web server used asynchronous and multi-threaded ?
Has the dependency tree of the integrated components been evaluated ?
Can dependencies be reduced by using an alternative component ?
Is the user informed of a processing in progress in the background ?
Has the integration of asynchronous processing been evaluated ?
Are unused resources freed up as quickly as possible ?
Is a VM necessary as opposed to a container solution ?
Does service availability require redundancy ?
Do interactions between components benefit from caching mechanisms ?
Are the browser caches not being blocked by the framework or technology used ?
Is there a lighter framework / library that meets the functional need ?
Is an Open Source solution available for the functional need ?
Are the versions of the components used tracked and deployed ?
Is the security implemented justified with regard to the operations carried out ?
Is the level of logs adapted to the environment ?
Are temporary files included in the "logrotate" ?