The backend represents the computer translation of business processes, the technical means and data implemented for their use, as well as all the external interactions implemented for their realization.
× Filtered by: Methodology
Filtered by:
Is the number of requests kept to a minimum (no looping) ?
Is sensitive user data secure ?
Does the API provide limits, filters and the list of fields to return ?
Is the data collected really useful ?
Is sensitive data collected ?
Do implemented queries use joins rather than multiple queries ?
Is the documentation of the functionality available to enable its reuse ?
Are temporary files included in the "logrotate" ?
Are unused resources freed up as quickly as possible ?
Is the data exchanged compressed before transmission ?
Is pagination used on data exchanges ?
Is the number of requests between the client and the server kept to a minimum ?
Does the data exchanged match the immediate need only ?
Is code analysis used in the continuous integration process ?
Are code quality metrics being tracked ?
Is the overview of data handling processes (GDPR) available ?
Is the risk analysis (RGPD) carried out ?
Is the RGAA taken into account ?
Is regulated data (banking, health, etc.) secure ?
Is the envisioned functionality useful ?
Are de-provisioning operations expressed at design time ?
Are all the technical equipment used by the service identified ?
Are the characteristics available for each equipment (year of construction, environmental performance data...) ?
Is each phase of the life cycle identified with specific actions ?
IsLCA data reused in the event of an adaptation of an existing service ?
