UQASAR: Universal Quality Assurance & Control Services for Internet Applications with Volatile Requirements and Contexts
UQASAR implements semantics in the field of Quality Assurance, whereas the techniques applied have to be light-weight or the performance of the platform can be seriously affected. This is specially critical in a big data context where the different monitoring services will be continuously gathering data from a mutating environment composed by personal IDEs of developers, designer tools, source code repositories, etc. In this field, there are several issues that can be taken into consideration for future work programmes:
- Complex semantics in real time big data environments with acceptable time responses.
- Identification of good/bad software engineering patterns out of the monitoring of the development environments.
These patterns could be obtained not only by the metrics gathered directly from repositories and tools but also from the categorisation of the coders’ and testers’ personal styles. This is of special interest in highly social development/testing contexts.
Up to now UQASAR has generated 2 main outcomes:
- An early prototype to demonstrate the validity of the concept, which is basically the monitoring of development contexts to provide the end user with evidences of the good or bad track of a development project or product. Currently the prototype allows the user to create quality models with quality goals, indicators and metrics; to set up quality assurance projects based on the previous models and gather data from two selected tools (JIRA and SONARQube). The Full Prototype, that will be ready by the end of February 2015, will propose changes to the Quality Objectives, Indicators and Metrics based on previous experience, will allow to establish negotiation processes to define the values of quality (e.g. thresholds of metrics).
- A methodology that indicates end-users how to identify the adequate collection of quality goals, indicatos and metrics depending on the type of process followed (agile, traditional) or type of product to be developed. UQASAR is looking for potential alfa-users of the platform once it’s launched on February/March 2015.
The aim of UQASAR is to become a service on the cloud, though there are some restrictions at this moment, such as the dependency to specific life cycle tools, thought the platform is open enough to incorporate new tools as the UQASAR community grows. Basic service can be offered at a very low price and charge for added value services such as smart reporting or statistical analysis. The setup of a SaaS orientation requires the creation a fully dedicated startup, which is one of the most promising options handled in our Exploitation Plan. Main barriers are the non-existence of a community figure for the setup of the company, as well as the initial personnel costs required for exploitation.
Cross collaboration has started with RISCOSS project. Several conversations have been maintained with different members of the consortium in order to define common needs. JIRA and SONARQube Wrappers developed within UQASAR are of interest for RISCOSS. For UQASAR the risk management strategy identified in RISCOSS is also of big interest to be integrated in the monitoring of management stage, which is part of our Monitoring Services.