14
Research plan – LSRT Consortium

Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Embed Size (px)

Citation preview

Page 1: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Research plan – LSRT Consortium

Page 2: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Targets

• Correctness approval Vs. Sybase database.

• Implementation of a validation scenario with TTI database.

• Demo preparations and participation

Page 3: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Correctness approvalTargets: validate the consistency of the LSRT database

Execution: This evaluation will be done by comparing the LSRT database to the commercial Sybase by comparing the results under traffic.

Testing environment: with the following capabilities: (1) Traffic generation that will generate load on both databases according to parameters

(2) Comparator process that will compare the results of the two processes and will report after comparing the databases if the databases are equal or not.

Page 4: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Environment •Traffic generator. The traffic generator is responsible to generate traffic according to predefined parameters. The user can control the traffic pattern like the number of transactions per second, the number of transactions in every batch etc.

•Sybase. The Sybase engine used in this test is the same database engine used by TTI.

Page 5: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Environment cont.

•LSRT database. The LSRT database is the database engine developed during this research in the Technion. The purpose of this test is to prove that this engine is consistent with Sybase.

•Comparator. The comparator is responsible for the logical checks of the two databases. As both engines run the same set of transactions, the comparator will check the physical content of the disk and will report on any discrepancies.

Page 6: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Research Targets

•Proving correctness and completeness

•Elementary integration with TTI

•Demo preparations and participation

Page 7: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Correctness and Completeness Will be performed in 3 phases

Construction of the basic environment and the development of the first version of the transactions generator

Page 8: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

This phase include the integration of the LSRT database engine developed in the Technion to one unified system. It also includes an upgrade of the Transaction generator capabilities

Phase 2

Page 9: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Phase 3

This phase includes the integration from the comparator with the capabilities to check the differences between the LSRT database engine developed in the Technion and Sybase.

Page 10: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Correctness and Completeness Timetable Iteration Sub step activity Duration Total

2 weeks

Installation and activation 1

Phase 1

First version of transaction generator 1

5 weeks

Enhancement of transaction

generator (parameters)

2

Phase 2

Connection to scheduler 3

4 weeks

Comparator development 2

Phase 3

tests 2

Total 11 weeks

Page 11: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Application

Elementary integration with TTI

Targets:1. Definition 2. Implementation3. Summarizing and results analysis

Page 12: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Elementary integration with TTI - Timetable

1. Definition - 2 weeks

2. Implementation - 3-4 weeks

3. Summarizing and results analysis - 2 weeks

Page 13: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Demo preparations and participation

1. Definition - 2 weeks

2. Implementation - 3-4 weeks

3. Participation

Page 14: Research plan – LSRT Consortium. Targets Correctness approval Vs. Sybase database. Implementation of a validation scenario with TTI database. Demo preparations

Global Timetable