sbahn database management tool georgi cholakov, sam joachim university of plovdiv “paisii...

SBahn Database Management ToolGeorgi Cholakov, Sam Joachim

University of Plovdiv “Paisii Hilendarski”, e-Commerce Laboratory in cooperation with Humboldt University

Data storage file• In XML format

The XML schema of the data file previously.

Database design• Conceptual model

word_transl_word

word_transl_word

word_transl_word

word_transl_lang_rel

alt_word_transl_rel

word_lang_rel

LANGUAGE

lang_idlang_name

<pi> SerialVariable multibyte (50)

<M><M>

lang_pk_id <pi>

WORD

word_idworddescrabbrevorigin

<pi> SerialVariable multibyte (50)Variable multibyte (300)Variable multibyte (20)Variable multibyte (50)

<M><M>

word_pk_id <pi>

WORD_TRANSL

word_transl_idword_transldescr_translabbrev_transl

<pi> SerialVariable multibyte (50)Variable multibyte (300)Variable multibyte (20)

<M><M>

word_transl_id <pi>

ALTERNATIVE

alt_word <pi> Variable multibyte (50) <M>

Key_1 <pi>Version 0.1 of the database design

Database design• Physical model

word_id = word_id

word_transl_id = word_transl_id

lang_id = lang_id

word_transl_id = word_transl_id

lang_id = lang_id

LANGUAGE

lang_idlang_name

intnvarchar(50)

<pk> identitynot null

WORD

word_idlang_idworddescrabbrevorigin

intintnvarchar(50)nvarchar(300)nvarchar(20)nvarchar(50)

<pk><fk>

identitynot nullnot nullnullnullnull

WORD_TRANSL

word_transl_idlang_idword_transldescr_translabbrev_transl

intintnvarchar(50)nvarchar(300)nvarchar(20)

<pk><fk>

identitynot nullnot nullnullnull

ALTERNATIVE

word_transl_idalt_word

intnvarchar(50)

<pk,fk><pk>

not nullnot null

WORD_TRANSL_WORD

word_idword_transl_id

intint

<pk,fk1><pk,fk2>

not nullnot null

Physical database model for MSSQL Server 2000

SBahn Database Management Tool• Overview of the system

SBahn Database Management Tool• Modules

– Configuration– Languages– List of Words– Find translation– Help

Modules• Configuration

Modules• Languages

Modules

• List of Words

Modules• Find translation

Modules• Help

Conclusions

• The database design needs to be checked for correctness

• The user interface can be more flexible• The help to be detailed