Implementation 3 Project Review

Slides:



Advertisements
Similar presentations
T Project Review SOLIData I2 Iteration 2005-FEB-08.
Advertisements

T Project Review X-tremeIT I2 Iteration
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 VirtuCo PP Iteration
T Project Review Groupname [PP|…|DE] Iteration
T Iteration Demo BaseByters [I1] Iteration
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
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
T Project Review Magnificent Seven Project planning iteration
T Iteration Demo Team WiseGUI I2 Iteration
Software Development project 2nd Iteration demo Supporting Collective and Collocated Use of Contextual Media.
T Project Review ITSUPS Implementation
T Project Review TeXlipse [I2] Iteration
T Project Review eGo I3 Iteration
T Final Demo Xylophone I2 Iteration
T Project Review X-tremeIT I1 Iteration
T Final demonstration Tetrastone-group [RosettaNet End-user Interface]
T Final Demo Tikkaajat I2 Iteration
T Final demo I2 Iteration Agenda  Product presentation (20 min) ‏  Project close-up (20 min) ‏ Evaluation of the results  Questions.
T Project Review Tetrastone [Iteration 2]
T Iteration Demo BitPlayers I2 Iteration
T Project Review WellIT PP Iteration
VirtuCo :: Process description ::. :: Reference ::
Planning Iteration Demo Suunto Training Program Planner.
T Iteration Demo Group name [PP|I1|I2] Iteration
T Iteration Demo OSLC 2.0 I1 Iteration
FINAL DEMO Apollo Crew, group 3 T SW Development Project.
T Project Review Sotanorsu I3 Iteration
T Iteration demo T Iteration Demo Team Balboa I1 - Iteration
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 BetaTeam I2 Iteration, Final Solution
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 Project Review Sotanorsu I1 Iteration
T Iteration I1 Demo Software Trickery PP Iteration
T Project Review MalliPerhe Iteration 3 Implementation
T Project Review ITSUPS Implementation
Software Development Process CS 360 Lecture 3. Software Process The software process is a structured set of activities required to develop a software.
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 Iteration Demo BitPlayers PP Iteration
T Project Review MTS [PP] Iteration
T Project Review Wellit I1 Iteration
T Project Review Sotanorsu I2 Iteration
T Iteration Demo LicenseChecker I2 Iteration
T Project Review X-tremeIT PP Iteration
T Iteration Demo Byte-Pit I1 Iteration
T Project Review X-tremeIT I1 Iteration
Groupname [PP|…|FD] Iteration
TeXlipse [I1] Iteration
T Project Review Group: pdm I2 Iteration
Johanna Rothman Know What “Done” Means Chapter 11
Presentation transcript:

Implementation 3 Project Review 17.3.2004 VirtuCo Implementation 3 Project Review 17.3.2004

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

Status of planned goals Multiplayer tank game Done to the promised extent Peer testing Done Produced information about the reliability of the system Finalize implementation Only bug fixes left Sami Hanhijärvi 17.3.2004

Status of planned deliverables Project plan Update to match delivery plans Technical documentation Architecture description of new requirements added Test case specifications Updated to cover the game Test report Created for ran tests Sami Hanhijärvi 17.3.2004

Realization of the tasks Quite as planned Some shifts between parallel tasks Sami Hanhijärvi 17.3.2004

Working hours by person Realized hours in this iteration Plan in the beginning of this iteration Real Plan Diff Hannu 34+1 38 -3 Jorma 18+1 33 -14 Kaarle 52+1 39 14 Kai 23+1 18 6 Petteri 49+1 12 Sami 36+3 46 -7 Ville 10+1 7 4 Total 222+9 219 PP I1 I2 Subtot I3 DE Total Hannu 30 67 55 152 36 22 210 Jorma 25 54 93 172 24 14 Kaarle 70 53 153 40 17 Kai 32 89 45 166 27 Petteri 41 72 57 160 18 Sami 59 159 21 220 Ville 44 203 9 8 257 465 451 704 194 121 1490 Latest plan (inc. realized hours and other updates) Work distribution could have been better. Delivery tasks clarified, planned hours reduced. PP I1 I2 I3 Subtot DE Total Hannu 30 67 55 35 187 16 203 Jorma 25 54 93 19 191 210 Kaarle 70 53 206 4 211 Kai 32 89 45 24 190 207 Petteri 41 62 57 50 2 212 Sami 59 39 198 18 220 Ville 44 11 214 257 465 451 231 1398 74 1472 Sami Hanhijärvi 17.3.2004

Hours per work type in I3 Sami Hanhijärvi 17.3.2004

Hours per work type in the whole project Sami Hanhijärvi 17.3.2004

Quality metrics Issue metrics PP I1 I2 I3 Peer Total Reported 92 4 25 10 11 142 Closed 8 132 Open 6 3 9 Implementation 3 Blockers Critical Major Minor Trivial Total Total open 2 3 9 This iteration reported 4 8 6 21 Peer testing produced bugs that are more informative than bugs to be fixed Sami Hanhijärvi 17.3.2004

Quality assessment J K Bugs remain, but many are out of our scope. Functional area Coverage Quality Comments Conversation 3 J Works overall. One minor bug remains. Push messages 2 Works, problems with actual internet connections and JBoss. Tank game K Some critical bugs in extreme situations. User management Works overall. 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 Bugs remain, but many are out of our scope. Sami Hanhijärvi 17.3.2004

Software size Lines of code I1 I2 I3 DE Client total 2114 5895 9971 Client comments 946 2404 3804 Server total 2006 4592 5958 Server comments 941 1958 2458 Common total 204 156 202 Common comments 109 99 132 Total 4324 10643 16131 Comments 1996 4461 6394 Lines of code per programming hour I1 I2 I3 DE Functional lines of code 15 17 40 Any line of code 27 28 61 Sami Hanhijärvi 17.3.2004

Risks MIDP2.0 phone Time underrun Neutralized, when phone was received. Software worked quite easily with phone. Time underrun Didn’t happen, because scope was limited in I2 Sami Hanhijärvi 17.3.2004

Work practices Unit tests Refactoring Usability tests Sami Hanhijärvi 17.3.2004

Unit tests Metrics (testclasses / actual classes) client: 12 / 38 = 31,6% common: 0 / 3 = 0% server: 5 / 63 = 7,9% all: 17 / 104 = 16,3% Presentation held in review Sami Hanhijärvi 17.3.2004

Refactoring Used while adding new functionality A presenation is held in review. Sami Hanhijärvi 17.3.2004

Usability tests Usability was considered when creating tank game Peer tests worked also as usability tests A presentation is held in review. Sami Hanhijärvi 17.3.2004

Results of the iteration Software Tank game Demonstration New documentation Peer test report Sami Hanhijärvi 17.3.2004

Lessons learned NDS doesn’t allow network connections in Linux. Sami Hanhijärvi 17.3.2004

Service overview by Jorma Rinkinen Sami Hanhijärvi 17.3.2004

Demonstration Sami Hanhijärvi 17.3.2004

Plans for the next iteration Goals Good documentation Deliverables Final report PSE documents Auth. & billing considerations SW package Risks Minor time underrun risk Sami Hanhijärvi 17.3.2004