Download 0 - SoberIT

T-76.4115 Iteration Demo
BetaTeam
PP Iteration
13.10.2005
T-76.4115 Iteration demo
Agenda

Project status (15 min)



Work results (20 min)



achieving the goals of the iteration
project metrics
presenting the iteration’s results
 project plan
 requirements
demo
 architectural structure
Used work practices ( 10 min)
2
T-76.4115 Iteration demo
Introduction to the project
Motivation: This is a use-case driven,
architecture centric and iterative
release project to NAPA Ltd.
Customer: NAPA Ltd ( computing-based
systems for ship safety and
performance )
Customer Coals: To implement, test and
delivery a product database server,
which work in the first phase together
with 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.
Project members goals: Geting the
product database server work done
with good quality, learning new
practices and tools as a team with
good team spirit.
3
T-76.4115 Iteration demo
Status of the iteration’s goals

Goal 1: Specify the goals of the project from all perspectives


Goal 2:Familiarize with the topic


OK
Goal 7: Defining the methods and tools and working environment


OK
Goal 6: Identifing risks


OK
Goal 5: Architecture at rought level


OK
Goal 4:Requirement Specification in general level including most
important requirements and use cases


OK, but customer current system familiarizing needs more effor from project
group
Goal 3:Familiarize with different stakeholder


OK
OK, defining has been doen at rough level, but practices need focusing
Goal 8, Focusing building and version control practices

OK, version control parctice has been described in separate instruction, but the
building process needs focusing
4
T-76.4115 Iteration demo
Status of the iteration’s deliverables

Project plan


Requirements document


OK, all important requirements documented in general level
Progess report


OK, building parctices and some roles needs refining
OK
Architecture (draft)

OK, part of requirement specification
5
T-76.4115 Iteration demo
Realization of the tasks
Status
Real
Plan
Diff
(Left)
Meetings & agenda
ok
37,75
39
-1,25
12
Lectures
ok
17,5
35
-17.5
12
CVS & WEB pages work
moving I1
0
5
-5
5
Tools & Infra & customer laptop evaluation
moving I1
0
20
-20
20
6
35
-29
32
37
-5
8
17
-9
Meetings and Lectures (PP iteration)
Requirements Specification (PP iteration)
finnishd
Architecture draft,
Requirements elicitation, priorisation, validation
and analysis, req Spe document
Project management (PP iteration)
finished
Project plan, progress report, working hour
management
Qality (PP iteration)
under work
Reviews, defining practices and tools
3
* unplanned task (= a new task added during the iteration)
6
T-76.4115 Iteration demo
Working hours by person
Realized hours in PP iteration
Ulla
Suomela
Jari Leppä
Raine Mäki
M4
M5
M6
M7
Total




Real Plan
62
91
Diff
-29
28
56
20
56
0
0
0
0
0
0
0
0
110 203
-27
-36
0
0
0
0
93
The customer laptop evaluation
couldn’t start as planned
Requirements work
overestimated
SEPA work starting has been
postponed
Unclear working hours
reporting period in the planning
phase
Plan in the beginning of this iteration
Ulla
Jari
Rane
M4
M5
M6
Total
PP
91
56
56
0
0
0
203
I1
90 30
56 50
56 50
0
70
0
70
0
70
203 340
Σ
I2 Total
30
150
44
150
44
150
80
150
80
150
80
150
358 900
Latest plan (inc. realized hours and other updates)
Ulla
Jari
Rane
Hannu
Juho
Kauko
Total
Σ
PP I1
62 48 110
28 72 100
20 60 80
0
70 70
0
70 70
0
70 70
110 390 500
I2
40
50
70
80
80
80
400
Total
150
150
150
150
150
150
900
7
T-76.4115 Iteration demo
Risks

What is the current situation regarding the risks?

The progress of the iterations are too rapid
Effort: There might be too little time to implement a critical and specific part
of the project deliverables.
Contolling actions:Everyone has a named backup person. Communication his
/hers schedule problems and sharing the work early enough.Sharing the
workload realistic and even.
8
T-76.4115 Iteration demo
Results of the iteration

Briefly describe the most important content of the major deliverables of
the iteration, e.g., the following



project plan
requirements
system architecture
9
T-76.4115 Iteration demo
Project plan
TKK Course
T-76.4115/5115

Stakeholders and staffing
Mentor: Mika Mäntylä
Project
Customer: NAPA ltd,
Ville Ylöstalo
Project
Project Manager, Ulla Suomela
Lead Developer,
Jari Leppä
Quality Manager, Raine Mäki
Development Team,
Testing Team,
Hannu Kankaanpää
Kauko Huuskonen
Juho Mäkinen
Hannu Kankaanpää
Kauko Huuskonen
Juho Mäkinen
10
T-76.4115 Iteration demo
Project customer goals
Goal
Verification criteria
Weight
3-1
Customer has been review the
3
1. Database ER model is ready.
ER model.
2. The database according to
2
Database exists.
ER model has been
implemented.
3. It is possible to test the
Testing of the database has
2
database.
been started.
4. Replacement of current
2
shared file style data
It is possible to test the
database by original data.
manipulation by database
server.
It is possible to test the
2
5. Architecture is ready and will
configuration of database for
support different end users.
different users.
It is possible to use the new
2
6. Interface to the old system
database with Interface
function (read) works.
function “read” that are
described in Req Spec /1/
It is possible to use the new
2
7. Interface to the old system
database with Interface
function (write) works.
function “write” that are
described in Req Spec /1/
It is possible to use the new
2
8. Update the database
database with Interface
Information.
function “write” that are
described in Req Spec /1/
It is possible to use the new
2
9. Interface to the old system
database with Interface
function (delete) works.
function “delete” that are
described in Req Spec /1/
10. The software is possible to
It is easy to install a new
run in one laptop (
relase to Win or Solaris
1
Win&Solaris)
computer
11
T-76.4115 Iteration demo
Project members goals
Goal
1. Pass the course
Verification criteria
The project team grade of the course is at least 1
2. The requirements from course
personnel fulfill and the deliverables of The project team grade of the course is at least 4
the project are at good quality level.
3. Customer is satisfied of the project
and its deliverables
Customer gives feedback according to iteration
demo.
4. Good Team Sprit
Everyone in the project is willing to help each
other and doing his/hers own duties in time.
5. All the important information
reaches all project members.
There is in project meetings a standard subject:
“Important information for next two weeks”.
6. Communication to customer, mentor Find out the mentor and customer needs. Plan
and course.
and implement the needed communication.
7. Studying and using new software
tools.
Taking Borland Together into use.
8. Clear working practices for coding,
building and testing.
Refining the working practices in the beginning
of iterations.
9. Workload inside the project is shared
Following the workload of the project regularly.
equally
10. Own study goals fulfills.
SEPA work succeeds.
12
T-76.4115 Iteration demo
Project practices and tools

Focusing the testing and building practises during next iteration
Tools
For implementation:
Borland, Together 2006
Eclipse 3.1, Java
Sybase SQL Adaptive Server Anywhere 9 (ASA)
CVS version control system
For reports and documents:
MS Office / Open Office Word, power point, Excel

13
T-76.4115 Iteration demo
Iteration phasing
IMPLEMENTATION 1 (21.10.- 8.12.2005) 6 weeks
1. Increment planning phase 21.10 -31.10 ( e-mail review)
2. Increment implementation & unit testing phase 1.11 - 21.11
3. Increment itegration and system testing phase 22.11 - 8.12
(iteration demo)
14
T-76.4115 Iteration demo
Requirements Specification, Functional requirements
ID Ver
Feature
Requirement
Source Rationale Priority Status
Looking for
Method
object of given Product
in Java
Manager
name and
class.
N.N.
returns its
Select
content.
F1 1
Reading data
object
F4 1
Checking, if
Find out, if
there exist a
particular data
specific data
object exists
object
F3 1
Writing data
object
Must
Proposed
Method
in Java
class.
Select
Must
Proposed
Method
in Java
class.
Insert
Must
Proposed
F2 1
Looking for
Method
object of given Product
Updating data
in Java
Manager
name and
object
class.
N.N.
writing its
Update
content over
Must
Proposed
F5 1
Find out, if
there exist
Deleting
particular data
particular data object and if
object
exists purge
specific data
object
Method
in Java
class.
Delete
Must
Proposed
F6 1
Query
generating for
specific data
objects by user
options
Generate query
to select
specific data
objects
Method
in Java
class.
Select
2.
Proposed
Iteration
F7 1
Generate query
Query to
to select
partially match
specific data
object content
objects
Method
in Java
class.
Select
2.
Proposed
Iteration
F8 1
Locking
specific
database object
Method
2.
in Java
Proposed
Iteration
class in
RDBMS
F9 1
User rights
handling to
Insert a new
data object
Traces
to use
cases
2.
Proposed
Iteration
15
T-76.4115 Iteration demo
Requirement Specification, Non-Functional
requirements
ID
Ver
Requirement
1
Current shared
file version and
new RDB –
system version
will both keep
supported for
long time to the
future
N2
Source
Rationale
Priority
Status
Product
Manager
N.N.
Application and its
data management
interface must
support both
implementations.
This have to keep in
mind in design.
Must
Proposed
1
Applications data
manipulation
manners will stay
such as they are
now
Product
Manager
N.N.
This have to keep in
mind in design
Must
Proposed
N3
1
Data objects are
combined into
BLOB datatypes
Product
Manager
N.N.
This have to keep in
mind in design
Must
Proposed
N4
1
Robust
architecture
Product
Manager
N.N.
This have to keep in
mind in design
Must
Proposed
N5
1
Reliability
Product
Manager
N.N.
This have to keep in
mind in design and in Must
implementation
Proposed
N6
1
Faster than
current system
Product
Manager
N.N.
This have to keep in
mind in design and in Must
implementation
Proposed
N7
1
Multiuser
support, data
locking
Product
Manager
N.N.
Is RDBMS feature
Must
Proposed
N8
1
Have to support
many platforms
Product
Manager
N.N.
RDBMS
Must
Proposed
N9
1
Have to operate
in local
workstation
Product
Manager
N.N.
This have to keep in
mind in design
Must
Proposed
N10 1
Data
manipulation
have to can
handle every
possible type of
data
Product
Manager
N.N.
This have to keep in
mind in design and in
implementation. This Must
is RDBMS feature
also.
Proposed
N1
Traces
to use
cases
16
T-76.4115 Iteration demo
Demo - Basic Architecture
17
T-76.4115 Iteration demo
Used work practices

How have you been using the planned work practices, what are the
experiences of



mandatory practices: time reporting
project meetings: standard agenda
Are you going to

adopt some new practices
Change chairman according the phases in the iteration
Increment implementation & unit testing phase 1.11 - 21.11
chairman is lead developer Jari Leppä
Increment itegration and system testing phase 22.11 - 8.12
chairman is quality manager Raine Mäki
18
T-76.4115 Iteration demo
Questions
19