Objective:
The applicant has identified the available resources of the MCP and of its interconnect in the intended final configuration, has allocated the resources of the MCP to the software applications hosted on the MCP and has verified that the demands for the resources of the MCP and of the interconnect do not
exceed the available resources when all the hosted software is executing on the target processor.
RU4 focuses on the handling of shared resources and tackles the question verifying that the usage always remains in the capacity offered by the platform. Thus, this objective does not require any embedded software development. As usual, the root is the objective and this results from a checking that the software demand on the resources never exceeds the capacities (W1). This checking is possible because on the one hand the software demand has been clearly identified and quantified (E2), and on the other hand the hardware resources with capacities have also been identified and quantified (E1). We chose not to refine (E2) because software analysis is a well known domain (with static analysis for instance). (E1), however, is quite new and needs precise low level knowledge on the multi-core internal components. Ideally, everything would be available in the processor documentation but as it is not the case, the applicant needs to perform additional activities to reverse engineer some information (W2).