T-76.4115 Iteration Demo

BetaTeamI1 Iteration

8.12.2005

2

T-76.4115 T-76.4115 IterationIteration demo demo

Agenda Project status (10 min)

achieving the goals of the iteration project metrics

Work results (30 min) presenting the iteration’s results

Technical Specification and system core architecture Demo: beta version of Product Database Server

Used work practices (5 min) Questions and comments (5 min)

3

T-76.4115 T-76.4115 IterationIteration demo demo

Introduction to the projectMotivation: To implement and integrate Product

Database Server solution to current NAPA product aiming to finding out the relation database effectivisity comparing the current shared file system.

Customer: NAPA Ltd ( computing-based systems for ship safety and performance )

Customer Goals: To implement, test and delivery a product database server, which work in the first phase together with current shared file style data manipulation. The new solution will be integrated to the application’s interface which already exists and uses its interface functions.

Project members goals: Geting the product database server work done with good quality, learning new practices and tools as a team with good team spirit.

4

T-76.4115 T-76.4115 IterationIteration demo demo

Project current situation 85% of customer goals has been reached Reached:

1. Database ER model is ready. 2. The database has been implemented according to the ER model. 3. It is possible to test the database. 5. The architecture is ready and will support different end users. 6. Interface to the current system function “read” works. 7. Interface to the current system function “write” works. 8. Update the database Information.9. Interface to the current system function “delete” works.

Will be done during I2 iteration (not planned exactly yet):4. Replacement of the current, shared file style data manipulation by the database

server. 10. The software is possible to execute on a laptop (Win & Solaris). 11. There is a Remote procedure call (RPC) interface. (This is an extra feature!)

53% of Working effort from Total project effort have been used Requiremets current situation in Requirements Specification document

5

T-76.4115 T-76.4115 IterationIteration demo demo

Status of the iteration I1 goals (1/2) Goal 1: To design the core architecture(ER model), the architecture in detail and

data model OK. Architecture has been changed from the first planned version and updated to technical

specification. Goal 2:The database implementation, basic classess’ impelemtation and unit

testing (read, write, delete and update) Database has been implemented and tested according to technical sepcification and ER

model. OK Read functionality has been focused, implemented and tested.OK Write functionality has been focused, implemented and tested.OK Delete functionality has been focused, implemented and tested.OK Update functionality is part of write functionality. Update works and it has been tested. OK

Goal 3:Familiarize with engineering and building environments Engineering Environment: Java, Intel compiling environment for Fortran, Visual C++

environemt for c -coding, Embedded SQL environment. Sybase –database server Building Environement: Napa Build and Eclipse (Java)

Goal 4:Familiarize with integartion and system testing environments OK, Integration and system testing environemnt is Napa environent with the new database

Goal 5: Kick-off meeting with project group, mentor and customer OK

6

T-76.4115 T-76.4115 IterationIteration demo demo

Status of the iteration I1 goals (2/2) Goal 6: Beta release of new product data server ( functional requirements

from ”must” category) OK. Database implemented, but not integrated to UI. All functionality read, write, update and delete has been planned, implemented and tested.

Goal 7: First phase of the SEPA OK, all has been given introduction to their SEPA subjects. iteration I1 diaries is in the web site. Subjects are ( meeting practices, pair programmin and unit testing)

Goal 8, Peer testing is planned NOK, This has been agreed with mentor and customer and move to I2 iteration

Goal 9: Project monitoring and tracking OK, regulary on monday meetings

Goal 10: Reporting the project progress and work effort to customer and mentor

OK, weekly reports to customer and mentor

7

T-76.4115 T-76.4115 IterationIteration demo demo

Status of the iteration’s deliverables

Updated project plan (especially chap. 5.2 QA plan) OK. Also I2 Iteration plan first draft

Updated requirements document OK

Technical specification OK, UML diagrams for all the planned features ( read, write, delete and update)

Test cases OK

Test report and test log OK

Peer testing instructions NOK, move to next iteration.

Progress report OK, this document

Release note OK

Beta version of the Product Data Server OK, it is possible to demonstrate the beta version.

8

T-76.4115 T-76.4115 IterationIteration demo demo

Realization of the tasks Design, architecture and Requirements, over run – 12.5h

Design takes more time than planned ( Lack of current system documentation) Implementation, left 49h

Design takes more effort than planned, unit testing very demanding Testing, left 50.5h

Testing started later than planned Testing tasks has been changed as follows:

"integration testing execution" ->"static testing of code" "system testing execution" -> "dynamic testing"

Status Real Plan Diff (Left)ME: Meetings 103.5 77 17 -26.5ST: SEPA & engineering environments 80.5 90 10 9.5Programming and PP : database implemtation, read, write, delete, build scripts

87 136 49 49Design architecture and Requirements 42.5 30 12.5 -12.5QA: testing and reviews *) 73.5 124 50.5 50.5PM: communication, reports,working hour management

60.5 63 2.5 2.5Documents: relese note, web pages 12 9 3 -3Total 459.5 529 143 69.5

* unplanned task (= a new task added during the iteration)

9

T-76.4115 T-76.4115 IterationIteration demo demo

Working hours by person

Juho was sick few days Testing has been started later

than planned ( Kauko was allocated to testing tasks )

This report has been made on Friday. (There is 4-5 working days left.)

Real Plan Left

Ulla Suomela 66 63 -3Jari Leppä 82 97 15Raine Mäki 90 90 0Hannu Kankaanpää

94 94 0Juho Mäkinen 71 90 19Kauko Huuskonen 58 95 37Total 461 529 68

Realized hours in this iteration

10

T-76.4115 T-76.4115 IterationIteration demo demo

Working hours by person

Implemetation has delayed Testing period has been

started later than planned Testing tasks actuals are

less than planned effort 53 % of the project effort

has been used Report has been made on

Friday ( few I1 days left)

Realized hours in I1 iteration Plan in the beginning of this iterationPP I1 Σ I2 Total

Ulla 73 63 136 54 190Jari 24 97 121 69 190Raine 36 90 126 64 190Hannu 5 91 96 94 190Juho 1 93 94 96 190Kauko 2 95 97 93 190Total 140 529 670 470 1140

Latest plan (inc. realized hours and other updates)PP I1 Σ I2 Total

Ulla 73 66 139 51 190Jari 24 82 106 84 190Raine 36 90 117 73 190Hannu 5 94 99 91 190Juho 1 71 72 118 190Kauko 2 58 60 130 190Total 140 461 559 547 1140

Real Plan LeftUlla Suomela 66 63 -3Jari Leppä 82 97 17Raine Mäki 90 90 0Hannu Kankaanpää

94 91 -3

Juho Mäkinen 71 93 19,5Kauko Huuskonen

58 95 37

Total 461 529 68

11

T-76.4115 T-76.4115 IterationIteration demo demo

Quality metrics in I1 iteration

No Critical bugs founded and only one major We won’t use severity classification normal anymore in I2 Two Bug’s are still open

I1 I2 TotalReported 20 20Closed 0 0Resolved 18 18Open 2 2

Bug metrics

Blockers Critical Major Normal Minor Trivial TotalTotal open 0 0 0 0 1 1 2This iteration reported

0 0 1 5 10 4 20

12

T-76.4115 T-76.4115 IterationIteration demo demo

Quality assessment, in I1 iteration

We made a lot of static testing during week 48 Reviews for Read, Write and Delete

Database was tested with Parser.java No problems or bugs found

Unit-tests for java-classes

Functional area Coverage Quality Comments

Parser 3 Tested

Read 2 Tested only with Unit-tests and code review

Write 1 Write tested only with Unit-tests and code reviewUpdate-function not tested with Unit-tests

Delete 2 Tested only with Unit-tests and code review

Database 2

Old and new 0 Not tested

Legend

Coverage: 0 = nothing1 = we looked at it2 = we checked all functions3 = it’s tested

Quality:= quality is good= not sure= quality is bad

13

T-76.4115 T-76.4115 IterationIteration demo demo

Software size in Lines of Code (LOC) N/A in I1 iteration

PP I1 I2Java, Client-side 0 1120C (JNI/Header) 0 956/309Fortran 0 50Test classes 0 542Parser 0 508Total (NCLOC + COM) 0 3485

Comment-lines included We made small changes in old Fortran code We used Parser.java inputting testdata to database Three Java classes

Db.java Dm.java DatabaseAccess.java

14

T-76.4115 T-76.4115 IterationIteration demo demo

Changes to the project during I1 iteration Peer test planning has been moved to I2 iteration

first draft is reday, but the document isn’t yet ready Decision for postpone to I2 iteration in project meeting, change has been

communicated to mentor and customer Testing process has been changed

Integration started very soon after implementation Unit testing has been done after integartion testing System testing has been doen only slightly

15

T-76.4115 T-76.4115 IterationIteration demo demo

Risks Risk management weekly in project meetings

ASA developer edition java support problems discussed with Vendor Risk not realized

Developer was sick

New risks, which have also realized The documentation of current NAPA system was minimal (Overhead)

Sharing infromation in customer meetings and emails concentrating only the most important NAPA features

One developer was sick (delay in Impelemtation and testing tasks ) Build script (to exe) is broken (delay in Impelemtation and testing tasks )

try to find out, which library functions are missing with customer testing features through *.dll

16

T-76.4115 T-76.4115 IterationIteration demo demo

Results of the iteration Testing documentation Technical Specification, System core architecture

17

T-76.4115 T-76.4115 IterationIteration demo demo

Technical Specification

18

T-76.4115 T-76.4115 IterationIteration demo demo

Technical Specification

19

T-76.4115 T-76.4115 IterationIteration demo demo

ER-Model

20

T-76.4115 T-76.4115 IterationIteration demo demo

DEMO Demo: product Data Server beta version -READ –operation from relational database

21

T-76.4115 T-76.4115 IterationIteration demo demo

Used work practices Iterative develpment

Important to start the implemetation as soon as possible Important to have milestones during the iteration

time reporting creating working hour management system takes time difficulties to add new task to the excel system Reporting practices works well

Risk management weekly during project metings

version control works well

Requirements and change management during customer meetings important to write up decisions to meeting minutes

SEPA meeting practices

works well. Important to sum up deadlines. pair programming unit testing statical metods

We are not going to make big changes to the current practices

22

T-76.4115 T-76.4115 IterationIteration demo demo

Thank your time ! Questions Comments