T Project Review ITSUPS Implementation

T Project Review 2 Agenda  Project status (15 min)  achieving the goals of the iteration  project metrics  Work results (20 min)  presenting the iteration’s results  demo  Used work practices (5 min)

T Project Review 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 Map HutSim HuVi: Positions, speeds and directions of vehicles ViHu: Borders of streets, trafficlines, traffic lights etc.

T Project Review 4 Conversion NovaPoint Virtual Map Path-Interface Coord-Interface HUTSIM Microsimulation System Conversion & Edit Land-XML CNF-file XYZ-coords XML Traffic Simulation3D-Visualization Integration of Traffic Simulation with 3D-Visualization I.Kosonen, HUT Line-Interface Configuration Data (Static) Vehicle Data (Dynamic)

T Project Review 5 Status of the iteration’s goals  Goal 1: Design HUTSIM->Virtual Map architecture  OK  Goal 2: Design Virtual Map->HUTSIM architecture  NOT OK, because ViaSys hasn’t been able to provide us their output  Goal 3: Discuss what data is needed from the LandXML  ViaSys hasn’t provided the LandXML, but we have discussed about it on formal level.  Goal 4: Pipes are planned but not implemented  We have discussed about the pipes and there is some documentation about, but because even the lines are not fully implemented the pipes have been in smaller role.

T Project Review 6 Status of the iteration’s deliverables  Implementation of HUTSIM->Virtual Map  Plan standard for for data transfer format for visualization and simulation programs. Format must upgradeable.  not OK  Implementation of Virtual Map->HUTSIM  roads to HUTSIM as lines  Not totally completed, because we don’t have the Virtual Map output  simple HUTSIM-model  Not totally completed, because we don’t have the Virtual Map output  Documents:  updated project plan (especially ch. 5.3 QA plan)  OK, QA plan as separate document  updated requirements document  OK, no great updates required  technical specification  OK  test cases  OK  test report and test log  OK  progress report  OK  updated SEPA diaries  OK, refactoring and test automation on system level not used as planned  risk management document  OK, updated weekly  resource management document  OK, updated when needed (2 times per iteration)

T Project Review 7 Realization of the tasks  We got the output of Virtual Map so hours were moved to the next iterations

T Project Review 8 Working hours by person  It was decided with the customer that lot of implementation (hours) is moved to the next iterations  Hours were not equally divided due to trips and work given from other courses RealPlanDiff Matti Pipsa Susse Minttu Niko Pihla Natalia Total Realized hours in this iterationPlan in the beginning of this iteration PPI1I2FDTotal Matti Pipsa Susse Minttu Niko Pihla Natalia Total PPI1Sub Tot I2FDTotal Matti Pipsa Susse Minttu Niko Pihla Natalia Total Latest plan (inc. realized hours and other updates)

T Project Review 9 Quality metrics I1I2I3DETotal Reported Closed Open 6--- Deffects in code BlockersCriticalMajorMinorTrivialTotal This iteration reported Tech. Spec.QA-plan Deffects Deffects found in document reviews

T Project Review 10 Quality assessment HuVi (Hutsim -> Virtual Map) Implementation started Output format still not defined Unit testing done while coding Module testing was done on draft level ViHu (Virtual Map -> Hutsim) Implementation started Input format still not defined Unit testing done while coding Module testing was done Functional areaCoverageQualityComments HuVi1  Implementation in early stage ViHu1 Some defects found, nothing serious 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

T Project Review 11 Quality assurance –plan (1/3)  Project management  Iterative lifecycle -> team and customer have same goals  Scheduling and time tracking -> project is in time  Communication -> all communication channels works  Risk management -> better project quality  Documentation  Language -> product can be developed in future  Templates -> all important issues are discussed  Document version control ->Everyone knows that has been changed since last time  Iterative process in documenting ->documents better  Review -> ensure quality

T Project Review 12 Quality assurance –plan (2/3)  Implementation  Design -> implementation in two groups  Practices -> improve code quality  Iterative process  Code conventions  Refactoring  Testing  Unit level -> coders  Module, Integration and System level -> organized  Acceptance level -> customer with group  Error management and documentation  Bugzilla -> reported defects and their states  Test log -> report used test cases  Tools  CVS  Eclipse  TikiWiki  Bugzilla

T Project Review 13 Quality assurance –plan (3/3)  This iteration  Tested implemented parts of ViHu & HuVi  Not tested  Not totally implemented functionalities  Effeciency -> product still draft  Metrics  Deffects and their states  Review results  Environment -> Eclipse  Recourses  2 testers  Test not own part of the code  Test rounds  Not yet, in future smoke tests

T Project Review 14 Software size in Lines of Code (LOC)  Any remarks on this metric?  Not so much was implemented as planned PPI1I2DE ViHu 0810 /70 HuVi 0514 /40 UI 0168 /20 Tests 0133 /20 Total (NCLOC + COM) Comments (COM) 0150

T Project Review 15 Changes to the project  Implementation hours moved from Implementation 1 to Impementation 2  We still don’t have the output of Virtual Map

T Project Review 16 Risks  Materialized risks  Other courses take time  Group member missing  Equipment not got in time  Preventative action: Hours moved to the next iterations  Time lost because we had to make demos in other way  Communication problems with ViaSys  Problem: We don’t know when we are going to get the output of Virtual Map  Greatest risks  Output of Virtual Map  Are we going to get?  If we get, when we are going to get it?

T Project Review 17 Results of the iteration  Virtual Map -> HUTSIM (ViHu)  Niko Setälä  HUTSIM -> Virtual Map (HuVi)  Minttu Mustonen

T Project Review 18 ViHu Module

T Project Review 19 ViHu Module

T Project Review 20 HuVi module  Converts data from Hutsim to 3D-animation application  Supports real-time animation  Can write data firrst to file and then run the animation  Converter for Virtual Map

T Project Review 21 Running the application 1. Parse data from Hutsim (use Ampel) objects pipes 2. Convert pipes to paths and positions 3. Make the XML output 4. Convert data to.ani-file

T Project Review 22 State Diagram of HuVi module

T Project Review 23 Class diagram of HuVi module

T Project Review 24 Used work practices  Week meetings  Time reporting  At least once a week (Sunday)  Version Control  CVS, server at SoberIT  Defect Tracking  Bugzilla  Risk Management  Separate document  Resource Management  Separate document  Sepas  Meeting practices  Static Methods  Still not used  Refactoring  Test Automation on System Level Testing