The requirements and objectives of the final examination

1.

Astana IT University
Information Communication Technologies
Final project proforma
This document describes the requirements and objectives of the final examination
project for the Information and Communication Technologies course. Students of
the course are expected to work in groups of a maximum of 2 people. However,
when it is not possible 3 people are accepted in a group. All participants of the
group are expected to reach the following learning objectives of the course by the
completion of the project.
Learning objectives to be addressed
The results of the Final examination project should demonstrate the following
learning objectives:
● Understand the fundamental roles of DBMS that play in the organization;
● Understand and utilize the SQL queries in depth;
● Design the database tables properly, so that your design and implementation
demonstrate logical integrity and coherence;
Skills that should be demonstrated on the completion of the project:
● Explain the relational database concepts;
● Understand and acquire the SQL DDL and DML statements;
● Design and implement SQL database;
Final project description
To summarize your knowledge from this course you are expected to design a
holistic database system. The project involves designing a complete database
management system to address a practical database need and implementing a
relational database based on that design. Your database system should be
designed to perform general information management tasks such as systematic
collection, update, and retrieval of information for a small organization. The topic
of the project should be approved by the instructor.
1. Define the purpose of your system.
15 points

2.

Describe the organization, its size, database
environment and objectives. Create clearly defined
business rules that explain the design of your database.
You need to know what information you want from the
database, give a detailed scenario. Define what kind of
data you should include.
The starting point of your project is to identify a
database need of a real or hypothetical client, and
explore questions such as:
• What is the purpose of the database? Why is it
needed? What should it do?
• Who are the users and what are their
information needs?
• What are the problems that the system should
solve?
• What input data is available to the database?
• What kind of information should be stored in the
database?
2. Create ERD using Crow’s Foot notation (min.10 20 points
well-organized entities; their attributes, and types of
relations);
3. Create database: tables with entities (tables) and 10 points
constraints (PK, FK, UK, and etc.);
4. Write 5 different (add, drop and constraints) ALTER 5 points
TABLE statements;
5. Write SQL query for DML statements (insert, delete, 5 points
update). Insert - for all tables at least 10 rows, Update
– for each table with a condition, Delete – for each
table with a condition;
6. Write at least 10 queries: using DISTINCT, 15 points
conditions (<,>,=), OR, AND, BETWEEN, IN, LIKE,
LENGHT, COUNT, MAX, MIN, SUM, AVG,
INNER JOIN, LEFT JOIN, RIGHT JOIN, FULL
JOIN and etc. The queries should be coherent and
complex.
7. Write at least 5 subqueries: single-row, multiple-row 5 points
and multiple-column subqueries, and etc.;

3.

Presenting your work
15 points
Formal project presentations will be held according to the
project presentation schedule. Your presentation should
consist of a description of the project and the design process,
and a walk-through demonstration of your project. If you
want to get more than 89 points, you should do tasks during
the defense.
You will need to create a .ppt presentation of your project
that contains the following:
1. Introduction to your project
2. The outline of your project
3. Responsibilities of each member in the group
4. Challenges while developing a project
5. Screenshots of your project steps according to the
outline
6. Learning outcomes from the work done
7. Your summary of the project including validation of
database against client/user/database objectives, list of
weaknesses and limitations of current implementation,
list of potential future upgrades
Documenting your work
The descriptions of the steps according to the task
requirements should be documented in a written report in
.doc format and converted to the .pdf before submission.
Please use 12 size of the “Times New Roman”, “Arial” or
“Calibri” fonts and 2.5 cm in margins.
The document should not exceed 30 pages without including
Cover page, List of figures and tables, References and
Appendix. Make sure that your document includes all
mentioned above content parts. The report should include a
clear explanation each step as well as comments for
programming part. The text should be clearly understandable
and written in English.
Reflection
Write a report reflecting your role in the project regarding
each of the tasks. Your report should clearly indicate your
input into the project. Each member of the group is expected
10 points

4.

to develop this part of the project individually and have an
equal contribution to the project. As a result, your final
submitted document should consist of two (or three)
individual reflections. Each member of the group will be
asked individual questions regarding their reflection. Failing
to write the reflection and explain your role in the final
project is automatically penalized as a fail.
Submitting your work
The submission should include following components as a
group in the following format Group_name_student_names:
• One written report in .pdf format;
• One .ppt file;
• Compressed database file in zip format.
Failing to submit one of these components means the project
is automatically failed. Please refer to the exam schedule for
submission deadline. Your work should be submitted one day
before your project presentation session. The late submission
window (24 hours) after the deadline date is being considered
as late submission and evaluated as half of the points.
Submission later than 24 hours after the deadline gets a zero
mark.
Plagiarism
The final report should be original work. Detecting cheating
in the final project is automatically penalized as a fail.
Plagiarism rules cover all types of cheating work including
using someone concept, design, ideas, diagrams, figures, part
of the text, approaches, source code, etc.