Skip to content
FR EN

Handbook of Sustainable Design of Digital Services

MENU
← go back
Frontend    ODD#12     ODD#13    

Are the functionalities related to regulated data processing (health, personal, banking) validated in terms of interoperability ?

Advice 

Technology

B People

C Planet

B Prosperity

Difficulty

N/A

Priority

/

Récurrence

/

Tests

Is each functionality linked to regulated data (health, banking) identified?

Precisions

The regulatory framework for certain categories of data is very strict, respect for this data to protect users is an important criterion. It is essential that in the development process no breach is possible and that all interoperability with the standard mechanisms of these areas be validated.

Additional elements

Rule for assessing the level of compliance of the criterion

0 / 0

Life cycle

Utilisation

11 other criteria related to the recommendation: Use environments and tools that limit impacts

Recommendation Essential

API

Are the functionalities covered by local actions (client side) privileged rather than API exchanges ?

Recommendation

Flux

Do you use caching mechanisms to limit exchanges ?

Recommendation

API

Is the data fed back by the APIs really only the data that the application needs when it is requested ?

Advice

API

Is an openSource alternative available for APIs ?

Recommendation

Technology

Do the libraries used allow you to take only the components that are actually useful ?

Recommendation

Technology

Are unused dependencies identified and removed ?

Recommendation

Technology

Couldn't the expected functionality be implemented with the native capabilities of the browser ?

Advice

Technology

Is an openSource alternative available ?

Recommendation

Technology

Are all the technical equipment used by the service identified ?

Advice

Technology

For each equipment, are the characteristics available ?

Advice

networks

Are the latest technical advances used when they really help reduce impact ?