T-76.115 Project Review ITSUPS Implementation 2 10.2.2004

T-76.115 Project Review

ITSUPSImplementation 2

10.2.2004

2

T-76.115 Project ReviewT-76.115 Project Review

Agenda

Project status (15 min) achieving the goals of the iteration project metrics

Work results (20 min) presenting the iteration’s results

HuVi (Pipsa Hellemaa) ViHu (Natalia Kaijalainen)

demo (Niko Setälä) Used work practices (5 min)

3


Introduction to the project

Project plan: ”The purpose of the project is to make the traffic simulation system of the laboratory of transportation engineering, HUTSIM, to collaborate with ViaSys’s city planning tool”

NovaPoint Virtual MapHutSim

HuVi: Positions, speeds and directions of vehicles

ViHu: Borders of streets, trafficlines, traffic lights etc.

4


Conversion

NovaPointVirtual Map

Path-Interface

Coord-Interface

HUTSIMMicrosimulation

System

Conversion& Edit

Land-XMLCNF-file

XYZ-coords XML

Traffic Simulation 3D-Visualization

Integration of Traffic Simulation with 3D-Visualization

I.Kosonen, HUT

Line-Interface

ConfigurationData (Static)

Vehicle Data(Dynamic)

5


Status of the iteration’s goals

HuVi Goal 1: Complete working program

Lots of implementation has been done Not done:

HuVi: Doesn’t get enough information from Ampel Goal 2: Simple user interface

OK ViHu

Goal 3: Complete working program All implementation has been done Not done:

ViHu: Pipes were not implemented Goal 4: Simple user interface

OK Goal 5: Write user guide

OK

6


Status of the iteration’s deliverables

Implementation of HUTSIM->Virtual Map OK

Implementation of Virtual Map->HUTSIM OK

Documents: Updated project plan

OK Updated requirements document

OK Updated technical specification

OK User guide

OK Test report, test cases and test log (one document)

OK Progress report

OK Updated SEPA diaries

OK Updated risk management document

OK Updated resource management document

OK

7


Realization of the tasks

Despite a few mistakes, the iteration went quite like planned

Mistakes in plan: User guide was a draft version User interface was forgotten

8


Working hours by person

Iteration went like planned Group members have quite

nicely evenly time left for the last iteration

Real Plan DiffMatti 47 46 +1Pipsa 80 73 +7Susse 47 57 -10Minttu 74 65 +9Niko 51 48 +3Pihla 52 50 +2Natalia 43 45 -2Total 394 384 +10

Realized hours in this iteration Plan in the beginning of this iteration

PP I1 I2 FD TotalMatti 60 41 47 42 190Pipsa 40 27 80 43 190Susse 36 52 47 55 190Minttu 27 56 74 33 190Niko 45 57 51 37 190Pihla 41 54 52 43 190Natalia 44 63 43 40 190Total 293 350 394 293 1330

PP I1 I2 Sub

Tot

FD Total

Matti 60 41 47 148 42 190Pipsa 40 27 80 147 43 190Susse 36 52 47 135 55 190Minttu 27 56 74 157 33 190Niko 45 57 51 153 37 190Pihla 41 54 52 147 43 190Natalia 44 63 43 150 40 190Total 293 350 394 647 293 1330

Latest plan (inc. realized hours and other updates)

9


Quality metrics

I1 I2 DE TotalReported 6 6 - 6Closed 0 0 - 0Open 6 6 -

Defects in code

Blockers Critical Major Minor Trivial TotalThis iteration reported

- - 5 1 - 6

Last iteration bugs were not fixed beacuse they were results of negative tests. We thought that the most important thing now is to implement first all the necessary functionality and then if there is enough time fix the bugs.

10


Quality assessment

• HuVi (Hutsim -> Virtual Map)• Implementation not ready• Realtime output format still not defined• Unit testing done while coding• Module testing was done

• ViHu (Virtual Map -> Hutsim)• Implementation ready• Unit testing done while coding• Module testing was done• Doesn’t check if the input data is valid

Functional area Coverage Quality Comments

HuVi 2 Some functionalities not ready

ViHu 3 Some defects found

Legend

Coverage:

0 = nothing

1 = we looked at it

2 = we checked all functions

3 = it’s tested

Quality:

= quality is good

= not sure

= quality is bad

11


Software size in Lines of Code (LOC)

Any remarks on this metric? Code is quite well commented

PP I1 I2 DE

ViHu 0 847/390 1115/504

HuVi 0 632/253 1919/679

UI 0 177/57 446/140

Tests 0 132/29 452/139

Total (NCLOC + COM) 0 1788 3932

Comments (COM) 0 729 1462

12


Changes to the project

HuVi took much more time than expected In the beginning of the iteration we decided with client that we won’t

implement the pipes Testing had to be done in different way

Code reviews Schedule changed

13


Risks

Materialized risks Faulty software

Virtual Map has some bugs Testing difficult

Code Reviews used

Greatest risks Some problems with the testing. We believe that we can solve the problems

when we have implemented more.

14


Results of the iteration

Virtual Map -> HUTSIM (ViHu) Natalia Kaijalainen

HUTSIM -> Virtual Map (HuVi) Pipsa Hellemaa

15


ViHu-component

Architecture Same like in previous iteration Changes for .dxf were easy to accomplish

Overview Conversion from VirtualMap to HUTSIM is ready and works Pipes will not be implemented in this project but researched

Faced problems during iteration Viasys sent incorrect input files Coordinates depends on location on the Earth Scaling from world coordinates to HUTSIM

16


HuVi: Overview

Receives HUTSIM simulation data via Ampel Converts HUTSIM 2D data into 3D XML data Supports real time visualization of the simulation (online mode) Optionally converts data into Virtual Map ani format

17


HuVi: State Diagram

18


HuVi: Class Diagram

19


HuVi: Goals for I2

Define HuVi output format Complete all missing functionality Produce test program for online-mode

20


HuVi: Problems during I2

HUTSIM server- Display card- Firewall

Ampel- Understanding took more time than presumed

HUTSIM output- Does not include line data

21


HuVi: Status

Input from HUTSIM Does not include all data used by HuVi, needs to be modified

Reading of HUTSIM data Works, not thoroughly tested

Coordinate mapping Problems with input, line data not provided by HUTSIM

HuVi output format Defined, accepted

XML stream/file creation Not implemented

Online test program Not implemented

XML-ani conversion Works, not thoroughly tested

22


Used work practices

Week meetings Time reporting

At least once a week (Sunday) Version Control

CVS, server at SoberIT Quality Assurance

Defect Tracking Bugzilla

Risk Management Separate document

Resource Management Separate document

Sepas Meeting practices Static Methods Refactoring Test Automation on System Level Testing