Is a summary of use cases of the features available ?
Architecture
B People
B Planet
B Prosperity
Difficulty
N/A
Priority
/
Récurrence
/
Tests
Are non-core functionalities identified and addressed in a step-down approach?
Precisions
The User Story / Use Case should be specified in relation to uses in order to avoid an excessive number of functionalities which would be superfluous in relation to the real needs of users. Proposing non-core functionalities will result in an unjustified environmental footprint, cost and lack of understanding of the service.
Additional elements
Rule for assessing the level of compliance of the criterion
0 / 0
Life cycle
Administration
13 other criteria related to the recommendation: Set up a methodology that promotes the consideration of Sustainable IT aspects
Life cycle
Is the envisioned functionality useful ?
Life cycle
Are the Sustainable IT aspects propagated and maintained across all stakeholders ?
Life cycle
Was a benchmark on the environmental criteria carried out for the choice of the infrastructure supplier ?
Life cycle
Does the design process / tools integrate the treatment of Sustainable IT requirements ?
Architecture
Does the sizing of infrastructure resources follow the life of the application ?
Architecture
Is the technical architecture permanently in line with the activity of the service ?
Architecture
Are de-provisioning operations expressed at design time ?
Architecture
Are all the technical equipment used by the service identified ?
Architecture
Are the characteristics available for each equipment (year of construction, environmental performance data...) ?
Life cycle
Is each function of the service understood in terms of its importance in the service ?
Life cycle
Do secondary functions also have a lower impact on the environmental footprint ?
Life cycle
Is each phase of the life cycle identified with specific actions ?
Life cycle
IsLCA data reused in the event of an adaptation of an existing service ?