t-76.4115 iteration demo team wisegui i2 iteration 5.3.2008
TRANSCRIPT
T-76.4115 Iteration Demo
Team WiseGUII2 Iteration
5.3.2008
2
T-76.4115 Iteration demoT-76.4115 Iteration demo
Agenda
Work results (25 min) demo presenting the iteration’s results
Project status (5 min) achieving the goals of the project project metrics
Used work practices (5 min) Quality (5 min)
3
T-76.4115 Iteration demoT-76.4115 Iteration demo
Demo
4
Introduction to the project
Customer: Houston Inc. Project: Loan Shark
Design and develop a Java EE online demo credit application system for unsecured customer loans
No human interaction from the banks side -> everything automated
Main deliverable: Demo for marketing purposes
Built using Java EE technologies Java Enterprise Edition 5 with EJB3 and JPA using JBoss Application Server 4.0 and JBoss
Hibernate Java Server Faces and Facelets using JBoss Seam 1.2
T-76.4115 Iteration demoT-76.4115 Iteration demo
5
Paper prototype
5
T-76.4115 Iteration demoT-76.4115 Iteration demo
6
Back end
Independent of the user interface About 15 methods in the interface between back end and front end Central element is the management of the business process
Business process is started when the user fills an application When the user comes back later the same process instance should be continued Changing the process should not require changes to the core code
Process has evolved during the course
6
T-76.4115 Iteration demoT-76.4115 Iteration demo
7
Javascript prototype
The customer wanted something to show up as fast as possible We developed a html prototype with Javascript tying the pages together Required a lot of effort As a result we did not have anything built upon the back end at the end of I1
Thus nothing that could be tested with test case based testing or exploratory testing Branded versions a further digression
7
T-76.4115 Iteration demoT-76.4115 Iteration demo
8
The real thing
Entire team working on the same thing Many new technologies for everyone
Combining the back end with the JS prototype Still a lot of new issues, mainly with input validation and navigation
T-76.4115 Iteration demoT-76.4115 Iteration demo
9
The real thing, without major bugs
Time to tie up loose ends Find and fix bugs Finalizing
Motivation boosters
T-76.4115 Iteration demoT-76.4115 Iteration demo
10
T-76.4115 Iteration demoT-76.4115 Iteration demo
Software size Non Commenting Source
Statements (NCSS) Roughly equivalent to LOC Other files calculated with wc -l
XML files hard to calculate as most stuff came with the stub
Branded JS prototypes missing Hard to calulate as much of the
code is identical to the original protype
I2 has mainly been about the GUI
Business Logic and the Process management sligthly trimmed
1483-CSS
396-Javascript
1354~200Facelet files (.xhtml)
~250~20XML
I2I1Other files (rows)
1283954Total
3233
3249
335565121181I2Code (NCSS) I1
Business Logic 254DAO:s 89Entities 444GUI 81GUI-BL interface 49Process 37
Total ~220Javascript prototype I1HTML files 1215CSS files 739JavaScript files 548Total 2502
11
T-76.4115 Iteration demoT-76.4115 Iteration demo
Status of the project’s goals
12
T-76.4115 Iteration demoT-76.4115 Iteration demo
Results of the project
Loan application for marketing purposes built using the JBoss application stack
Code base is transferred to Houston for further development Documentation consists of on-screen help, architecture document and code
comments
HTML+CSS+JS prototypes for demo purposes 1 official 2 personalized versions
A load of documents and materials used during the project Project plan, risk management document, QA plan, requirements document,
architecture document etc. Test logs, test cases, test charters, usability test reports etc. 3 paper prototypes, of which one was chosen to be developed
13
T-76.4115 Iteration demoT-76.4115 Iteration demo
Status of the iteration’s goals
I1G1 Working GUI prototype for demo purposes [OK]
I1G2 Framework with interfaces for the GUI [OK]
I1G3 Get our working practices running smoothly [OK]
I1G4 Have knowledge of Seam needed in the next iteration [OK]
I1G5 Deliver all deliverables [pending]
14
T-76.4115 Iteration demoT-76.4115 Iteration demo
Status of the iteration’s deliverables
6.4.2.1. Sprint 3 Working increment of the software, including integrated GUI and backend [OK]
6.4.2.2. Sprint 4 Enhanced increment of the software, including bugfixes, usability
enhancements and other minor improvements [OK] Updated project plan Updated architecture description (will work as technical documentation as
agreed upon with Houston) QA report Test session charters (for own group and peer group) Test cases Test log Summary of peer testing Final report Demo presentation slides [OK] Peer testing guidelines [OK] Updated SEPA diarys
15
T-76.4115 Iteration demoT-76.4115 Iteration demo
Effort used per person
Budgeted hours
PÖ MB LÅ MH WW MV IV PS MA SUMPP 81,5 63 67 33 29 30 35,5 28 25,5 392,5I1 44,25 64,5 70,25 69,75 81,5 71 41 39,5 53 534,75I2 38,5 48 23,5 63,5 36,75 74,5 67,75 78,25 71,5 502,25Total 164,2
5175,5 160,7
5166,2
5147,2
5175,5 144,25 145,75 150 1429,5
PÖ MB LÅ MH WW MV IV PS MA SUMPP 75 60 60 35 30 30 35 30 30 385I1 50 55 55 70 60 70 55 60 60 535I2 50 60 60 70 60 75 60 60 60 555Total 175 175 175 175 150 175 150 150 150 1475
Actual used hours
16
Communication
17
T-76.4115 Iteration demoT-76.4115 Iteration demo
Used work practices
Used practices Development in the same place at the same time [excellent] Pair programming [excellent] Technology training [good] Weekly scrums [good] Weekly reporting with progress and risks [good] Retrospectives for process improvement [good] Riskit-method risk management [good] Motivation boosters [not good, not bad, mostly funny] TDD [tried, cancelled]
Changes TDD was not enforced, but unit tests were required before commit Tasks have been presented in more usable ways for each iteration and
developers have had a chance to change unsuitable granularity
18
T-76.4115 Iteration demoT-76.4115 Iteration demo
Risks
No NEW major risks have materialized during I2 Used Jyrki Kontio’s Riskit method to develop our risk management.
Including identification, analysis, control, monitoring and more (see http://users.tkk.fi/~wawilson/houston/Deliverables/documents/bin/view/Main/RiskManagementPlan.html for details)
Risks are separated in the risk management document
19
T-76.4115 Iteration demoT-76.4115 Iteration demo
Changes to the project
Project was divided into simultaneous subprojects There was a need to get a prototype out fast
Additional html prototypes needed
TDD was skipped as too demanding for our use
20
T-76.4115 Iteration demoT-76.4115 Iteration demo
Quality dashboard
21
T-76.4115 Iteration demoT-76.4115 Iteration demo
Quality practices and goals
22
T-76.4115 Iteration demoT-76.4115 Iteration demo
Quality goals