Data Storage (database) Design

It describes the design of the database or data hosting Enviroment , the database is the place where
all of the data utilized by the system resides and also describes how the database is designed /
configured. The designer determines the information that must be stored on withdrawal, lag,
placement choice and how the data elements interrelate with each other , with the included
information we will begin to fit the data to the database model. Data storage design involves
classifying data and identifying relationships and these representation of data is called ontology ,
these ontology is used to represent the theoretical representation of our database design. There are
steps on determining what type of data must be stored on our database design : we all have to note
that our database designer is a person who is expertise in the area of database design rather than an
expertise in the domain from which the data to be stored is drawn from, the data type that must be
stored is part of requirement analysis, this is because those with the necessary domain knowledge
frequently cant express clearly what their system requirement for the database are as they are
unaccustomed to thinking in terms of the discrete data elements which which must be stored, data to
be stored can be determined by requirement specification. The next step is determining the data
relationships , once the database designer is aware of the data that must be stored on the database,
the designer will check if there is a dependency within the data , and if we changed some of our data
we will have to change data’s that are not visible, according to our data storage design, it is
conformed that there is no dependency among the stored data , it can be interrelated and come
under one category but they are completely independent from one another in which they supply
different information for the informed student and after determining the relationships and
dependencies amongst the pieces of information that have been determined on withdrawal, lag,
placement choice, it is possible to arrange the data into logical structure which can then be mapped
into storage objects supported by data base management system , if we are considering to structure
the data logically using relational database the storage objects are tables that store the mentioned
data in rows and columns , but if we choose the object database the storage object is similar to the
object used by the object oriented programming language that is used to write the applications that
will manage and access the data in this design phase we will choose the relational database to hold
our data by using tables that arranges them by using rows and columns that will be illustrated at the
end of this section and the way how this mapping of data is performed is such that each set of related
data that depends on a single object, whether real or abstract , is placed on the table , the
relationships between these dependent objects is then stored as links between the various objects .
each table represent the implementation of the logical object or a relationship joining one or more
instances of one or more logical objects , the relationships between the tables can be stored in a form
of a link connecting the child table with parent table and sometimes complex logical relationships are
themselves tables and the will probably have links to more than one parent.

JU S.I.S STUDENT ID DEPARTMENT WITHDRAWA LAG INFO PLACEMENT

NAME L INFO INFO
STUDENT1 74892 CS
STUDENT2 02874 IT
STUENT3 05681 SOFTWRE
WITHDRAWAL STUDENT NAME APPLYING STUDENT RECORD LEAVING DATE
REASON INFO
JEMAL SICKNESS CLEAN 28/11/2022
AYANA GRADE FAULT CRIME RECORD _
BIFTU EMERGENCY CASE CLEAN 29/11/2022

LAG STUDENT ACCEPTANCE LAG REQ LAG LAG

NAME PROCEDURES MATERIALS
FAISAL ACCEPTED SCORE>70
FETAH DENIED SCORE>80
FASIL ACCEPTED SCORE>50

PLACEMENT STUDENT NAME PLACED FIELD FIELD INFO FIELD

INTERCHANGE
INFO
KEDIR CS
KALEAB IS
KEROD IT

The above relational database that is represented is classified as parent table which is represented in
the first figure and the rest of these figures is the child table that has the relationship of composition
(part-of) relationship. The data storage design may include ER diagram that helps to design the
database in efficient way and the ER model is commonly known as information system design , it can
assist to describe our information or the type of information to be stored in the database design we
will not be including it because using ER model would be the same as using a use case diagram as it
only specifies the action measures taken by actors and their interaction with the environment so
while working on these projects we will be focusing on the relational database to express the design
of the stored data, in this field of design we will use the rule of normalization in which the systematic
way of ensuring whether the database structure is appropriate general purpose querying and it make
sure that it is free of certain unwanted characters like insertion, update and deletions anomalies that
leads to loss of data integrity , the guidance for standard database design suggests a designer should
create a fully normalized design , but there could be situations we can perform selective
denormalization that can be done for performance reasons only. The more normalized the design is ,
the less data redundancy will be which takes up a little space to store , but there are some common
data retrieval patterns that needs complex joints , merges and sorts that takes up more data read and
computing cycles , but like our team chose this modeling techniques , there is a modeling discipline
called dimensional modeling approach that is used for data warehouse design the recommends a non
normalized design . normalization consists of normal forms that are 1NF,2NF,3NF,BCNF,4NF and 5NF.

A) Physical database design

The physical design of the database specifies the physical configuration of the database on the
storage media. It is the detailed design of a system that includes modules and the database
hardware and software specifications of the system , the aspects which are addressed on this
physical layer :
1) security : the students information that is included to use our website is secured by
covering the identity from their school friends and school administration which is part of end
users security and the admin that works on the project should secure their system security by
making it invincible against hackers.
2) Replication : the piece of information that is included get copied over other database
everytime, the multiple master is the student information that gets copied many times when a
piece of data is transferred into another database.
3) High Availability : The configuration is Active Active and the topology , the coordination
scheme and the reliability targets all are defined.
4) Partitioning : The database is distributed for a single entity student information and the
above target info is distributed amongst all the partitions of the database and the partition
failure is taken into account.
5) Backup and Restore the scheme.

When this design phase reaches the application level, other aspects of this physical design
include the need to define stored procedures or materlized query views.