Clear requirements (both functional and non-functional requirements), applicable principles, and standards are important in order to achieve consistency or shared services / resources across federated platforms.
The documents are currently limited in their definition of the non-functional requirements applicable to the EO exploitation platform. It would be very useful to have the (minimum) non-functional requirements applicable to each of the domain areas. These would include system / services availability (including capability to cope with failures), system performance (including SLAs, capability to cope with variable / increasing demand / workload), security (including data security), Recovery Time Objective (RTO), Recovery Point Objective (RPO), etc.
The definition of clear non-functional requirements would help achieving the level of consistency among various EO platforms.
What would happen if federated platforms implement different levels of non-functional requirements, e.g. a resource / service from a federated node might not be available due to the system not being able to scale up & cope with current workload, different service availability, RPO & RTO, etc?
Clear requirements (both functional and non-functional requirements), applicable principles, and standards are important in order to achieve consistency or shared services / resources across federated platforms. The documents are currently limited in their definition of the non-functional requirements applicable to the EO exploitation platform. It would be very useful to have the (minimum) non-functional requirements applicable to each of the domain areas. These would include system / services availability (including capability to cope with failures), system performance (including SLAs, capability to cope with variable / increasing demand / workload), security (including data security), Recovery Time Objective (RTO), Recovery Point Objective (RPO), etc. The definition of clear non-functional requirements would help achieving the level of consistency among various EO platforms. What would happen if federated platforms implement different levels of non-functional requirements, e.g. a resource / service from a federated node might not be available due to the system not being able to scale up & cope with current workload, different service availability, RPO & RTO, etc?