1. T -76.4115 Iteration Demo BetaTeam I2 Iteration, Final Solution 2.3.2006

2. T-76.4115 Iteration demo 2 Agenda Marketing-spirited Presentation of Project Outcome (20 min) General situation System Core Architecture Solution and its Benefits Relationdatabase vs. flat- file technology BetaTeam Demo: Product Database Server Project Evaluation (20 min) Project Effort Project Progress Goals Metrics Practices Educational value Closing and discussion (5 min)

3. T-76.4115 Iteration demo 3 General Information Customer: NAPA Ltd ( computing-based systems for ship safety and performance ) Motivation: To implement and integrate a Product Database Server solution to the current NAPA product, aiming to find out the relation database effectivity compared to the current shared file system. Customer Goals: To implement, test and deliver a product database server, which would in the first phase work together with the 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.

4. T-76.4115 Iteration demo 4 Technical Specification – System architecture

5. T-76.4115 Iteration demo 5 Technical Specification – Read operation

6. T-76.4115 Iteration demo 6 Solution and its benefits Product Database Server concept Architecture provides configuration to multiusers environment Architecure offers users an open solution for future performance level (new compiling tool- kits, new server, new platforms)

7. T-76.4115 Iteration demo 7 Advantages of relationaldatabase technology vs. flat-file(1/2) reduced network traffic handling concurrent users handling concurrent data manipulation reliable architecture automatic datacorruption recovery

8. T-76.4115 Iteration demo 8 Advantages of relationaldatabase technology vs. flat-file(2/2) high data integrity scalable technology standard technology possible to use 3.rd party appliances performance especially multiuser environments backup features

9. T-76.4115 Iteration demo 9 Demo script Product Database Server: Connecting to the database from the UI using DB.OPEN command. Querying descriptions from the database using CAT command. Setting partial match conditions for query using SEL command. Reading records from description with GET and NEXT commands. Using explorer to view contents of the database.

10. T-76.4115 Iteration demo 10 Project Evaluation Project Effort Project Progress Goals Metrics Practices Educational value Closing and discussion

11. T-76.4115 Iteration demo 11 Working hours by person RealPlanDiff Ulla Suomela 190 0 Jari Leppä 163190-27 Raine Mäki 202190+12 Hannu Kankaanpää 194190+4 Juho Mäkinen 173190-17 Kauko Huuskonen 158190-32 Total 10801140-60 Realized hours in whole project 95% from planned Effort

12. T-76.4115 Iteration demo 12

13. T-76.4115 Iteration demo 13 Comparing to previous years projects

14. T-76.4115 Iteration demo 14 Project progress PP Iteration, Highlights Organizing the project Starting the Infra Studing the subject Starting the quality work reviwing the documents very rapid iteration Important to share the working tasks

15. T-76.4115 Iteration demo 15 Project Progress, I1 iteration, Highligts Spliting the iteration to testing milestone Starting the work asap Architecture work important to review by customer  Flexible architecture  optional features  possible to modificate implementation to features from ”must” category Testing the implementation by original data asap Effective meeting practices Testing process has been changed Integration started very soon after implementation Unit testing has been done after integration testing System testing has been done only slightly Problem of building exe

16. T-76.4115 Iteration demo 16 Project Progress I2 Iteration Change management : Picking up the most important requirements with customer Rest of the ”must” category features Solving the exe building problem Choosing relationdatabase from NAPA UI System testing started after solving the exe building problem Finalizing the implementation performance testing arrangements demanding

17. T-76.4115 Iteration demo 17 Project Goals Customer Goals 98 % achievment from PP phase Customer Goals 9 Goals achieved( implemented and tested) 1 Goal implemented ( not possible to test, not a unix environment available for testing purposes) Project Team Goals Achieved grading goals not yet evaluated Personal learning Goals Almost all the goals achieved Iteration Goals ( Documentation) Achieved

18. T-76.4115 Iteration demo 18 Quality metrics N/A in PP iteration Description of blocker and critical bugs found and open other QA metrics  unit test coverage  code reviews  source code metrics ... I1I2Total Reported Closed Open … or make a more detailed table/graph, where you show per module bugs, and/or classifications per criticality, origin (own system testing, code reviews, customer, peer group) etc. Bug metrics BlockersCriticalMajorMinorTrivialTotal Total open This iteration reported

19. T-76.4115 Iteration demo 19 Legend Coverage: 0 = nothing 1 = we looked at it 2 = we checked all functions 3 = it’s tested Quality:  = quality is good  = not sure  = quality is bad Quality assessment 27.2.2006 Functional areaCoverage QualityComments Read3Tested Write, Update3Tested Delete3Tested Database and ER3Tested Database operations3Tested Performance2Tested locally Query3Tested Testing is automated in Unit-level, System-level test-suites Database: We reported two little difference between db and ER Partial update and who has made last update tested connection tests are fully covered There are some test-cases for multi-connections Performance needs to be test with multiple database-connections and over noisy network Query: Is tested Exe-compiling: tested

20. T-76.4115 Iteration demo 20 Software size in Lines of Code (LOC) N/A in PP iteration Any remarks on this metric? lots of new functinality was implemented refactoring reduced LOC PPI1I2 Total (NCLOC + COM) 010004000 Comments (COM) 0100200 PPI1I2 Part A Total /com 0500 /90 3000 /100 Part B 500 /10 1000 /100 Part C Part D Part E Total (NCLOC + COM) 010004000 Comments (COM) 0100200 … or make a more detailed table, where you can show per module LOCs, or proportion of real code vs. test code

21. T-76.4115 Iteration demo 21 Risks Risk management weekly in project meetings regualy weekly reporting to customer and mentor New risks, which have also realized The documentation of current NAPA system isn’t sufficient (Overhead)  Sharing infromation in customer meetings  concentrating only the most important NAPA features project member has been sick (delay in Impelemtation and testing tasks ) Build script is broken (delay in Impelemtation and testing tasks )  try to find out, which library functions are missing with customer  testing features through *.dll Problems in working effort estimation  Requirements focusing was a demanding task Other courses and daily work priorization

22. T-76.4115 Iteration demo 22 Used work practices Iterative planning  A good way to work with changing requirements Iterative development  Important to start the implementation as soon as possible  Important to have milestones during the iteration  Important to test with original data asap Time reporting  Creating the working hour management system takes time ( no template from course )  Difficulties to add new tasks to the Excel files  Reporting practices work well Risk management  Weekly, during the project meetings minimizing the risks Version control Requirements and change management  During customer meetings  Important to write up decisions to the meeting minutes SEPA  Meeting practices Works well. Important to sum up deadlines  Pair programming good practice during demanding, many interfaces including programming phases  Unit testing  Statical methods

23. T-76.4115 Iteration demo 23 Educational value Working in real project with real Development work to real customer balance between different stakeholders : mentor, customer, course Importance of maintenace in Software Development ( Sofware life- time) it is expencive to re-write code Risks to change a major part of implementation Difficulties to take new technologies 4 different programming languages: Fortran, JNI interfaces, etc.. Not a classical testing processes unit testing, integration testing, system testing All the product development parts involve: from requirements to delivery and handover Team work - Learning by doing together New intresting Business area - a fine experience

24. T-76.4115 Iteration demo 24 Thanks to all Questions & Discussion