1. TeXlipse [I1] Iteration 1.12.2004
T Project Review
TeXlipse
[I1] Iteration

2. Agenda Introduction to the project Project status (10 min)
Status of the iteration's goals
Status of the iteration's deliverables
Realization of the tasks
Working hours per person
Risks
Work results (25 min)
Results of the iteration
Demo
Used work practices (5 min)
Chosen common work practices
SEPAs

3. Introduction to the project
The customer has a constant need for the creation of LaTeX documents.
The Eclipse IDE is free, powerful and gaining in popularity and it offers a rich environment for extension through a plugin architecture.
There are existing free plugins for this, e.g. the ecleTeX -project, but they are lacking in features.
The general purpose of this project is to create a LaTeX plugin for Eclipse IDE.
The developed plugin, TeXlipse, is to provide a efficient developing environment for creating LaTeX-documents.
Some of the key features to achieve this include:
Syntax highlighting
Folding
Templates
Build support
Keyboard shortcuts
Support for several platforms
One of the most important goals of this project is to provide a solid architectural platform that supports future development of the plugin.

4. Status of the iteration’s goals
Goal 1: Plan a solid architecture for the plugin. OK
Goal 2: The customer’s top 5 plugin features:
a) Support for a Latex project
b) View the outline
c) Displaying errors and linking them to source
d) File output (dvi, pdf, ps...)
e) Templates (itemize etc.), hotkeys for templates, placeholder for hotkey templates

5. Status of the iteration’s deliverables
All these documents have been delivered
Updated project plan
Updated requirements document
QA plan
Technical specification
Progress report
Updated SEPA diaries
These issues are also discussed in the documents in some extent
Test plan, test cases

6. Realization of the tasks
Task specific
General
The group uses a separate planning method for the task specific resource allocation.
It helps with assessing the total resource need.
The Trapoli time reporting system is used in parallel with this method.
Trapoli is still the main reporting tool for general tasks.

7. Working hours by person
Not enough time was spent during this iteration.
The remaining time will be shifted to the I2-iteration.
If necessary, some of this time will be further shifted to the F&D-iteration.

8. Quality metrics
No true quality metrics can be presented at the moment.

9. Quality assessment
Quality testing will be performed in four different levels:
unit testing continuously during the development
integration testing when integrating an implemented feature
system testing in the end of each iteration, also at some state by thepeer group
acceptance testing before delivering the product
Execution of each test case will be recorded in a test log. Entry of the test log entry contains the following items:
date and time
tester
environment identifier
version/build numbers
test case identifiert of all executed test cases
test result (passed/failed)
bug ID (if failed)
other issues or comments

10. Quality assessment
All the defects found during testing or some other activity will be recorded in Bugzilla defect tracking system, unless the defect is fixed immediately.
The defects will be classified according to severity levels:
Blocker: Further development will be blocked until the defect is fixed.
Critical: The defect causes data loss or crashes the plugin or the Eclipse platform.
Major: Major defect in functionality.
Minor: Minor defect in functionality.
Trivial: Cosmetic defect with no effects on functionality.

11. Software size in Lines of Code (LOC)PP I1 I2 I3 DE
Total (NCLOC + COM)
1200
Comments (COM)
200
This was the first iteration when actual code was written.

12. Risks Current situation regarding the risks
No risks have materialized yet.
The risks are now discussed in more detail in a separate risk management –document.
Identifying the risks before they have a slightest possibility to materialize is a key success factor.
”Risk in itself is not bad; risk is essential to progress, and failure is often a key part of learning. But we must learn to balance the possible negative consequences of risk against the potential benefits of its associated opportunity.”
Van Scoy, Roger L., Software Development Risk: Opportunity, Not Problem.

13. Changes to the project No major changes were made to the project.
The importance of the core architecture was emphasized.

14. Results of the iteration
The most important substance of the major deliverables of the iteration:
project plan
Requirements document
system architecture (technical specifications)
QA approach
implemented use cases (I1-FD)
Demonstration of the developed software:
We will give a short demonstration of the plugin at the moment.
There is no need for a separate demo-script.

15. Used work practices Experiences of used practices Mandatory practices
Time reporting with Trapoli
A new dual-way was found with working with Trapoli.
The reporting has been done almost directly after each task.
Version control
The CVS version management tool has been a good help.
Risk management
Bugzilla has not been taken into use yet.
SEPAs
PM’s Diary (Jani)
Communication practices (Jani)
Static Methods (Esa, Oskar)
Pair Programming (Laura, Taavi)
Design Patterns (Antti, Kimmo)