T-76.115 Project Review

1. T-76.115 Project Review BigBrother PP Iteration3.11.2004

2. Project introduction (5 min) Project team Project customer Project goals Project status (10 min) achieving the goals of the iteration project metrics Work results (10 min) presenting the iteration’s results Used work practices (5 min) Next iteration planning (5 min) Agenda 1 5 min 10min 10min 5min 5min

3. Introduction to the project • Customer: Beconnected Finland Ltd. • Produces IP-based video surveillance systems for international market • Main product: ASAN = Automatic Surveillance and Alarming Network • Customer representative: PhD Michael Samarin • Project team: • Aino Lahdenperä, Maija Kangas, Outi Syysjoki, Janne Ojala, Antti Alestalo, Juhani Nokela, Ville Vatén • GOAL: Produce tools, which help Beconnected in their customer support work and reduce costs through increased productivity • Three tools will be created: • Watchdog – Automatic monitoring of network cameras • HourLogger – Log support person’s work hours per customer/target • LogAnalyzer – Search for error patterns from ASAN logs • Beconnected’s goals: • Working software is the only thing that matters • KISS – Concentrate on simplicity, maintainability, quality. No fancy features • Very busy making business – we should bother them as little as possible • Minimize costs – all costs should be covered by the attendance fee to SoberIT 4 5 min 10min 10min 5min 5min

4. Overview of the problem domain 5 5 min 10min 10min 5min 5min

5. Status of the iteration’s goals • Goal 1: Get to know the customer and their goals for the project. • OK • Goal 2: Learn their working methods and tools. • Not as important as assumed • Goal 3: Synchronize mutual project goals, methods and schedule between the customer, project team and course staff. • OK. • Goal 4: Plan the project and write the project plan • Not 100%, but close enough for this phase • Goal 5: Gather customers requirements from customer and write initial requirements specification document • OK • Goal 6: Study the application domain and familiarize the project team with the concepts and challenges in it. • OK for those who have been able to attend all customer meetings • Goal 7: Set up all the needed tools and environments for communication, documentation and programming. • OK, except development server from students’ own resources not available 7 5 min 10min 10min 5min 5min

6. Status of the iteration’s deliverables • Project Plan • OK, except some minor tuning needed • QA plan will be delivered 9.11. • Requirements document • Only a few most important use cases written in detail • More use cases will be added in the next iteration • Watchdog • OK, enough to start design and implementation • HourLogger • OK, enough to start design and implementation • LogAnalyzer • OK, enough to start design and implementation • Non-functional requirements • OK, but might still need some work with the customer. 8 5 min 10min 10min 5min 5min

7. Realization of the tasks • Major discrepancies • Lectures: people didn’t attend as much as expected (Tools: PM was alone!) • RE: much of the elicitation was done in project kick-off meeting and review was performed by email. • Internal status & planning meetings very efficient, some planning work moved to project plan writing sessions • Write project plan • Includes a lot of other planning work too • Slower progress than expected • Not started: • SEPA practices not started yet • Project review not included yet • Much of the work was included in the project plan writing • Extranet not as complicated as expected  • Delivery preparations not included yet • NOTE: Only hours until 1.11. have been included in these figures! 10 5 min 10min 10min 5min 5min

8. Realization of budget • Monthly allowance of € 100 for miscellaneous well justified project costs • October costs: • € 1 for mailing the NDAs • $ 43 for buying Core Servlets and JavaServer Pages, Vol. 1 from Amazon 11 5 min 10min 10min 5min 5min

9. Working hours by person Realized hours in this iteration • These figure DON’T include the PP-delivery and PP-project review hours • Ville put more work in RE than originally planned. This plan already takes it into account. • The personal work distribution was NOT planned in the PP-iteration plan. This reflects the situation of the plan a week ago. • Work distribution among members not satisfactory 12 5 min 10min 10min 5min 5min

10. Quality assessment Legend Coverage: 0 = nothing 1 = we looked at it 2 = we checked all functions 3 = it’s tested Quality: J = quality is good K = not sure L = quality is bad 13 5 min 10min 10min 5min 5min

11. Risks • Risks • Development Environment not set up yet • NDA is very strict • We can not publish something critical to the course • We publish something that breaches the NDA • Busy schedules among group members • More work used than planned • Potential communication problems • English is used as the primary project language • Quality problems among team member deliverables 15 5 min 10min 10min 5min 5min

12. Results of the iteration • Project Plan • Requirements Document • Demonstration 16 5 min 10min 10min 5min 5min

13. Project plan • Stakeholders and staffing (next slide) • Project goals (discussed before) • Special attention to the verification criterias has been given • Project resources (discussed before) • Project practices and tools • Iterative and incremental development • Use-case driven development • Chief engineer centered development and group sessions • Communication through mails and Wiki • Meetings: efficient, good meeting minutes, avoid meetings • Work hour logging: strict, needed for the course • SEPA: Pair programming, Usability tests, Design patterns, Meeting practices • Phasing overview • Watchdog and HourLogger main functionality in I1 • LogAnalyzer in I2 • Minimum requirements ready at the end of I2 18 5 min 10min 10min 5min 5min

14. Project Plan (continued) • Stakeholders and their relations 20 5 min 10min 10min 5min 5min

15. Requirements document • Watchdog • Monitors status of network camera on predefined intervals • Alarms when malfunction occurs • Allows user to configure the monitoring parameters, including ASAN server database authentication data • Records historical data of network camera statuses and erases old data • Presents data in illustrative form • HourLogger • Logs technician's work hours per customer, per target and per work type • Provides statistical analysis of the recorder work hours • Provides output filter for comma-separated list for the recorded work hours • Log Analyzer • Parses ASAN Server logs for error patterns • Provides overview and browsing of log events • Allows user to configure log analyzer parameters • Non-functional requirements • Special attention given 23 5 min 10min 10min 5min 5min

16. Demonstration • Demo of network cameras for the development purpose of this project • Originally, this demo was planned to be performed through our development server to demonstrate the availability of all development tools. 25 5 min 10min 10min 5min 5min

17. Used work practices • Time reporting in Trapoli • Difficulties in dividing working hours into concrete tasks and work types • Version control with CVS • Now in CC-work, before some quota problems • All documentation in HTML • Problems with Word HTML, Trellian… • Meetings • Laptop is pop • Risk Management • Has started • Requirements Elicitation and Analysis • Informal, unstructured interviews with the customer • Brainstorming • Group working sessions • Project plan writing • Requirements analysis & representation & validation sessions 30 5 min 10min 10min 5min 5min

18. Iteration I1 Goals • Generic goals: • Tools classes implemented • Development environment fully up and running • Requirements document actively maintained and requirements detail level is raised • Watchdog goals • Architectural design • User interface design • Detailed design • Background process implemented and tested • Login screen implemented and tested • Main view implemented and tested • Background process configuration implemented and tested • HourLogger goals: • Architectural design • User interface design • Detailed design • Login screen implemented and tested • Input view implemented and tested Overview view implemented and tested • Summary view implemented and tested • Configuration view implemented and tested • LogAnalyzer goals • Architectural design • User interface design • SEPA goals: • Pair programming sessions • Usability tests performed • Design patterns used in the architectural and detailed design • Meeting practices are reviewed and next version is taken to use 34 5 min 10min 10min 5min 5min

19. Questions? 35 5 min 10min 10min 5min 5min