SQuAT (Software Quality Assurance and Trustworthiness) Session

Schedule: Wednesday Nov 23, 01:00 - 04:00pm.
Room: room 2.
Session Chair: tbc
Description: SQuAT is an initiative that was launched by OW2 in 2010 with the aim to improve the quality of code by generalizing quality tests on OW2 technologies and setting up a quality label. The session will introduce several projects which are bringing methodology and tools to achieve this objective, and present the status and milestones of the initiative.
 

Program

1. Helping development teams to manage FOSS during the whole development process.


Schedule: 01:00 - 01:30
Room:
Speaker: Frederic Munoz,Antelink
Abstract: Today, most software development teams use free and open source software (FOSS) components, because it increases the speed and the quality of the development. Many open source components are the de facto standard of their category. However, FOSS has licensing restrictions, and corporate organizations usually maintain a list of allowed and forbidden licenses. But how do you enforce this policy? How can you make sure that ALL files in your source repository, either belong to you, or fit your licensing policy?
A first, preventive approach is to train and increase the awareness of the development team to these licensing issues. Depending on the size of the team, it may be costly but necessary.
However, this does not ensure that a single individual will not add a forbidden icon or library, and jeopardize the legal status of the whole release — or the company, since software is becoming more and more a critical asset. Another approach is to verify what is included in the source repository, and check whether it belongs to the open-source world.
This can be done on-the-fly, whenever a new file is added into the source repository. It can also be part of the release process, as a verification step before publishing the release. In both cases, there are some tools to automate the detection process.
This talk explores the various options regarding FOSS detection, how this process can be integrated in the "software factory", and how the results can be displayed in a usable and efficient way.

2. The Introduction of Management of Trustworthiness Software Resource

Schedule: 01:30 - 02:00
Room:
Speaker: Junfeng ZHAO, Pekin University
Abstract: To manage trustworthiness software resource is important for trust software development. We will introduce a method to evaluate the trustworthiness of software resource, such as Java API and Web service. Then, we will give an instance that has been realized in the software resource library, named as TSR (Trustie Software Resource Repository). TSR can be used as a component managing tool which provides mechanism to describe, collect, evaluate, classify and manage software resources’ trustworthiness, to support trust software development. The TSR has been published on OW2 on July, 2010. 

3. FOSSOLOGY

Schedule: 02:00 - 02:30
Room:
Speaker: Bruno Cornec, HP and Alexandre Lefebvre, FT & OW2 CTO.
Abstract: 

4. Developing community management metrics and tools for OW2

Schedule: 02:30 - 03:00
Room:
Speaker: Minghui Zhou, Pekin University
Abstract: Processes that limit the size or potential of our community limit our products. Conversely, making it easier for people to cooperate, collaborate, experiment and play enhances the community's capacity.
We set out to improve contributor's productivity and product quality, and to improve the general understanding of issue-tracking practices. We develop community management metrics to measure contributors, projects, and their interaction, such as technical climate, project relative sociality,and their influences for newcomers. We introduce a visualization tool to reverse-engineer and improve issue-tracking practices. Using GNOME project data we demonstrate how our tool can be used to discover the evolution of issue tracking practices.

5. SONAR (tbc)
6. Qualipso (tbc)
Tags:
Created by Catherine Nuel on 2011/10/28 18:20
Conference Sponsors
Powered by XWiki Hosted by Xsalto Free PageRank Checker Creative Commons 2.0 license Legal Notice