1 / 22

T-76.4115 Iteration Demo

T-76.4115 Iteration Demo. BaseByters [I1] Iteration 04.12.2005. Project status (15 min) achieving the goals of the iteration project metrics Work results (15 min) presenting the iteration’s results demo Used work practices (5 min) Discussion (5 min). Agenda.

neron
Download Presentation

T-76.4115 Iteration Demo

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. T-76.4115 Iteration Demo BaseByters [I1] Iteration04.12.2005

  2. Project status (15min) achieving the goals of the iteration project metrics Work results (15 min) presenting the iteration’s results demo Used work practices (5 min) Discussion (5 min) Agenda

  3. Introduction to the project • Customer: Nokia Networks / Service Business Unit • Customer representatives: • Jari Jyrävä – business issues • Antti Ahonen – technical issues • Project team: • Management team: Jukka Kurkinen (PM), Tapio Janasik (QaM), Sami Saariaho (LD) • Development team: Janne Ruskeeniemi, Semi Arajuuri, Sun Jian, Pu Fan • Project’s purpose • To produce a database upgrade tool which enables automatic database upgrades from unknown database structure.

  4. Stakeholders and staffing Customer Mentor Markus Rautopuro Antti Ahonen (technical) Jari Jyrävä (business) Mgmt Team Tapio Janasik QA Sami Saariaho LD Jukka Kurkinen PM • Pu Fan Dev • Java, XML, testing • Janne Ruskeeniemi Dev • RE, DataBase, Java • Semi Arajuuri Dev • DataBase, SQL • Sun Jian Dev • Java, testing

  5. Status of the iteration’s goals • Goal 1: Design core architecture • OK • Goal 2: Implement selected use cases (UC2 and UC4) • OK • Goal 3: Deliver the first limited version of the system for trialing • OK

  6. Status of the iteration’s deliverables • Project plan • OK • QA plan • OK • Requirements document • OK • Technical specification • OK • Test cases, test report and test log • OK • SEPA diaries • OK • Progress report • OK

  7. Realization of the tasks

  8. Working hours by person Realized hours in this iteration • Major discrepancies in realizations: • Effort estimation inaccuracies

  9. Working hours by person Realized hours in I1 iteration Plan in the beginning of this iteration Latest plan (inc. realized hours and other updates)

  10. Quality metrics I Bug metrics

  11. Quality metrics II Other QA metrics • unit test coverage: 41% (Coverlipse) • calculated using integration test suite • Not all trivial exceptions covered • help methods (for testing for examle) not covered • Data Access Service not included since there is a problem with Coverlipse and reading db over network • UI not JUnit tested (tested during system tests)  not included in coverage report • code reviews • Static analysis: https://baseb.nbl.fi/staticanalysis/ • Some refactoring needed ( I2) • source code metrics • See page 12 Blocking bugs found: • Bug11: NullPointerException from XmlGenerator (null objects) • Bug17: NumberFormatException from XmlParser (“null” input string)

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

  13. Software size in Lines of Code (LOC)

  14. Changes to the project • No major changes during the I1.

  15. Risks • Risk status:

  16. Results of the iteration • Technical specification • PL/SQL script • User interface • UC2 and UC4

  17. System overview The system consists of the following high level features: • It handles upgrade from unknown database structure to given target structure. • It supports both Oracle and MySQL. • It has a graphical user interface, a command line interface and it can be used from another Java application. • It has a PL/SQL based upgrade solution for Oracle databases. • It can create an XML description file of existing database. This file can be then used to specify the target structure for upgrade. Use case diagram:

  18. Technical specification – components and services Components and services of the system:

  19. Technical specification – core architecture Core architecture of the system:

  20. User interface and UC 2 and UC4 • Demo…

  21. Used work practices • Time reporting • Time reporting done according to iteration task list (little variation to task list) • Iterative development • Tasks identified and planned at the beginning of the iteration • Implementation status reviewed in the middle of the iteration • Not possible tasks transferred to I2 • Risk management • Risks identified in the risk workshop and documented • Risk status gone trough in project team meetings • Communication • Face2face communication in meetings • Emails • IRC discussions • Phone calls and conference calls • Wiki used for meeting memo delivery and discussions • Subversion used for document store and delivery • Effort estimation • Effort estimation done by LD and developers • Work practices to be changed in I2: • Time reporting could be still made more accurate to match exactly task list • Effort estimation could be made more accurate

  22. Questions, comments?

More Related