Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
15 views2 pages

Project. Part 1

Uploaded by

hastpauli
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
15 views2 pages

Project. Part 1

Uploaded by

hastpauli
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

Project

Part 1. Subject Area Analysis (individual topic, teamwork)

Goal: to perform a first step of database design - Subject Area Analysis.

Task: to make a description of a future database according to the following plan.


Topic of the database is according to the individual task. Note: the database should
contain minimum 10 entities (tables).

Plan:

1. Describe in detail what information will be stored in a future database.


Specify a goal of the database design, what problem it can solve, or what
processes it can improve. In other words, describe the subject area.

2. List all entities and attributes (tables and columns) in the required format.
Every entity should have a Primary key, underline it in the description. Note: the
database should contain minimum 10 entities.

Example.
Entity_name (PK attribute name, attribute_name_2, …, attribute_name_n)

3. List and describe all relationships between entities.


To describe a relationship between two entities (tables) answer 2 questions. First
of them is how one row from the first table refers to one or several rows from the
second table, and the second question (from the other side) is how one row from
the second table refers to one or several rows from the first table.

4. List all constraints (3-5 will be enough).


Note: constraints should only apply to the information that is stored in the database,
otherwise they cannot be implemented.

5. Specify all groups of users and their access rights (2 will be enough).
Database is used by different groups of users, and they have different access rights.
A group of users is all users who have the same access rights. Specify access
rights at the table level - access can be read-only or read-write, in other words,
write which tables these users will be able to edit, and which - only view (see
example). Note: do not specify the database administrator - it exists by default.

Example.
User_group_1. Access rights: table_name (read-write).

6. List all potential queries from users (10-15 will be enough).


Users will be able to get information from the database by writing a query. In other
words, a query is a question to the database to display certain information.

Upload: *.doc(x) or *.pdf


Materials:
• Lecture 1;
• Connolly, Thomas M. Database Systems: A Practical Approach to Design,
Implementation, and Management.

You might also like