T76.4115 Iteration Demo

1
T-76.4115 Iteration Demo

• Group name
• I2 Iteration12.12.2006

2
Agenda

• Project status (15 min)
• achieving the goals of the iteration
• project metrics
• Work results (20 min)
• presenting the iterations results
• demo
• Used work practices (5 min)

3
Status of the iterations goals

• Goal 1 Documenting selected use cases
• OK
• Goal 2 Performing QA practices described in QA
  plan.
• OK
• Goal 3 Prototyping
• OK (both paper and programmed)
• Goal 4 Designing
• OK
• Goal 5 Producing working pieces of software
• UC3.1 Search Hotels OK
• Secondary goal (UC3.2 Display hotel info and
  UC3.3 Display rooms available) Not done, not
  enough time
• Goal 6 SEPA tasks
• Heuristic evaluation OK
• Code review OK

4
Status of the iterations deliverables

• Project plan
• OK
• Requirements document
• OK
• Use case 3.1 implemented and tested
• OK
• Source code and software
• ZIP sent to customer with password - OK
• Technical specification
• Same ZIP, General architecture as picture - OK
• QA plan, report and log
• OK
• Progress report
• OK
• Risk log
• OK
• SEPA diaries
• OK

5
Realization of the tasks

6
Realization of the tasks

7

8
Resource usage
Plan after Project planning
Realization and updated plan
(realized hours and updates)

• Amount of work wasnt much larger than planned
  but because of less people, we have less time for
  iteration 2.
• Goal during iteration 1 was developing working
  piece of software without saving hours tactically
  to iteration 2.

9
Defects and other quality metrics

• The two major bugs still open are
• Search screen does not check for old inputted
  dates will be fixed asap
• Information not preserved when pressing
  back-button
• Other QA metrics
• Time to make reservation Probably long
• User perception of system Medium/Low, due to
  slow connection
• Maintainability High, all code documented

10
Quality dashboard

• Quality of the parts of the system
• More effort has been put on precautionary (such
  as reviews and evaluatiuons) QA practices than on
  reactionary (such as testing)
• Coverage is good, except for hotel search
  responses, there only a couple of inputs were
  tested

Legend ConfidenceLow-Medium-High Quality ?
quality is good ? quality seems ok ? quality
is bad
11
Quality goals

• Robustness
• High
• We have a couple of open bugs, but they will be
  resolved asap. It should be no big problem
• Security
• Status unknown
• We have done no security testing since no
  sensitive functionality was implemented in I1
• Usability
• Medium
• A lot of effort has been put into this
• Heuristic evaluation Many violations found,
  most resolved
• User interviews
• Satisfied with functionality
• Slowness of system and input functions
  frustrating
• Not much to do about this
• Maintainability
• High
• All code properly documented

12
Software size in Lines of Code (LOC)
13
Changes to the project

• One group member left course
• No possibility to prevent (too many courses)
• No significant information lost
• Less time for whole project / more effectively
  used time
• System test with developer box
• Computer software box tv
• Example software tested

14
Risks

• What is the current situation regarding the
  risks?
• materialized risks?
• new risks identified?

REST OF THE SLIDES WILL BE UPDATED BEFORE DEMO
15
Results of the iteration

• Briefly describe the most important content of
  the major deliverables of the iteration, e.g.,
  the following
• system architecture (especially in I1 review)
• QA plan (especially in I1 review)
• implemented use cases (I1-I2)
• users manual (I2)
• Demonstrate the developed software
• first tell briefly to the audience what you are
  going to demonstrate
• distributing a demo script to the audience helps
  following the demo
• concentrate on new functionality

16
Example Project plan

• Present the following
• Stakeholders and staffing (a diagram?)
• Project goals (discuss most important goals and
  verification criteria)
• Project resources (already shown in the project
  status?)
• Project practices and tools (discuss most
  important practices and tools you have chosen,
  what, why, when, )
• Discuss phasing if there are some major plans
  already

17
Example Demo script

• System Administrator
• function X
• function Y
• Basic user
• function Z1
• function Z2

18
Used work practices

• How have you been using the planned work
  practices, what are the experiences of
• mandatory practices time reporting, version
  control,
• any other practices
• Are you going to
• adopt some new practices
• change the use of the current practices
• stop using some adopted practices

19
Performed QA practices

• Test-case based testing
• Static review
• Coding conventions
• Prototyping
• Heuristic evaluation
• User interviews
• Pair programming
• Unsystematic unit testing by developers, e.g.
  JUnit used