In order to establish a quality model to Rescuer platform evaluation, by understanding of its strong relation with SoS, this proposal will be conduced in six main steps. Also, an example of a general quality model is illustrated on table below.
Step 1: Identification of related elements by using contexts, goals, projects, stakeholders, interests, and software artifacts by means of a tailoring process.
Step 2: Identification of quality characteristics using the ISO/IEC 9126 standard.
Step 3: Identification of systems of systems elements that could be contained in Step 1.
Step 4: Identification of a set of questions related to each objective, goal and metric to evaluation contained in using context.
Step 5: Building of a dynamic model to evaluation by: using contexts, goals, projects, stakeholders, interests, etc... By select these criteria on an assessment interface.
Step 6: Perform the evaluation using the artifacts and the generated quality model.
The quality model presented on table above have illustrated a relation between the system elements and each task of package 5. It have assumed that each task has an ISO/IEC 9126 quality metric, thus, it should be related to an element of SoS's taxonomy. In this aspect, it is believed that the reference architecture's taxonomy for systems elements (Nakagawa et al, 2012) can be fit to SoS proposals, specially to the Rescuer platform. The evaluation model will: (i) ensure the quality of software artifacts, (ii) avoid pitfalls on software development process, and (iii) support the measuring of each development phase, before and after to apply the evaluation model. However, it still is need to investigate and building a SoS’s taxonomy using a Systematic Literature Review (Kitchenham, 2004) avoiding a wrong model that will not fulfill the Rescuer project objectives, beyond of following the six steps said above.