VirtuCo Implementation 1 Project Review

VirtuCo v©v© Sami Hanhijärvi Project status –achieved goals in the iteration –project metrics Used work practices Completed work –Mobile demo Plans for the next iteration Agenda

VirtuCo v©v© Sami Hanhijärvi Status of planned goals Develop message transmission capable architecture –A basic architecture build with future requirements in mind. –Kept simple. –Produced in MIDP2.0, MIDP1.0 proxies will be done later. Produce simple conversation demo –Working demo is ready. –Is presented later on.

VirtuCo v©v© Sami Hanhijärvi Status of planned deliverables Project plan and requirements documents –Updated to match current situation Technical documentation done in a general perspective –UML used, but not strict –Slideshow format Test case specifications –Done for the implemented software Test report –Done for executed tests

VirtuCo v©v© Sami Hanhijärvi Realization of the tasks –Client architectural design Trapoli –Requirements –Prepare testing Test plan –Setup development environment Problems with emulators –Unplanned

VirtuCo v©v© Sami Hanhijärvi Working hours by person Unfamiliar with technology More to do than first anticipated RealPlanDiff Hannu Jorma Kaarle Kai Petteri Sami Ville Total Realized hours in this iterationPlan in the beginning of this iteration PPI1I2I3DETotal Hannu Jorma Kaarle Kai Petteri Sami Ville Total Latest plan (inc. realized hours and other updates) PPI1I2I3DETotal Hannu Jorma Kaarle Kai Petteri Sami Ville Total

VirtuCo v©v© Sami Hanhijärvi Quality metrics Results of system testing PPI1Total Reported92496 Closed92395 Open011 Issue metrics Implementation 1BlockersCriticalMajorMinorTrivialTotal Total open This iteration reported110204

VirtuCo v©v© Sami Hanhijärvi Quality assessment Overall quality is good enough for a demonstration Further testing needed for product use More thorough unit testing –Test MIDLet Functional areaCoverageQualityComments Conversation2 Some defects found and all above minor were fixed. 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

VirtuCo v©v© Sami Hanhijärvi Software size Lines of code I1I2I3DE Client total 2114 Client comments 946 Server total 2006 Server comments 941 Common total 204 Common comments 109 Total 4324 Comments 1996 Lines of code per programming hour I1I2I3DE Functional lines of code 15 Any line of code 27

VirtuCo v©v© Sami Hanhijärvi Changes to the project

VirtuCo v©v© Sami Hanhijärvi Risks Risk management document refactored –Contains only 8 risks –Previous one merged and generalized Risk for development tool problems –Risk realized –Produced work-around for problems

VirtuCo v©v© Sami Hanhijärvi Work practices Process construction and tuning Design patterns Software Configuration Management Automated unit tests

VirtuCo v©v© Sami Hanhijärvi Results of the iteration Software –Message transmission capable architecture Server and client –Demonstration New documentation –Technical specification –Test plan –Test cases –Test report

VirtuCo v©v© Sami Hanhijärvi Demonstration

VirtuCo v©v© Sami Hanhijärvi Plans for the next iteration Goals –Community architecture –Community demo Deliverables –User’s guide Risks –Practices not followed –Tools produce problems Schedule –Task dependencies