Changes for document Software Quality Assurance and Trustworthiness

From version 3.1

edited by Alexandre Lefebvre
on 2010/10/11 12:12

To version 4.1

edited by Alexandre Lefebvre
on 2010/10/11 12:15

Change comment: There is no comment for this version

Content changes
•methods,Methods, processes and tools provided by Trustie OW2 will become a user of the Trustie processes to enhance the quality of our software. This requires the help from Trustie, to discover, understand implement and use the Trustie methodologies and tools. •tools,•Code checking tools, which include Sonar (integrated in NovaForge): we will also be looking at tools and methods delivered by the Qualipso • IP verification tools to be used (use1.1 IP of these tools by OW2 has been already agreed by tools providers)the code • - FOSSology (license analysis)IP verification tools to be used (use of these tools by OW2 has been already agreed by tools providers) include: • - Antelink (source code IP)- FOSSology (license analysis) • We will require mature projects to publish the reports, and leave the final user the final decision (OW2 is not a certification office). Such tools will be added to the technology infrastructure and integrated with NovaForge.- Antelink (source code IP) • WH: code quality is essential. The way OW2 should support high quality of the code should be based on open source, based on a community contributions, in orderWe will require mature projects to aggregate world-wide intelligence. Thispublish the reports, and leave the final user the final decision (OW2 is not a philosophical approach.certification office). Such tools will be added to the technology infrastructure and integrated with NovaForge. • The OW2 Forge is important to support getting high quality software. In a wiki, anybody can contribute his/her idea to build a higher quality document. Similarly, we need a similar platform to support good quality code. We need to provide an approach where contributors can improve the quality. This is a trust platform idea. • Anybody can create a project, share a component. To obtain the evidence, Trustie wants to play this rule to gather the evidence for ranking of code components. OW2 should get this technology for code ranking, based on evidence, relying on an open platform. • CT: SQuaT has been informally discussed with projects. We want the go ahead from the board to launch this major quality effort. • JPL: before we JPL would like to get some feedback from the project. Action items: • SQuaT to be introduced at the next TC, and the feedback to be reported to the next board meeting. • Identify possible CSTC tools to use • Identify usage of Trustie tool for quality ranking

Content changes

•methods,*Methods, processes and tools provided by Trustie* OW2 will become a user of the Trustie processes to enhance the quality of our software. This requires the help from Trustie, to discover, understand implement and use the Trustie methodologies and tools.

•tools*,•Code checking tools*, which include Sonar (integrated in NovaForge): we will also be looking at tools and methods delivered by the Qualipso

• IP verification tools to be used (use1.1 IP of these tools by OW2 has been already agreed by tools providers)the code

• - FOSSology (license analysis)IP verification tools to be used (use of these tools by OW2 has been already agreed by tools providers) include:

• - Antelink (source code IP)- FOSSology (license analysis)

• We will require mature projects to publish the reports, and leave the final user the final decision (OW2 is not a certification office). Such tools will be added to the technology infrastructure and integrated with NovaForge.- Antelink (source code IP)

• WH: code quality is essential. The way OW2 should support high quality of the code should be based on open source, based on a community contributions, in orderWe will require mature projects to aggregate world-wide intelligence. Thispublish the reports, and leave the final user the final decision (OW2 is not a philosophical approach.certification office). Such tools will be added to the technology infrastructure and integrated with NovaForge.

• The OW2 Forge is important to support getting high quality software. In a wiki, anybody can contribute his/her idea to build a higher quality document. Similarly, we need a similar platform to support good quality code. We need to provide an approach where contributors can improve the quality. This is a trust platform idea.

• Anybody can create a project, share a component. To obtain the evidence, Trustie wants to play this rule to gather the evidence for ranking of code components. OW2 should get this technology for code ranking, based on evidence, relying on an open platform.

• CT: SQuaT has been informally discussed with projects. We want the go ahead from the board to launch this major quality effort.

• JPL: before we JPL would like to get some feedback from the project. Action items:

• SQuaT to be introduced at the next TC, and the feedback to be reported to the next board meeting.

• Identify possible CSTC tools to use • Identify usage of Trustie tool for quality ranking

Useful Links

Newsletter Subscription

OW2 Newsletters Archive

Top Downloads

For the past seven days
SpagoBI
Bonita
XWiki
JOnAS
ASM
EasyBeans
eXo Platform
JOTM
JavaService
Orchestra

Join OW2

Join industry leaders, academics and individuals and help shape the future of middleware

Changes for document Software Quality Assurance and Trustworthiness

Useful Links

Top Downloads

Join OW2

Project News

Community Events