T-76.115 Project Review

T-76.115 Project Review Rajoitteiset I1 Iteration3.12.2003

Project status (15 min) Achieving the goals of the iteration Status of the deliverables Resource usage Changes to the project Risk review Work practices (5 min) Completed work (15 min) Presenting the iteration’s results and deliverables more precisely Project plan Requirement specification Technical specification Test plan Plans for the next iteration (5 min) Agenda

Status of planned goals of the iteration • Goal 1: Designing client-server model • OK • Goal 2: Implementation of linearization • OK • Goal 3: Finalization of technical specification • OK, although finalization is a strong word • Goal 4: Translating model from language • OK • Goal 5: Designing linearisator and defining its interfaces • OK • Goal 6: Designing interface for the solver • OK, but interface has not been confirmed • Goal 7: Building the basis of the client • POSTPONED to I2 due to changes in resource availability

Status of planned deliverables of the iteration • Project plan • OK • Requirements document • OK • Technical specification • OK • Test plan • OK

Realization of the tasks • Time allocated for meetings was used for understanding the underlying mathematics • Client meetings were planned as part of meetings in general • Need for rewriting the project plan was not planned, however included work for planning the next iteration • Work for designing interfaces was spent on documenting • basicly same work, different form! • Integration of new tools took time • GENERALLY SOMEWHAT OVER PLANS IN RESOURCE USAGE, but succesful completion of project not endangered.

Working hours by person Realized hours in this iteration Plan in the beginning of this iteration Latest plan (inc. realized hours and other updates)

Quality assessment • Systematic testing will be started in iteration I2 • Currently no estimates on the quality levels of different components can be made • Number of reported bugs is low because of lack of testing • The goal of the iteration I1 was to develop a test plan Legend Coverage: 0 = nothing 1 = we looked at it 2 = we checked all functions 3 = it’s tested Quality: J = quality is good K = not sure L = quality is bad

Software size in Lines of Code (LOC)

Changes to the project • Project responsibilities were adjusted during the iteration. • Responsibilities are divided into process and subsystem responsibilities • Process responsibilities • Project management Hannu Kauppinen • Requirements management Vesa Salento • Documentation management Jouni Karppinen • Testing Kalle Valo • Subsystem responsibilities • System architecture Tuomas Luttinen • Model Jouni Kekoni • Server-Client structure Vesa Salento • User interface Mitro Kuha

Risks • Risk management has been performed on ad-hoc basis • Trapoli risk was materialized in previous iteration • all hours were written down in addition to maintaining information in Trapoli • No new risks were identified

Work practices • All planned work practices have been used • Usage of work practices have not been evaluated so far • Trapoli has worked better than in first iteration • however, there have still been some breaks in the system which have caused additional work during the iteration • Documentation and meeting practices and the usage of design patterns were presented during iteration • Pair programming has been used • Test practices and heuristic evaluation will be presented in next iteration • No changes in work practices planned so far

Project plan updates • Project organization was redefined as described earlier • Rights to project outcome were decided with customer • classified agreement will be signed later • Task-level planning for remaining iterations was included • Some new tools were specified • JUnit • HttpUnit • Checkstyle • PMD • Findbugs

Requirement specification updates • Some requirements were specified more closely after feedback from mentor and customer • Some prioritizations were redefined in co-operation with the customer

Technical specification General functionality Server-client structure

Technical specification (2) Using Lmodels with CLI Client

Technical specification (3) Lmodels packages

Test plan • Testing is focused on Lmodels Server • Lmodels Web client and CLI client are only tools to perform testing • Test approach • Unit testing • Automated system testing • Release testing • Load testing • Delivery acceptance testing • Test arrangements • Test cases • Test reporting • Error reports

Plan for the next iteration • Goals • Optimizing the model to shorten the processing time • Implementation of the linearizator • Implementation of the wrapper for the solver • Building the graphical user interface. • Implementing the client-server structure • Deliverables • Project plan (updated) • Requirements specification (updated) • Technical specification (updated) • Test plan (updated) • Test report • Test cases • Implemented software

Plan for the next iteration (2) • Optimizing the model is the least important goal for the iteration • Risks / uncertainties • Exact impact of holidays, how do different people use the holidays • Schedule • schedule and internal deadlines will be decided at the beginning of the iteration

Thank you for your attention! For any further questions, please contacthannu.kauppinen@iki.fi Rajoitteiset I1 Iteration3.12.2003

T-76.115 Project Review