T-76.4115 Iteration Demo Team 13 I1 Iteration 11.12.2007.
Post on 13-Dec-2015
227 Views
Preview:
Transcript
T-76.4115 Iteration demoT-76.4115 Iteration demo
2
Agenda
Project status (15 min) achieving the goals of the iteration project metrics
Work results (20 min) presenting the iteration’s results demo
Used work practices (5 min)
T-76.4115 Iteration demoT-76.4115 Iteration demo
3
Introduction to the project
What is this project about? Web portal to Simulation system Simantics Bringing the power of simulations to the general public Creating a community for simulation users and
model/solver developers Creating a marketing channel for solver developers
T-76.4115 Iteration demoT-76.4115 Iteration demo
4
Status of the iteration’s goals
Goal 1: Simantics player & editor integration Simupedia OK?
Goal 2: Basic functions of the Simupedia implemented OK
Goal 3: Simupedia is running on the www.simupedia.fi-server OK
T-76.4115 Iteration demoT-76.4115 Iteration demo
5
Status of the iteration’s deliverables (1/3)
Public site Main page with menu
Ok Search function
Ok Solver information page
Ok User registration page
Ok Login module
Ok
T-76.4115 Iteration demoT-76.4115 Iteration demo
6
Status of the iteration’s deliverables (2/3)
Registered site Model/solver/experiment comment module
Ok Support for model and experiment publish
Ok User profile management/unregistration –page
Ok User support page (help/faq/privacy statement)
Ok Administration
Possibility to administrate all functionalities aboveOk
T-76.4115 Iteration demoT-76.4115 Iteration demo
7
Status of the iteration’s deliverables (3/3)
Documentation updated project plan
Ok updated requirements document
Ok quality assurance report
test casesOk
test logOk
progress reportOk
T-76.4115 Iteration demoT-76.4115 Iteration demo
8
Realization of the tasks
The developers didn’t have time to work as much as they needed to Hours will be fixed before the next iteration starts
Implementation 1
Planned Realized Left
Project management 100 19 81
Design 30 0 30
Quality assurance 60 2 58
Project infrastructure 10 15,5 -5,5
Programming 294,5 194,8 99,75
Documenting 40 43 -3
Studying 30 11,5 18,5
Total 564,5 285,8 278,8
T-76.4115 Iteration demoT-76.4115 Iteration demo
9
Resource usage
Original plan (in the beginning of the iteration)
Realization and updated plan
(realized hours and updates)
Planned
Joni JP Nina Ville Antti Juha Oleg Ferran
Total 150 150 150 150 150 150 150 150
PP 49 38 26 2 10 2 10 4
I1 51 63 74 78 75 78 70 76
I2 50 50 50 70 65 70 70 70
Joni JP Nina Ville Antti Juha Oleg Ferran
Total 150 150 150 150 150 150 150 150
PP 49 38 26 2 10 2 10 4
I1 45 58 47 43 37 31 47 26
I2 56 55 77 105 103 117 93 120
T-76.4115 Iteration demoT-76.4115 Iteration demo
13
Defects and other quality metrics
Description of blocker and critical bugs found and open
Other QA metrics performance analysis metrics usability test results source code metrics ...
Use this template 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.
Blockers Critical Major Minor Trivial TotalReported in Ix 0 1 10 15 19 45Reported total 2 2 20 25 25 74Open 1 2 5 10 17 27
T-76.4115 Iteration demoT-76.4115 Iteration demo
14
Quality dashboard
Evaluate the quality of the parts of the system how much effort has been put on QA practices what is the coverage of testing what can you say about the quality of a particular part
based on your test results and ’gut feeling’ during testing is the number of reported bugs low because of lack of
testing or high because of intensive testing
Part of the system Quality Confidence Comments
File conversions 2Only few minor defects found, very efficient implementation.
GUI editor 0 Not started
Encoder 32 critical bugs found during last test round, lots of small problems
Admin tools 1 Nothing serious yet
LegendConfidence:(use your own scale)
Quality:(use your own scale e.g.:3 = quality is good2 = not sure1 = quality is bad
T-76.4115 Iteration demoT-76.4115 Iteration demo
15
Quality goals
Evaluation of the status of the project's quality goals
T-76.4115 Iteration demoT-76.4115 Iteration demo
16
Software size in Lines of Code (LOC) (or some better metric)
Any remarks on this metric? lots of new functinality was implemented refactoring reduced LOC
PP I1 I2Total (NCLOC + COM) 0 1000 4000Comments (COM) 0 100 200
T-76.4115 Iteration demoT-76.4115 Iteration demo
Changes to the project
One team member has left the team at the beginning of this iteration
17
T-76.4115 Iteration demoT-76.4115 Iteration demo
18
Risks
ID Risk Probability Severity
1 One of the team members leaves the group.
2 3
2 Server crash& Data loss 1 3
3 Simantics-system is not ready to be used during this project.
3 3
4 Team member may not have enough skills to accomplish his tasks
2 2
5 Communication is insufficient 3 3
6 Sprints are too short 2 2
T-76.4115 Iteration demoT-76.4115 Iteration demo
Risks
One risk materialized: Roch got an internship in Paris and left the team Fortunately it happened at the begin of this iteration
19
T-76.4115 Iteration demoT-76.4115 Iteration demo
20
Results of the iteration
www.simupedia.fi Updated documents
Project Plan Requirements Document Qa-report (new)
T-76.4115 Iteration demoT-76.4115 Iteration demo
www.simupedia.fi - infrastructure
21
Internet
Simupedia server
Apache – Web server
Jboss Application Server
T-76.4115 Iteration demoT-76.4115 Iteration demo
Simupedia-application architecture
22
Simupedia uses Java Struts 2 framework which is based on Model-View-Controller 2 (MVC 2) Architecture
In Struts 2 every web page has an own action class, which can be easily tested with JUnit. After action is executed, the actual visualization is done in .jsp pages.
Picture from: http://www.ibm.com/developerworks/webservices/library/ws-arcstruts/
Struts 2 provides also a large amount of functionalities to help web development.
For database access we are using Hibernate and the actual database is MySQL.
T-76.4115 Iteration demoT-76.4115 Iteration demo
Working Methods
In addition of mandatory practices of this course Practices
Scrum-like iterative methods Weekly time reporting in our time tracking system
24
T-76.4115 Iteration demoT-76.4115 Iteration demo
25
Used work practices
IRC as a non-formal discussion channel works well Wiki has proven itself a useful tool as a information
channel But it needs effort to keep it readable
Coding sessions every week Voluntary but still very useful
Three sprints in iteration didn’t work Exam week took too much time from the first sprint There were too few hours made in the second sprint
-> Next iteration will be divided in two sprints
top related