Your SlideShare is downloading. ×
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
A GQM plan for the evaluation of the trustworthiness of open-source software
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

A GQM plan for the evaluation of the trustworthiness of open-source software

1,146

Published on

Published in: Economy & Finance, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,146
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
41
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • 1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007
  • Transcript

    • 1. A GQM plan for the evaluation of the trustworthiness of open-source software Michele Chinosi, Vieri Del Bianco, Luigi Lavazza, and Davide Taibi Università degli Studi dell’Insubria Dipartimento di Informatica e Comunicazione
    • 2. Qualipso objectives
      • Software adoption/rejection depends on trustworthiness
        • Trustworthiness of OSS products
          • regarded by some as not as guaranteed
          • viewed as more difficult to assess
      • industrial organizations interested to assess the trustworthiness
      • To help foster the adoption, use, and production of OSS products, it is therefore important that the real goals and needs of software organizations be given top priority when investigating assessment methods, techniques, and indicators for OSS products.
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 3. Qualipso approach
      • QualiPSo project trustworthiness
        • three-step approach:
          • Information about the corporate goals of the European software industry with respect to open source trustworthiness was acquired via several interviews.
            • The variety of goals and needs of different organizations emerged.
          • The factors and measures for trustworthiness that are relevant in the context of those needs and goals are defined
            • the Goal/Question/Metric paradigm is used.
          • The metrics defined will be validated by means of measures on the field and by carrying out studies on several real-life projects.
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 4. The G/Q/M 1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - - Goal(object, purpose, quality, viewpoint, environment) definition Q1 Q2 Q3 Q4 Implicit model M1 M2 M3 ... interpretation
    • 5. The role of OSS in SW organizations
      • An organization perceives the trustworthiness of the OSS on the basis of the role that the OSS plays with respect to the organization itself.
        • OSS producer of OSS
        • User
        • Customizer or value adder
        • etc.
      • Since the role of OSS is fundamental to determine the trustworthiness criteria, we define a GQM plan for each relevant case of OSS role.
      • The identification of the different types of usage of OSS in software organizations is still ongoing
        • Since the analysis of the information collected buy means of questionnaires is not yet completed
      • The GQM goals presented here must be regarded as a preliminary hypothesis of work.
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 6. The GQM goals
      • Goal 1: Analyse OSS for the purpose of evaluating the trustworthiness from the point of view of users (people who use the SW as is).
      • Goal 2. Analyse OSS for the purpose of evaluating the trustworthiness from the point of view of developers (e.g., organizations involved in development, organizations whose business involves OSS development)
      • Goal 3. Analyse OSS for the purpose of evaluating the trustworthiness from the point of view of integrators (e.g., organizations that integrate SW into their products, especially if modifications are required).
      • Goal 4. Analyse the OSS development process for the purpose of evaluating the relation between the trustworthiness of OSS and the characteristics of the process.
      • Goal 5. Analyse the OSS usage process for the purpose of evaluating the relation between the (perception of) trustworthiness of OSS and the characteristics of the process.
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 7. Goal 1
      • Analyse OSS for the purpose of evaluating the trustworthiness from the point of view of users (people who use the SW as is).
        • Quality foci:
          • Software quality
            • direct evaluation of functional and non-functional aspects
            • direct or indirect evaluation of internal qualities, e.g., code qualities
            • functional and non functional qualities evaluated indirectly, e.g., considering the reputation of developers, the opinions of the users community, etc.
            • indirect evaluation, through evaluations, certifications and assessments made by an external organization
          • Economic factors
          • Availability and quality of support, guidance, documentation, etc.
          • Availability and quality of SW maintenance in the short term
          • Perspective of support in the future
          • Perspective of SW maintenance in the future
          • Perspective of SW evolution in the future
        • Variation factors:
          • Problem domain
          • Software criticality
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 8. Goal 2.
      • Analyse OSS for the purpose of evaluating the trustworthiness from the Point of view of developers
      • Trustworthiness is perceived as the quality that the organization wants to build in the OSS to be released.
        • If development is carried out cooperatively
          •  Trustworthiness affected by external factors
      • Quality foci :
        • Software quality
          • direct evaluation of functional aspects
          • direct evaluation of non-functional aspects
          • direct evaluation of internal qualities
        • Perspective of support in the future
        • Customer related issues
      • Variation factors:
        • Economic factors
        • Business model
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 9. Goal 3.
      • Analyse OSS for the purpose of evaluating the trustworthiness from the point of view of integrators
      • Combine the points of view of the first two goals.
      • Quality foci :
        • How the internal code quality affects the trustworthiness of the final product.
        • Economic factors
        • Legal (mainly license-related) issues.
        • Availability of support, guidance, documentation...
        • Availability of technical support, guidance, documentation...
        • Availability of SW maintenance in the short term
        • Perspective of support in the future by other organizations involved in the development
        • Perspective of SW maintenance in the future
        • Issues related to customers
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 10. Goal 4 .
      • Analyse the OSS development process for the purpose of evaluating the relation between the trustworthiness of OSS and the characteristics of the process.
      • Quality foci:
        • Trustworthiness of products (as defined in previous goals)
        • Maturity of the software development process, including
          • development release planning
          • creation and maintenance of product documentation
          • process modelling
          • Etc...
        • Qualification and experience of developers
        • Quality assurance practices used in the development process
        • Development process retrospectives
      • Variation factors:
        • Business model of development
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 11. Goal 5 .
      • Analyse the OSS usage process for the purpose of evaluating the relation between the perception of trustworthiness of OSS and the characteristics of the process.
      • Quality foci:
        • Trustworthiness of products
        • Adaptations
        • Extensions
        • Functionality used
        • User interfaces used
      • Variation factors:
        • Type and experience of the user
        • Type of usage
        • Effort and duration
        • Methodology and tools employed
        • Status of the OSS project
        • Platform and language
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 12. Future work
      • Refine the definition of goals according to classes of use.
        • Each class should be characterized by a unique combination of values of the following attributes:
          • OSS is used only within the organization [yes|no (it is released outdside)]
          • OSS is modified [yes|no (it is used ‘as is’)]
          • OSS is integrated with other SW [yes|no]
      • Additionally, evaluation criteria should be taken into consideration:
        • E.g., ethical vs. commercial
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -
    • 13. Acknowledgments
      • The research presented was partially funded by the Qualipso IST project , sponsored by the EU in the 6th FP (IST-034763).
      • http://www.qualipso.eu
      1st International Workshop on Trust in Open Source Software - Limerick, Ireland, June 14, 2007 - -

    ×