Introduction to the evaluation of libre software projects

8/3/2019 Introduction to the evaluation of libre software projects

1/19

Evaluation of Libre Software Projects

Master on Libre Software (URJC)http://master.libresoft.es

Daniel Izquierdo-Cortazar

[email protected]/LibreSoft, Universidad Rey Juan Carlos

November 2011

Daniel Izquierdo-Cortazar Evaluation of Libre Software Projects
http://master.libresoft.es/http://master.libresoft.es/http://find/http://goback/


2/19

c2011 Daniel Izquierdo Cortazar.Some rights reserved.

This document is distributed under theCreative Commons Attribution-ShareAlike 3.0 licence,

available inhttp://creativecommons.org/licenses/by-sa/3.0The original version of this document is available at

http://master.libresoft.es

http://creativecommons.org/licenses/by-sa/3.0http://master.libresoft.es/http://master.libresoft.es/http://creativecommons.org/licenses/by-sa/3.0http://goforward/http://find/http://goback/


3/19

Introduction to Evaluation of

FLOSS Projects

http://goforward/http://find/http://goback/


4/19

Why is this important?

The evaluation of projects is a critical task for IT managers

The costs of selecting the wrong technology could be laterunapproachable



5/19

General questions made

Which software fits best my current requirements?

Requirements such as:Functional requirements: looking for specific functionalityTechnical requirements: looking for specific technologies



6/19

More requirements

Safety, security, reliability, robustness, testability

adaptability, complexity, maintainability, portability



7/19

Even more

Reusability, installability, efficiency,

correctness, modularity



8/19

And FLOSS projects?

Is the license included above?

Social networks: territoriality, hubs of people (or knowledge)Others...


S


9/19

Selecting proprietary systems

Some limitations due to depend on proprietary software:

Cost: generally higherClosed source code: some requirements could not been

measured: e.g. quality of the softwareThere is not influence in the roadmap at allFormatsOthers


S l i FLOSS


10/19

Selecting FLOSS systems

Some limitations when selecting FLOSS projects:

Limitless optionsIn some cases there is not professional support (as requested

by companies)Longevity (although this is also a problem in proprietarysoftware)Stability: following a release often, release early may be seenas a weak point by companies


Th


11/19

Thus...

If you need a specific technology then it is clear the option

However it is not clear if there are some potential productsthat fit your requirements

How to select them?



12/19

Initial Assessment


FLOSS A t


13/19

FLOSS Assessments

Light-weight: OpenBRR or QSoS

Heavy-weight: QualOSSThose will be studied in following lessons


FLOSS Ass ss ts


14/19

FLOSS Assessments

However, what type of data do they retrieve?

Programming languageQuality of the source code

General architectureLicenseSpecific functionalitySupport


How to proceed?


15/19

How to proceed?

Following specific methodologies that facilitate this process

(e.g.: Goal-Question-Metric).Following specific quality models (that define methodologies)



16/19

Exercises


Exercise


17/19

Exercise

Goal: We have to install 5,000 FLOSS e-mail clients in acompany. Specific development and translations will be neededin any case. We will re-sell the product and provide support.

Specific mission: Select five requirements that you think are

important when selecting this e-mail client.

Other considerations: This should be made based on yourcurrent and personal experience.

Methodology: Create an initial methodology to be followed for

other people.


Exercise


18/19

Exercise

Improve the previous exercise with a GQM approach


Exercise


19/19

Exercise

Improve the previous exercise adding info from the ISO 9126

that could be useful


Date post:	06-Apr-2018
Category:	Documents
Upload:	dicortazar
View:	218 times
Download:	0 times

Introduction to the evaluation of libre software projects

Documents