T Iteration Demo Tempus I1 Iteration

T Iteration demo 2 Agenda  Project status (15 min)  Status of goals and deliverables  Project metrics  Used work practices  Work results (15 min)  presenting the iteration’s results  demo  Discussion (10 min)

T Iteration demo 3 Introduction to the project  What is this project about?  Develop a calendar sharing solution based on the Session Initiation Protocol (SIP)  Based on IETF draft chaired by the customer  Extend Mozilla Calendar Project for client  First create own test server, later replace with version from customer  Work on the draft as necessary  Context of the project  Practical part of the T Course  Project group composed of 9 students from Helsinki University of Technology  Customer is Nokia Research Center  Time: September 2005 – March 2006  Size: Work limited to a total of 1710 hours for the project group

T Iteration demo 4 Status of the iteration’s goals  Goal 1: Complete initial planning of the project and move to the implementation phase  Ok  Goal 2: Improve communication both inside the group and towards the customer and mentor  Improved: Communication towards the customer still needs work.  Goal 3: Distribute work and get developers involved in project planning  Ok: Weekly group meetings and developer sessions have worked.  Goal 4: Design the overall software architecture  Ok  Goal 5: Implement subscribing to calendars and serving subscription requests  Partly ok: Subscribing is implemented. Serving requests is incomplete.  Goals 6-7: Implement publishing calendars and sending related notifications and Implement basic authorization functionality  Moved to I2 due to schedule overruns.  Refine customer requirements, architecture and IETF draft as needed  Work ongoing. IETF draft changes not relevant after postponing goals 6-7.

T Iteration demo 5 Status of the iteration’s document deliverables  Updated Requirements Specification  Ok  Technical Specification  Main points covered.  Test plan, test cases and test reports  Ok  Progress report  Ok  Updated Project Plan  Ok  Updated Quality Handbook  Ok  SEPA diaries up to I1 chapters  Mostly ok. Some deployments delayed due to project delays. TDD SEPA refocused.

T Iteration demo 6 Status of the iteration’s software deliverables  Subscribe to a remote calendar (UC-1)  Ok  Receive and process subscription (UC-2)  Incomplete  Publish calendar (UC-3)  Moved to I2  Update published calendar (UC-4)  Moved to I2  Manage authorization rules for an integrated calendar store (UC-5)  Moved to I2

T Iteration demo 7 Realization of tasks by type Research and ground work (integration of SIP library) took a lot more time than anticipated Completion percentages not necessarily accurate as averages also contain postponed tasks

T Iteration demo 8 Non-document task hours

T Iteration demo 9 Working hours by person Realized hours in this iteration

T Iteration demo 10 Working hours by person Plan in the beginning of this iterationLatest plan Annu Lauri I Juha Total Anu Sakke Juho Janne Paula Heipa TotalI2 Σ PP 19083,5106,595,511 Annu 19086,5103, Lauri , ,5 130,5 I ,5151,532 Juha Total Anu Sakke Juho 19023,5166,550 Janne 19082,5107,512 Paula 19047,5142,512 Heipa TotalI2 Σ PP 12 95,5 A lot more resources used than expected Mostly research (all developers) and SIP integration (Janne, Juho, Heipa) Will need to carefully consider the scope of I2

T Iteration demo 11 Quality metrics  There is still rather little code and limited functionality  Mostly smoke testing against the simplest use scenarios and limited explorative testing  Javascript test pages also used  This is a common test method for Mozilla  Integration testing has been especially challenging as the Mozilla platform limits the ability to use conventional debugging tools  One code review was also held  Mostly focused on naming conventions and comment quality  Also served as a structural overview for non-developers  This slide may be updated for the iteration demo as testing progresses.

T Iteration demo 12 Quality assessment  This slide will be updated for the iteration demo as testing progresses. New documents received multiple reviews. Old documents updated and reviewed. 3Documents Looks fine.  2User interface Reviewed statically, but not tested in practice yet.  1Calendar logic Basic functionality tested using Javascript test pages. Some issues remain.  1SIP integration CommentsQualityCoverageFunctional area 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 Iteration demo 13 Software size in Lines of Code (LOC) ?-0 Comments (COM) ?-0 Total (NCLOC + COM) I2I1PP Total (NCLOC + COM) Comments (COM) Part E Part D Part C 1000 / /10 Part B 3000 / /90 0 Part A Total /com I2I1PP  This slide will be created for the iteration demo

T Iteration demo 14 Risks  Realized risks  Customer server software was delayed  Customer server not always reliable and problems with firewall  Effort needed for research and Mozilla platform setup severely underestimated  Mozilla platform not completely stable and documentation sometimes flaky  Current major risks  A lot of resources have been spent  Mozilla platform may still pose unexpected challenges

T Iteration demo 15 Used work practices  Documents in Latex working will  Not all documents could be converted (spreadsheets)  Wiki working will for meeting agendas and minutes  At least one SEPA diary moved from wiki to Latex due to a lack of image support  Weekly meetings have been useful  Also IRC status reviews on Fridays  Status s have been useful when sent  Need to keep these up  Working hour logging not always up to date  Dotproject has worked well, but manual spreadsheet work is needed to extract all the relevant information  More efficient communication and cooperation between developer groups is still needed

T Iteration demo 16 Overall Mozilla Architecture

T Iteration demo 17 Mozilla Calendar Overall Architecture

T Iteration demo 18 Tempus Architecture 1/2

T Iteration demo 19 Tempus Architecture 2/2 Relatively simple modular structure Sofia SIP as a library written in C A simple C-to-C++ interface layer A C++ wrapper inside a Mozilla XPCOM component with XPCOM interafaces Separate client and server functionality modules inside Mozilla written in Javascript Interaction with the C++ wrapper, Mozilla calendar store and user UI components written in XUL and Javascript as overlays for the Mozilla Sunbird calendar UI

T Iteration demo 20 Current functionality  Subscribing to a remote calendar  This slide will be updated for the Iteration Demo