T -76.4115 Iteration Demo BetaTeam I2 Iteration, Final Solution 2.3.2006.
T-76.4115 Iteration Demo BetaTeam PP Iteration 13.10.2005.
-
Upload
octavia-henderson -
Category
Documents
-
view
227 -
download
0
Transcript of T-76.4115 Iteration Demo BetaTeam PP Iteration 13.10.2005.
T-76.4115 Iteration Demo
BetaTeamPP Iteration
13.10.2005
2
T-76.4115 T-76.4115 IterationIteration demo demo
Agenda
Project status (15 min) achieving the goals of the iteration project metrics
Work results (20 min) presenting the iteration’s results
project plan requirements
demo architectural structure
Used work practices ( 10 min)
3
T-76.4115 T-76.4115 IterationIteration demo 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.
4
T-76.4115 T-76.4115 IterationIteration demo demo
Status of the iteration’s goals
Goal 1: Specify the goals of the project from all perspectives OK
Goal 2:Familiarize with the topic OK, but customer current system familiarizing needs more effor from project
group Goal 3:Familiarize with different stakeholder
OK Goal 4:Requirement Specification in general level including most
important requirements and use cases OK
Goal 5: Architecture at rought level OK
Goal 6: Identifing risks OK
Goal 7: Defining the methods and tools and working environment 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
5
T-76.4115 T-76.4115 IterationIteration demo demo
Status of the iteration’s deliverables
Project plan OK, building parctices and some roles needs refining
Requirements document OK, all important requirements documented in general level
Progess report OK
Architecture (draft) OK, part of requirement specification
6
T-76.4115 T-76.4115 IterationIteration demo demo
Realization of the tasksStatus Real Plan Diff (Left)
Meetings and Lectures (PP iteration)
Meetings & agenda ok 37,75 39 -1,25 12Lectures ok 17,5 35 -17.5 12CVS & WEB pages work moving I1 0 5 -5 5Tools & Infra & customer laptop evaluation moving I1 0 20 -20 20Requirements Specification (PP iteration) finnishd
Architecture draft,Requirements elicitation, priorisation, validation and analysis, req Spe document
6 35 -29
Project management (PP iteration) finished
Project plan, progress report, working hour management
32 37 -5
Qality (PP iteration) under work
Reviews, defining practices and tools 8 17 -9 3
* unplanned task (= a new task added during the iteration)
7
T-76.4115 T-76.4115 IterationIteration demo demo
Working hours by person
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
Real Plan DiffUlla Suomela
62 91 -29
Jari Leppä 28 56 -27Raine Mäki 20 56 -36M4 0 0 0M5 0 0 0M6 0 0 0M7 0 0 0Total 110 203 93
Realized hours in PP iteration Plan in the beginning of this iteration
PP Σ I1 I2 TotalUlla 91 90 30 30 150Jari 56 56 50 44 150Rane 56 56 50 44 150M4 0 0 70 80 150M5 0 0 70 80 150M6 0 0 70 80 150Total 203 203 340 358 900
Latest plan (inc. realized hours and other updates)
PP I1 Σ I2 TotalUlla 62 48 110 40 150Jari 28 72 100 50 150Rane 20 60 80 70 150Hannu 0 70 70 80 150Juho 0 70 70 80 150Kauko 0 70 70 80 150Total 110 390 500 400 900
8
T-76.4115 T-76.4115 IterationIteration demo 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.
9
T-76.4115 T-76.4115 IterationIteration demo 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
10
T-76.4115 T-76.4115 IterationIteration demo demo
Project plan
Stakeholders and staffing
TKK Course T-76.4115/5115
Customer: NAPA ltd, Ville Ylöstalo
Mentor: Mika Mäntylä
Project
Project
Project Manager, Ulla Suomela
Lead Developer, Jari Leppä
Quality Manager, Raine Mäki
Testing Team, Development Team,
Kauko Huuskonen
Hannu Kankaanpää
Juho Mäkinen
Hannu Kankaanpää
Juho Mäkinen
Kauko Huuskonen
11
T-76.4115 T-76.4115 IterationIteration demo demo
Project customer goals
Goal Verification criteria Weight 3 - 1
1. Database ER model is ready. Customer has been review the ER model.
3
2. The database according to ER model has been implemented.
Database exists. 2
3. It is possible to test the database.
Testing of the database has been started.
2
4. Replacement of current shared file style data manipulation by database server.
It is possible to test the database by original data.
2
5. Architecture is ready and will support different end users.
It is possible to test the configuration of database for different users.
2
6. Interface to the old system function (read) works.
It is possible to use the new database with Interface function “read” that are described in Req Spec /1/
2
7. Interface to the old system function (write) works.
It is possible to use the new database with Interface function “write” that are described in Req Spec /1/
2
8. Update the database Information.
It is possible to use the new database with Interface function “write” that are described in Req Spec /1/
2
9. Interface to the old system function (delete) works.
It is possible to use the new database with Interface function “delete” that are described in Req Spec /1/
2
10. The software is possible to run in one laptop ( Win&Solaris)
It is easy to install a new relase to Win or Solaris computer
1
12
T-76.4115 T-76.4115 IterationIteration demo demo
Project members goals
Goal Verification criteria
1. Pass the course The project team grade of the course is at least 1
2. The requirements from course personnel fulfill and the deliverables of the project are at good quality level.
The project team grade of the course is at least 4
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 and course.
Find out the mentor and customer needs. Plan 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 equally
Following the workload of the project regularly.
10. Own study goals fulfills. SEPA work succeeds.
13
T-76.4115 T-76.4115 IterationIteration demo 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 systemFor reports and documents: MS Office / Open Office Word, power point, Excel
14
T-76.4115 T-76.4115 IterationIteration demo 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)
15
T-76.4115 T-76.4115 IterationIteration demo demo
Requirements Specification, Functional requirements
ID Ver Feature Requirement Source Rationale Priority Status Traces to use cases
F1 1 Reading data object
Looking for object of given name and returns its content.
Product Manager N.N.
Method in Java class. Select
Must Proposed
F4 1 Find out, if particular data object exists
Checking, if there exist a specific data object
Method in Java class. Select
Must Proposed
F3 1 Writing data object
Insert a new data object
Method in Java class. Insert
Must Proposed
F2 1 Updating data object
Looking for object of given name and writing its content over
Product Manager N.N.
Method in Java class. Update
Must Proposed
F5 1 Deleting particular data object
Find out, if there exist particular data object and if 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. Iteration
Proposed
F7 1 Query to partially match object content
Generate query to select specific data objects
Method in Java class. Select
2. Iteration
Proposed
F8 1 Locking specific database object
Method in Java class in RDBMS
2. Iteration
Proposed
F9 1 User rights handling to
2. Iteration
Proposed
16
T-76.4115 T-76.4115 IterationIteration demo demo
Requirement Specification, Non-Functional requirements
ID Ver Requirement Source Rationale Priority Status Traces to use cases
N1 1
Current shared file version and new RDB –system version will both keep supported for long time to the future
Product Manager N.N.
Application and its data management interface must support both implementations. This have to keep in mind in design.
Must Proposed
N2 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 implementation
Must Proposed
N6 1 Faster than current system
Product Manager N.N.
This have to keep in mind in design and in implementation
Must 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 is RDBMS feature also.
Must Proposed
17
T-76.4115 T-76.4115 IterationIteration demo demo
Demo - Basic Architecture
18
T-76.4115 T-76.4115 IterationIteration demo 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
19
T-76.4115 T-76.4115 IterationIteration demo demo
Questions