Presentation in English about U-QASAR and how it connects with the current problems found by the growing number of SQA SaaS tools found in the enterprise market.
2. U-QASAR in brief
U-QASAR. This project has received funding from the European Union’s
Seventh Framework Programme for research, technological development
and demonstration under grant agreement no. 318082.
8 organizations from Finland, Norway, Germany, Luxembourg and Spain:
Experts in SW Quality, Ontology modeling and implementation, SW
Engineering methods, SW Measurement and Commercialization
3. U-QASAR in brief
OBJECTIVE: Create a solution to provide project managers, software
engineers, testers and other actors with an objective measurement of
quality for:
Software Development processes
Software Products
24. The U-QASAR concept
Solution is paradigm agnostic, for any SW dev model
Two elements in U-QASAR
● A methodology
○ the main innovation of the project
○ how to measure SW quality
● A platform
○ with semantic capabilities
○ measuring the SW quality (processes and products)
SECTION C
25. How does it work?
Starting point: a Quality Model is needed
● It can be based on existing standards or models
● It can be an organization’s self-made model
● It can deal with process, products, or both
● U-QASAR will provide templates
U-QASAR Methodology can be
used to define
- QOs, QIs and Metrics
SECTION C
26. How does it work?
Next step: entering the QM in the U-QASAR Platform and
create QA Projects
Link Quality Metrics to existing connectors or wrappers (or Introduce
values manually)
Create Quality Objectives (QOs) or Select existing ones
Select or create Quality Indicators (QIs) by aggregating metrics
SECTION C
28. Key problems we’re trying to solve
SECTION D
KP.1: Segmentation
SQA tools need to address different
stakeholders and their perspectives in
decision making; they need to provide
different levels of granularity to
different groups of stakeholders so
they can be on the same page
KP.2: Integration
Lots of different tools used in SQA that
are not integrated in a shared view;
need for automatic real-time
monitoring
KP.3: Data Accessibility
No method to make the
heterogeneous SQA data
comprehensive and accessible
KP.4: Tool Usability
Using SQA tools is not a pleasant
experience; experience should be
consistent; etc.
29. Key solutions that might solve them
KS.1: Levelling
Quality model organizes the levels of
information according to the different
stakeholders’ needs.
KS.2: Open architecture
A pluggable monitoring architecture to
facilitate integration with external
sources
KS.3: Visualization
Comparative tools allows for simplified
views; simple visualization of the
relative importance of various metric
types
KS.4: Usability
Intuitive quality model editor; flat UI
design; intuitive Admin environment;
SECTION D
Editor's Notes
Ask people whether they consider any advantages on SaaS or Cloud over their own hosted solution. what will make them move to SaaS. Concerns