T76 4115 Iteration Demo Team License Checker Group

T-76. 4115 Iteration Demo Team License. Checker – Group 8 I 1 Iteration 11. 12. 2008

T-76. 4115 Iteration demo Agenda Project status (10 min) Work results (10 min) achieving the goals of the iteration project metrics presenting the iteration’s results demo Used work practices (5 min) 2

T-76. 4115 Iteration demo Introduction to project Open Source License Chekcer v 3. 0 Based on Open Source License Chekcer v 2. 0 Tool that is easy to use and is accurate Introducing more licenses Better GUI From project to community 3

T-76. 4115 Iteration demo Status of the iteration’s goals Getting the team functioning properly Following and refining the defined practices Done Delivering a working system that has the defined new functionality and features 5/7 achieved their planned hours Implementing all tasks assigned Work was divided fairly equally Achieving, or if necessary slightly exceeding the budgeted hours Done although QA started a bit late Dividing the workload more equally No conflicts, no bad spirit Demo Opening connections to the Open Source Community Presentation of OSLC @ Paris Invitation to present OSLC to whole OW 2 community New contributor 4

T-76. 4115 Iteration demo OSLC @ Paris Strong interest expressed about OSLC Université Josep Fourier (Didier Donsez) Mandriva (Arnaud Leprevote) Siemens (Oliver Fendt) OW 2 CNRS (Plume Project) Thales Additional feature request Maven plug-in for automated testing 5

T-76. 4115 Iteration demo New contributor Didier Donsez professor in Computer Sciences at Université Grenoble 1 (France)

Status of the iteration’s deliverables - documentation T-76. 4115 Iteration demo Project plan Added new processes Iteration plan and QA Plan as separate documents Requirements document Added new features QA plan and report Separate documents Technical specification Based on the previous technical specification but with new features Use cases Implemented and approved for all functional requirements Test cases Implemented and tested F 1, F 2, F 3, F 6, N 1, N 2 and N 3 Test log and results As separate document Progress report Done 7

Status of the iteration’s deliverables - software T-76. 4115 Iteration demo SVN/CVS support Works on CLI and GUI Copyright check Works on CLI and GUI, WIP GUI to add new licenses Works, but problems with GUI layout and a new model of meta-data usage is needed List compatible licenses Works, WIP Reports as RTF and PDF Works on CLI not GUI yet Localization Works, problems with Scandinavian characters Support for Javascript Works Installer Works Standardized license notation Moved to next iteration 8

T-76. 4115 Iteration demo Realization of the tasks 9

T-76. 4115 Iteration demo Realization of the features 10

T-76. 4115 Iteration demo Resource usage Original plan (in the beginning of the iteration) Realization and updated plan 11

T-76. 4115 Iteration demo Time Tracking This iteration Previous iteration 12

T-76. 4115 Iteration demo Time Tracking This iteration Previous iteration 13

T-76. 4115 Iteration demo Quickly: Quality Assurance in OSLC 3 Developers QA Team Design and run tests of the programs features Help to insure that relevant QA practices are used by the whole team QA Manager Unit tests and integration testing for their own code Help the QA Team to test the features they have implemented Tries to manage the whole thing Assigns tasks and makes sure everything (at least almost everything) gets done to an acceptable degree of correctness Following the lessons learned in iteration I a few changes will be made… Test cases and testing will be given more weight in I 2 Acceptance testing given the highest priority Unit tests monitored more closely during every build A more extensive code review planned for I 2, as there was no time for it in I 1

T-76. 4115 Iteration demo Defects and other quality metrics No critical defects Current major problems related to Identifying all the relevant files to search license information in Loading large archive files Identifying the copyright holders correctly Smaller problems related to character set usage 15

T-76. 4115 Iteration demo Quality dashboard All implemented features work, though some need more functionality and/or a better GUI “Adding new licenses” –feature needs changes to be made to the OSLC 2 basis The meta-data handling has to be re-done, the current system relatively ad-hoc QA procedures (especially testing) will be emphasized more in the last iteration Scheduling problems No wide scale regression tests were done in I 1 The implemented features rely on OSLC 2’s features and no major changes to the original architecture were not made -> That we’ll be done in I 2 No code reviews either in I 1 Simply ran out of time 16

T-76. 4115 Iteration demo Quality goals Functionality The program has more functionality than the previous version and that functionality is easier and more efficient to use Correctness The program works as documented and has no fatal errors Maintainability The program maintains coding and documenting standards for easier expansion and maintenance operations in the future Usability The new GUI is provides usage of all the new features, is more logical and easier to use then the previous versions and has a more polished/release ready look to it 17

T-76. 4115 Iteration demo Changes to the project Team size shrunk from 8 to 7 Defined two new practices License control for external packages Progress of features Decided to emphasize QA more on last iteration Found a critical defect from previous groups work 18

T-76. 4115 Iteration demo Risks 19

T-76. 4115 Iteration demo Results of the iteration System architecture Mainly based on previous groups work QA plan Processes defined, now needs to be put on use Implemented use cases For all functional requirements Was done at early stages of the iteration Approved by the customer Demonstration 20

T-76. 4115 Iteration demo Demo script 1. 2. 3. 4. 5. 6. Installing the software Changing the language Using the SVN Checking the copyrights Adding new license Viewing compatible licenses 21

T-76. 4115 Iteration demo Changing the language The class provides strings which as stored as a key value pairs. Instead using arbitrary keys, the GUI uses english version of the strings as keys. Always some text for GUI -> less exceptions.

T-76. 4115 Iteration demo Using the SVN Uses open source SVNKit library. SSH connections use Trilead library (trilead. jar). Following connection methods to access the repository are supported: http, https, svn+ssh

T-76. 4115 Iteration demo Checking the copyrights Uses copyright identifiers to find copyright text i. e. (c) Then: Discard the lines that contain some of the words that are typicalliy used in copyright templates (COPYRIGHT_EXCLUDERS) Remove the words that are not likely included in the name of the copyright holder (JUNK_WORDS) Remove the COPYRIGHT_IDENTIFIERS from the line Create Copyright. Holder objects from a comment line that contains the names of the copyright holders, the names are separated by NAME_SEPARATORS Separate email and web site addresses from the names (identified by AT_MARK and WWW) Remove all special characters from the names

T-76. 4115 Iteration demo Adding new license Wizard alike tool for adding new licenses. Asks user about license name and license text, then opens up selection box from where the user can select compatible licenses. License. Writer writes licensename. txt and licensename. meta files. Naming of files and tagging the license text at user responsibility, licenses with wrong name declined by the parser. Easy to use feature was difficult to make because database is designed so that only developers add new licenses. -> Database and parsing refactoring in I 2 -> easier interface for adding new licenses.

T-76. 4115 Iteration demo Viewing compatible licenses Tool to view compatible licenses of the selected license. Opens up list of all licenses from which user can select compatible licenses. When database is refactored will be changed to View/edit licenses. Another tool will be added which will show compatible licenses from the opened package.

T-76. 4115 Iteration demo Used work practices Preferred work practices IRC, Wiki, weekly meetings – Communication and transparency Development sessions – Problem solving Meeting minutes – Chance to recall what was agreed There was some problem with Time reporting Getting documentation started Were are going to Continue with defined practices Be open to new practices 27

T-76. 4115 Iteration demo Feedback about the reflection workshop “We also learned a few valuable lessons in how to do, and not to do certain things in the future, mainly related to resource deployment and communication between the developers and the management team while a feature is still in development” “On the negative side, it seemed that we made a little too optimistic effort estimates, which should be addressed by adding some extra buffer time when planning tasks for I 2”

T-76. 4115 Iteration demo Next Implement rest of the features Add our own features Extensive testing and quality assurance Starts already in the beginning of the iteration Reviews TDD Continue building the community Setting up OW 2, wiki, etc. 29