T-76.4115 Iteration Demo

1. T-76.4115 Iteration Demo BitPlayers I1 Iteration7.12.2005

2. 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) Agenda

3. Introduction to the project • Topic: ContextMUPE • Customer: HIIT (Helsinki Institute of Information Technology) • Goal 1: Integrate MUPE (Multi-User Publishing Environment) and ContextPhone so that it is possible to use context data in MUPE applications • Goal 2: Develop with ContextMUPE an application that demonstrates the use of context information. ContextMUPE ContextPhone MUPE Context information

4. Status of the iteration’s goals • Goal 1: Adding context data acquired by ContextPhone to MUPE • NOT FINISHED, will be continued in Implementation II • Project has started slowly • Developing the architecture took a lot more time than expected to the fact that neither ContextPhone or MUPE are documented -> time wasted waiting for answers and architecture redone several times • Connections work, but logic has not been incorporated in ContextMUPE. • Missing parts will be done in the beginning half of Implementation II and integration testing started in the middle of Implementation II • Goal 2: creating the specifications for a ContextMUPE application • MOVED TO LATER • Brainstorming session for what the application will be like with customer after the iteration demo • Specifications will be developed during Christmas “vacation”, finalized during Implementation II iteration planning. • Development of the application will go in parallel with the development of the system

5. Status of the iteration’s deliverables • Project plan • OK, except • chapter 5.1.12 Peer testing • Chapter 6.4. Implementation II • Requirements document • OK, some requirements further specified based on new information • QA documentation • QA plan ok • Test cases not yet defined • Use case 1 partly implemented • Context data can be sent to server

6. Realization of the tasks • Show status and effort distribution per task or task group • More time spent on design (also a bit more effort) than expected • Programming work started very late because architecture late, programming task smaller than expected • No testing conducted yet (no test documentation either) • Very minimal documentation (no user guides etc.) • Too much time budgeted on meetings

7. Working hours by person Realized hours in I1 iteration Plan in the beginning of this iteration • Knowledge a bottle neck -> developing work not divided equally • No testing done • Generally project has started slowly • Some group members busy with other courses/activities • Tasks will be moved to Christmas vacation and I2, which was originally planned to be a lighter iteration Latest plan

8. Quality assessment • Only very preliminary unit testing conducted on currently existing components • Check that the software compiles without critical errors • Actual unit and integration testing will be conducted during I2

9. Software size in Lines of Code (LOC) • Remarks • lots of new functinality was implemented • A lot remains to be done • More through commenting and refactoring may change the size in the near future

10. Changes to the project • Division of work: • Development of ContextMUPE will continue during Christmas vacation and Implementation II • System can only be tested on the test phone, not possible in emulator • Some unit testing can be conducted using dummy data if necessary • Minor revisions to requirements • The priorities of some requirements need to be discussed with the client • Refining the architecture • XML parser functionality needed to be added in order to get communications operating • ContextPhone interface was done as Blackboard client

11. Risks • What is the current situation regarding the risks? • Materialized risk: • Some group members have not had much time for this project • New, materialized risks: • Questions regarding ContextPhone and MUPE are answered slowly (stakeholders are not reachable, infosite down) -> project can not progress: All problems need to be documented (in Wiki) and questions asked IMMEDIATELY • Can't find the answer to questions regarding ContextPhone and MUPE (stakeholder says he doesn’t know answer) -> project can not progress: Contact directly the developer of the system, he must have the answer. • New risk: • Integrating Java and Symbian based systems is not possible or is very difficult -> Project can not be carried out: Redetermine goals/scope of the project with customer.

12. Results of the iteration • System architecture • Architecture refined to make the best out of new information that was achieved • The amount of code required was reduced from what was expected • The current architecture can be implemented • QA plan • Testing will be done in I2 • Most of the testing will have to be done on the phone • Implemented use cases • Use case 1 partially implemented • Demonstrate the developed software • There is no testable software yet – only parts of the software that are runnable separately • Complete parts: Sockets, ContextHandler, MUPE parser • Partially developed: Filter, Mupe Configuration, GUI

13. Architecture and status

14. Used work practices • How have you been using the planned work practices, what are the experiences of • mandatory practices • Iterative development, iteration planning, documenting, risk management, time reporting, software size reporting, communication, iteration demo, version contro, coding convention, defect tracking. • other practices • Weekly meetings • Problem log • Design Patterns (SEPA) • New practices • Reflection workshop (SEPA) • Agenda for meetings • Refactoring (SEPA)