You are here

Database – creation and loading

The database of the Mobile Language Teaching Centre has to store the following data groups:

1. Students’ master data:
• data of identification
• selected language(s) (can be more than one)
• aimed level of knowledge (for each selected language)
• current level of knowledge (for each selected language)
• current balance of tuition fee account

2. Teachers’ master data:
• data of identification
• language(s) to teach (can be more than one)
• level of accreditation (for each taught language)
• current account balance

3. Students’ course record data:
• lessons taken
• answers to exercises (with date stamps)

4. Data of teaching materials:
• list of teaching material units (designed set of exercises)
• independent teaching material units with the following attributes :
• language
• level
• type
• content (according to type)

The database services are closely related to the database itself, practically data can only be accessed via these applications. The services (database APIs):
• prevent unauthorized access to data
• provide consistent, pre-processed data
• are highly effective, high speed applications

For example, the list of 50 randomly selected exercises to which a certain student has not yet given correct answers can be queried with a single service call parameterized by the identifiers of the student and the language.

Database applications can support many other system functions effectively. For example:
• upload of teaching material units into the database using a web-based interface
• download of teaching materials to PCs or mobile (smart) phones
• upload of answers to exercises to the database
• upload of answers to exercises requiring instructor’s assessment, the query of the task list, completion of assessment
• mediation of questions and consultation requests between students and instructors
• account clearing (for teachers / students, for services provided / accepted)
• issuing certification of course completion for students
• preparing statistical analysis of historical data for the refinement of methods

It is worth mentioning here the portal’s own database, which is required for storing the data needed for keeping in contact with users. User interfaces will run as the modules of the portal and will call for the services of the database of the Centre to meet their demands for data. In this way external users will not have access to the database directly, and that is very advantageous from the point of view of data security.

User login

Navigation

Who's online

There are currently 0 users online.