T-76.115 Project Review Sotanorsu I3 Iteration 17.03.2004.

Slides:



Advertisements
Similar presentations
T Project Review X-tremeIT I2 Iteration
Advertisements

T Project Review I3 Iteration T Project Review X-TremeIT Valeria, Konstantin, Roman, Olesia, Vladislav, Seppo, Aleksandr 2 Agenda.
VirtuCo Implementation 1 Project Review
T Project Review Groupname [PP|…|DE] Iteration
T Iteration Demo BaseByters [I1] Iteration
Cornell University Library Instruction Statistics Reporting System Members: Patrick Chen (pyc7) Soo-Yung Cho (sc444) Gregg Herlacher (gah24) Wilson Muyenzi.
Release & Deployment ITIL Version 3
1 © 2006 Cisco Systems, Inc. All rights reserved. Session Number Presentation_ID Using the Cisco Technical Support & Documentation Website for Security.
© 2008 The McGraw-Hill Companies, Inc. All rights reserved. M I C R O S O F T ® Preparing for Electronic Distribution Lesson 14.
University of Palestine software engineering department Testing of Software Systems Fundamentals of testing instructor: Tasneem Darwish.
If you are very familiar with SOAR, try these quick links: Principal’s SOAR checklist here here Term 1 tasks – new features in 2010 here here Term 1 tasks.
Planning Iteration Demo Suunto Training Program Planner.
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
DaISy – Datacast Information System Group: Sotanorsu Customer: Digita Oy T Final Demonstration and Review.
T Project Review RoadRunners [PP] Iteration
Project Tracking. Questions... Why should we track a project that is underway? What aspects of a project need tracking?
T Project Review Magnificent Seven Project planning iteration
T Iteration Demo Team WiseGUI I2 Iteration
T Project Review ITSUPS Implementation
T Project Review TeXlipse [I2] Iteration
T Project Review eGo I3 Iteration
T Project Review X-tremeIT I1 Iteration
T Final Demo Tikkaajat I2 Iteration
T Iteration Demo CloudSizzle PP Iteration
T Project Review Tetrastone [Iteration 2]
T Iteration Demo BitPlayers I2 Iteration
T Project Review WellIT PP Iteration
COMP 208/214/215/216 – Lecture 8 Demonstrations and Portfolios.
T Iteration Demo Group name [PP|I1|I2] Iteration
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
T Project Review (Template for PI and I1 phases) Group name [PI|I1] Phase
T Project Review RoadRunners [IM1] Iteration
T Iteration Demo Team DTT I1 Iteration
T Iteration Demo BitPlayers I1 Iteration
T Iteration Demo Team 13 I1 Iteration
T Project Review eGo PP Iteration
T Sprint Demo Team Tarantino Iteration 1 / Sprint
T Project Review RoadRunners [IM3] Iteration
T Final Demo BaseByters T Final demo 2 Agenda  Project introduction (5 min)  Project status (5 min)  achieving the goals.
T Project Review eGo I2 Iteration
T Iteration Demo Team DTT Project planning (PP) Iteration
T Iteration Demo Software Trickery I2 Iteration
T Project Review WellIT I2 Iteration
T Iteration Demo Group name [PP|I1|I2] Iteration
T Iteration Demo Group 1 Project Planning Iteration
T Project Review Sotanorsu I1 Iteration
T Iteration I1 Demo Software Trickery PP Iteration
T Iteration Demo Tikkaajat [PP] Iteration
T Project Review MalliPerhe Iteration 3 Implementation
T Project Review ITSUPS Implementation
T Iteration Demo MapGuide based Web Edit Interface I2 Iteration
T Project Review RoadMappers I2 Iteration
T Project Review Rajoitteiset I2 Iteration
T Project Review Muuntaja I1 Iteration
T Iteration Demo Tempus I1 Iteration
T Project Review MTS [PP] Iteration
T Project Review Wellit I1 Iteration
Increment 2 Development Plan - License Checker 2.0 Jing Jing-Helles
CIS-NG CASREP Information System Next Generation Shawn Baugh Amy Ramirez Amy Lee Alex Sanin Sam Avanessians.
T Project Review Sotanorsu I2 Iteration
T Iteration Demo LicenseChecker I2 Iteration
T Project Review X-tremeIT PP Iteration
T Project Review MalliPerhe PP Iteration
T Project Review X-tremeIT I1 Iteration
Development Environment
Groupname [PP|…|FD] Iteration
TeXlipse [I1] Iteration
Archiving and Document Transfer Utilities
T Project Review Group: pdm I2 Iteration
Implementation 3 Project Review
Presentation transcript:

T Project Review Sotanorsu I3 Iteration

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

T Project Review 3 Status of planned goals of the iteration  Goal 1: Test the system in final environment at the end of I3 with at least using 2 separate PC configuration  OK  Demonstration will use sotanorsu.soberit and comsy.soberit and transfer content between them  Goal 2: There are no major open implementation issues at the end of I3  OK  Mainly some UI improvements remain  Goal 3: A visualization UI for the GPS is developed  Dropped  Agreed with customer, that the visualization will be done using a video screen and a printed map of the area  Goal 4: Presentation counts are stored and transferred in the system  OK  Goal 5: The presentations are shown according to time of day specified in them  OK  Goal 6: Large system issues are designed in technical documentation  Not done  Not enough time to complete this  Discussed with customer, that it is more important to get the system done and working  Goal 7: Complete peer testing  OK  Other achievements  Summary display added to CoMSy according to customer’s wish  CoDSy control from CoMsy – starting, stopping, resetting and transfering files are now commands in CoMSy- side UI  Querying, modifying and removing presentation packages is now possible  Removing JPEGs and MPEGs from the system is now possible  Some finalization done as well – removed hardcoded constants, improving configurability and error messages

T Project Review 4 Status of planned deliverables of the iteration (1/2)  Updated project plan  OK  Updated requirements  OK, also markings for implementation phases added now  Updated technical specification  OK, but Rose was still not working in the classroom, some pictures not updated  Updated test cases  OK  Test report and test log  OK  Peer test plans and plans prepared by the peer testing group  OK  Peer test report and report made by the peer testing group  OK  Updated user’s manual  OK, much left to be done in DE phase, though  Progress report  OK

T Project Review 5 Status of planned deliverables of the iteration (2/2) [The ones added during the iteration have been marked as NEW]  GPS data from serial port (F227)  GPS data can be read from serial port, since this was done when collecting demonstration data  The current CoDSy implementation reads this only from file  Default content displayed, when no GPS data available (F218)  OK, tested  User interface (P103, U145 (NEW), U146 (NEW))  OK, tested  Store, transfer and query presentation count (F104, F21, F219, F224)  OK, tested  Advanced location coordinates (U141, U142, U143)  OK, tested  Additional presentation package features (U121, U123 (NEW), U124 (NEW), U125 (NEW))  OK, tested  Additional CoMSy features (U148 (NEW), U149 (NEW), U150 (NEW))  U148, U149, U150 (stop/start/reset CoDSy from CoMSy) Implemented, working, but not thoroughly tested  PDA features (U113, U205, U116, U144, research Bluetooth)  U113 (remove PDA content) OK, tested  U205 (MP3 on PDA) OK, tested  U116, U144 (static PDA content) not completely implemented, not tested  Bluetooth research documented

T Project Review 6 Reactions to I2 feedback  Statistics of number of use cases implemented  Statistics updated in requirements document and added to these review slides (see slide software size)

T Project Review 7 Realization of the tasks (1/2)  See summary of I3_Additional_comsy_features and Unplanned tasks on next slide  refactoring and database code cleanup took more time than assumed  Demo preparation took much longer time than expected  Made demonstration content for final demo and delivery as well  Recorded demo material on video tape  General organization did not take as long as expected  New manager had routines running well from I3  Ran out of time for specifying large system issues  GPS visualization GUI was dropped

T Project Review 8 Realization of the tasks (2/2)  Adding time of day to presentations had been forgotten from I3 plans and in addition it also took 17 hours more than was originally planned  Some essential user interface features were added, although they had not been planned previously  Authentication and changing to port 80 done in order to be able to view the system from external networks (e.g. customer’s)  Some essential bug fixes took some extra time

T Project Review 9 Working hours by person  The working hour estimation for final 5 days in the end of I2 failed by about 25 hours. Now those hours are updated to the tables  Implementing Time of Day functionality took much more of Essi’s time than was planned  Simo and Kirsi were busy with other courses and activities Realized hours in this iterationPlan in the beginning of this iteration Latest plan (inc. realized hours and other updates)

T Project Review 10 Quality metrics – Bugs and code review  No major bugs remain I1I2I3DETotal Reported Closed Open 186 Bug metrics (Mon ) BlockersCriticalMajorMinorTrivialTotal Total open This iteration reported Issues: I1I2I3DETotal Reported 67 Closed 33 Open 34 Code review metrics from I2 – no code review done in I3, will be done in DE  Mostly minor issues still remain, time allocated in DE to fix the main ones

T Project Review 11 Quality assessment Functional areaCoverageQualityComments CoMSy3 Only some UI prettyfying left CoDSy3 OK, tested Data transfer3  Works well, but there some trashing of database connections has been noticed PDA connection3 Still OK, no changes in I3 PDA content display1  OK, file path problems solved. But static content feature currently not completely implemented and removing of PDA content does not work. Legend Coverage: 0 = nothing 1 = we looked at it 2 = we checked all functions 3 = it’s tested CR = it’s code reviewed Quality:  = quality is good  = not sure  = quality is bad  Quality is OK

T Project Review 12 Software size Metrics (Sun )

T Project Review 13 Changes to the project  GPS visualization UI dropped  Visualization using a printed map and video is used instead  New requirement from customer, summary display on CoMSy (U145)  New implemented requirements from within the group in order to improve the system usability. These have been briefly discussed and agreed upon with the customer:  U123, U124, U125 Query, modify, remove presentation packages  U146 Remove JPG / MPEG from the system  U147 Transfer all presentation packages from CoMSy to CoDSy  U148 Stop CoDSy from CoMSy  U149 Start CoDSy from CoMSy  U150 Reset CoDSy from CoMSy  U121 Add time of day  Entering task for this in Trapoli was forgotten in the beginning of I3, 5 hours had been preplanned in discussions with the customer  Peer testing not completed as early as planned  The peer testing had to be postponed from the early start of I3 to couple weeks later

T Project Review 14 Risks  The ligther risk management practises have been carried out:  An array of risks and their status is still documented in the project plan  Risks were identified in the beginning of iteration in a separate meeting and have been checked in project group meetings a couple of times  Materialized risks  3: Requirements change  Summary page to CoMSy UI  No GPS visualization software  7: Internal deadlines are not met.  Some impact in the end of I3, mainly unable to get the static PDA content features done early enough  New risks identified  None

T Project Review 15 Results of the iteration  Software and documents are close to their final versions  Demonstration of the new functionalities

T Project Review 16 Plan for the next iteration (1/2)  Goals  Fix remaining major bugs  Write final versions of all the documents  Sign the contract with the customer  Review and finalize the program code  Create and deliver the installation package to customer  Improve the UI concentrating on issues related to use in final demonstration environment  Arrange training to the customer  Deliverables  Final report  Test report and log (if necessary)  Final versions of all documents produced during the project

T Project Review 17 Plan for the next iteration (2/2)  Implemented features and fixes  DE_Fix_remove_hard_coded_constants – Make the software easier to update  DE_Fix_trashing_DB_conn – There is a minor problem with trashing DB connections. Fix it.  DE_UC_GPS_data_from_serial_port –Make it possible to read the GPS data from serial port in addition to file  DE_UC_CoDSy_PDA_content_remove – Removed PDA content is currently not correctly updated to the CoDSy side  DE_UC_CoMSy_apperance – Improve the CoMSy appearance according to customer’s wishes if needed  DE_Fix_MPEG_problem – Get the MPEG movies to work correctly in CoDSy (refresh problem remains)  DE_UC_CoMSy_clear_DB_command – Make it possible to empty all databases by single CoMSy command button  DE_UC_CoMSy_reset_counts – Make it possible to reset presentation counts by single CoMSy commad button  DE_UC_Setting_CoDSy_current_time – It would be best for demonstration purposes, that the clock of CoDSy PC could be set from CoMSy user interface. Check, if this is possible and implement. If not possible, create and document an easy-to-use script for doing this manually on CoDSy or make CoDSy to read it’s time from some memory variable, which can be changed through CoMSy.  DE_UC_CoDSy_appearance – Improve the CoDSy appearance, remove debug messages and change it to run in full screen mode  DE_UC_CoMSy_side_preview – Make it possible to preview content objects on CoMSy side prior to uploading them to CoDSy  Risks / uncertainties  No major risks remain  Tight schedule, extremely important for the group to keep the internal deadlines  Timetable and dependencies in following slides

T Project Review 18 Timetable (1/2)

T Project Review 19 Timetable (2/2)