Data Analysis and Design: A Comprehensive Guide to Relational Database Systems

This comprehensive guide delves into the intricacies of data analysis and design, focusing on relational database systems. Explore various data models, their advantages and disadvantages, and the normalization process. Learn how to design and implement relational databases using MS Access, and master the art of data manipulation and querying with SQL. This guide also covers verification and validation techniques, access control mechanisms, and user documentation, providing a complete understanding of relational database systems.

DATA ANALYSIS AND DESIGN

Contents
Introduction..............................................................................................................................................................4
LO1 –Task 1 Understand data models and database technologies.........................................................................5
A.C.1.1 Critically compare different data models................................................................................................5
A.C.1.2 Critically discuss the benefits and limitations of different database technologies...............................12
A.C. 1.3 Analyse different approaches to database design................................................................................17
LO2 Task 2. Be able to design and implement relational database systems.........................................................21
A.C.2.1 Design a relational database system to meet given requirements provided in the given case study..21
A.C.2.2- Build a relational database system for the database design in A.C 2.1 using an appropriate database
software application...........................................................................................................................................24
A.C.2.3 Apply a range of database tools and techniques to enhance the user interface to meet the given case
study requirements............................................................................................................................................28
LO3 - Task 3. Be able to use manipulation and querying tools..............................................................................31
A.C. 3.1 Explain the benefits of using manipulation and query tools in a relational database system as per the
requirements gave in the case study..................................................................................................................31
A.C. 3.2 Implement a query language into the relational database system that has been implemented in task
2.2.......................................................................................................................................................................34
A.C. 3.3 Critically evaluate how meaningful data has been extracted through the use of query tools for the
given case study.................................................................................................................................................39
LO4 -Task 4. Be able to test and document relational database systems.............................................................42
A.C. 4.1 Critically review and test the implemented relational database system.............................................42
A.C. 4.2 Create documentation to support the implementation and testing of the relational database system
that has been implemented in Task 2.2.............................................................................................................43
A.C. 4.3 Create user documentation for the developed relational database system in task 2.2......................47
A.C. 4.4 Explain how verification and validation have been addressed in the developed relational database
system................................................................................................................................................................50
A.C. 4.5 Explain how control mechanisms have been used in the developed relational database system......53
Conclusion-.............................................................................................................................................................57
References-............................................................................................................................................................58
Appendix................................................................................................................................................................59
1

List of figures:
Figure 1: OOBM.......................................................................................................................................................6
Figure 2 Relational model.......................................................................................................................................7
Figure 3:-Top-Down design...................................................................................................................................19
Figure 4: Bottom-up design...................................................................................................................................20
Figure 5: Academic manager table.......................................................................................................................24
Figure 6: Admin table............................................................................................................................................25
Figure 7: College table...........................................................................................................................................25
Figure 8: Course table............................................................................................................................................25
Figure 9: Lecturer table.........................................................................................................................................26
Figure 10: Student table........................................................................................................................................26
Figure 11: Unit table..............................................................................................................................................26
Figure 12: Academic manager tables of Form......................................................................................................28
Figure 13: Admin tables of Form...........................................................................................................................28
Figure 14: College tables of Form.........................................................................................................................28
Figure 15: Course tables of Form..........................................................................................................................29
Figure 16: Lecturer tables of Form........................................................................................................................29
Figure 17: Students tables of Form.......................................................................................................................30
Figure 18: Units tables of Form.............................................................................................................................30
Figure 19:Acedemic_manager query....................................................................................................................32
Figure 20:Students query......................................................................................................................................32
Figure 21:Acedemic_manager SQL query.............................................................................................................33
Figure 22: Students SQL query..............................................................................................................................33
Figure 23: Query 1.................................................................................................................................................33
Figure 24Query 2...................................................................................................................................................33
Figure 25: Query 3.................................................................................................................................................34
Figure 26Query 4...................................................................................................................................................34
Figure 27: Query 5.................................................................................................................................................34
Figure 28: Query 6.................................................................................................................................................35
Figure 29: Query 7.................................................................................................................................................35
Figure 30: Query 8.................................................................................................................................................35
Figure 31: Design View of Query1.........................................................................................................................35
Figure 32: Design View of Query2.........................................................................................................................36
Figure 33: Design View of Query3.........................................................................................................................36
Figure 34: Design View of Query4.........................................................................................................................36
Figure 35: Design View of Query5.........................................................................................................................36
Figure 36: Design View of Query6.........................................................................................................................37
Figure 37: Design View of Query 7........................................................................................................................37
Figure 38: Query 8 Design View............................................................................................................................37
Figure 39: Query1..................................................................................................................................................38
Figure 40: Query2..................................................................................................................................................38
Figure 41: Query3..................................................................................................................................................38
Figure 42: Query4..................................................................................................................................................39
Figure 43: Query5..................................................................................................................................................39
Figure 44: Query6..................................................................................................................................................39
Figure 45: Query7..................................................................................................................................................40
Figure 46: Query8..................................................................................................................................................40
Figure 47: Objective Plan 1....................................................................................................................................44
Figure 48: Objective Plan 2....................................................................................................................................44
2

Figure 49: Objective Plan 3....................................................................................................................................45
Figure 50: Objective plan 4....................................................................................................................................45
Figure 51: Objective Plan 5....................................................................................................................................45
Figure 52: Objective Plan 6....................................................................................................................................46
Figure 53: form of Accedemic_Manager..............................................................................................................48
Figure 54: Form of Admin......................................................................................................................................48
Figure 55: Form of College....................................................................................................................................48
Figure 56: Form of Course.....................................................................................................................................48
Figure 57: Form of Lecturer...................................................................................................................................49
Figure 58: Form of Students..................................................................................................................................49
Figure 59: Form of Units........................................................................................................................................49
Figure 60: Design of V-Model................................................................................................................................50
Figure 61:Verification Phases................................................................................................................................51
Figure 62:Validation Phases..................................................................................................................................52
Figure 63: Acedemic_manager for access control mechanisms..........................................................................53
Figure 64: Admin for access control mechanisms................................................................................................54
Figure 65: college for access control mechanisms...............................................................................................54
Figure 66: Course for access control mechanisms................................................................................................55
Figure 67: lecturer for access control mechanisms..............................................................................................55
Figure 68: Students for Access Control Mechanisms...........................................................................................55
Figure 69: Units for access control mechanisms..................................................................................................56
3

Introduction
In this Dominican college, there are different types of issues as they are not managing their
database properly so that they have face problems in the database. Here we described all
the tables which they are facing problems, we have made seven different types of tables so
that we can relate them to their queries and solved them queries. Describe E-R Diagrams
and data models and database technologies of implementation, normalization process and
all screen sorts of the table which is used in the structured query language.
4

LO1 –Task 1 Understand data models and database technologies
A.C.1.1 Critically compare different data models
What is Data model?
In the database model, including their relationships and constraints that decide how data
can keep and retrieve, in this model reveal the logical structure of a database. All the single
database models are a plan to build by their rules and conception. All the data models are
constituted follow by their database diagram.
Types of database models
The various types of data models are-
1. Object-oriented database model
2. Relational of model
3. Entity-Relationship model
4. Networking model
5. Hierarchical database model
1. Object-oriented DBM (Database Model)
An object-oriented database model is a group of reusable, software elements,
objects & property, and techniques. There are many types of object-oriented
databases: -
 Hypertext database: -In the hypertext database permit there any objects to
connect to any others object and its use for any corporation to a large amount of
data, but it’s not perfect for the numerical survey.
 Multimedia database: -In the multimedia database they could not store any
images so a database is integrated media.
Since it integrated tables, the OODM is famous familiar upright-relational DBM.
These types of OODM are also called as hybrid DBM.
5

Figure 1: OOBM
2. Relational of model
The popular model, each table are consisting of column and rows, so this model
sorted statistics into tables called relations. Each one column lists have an attribute
of the entity. The domain is called the attribute in a relation. The primary key is
chosen as a specific attribute or combination of attributes which was referred by
another table, then it’s called foreign key.
Each row of a table is a tuple, involves data into some particular examples of the
entity.
There are kinds of connections between the tables, many-to-many, one-to-many,
one-to-one, and connections. Below some examples are given: -
6

Figure 2 Relational model
3. Entity-Relationship model
This model is similar to the network model, and relationships between real-world
entities, but the physical structure of the database is not directly tied in this model.
Figure 3: Entity-Relationship model
4. Networking Model
7

To construct on a hierarchical model to allow many-to-many connections between
associated data. They built with puts of interconnected data found on the
arithmetically set hypothesis.
It is defined the CODASYL after it was most popular in the 70s.
Figure 4: a Network model
5. Hierarchical model
In these hierarchical model, the data are well-ordered into a tree-like structure,
where single parents or root have each record. Records of the siblings are sorted
into specific order. For keeping the DB that physical order used as an order. Actual
earth connections are describing in this hierarchical model.
8

Figure 5: Hierarchical model
Advantages and Disadvantages of each database model
1. Object-oriented database model
Advantages
 Removal of impedance mismatch
In this, control the impedance inconsistency is a one language interface
between the DML (Data Manipulation Language) and the programming
language.
 Improved Performance
Over relational DBMS, there have been numbers of specifications that have
been propose OODBMS give remarkable show advance.
 Efficient of holds a huge variety of data types
Hierarchical, network or relational database are a different conventional
database, they are efficient to keep dis-similar kinds of records such as text,
voice video pictures and etc.
Disadvantages
 Competition
 Lack of standard
 Lack of support for security
 Complexity
9

2. Hierarchical database model
Advantages
 For new information easy addition and deletion
 Easy to work
 It works one-to-many relationships
Disadvantages
 Sophisticated relationships
 Repetitively data store in many different entities
 Slow when searching for information
3. Relational model
Advantages
 Data independence
 Data Manipulation
 Security
Disadvantages
 Slow extraction of meaning from data
 Performance
 Physical storage consumption
4. Entity-Relationship model
Advantages
 Easy conversion
 Effective communication tools
 Conceptually it is very simple
Disadvantages
 Limited relationship representation
 Popular for high-level design
 Loss of information content
5. Network model
10

Advantages
 Data independence
 Ease of data access
 Conceptual simplicity
Disadvantages
 Operational anomalies
 The absence of structural independence
 System complexity
11

A.C.1.2 Critically discuss the benefits and limitations of different database technologies
There are various different kinds of DB technologies such as: -
1) web-based technology (cloud computing)
2) object-oriented database
3) Relational database
4) data warehousing (data mars and data mining)
5) Multimedia database
6) File-based
7) distributed database
web-based technology (cloud computing)
It (information technology) is a cloud computing that authorizes everywhere contact to
divide pools of structural properties and level of facilities is higher than speedily with the
slight attempt, frequently above the net.
Advantages
 Accessibility
warehoused files can be retrieved from anywhere via the internet.
 Bandwidth
You can send a web link to recipients through emails and avoid emailing files to
individuals.
 Cost savings
By using cloud storage, corporate and administrations can frequently decrease
annual operating costs, to store data they cost 3 cents/gigabytes.
Drawback
 Intelligibility
If you have no net linking, you have no contact with your information.
 Bandwidth
Specific bandwidth allowance has a several cloud storage services. Though,
some providers permit unrestricted bandwidth.
12

 Software
On all devices, you have first downloaded the facility, between numerous
implement you want to able to operate your folder locals.
object-oriented database
Normal database objects are different from main objects and the important features are
allowing the definitions of objects. An object-oriented database is an opening of
contribution in the relational database management system (RDBMS) area.
Advantages
 Transactions and long-duration for support
 Expansive query language
 Extensibility
13

Disadvantages
 Lack of experience
 Complexity
 Lack of Support for security
Relational database
Data are organized in dis-similar ways in a relational database. Each table in a relational
database is called relation, there are more than one category columns.
Advantages
 Precision
 Flexibility
 Security
Disadvantages
 Slow extraction of meaning from data
 Performance
 Physical storage consumption
Data warehousing (data mars and data mining)
Data warehousing, they gather and managing data from wide-ranging sources to provide
expressive business visions. The strategic use of data is blended with technologies and
components.
Data mining
knowledge discovery in the database in computer science is also called data mining. The
field merge tools from machine learning and neural networks, statistics to analyze the huge
amount of data collections.
Data mars
MARS (Marine Sediment) database carry complete information on seabed remains features
for representative’s collection from, including the Australian Antarctic Territory and
Australian’s marine jurisdiction.
Advantages
 Integrating data from multiple sources
14

 Reducing cost to historical data
 Performing new types of analysis
Disadvantages
 Ownership concerns
 Inflexibility data
 Demand for huge amounts of resources
Multimedia database
Multimedia database is a group of interrelated multimedia data that comprise
sketches, drawing (graphics), text, animations, audio, video etc and multimedia data
have huge amounts of multisource. The multimedia database management system is
called the structure that can organize dissimilar types of multimedia records which
will be delivered, stored, and use by dissimilar ways.
Advantages
 Data independence
 Query support
 Hold up multiple formats of data (video, audio, text etc)
Disadvantages
 A lot of bandwidth and processing time
 Multimedia data need a huge storage.
Based-file
Such as production of reports, a collection of application programs that complete services
for the end users. Each data can be managed by itself.
Advantages
 Secure
 Privacy
 Easy access to data
 No redundant data
Disadvantages
15

 Performed
 DBMS
 Performance
Distributed database
The group of multiple interconnected databases, in a various location which was spread
physically that communicate via computer networks.
Advantages
 Better response
 More reliable
 Lower communication cost
Disadvantages
 Data integrity
 More complex in database design
 Complex software
16

A.C. 1.3 Analyse different approaches to database design
Approaching of Top-down
ER Approach
An ERM is a theoretic and abstract method of presentation data relationships in software
expansion. An abstract illustration or graphic depiction of an organization record that can be
pleasant in cunning an RDB is methods of ERM database.
These diagrams are called ER diagrams, ERDs, entity-relationship diagrams.
Abstract ER diagram symbols
A. ERD entity symbols
Entities are objects or ideas of significant data. In a relationship diagram, they used
commonly three types of entities
Symbol OF Entities Title Explanation
Strong entity
Rectangular shapes are also
called parents entities
because shapes are self-
determining from other
entities, weak entities are
dependent on strong
entities. In strong entity
have a primary key.
Weak entity
Weak entities do not have a
primary key. These entities
are depending on another
entity type. Without their
parent entity, there is
meaningless in the diagram.
Associative entity
They narrate the examples
of some entity variety. They
comprise between those
entity examples.
17

ERD relationship symbols
Documents are an interaction between two entities are used in a relationship, inside entity-
relationship diagrams. There are only two types of relationships
Symbol of
Relationship
Title Explanation
Relationship
These relationships are associations among or
between entities.
Weak
Relationship
The connections between a weak entity and its
holder are called weak entities.
ERD attribute symbols: - The entity that helps users to understand the database are
characteristics in the ERD entities. There are four types of ERD attribute symbols
Symbol of Attribute Name Description
Attribute
The characteristics of an
entity, one-to-one
relationship or many-to-
many relationship are called
attributes.
Multivalued attribute
They take more than one
value is called multivalued
attribute.
Derived attribute
The merit can deliberate
from connected attribute
values are called derived
attribute.
Relationship
The associations between or
among entities are called
relationships.
18

Explain the role of the top-down approach regarding designing database systems
The role of top-down design technique begins from the normal and progress to the
particular. You can begin with normal design what is require for the structure & effort your
method down to the addition of particular details of how the structure will interact. This
operation involved the method of each entity attribute and the recognition of dissimilar
entity types.
Figure 3:-Top-Down design
Explain the role of the Bottom-up approach regarding designing database systems
The role of B-U approach starts with particular features and progress up to normal. This is
ready and first recognize the data components and they together grouping in data sets. In
another word, B-U methodology first recognizes the attributes and then configuration
entities are grouped them.
Figure 4: Bottom-up design
19

Compare and contrast how these two approaches would help in database designing
process
Top-down Approach Button-up Approach
In this approach they essential the smash
down of a program to obtain perception
into its compact program in a back-
engineering trend.
In this approach, they are assembled jointly
of the module to allow the increase to the
extra composite program, thus
manufacturing the indigenous modules of
the beginning of the program.
C programming language is a structure or
procedure-oriented programming followed
the T-D approach
C++ and JAVA programming language is
object-oriented programming language
followed the B-U approach.
In this strategy, they started with a high-
level language but they ended up with low-
level language in T-D approach.
In this procedure, they are stared with
lower level language but here they ended
up with a high-level language, just opposite
to T-D approach in a bottom-up approach.
In the top-down approach, sub-functions
are based on the requirement so all sub-
functions are called the main function but
the main function is written first.
In button-up approach, modules are
developed from code and the main
function is integrated with these modules.
20

LO2 Task 2. Be able to design and implement relational database systems
A.C.2.1 Design a relational database system to meet given requirements provided in the
given case study.
Normalisation process
-Un-normalised form: -
-First normal form(1NF)
 The single value should contain each table cell.
 Each record needs to be unique.
Example of the First normal form(1NF)
-Second normal form(2NF)
21

 Follow the rules of the first normal norm.
 The single column should be the primary key
Example of the Second normal form(2NF)
-Third normal form(3NF)
 Follow the rules of 3NF.
 3NF has no transitive functional dependencies.
Example of the Third normal form(3NF)
22

A completed ER diagram
23

A.C.2.2- Build a relational database system for the database design in A.C 2.1 using an
appropriate database software application.
Third normal form(3NF)
Ms-access: - Pseudo-relational database engine from Microsoft is Microsoft Access. Excel,
word, and outlook are the part of Microsoft office suite of applications. The jet Database
engine for data storage uses access. The stand-alone product of access is available for
purchase.
Small and large database deployments both are used in access. Visual Basic for applications
and Microsoft’s own SQL server database engine is the somewhat require to its easy to use
graphical interface, as with further applications & programme.
Tables of database system design
Figure 5: Academic manager table
Purpose- All the lecturer are allocated to what types of courses they want to teach.
24

Appropriate keys-Here we used primary key and foreign key. The primary key is
Academicmanager_id from Academic manager table and the Foreign key is units_id from
the unit table and lecturer_id from lecturer table.
Figure 6: Admin table
Purpose- Admin table used when students want to questionnaire and admission purpose.
Appropriate keys- Here we used primary key and foreign key. The primary key is Admin_id
from Admin table and the Foreign key is college_id from college table.
Figure 7: College table
Purpose- College have to assign all the duty is for admin and academic manager to allocate
according to with their students choose.
Appropriate keys- Here we used primary key and foreign key. The primary key is College_id
from College table and the Foreign key is lecturer_id from lecturer table.
Figure 8: Course table
Purpose- All the students have to choose a course for their skills and what they want on
which campuses.
Appropriate keys- Here we do not use any kind of primary key or foreign keys.
25

Figure 9: Lecturer table
Purpose- Lecturer table used to allocate to the lecturer to assign duty that which course
who get teaching on which class.
Appropriate keys- Here we used primary key and foreign key. The primary key is Lecturer_id
from Lecturer table and the Foreign key is course_id from course table.
Figure 10: Student table
Purpose- The course is given by the admin the students should choose them and admin
have to assign all the students to as per course.
Appropriate keys- Here we used primary key and foreign key. The primary key is
Students_id from Students table and the Foreign key is Course_id from Course table,
Units_id from Units table, College_id from College table.
Figure 11: Unit table
Purpose- There are various types of units are given in database as per year and course name.
26

Appropriate keys- Here we used primary key and foreign key. The primary key is Units_id
from Units table and the Foreign key is Course_id from Course table, Course_name from
Course table and Lecturer_id from Lecturer table.
Table Names Attributes Data Types PK/FK
Description of
Academic Manager
Academicmanager_id Number PK
Units_id Number FK
Lecturer_id Number FK
Description of Admin Admin_id Number PK
Admin_name Short Text
College_id Number FK
Description of College College_id Number PK
College_name Long Text
Lecturer_id Number FK
Description of Course Course_id Number PK
Course_name Long Text
Course_location Long Text
Description of Lecturer Lecturer_id Number PK
Lecturer_name Long Text
Lecturer_skills Long Text
Course_id Number FK
Description of Students Students_id Number PK
Students_name Long Text
Course_id Number FK
Units_id Number FK
College_id Number FK
Description of Units Units_id Number PK
Course_id Number FK
Course_name Long Text FK
Lecturer_id Number FK
27

A.C.2.3 Apply a range of database tools and techniques to enhance the user interface to
meet the given case study requirements.
Forms of given database system designs are: -
Figure 12: Academic manager tables of Form
Figure 13: Admin tables of Form
Figure 14: College tables of Form
28

Figure 15: Course tables of Form
Figure 16: Lecturer tables of Form
29

Figure 17: Students tables of Form
Figure 18: Units tables of Form
30

LO3 - Task 3. Be able to use manipulation and querying tools
A.C. 3.1 Explain the benefits of using manipulation and query tools in a relational
database system as per the requirements gave in the case study.
SQL (Structured Query Language)
SQL commands are used to interface with the database to execute particular functions,
queries, work, and tasks, with data and are coded int SQL statements.
Let’s take an example, we can create tables, or modify data, drop the table, set permissions,
add data to tables for users are also performs in these functions in the database, SQL
command is not only used searching the database they also perform various types of
function in this SQL command. SQL command is collected into four crucial classifications
depending on their functionality-
 DDL (Data Definition Language)
In this SQL command, DDL used for modifying, dropping & creating the formation
of database objects. TRUNCATE, CREATE, RENAME, ALTER and DROP is the command
of DDL.
 DML (Data Manipulation Language)
DML SQL command is used for retrieving, modifying, deleting and storing data.
DELETE, UPDATE, SELECT, INSERT is the command of DML.
 Transaction Control Language (TCL)
TCL SQL commands are used for managing changes affecting the records. ROLLBACK,
SAVEPOINT, and COMMIT is the command of TCL.
 Data Control Language (DCL)
DCL SQL commands providing safety to database objects. REVOKE and GRANT is the
command of DCL.
Benefits of using those commands in relation
 Interactive Language
31

Interactive language receives answers to the composite questions in second and
they can be used for interface with the database.
 No coding needed
By using SQL, it is very easy to control the database systems without any need to
note the considerable number of the code.
 Multiple Data views
In these multiple data views, users can make dis-similar types of views of database
and databases for dis-similar users.
 Portability
Portability of SQL commands is users can create their programs or database in
servers, even some of the mobiles phone, laptops, PCs.
Figure 19:Acedemic_manager query
Figure 20:Students query
32

Figure 21:Acedemic_manager SQL query
Figure 22: Students SQL query
33

A.C. 3.2 Implement a query language into the relational database system that has been
implemented in task 2.2
Figure 23: Query 1
Figure 24Query 2
Figure 25: Query 3
Figure 26Query 4
34

Figure 27: Query 5
Figure 28: Query 6
Figure 29: Query 7
35

Figure 30: Query 8
Figure 31: Design View of Query1
Figure 32: Design View of Query2
Figure 33: Design View of Query3
36

Figure 34: Design View of Query4
Figure 35: Design View of Query5
Figure 36: Design View of Query6
Figure 37: Design View of Query 7
37

Figure 38: Query 8 Design View
38

A.C. 3.3 Critically evaluate how meaningful data has been extracted through the use of
query tools for the given case study.
Figure 39: Query1
Query1 in these Course, Units and admin details are explained in this query.
Figure 40: Query2
Query2 in these Acedemic_manager, Lecturer, units, Course, Students details are explained
in this query.
Figure 41: Query3
Query3 in these Admin, Students, Units, Lecturer, Course details are explained in this query.
39

Figure 42: Query4
Query4 in these Students, Course details are explained in this query.
Figure 43: Query5
Query4 in these Acedemic_manager, Students, Course details are explained in this query.
Figure 44: Query6
40

Query5 in these Lecturer, Course, Units details are explained in this query.
Figure 45: Query7
Query6 in these Lecturer, Acedemic_manager, Units, Lecturer details are explained in this
query.
Figure 46: Query8
Query7 in these Admin, Course, Students, Course details are explained in this query.
41

LO4 -Task 4. Be able to test and document relational database systems
A.C. 4.1 Critically review and test the implemented relational database system
SNO FEEDBACK USERS1 USER2 USER3
1 The details of the
database are clear or
not?
Agree Disagree Don’t know
2 To accomplish what I
need to do, it takes a
few clicks or steps
Strongly Agree Agree Don’t know
3 Is database is easy to
navigate or not? Disagree Strongly
Agree
Agree
4 The database is user-
friendly Agree Strongly
Agree
Agree
5 All the information in
the database is
valuable?
Disagree Don’t know Agree
6 Are the details of the
database is accurate
or not?
Agree Strongly
Agree
Don’t know
Testing of Black Box -
Method- testing of Black Box is a software method in the implementation, design, internal
construction of things existence perform is not familiar to the tester.
Testing of White Box -
Method- testing of White Box is a software method in the design, internal construction,
executions of the things existence examine is familiar to the tester.
42

A.C. 4.2 Create documentation to support the implementation and testing of the
relational database system that has been implemented in Task 2.2
SNO Objectives Expected Result Actual Result Pass/Fail
1 You entered
wrong
Lecturer_name
fields in
Lecturer table
It should create
an error
message, isn’t
valid for this
field
Creates the
valid field size of
a numeric value
which was
smaller than the
size
Pass
2 First, you have
to enter the
Lecturer_id
If you skip
Lecturer_id
then they show
you error
You have
entered the
value of
Lectured_id
Pass
3 First, you enter
the Students_id
datatypes,
select from
them but
cannot skip
these records.
If you skip
entering your
Students_is
data type show
you error
You have to
select the data
types from
listed items
Pass
4 You cannot
change the
records
whenever it
exists on record
It should
generate a
wrong message
It generates
association
records is
related to table
Pass
5 You get
incorrect fields
of size
It should
produce an
error message
and its not valid
for these fields
Creates the
valid field size.
Pass
6 You entered the It should create Creates the Pass
43

wrong size of
fields
a wrong
message, isn’t
well-founded
for this field
well-founded
field size of a
numeric value
which was
smaller than the
size
Figure 47: Objective Plan 1
Figure 48: Objective Plan 2
44

Figure 49: Objective Plan 3
Figure 50: Objective plan 4
Figure 51: Objective Plan 5
45

Figure 52: Objective Plan 6
46

A.C. 4.3 Create user documentation for the developed relational database system in task
2.2
User Documentation
User documentation relates how a program is used, user documentation is different code
documents. In the instance of library software, user documents and code documents could
in some instance worth conjoining and effectively identical but this is not often true for
general application.
In the user documentation, helps the user in realizing each feature and describes each
feature of a program. Through troubleshooting assistance for good documents can also go
so far. These are very important for user documents the work should be up-to-date and not
be confusing. For the user documentation, it’s very important to have a thorough the guide
and don’t need to be well-ordered in any specific way.
In user documentation simplicity and stability is very valuable. User documentation is
considered to establish an agreement identifying what the software will do. User
documentation can be constructed in a variation of online and print formats. However, user
documentation can be well-ordered by three wide ways –
 List of Reference
The last type of arranging concept is one in which tasks or orders are simply listed
logically or alphabetical grouped, frequently via the cross-referenced guide. This final
approach of considerable use to advanced users who know absolutely what sort of
data they are looking for.
 Tutorial
For new users, a tutorial approach is considered the most useful, in which they are
guided through each step to achieving specific tasks.
 Thematic
A thematic approach, where chapters or sections focus on one specific zone of
attentiveness, is more common use to a middle user.
Benefits of User Documentation
 Good documentation will reduce your support costs
One less call or email to your support desk means every solution that your user finds
in the user guide or online help. Rather than explaining to a customer how to
47

operate a computer program, the support team can concentrate on finding answers
to real problems.
 Satisfied Users
Because of high quality written materials, the end user experience is more
successful. insufficient on-line help wastes valuable time, imaginary or poor user
manuals isolate customers and support that is not accessible instantly.
Figure 53: form of Accedemic_Manager
Figure 54: Form of Admin
Figure 55: Form of College
Figure 56: Form of Course
48

Figure 57: Form of Lecturer
Figure 58: Form of Students
Figure 59: Form of Units
49

A.C. 4.4 Explain how verification and validation have been addressed in the developed
relational database system.
V-Model
V-Model is also known as Verification and Validation model. In these model, an SDLC model
where implementation of procedure happens in a sequential manner.
For each corresponding growth of stage, the V-Model is the inclusion of the waterfall model
and is built on the union of a testing stage. There is a directly related testing phase for every
single phase in the development cycle in this model. The next phase starts only when the
first stage of compilation is done and this development of phase is an extremely-disciplined
model.
Figure 60: Design of V-Model
Verification Phases-
There are many types of verification phase, they are as follow-
 Coding phase
 Business Requirement Analysis
 Architectural Design
 Module Design
50

 System design
Validation Phases-
There are many types of validation phase, they are as follow-
 Acceptance Testing
 Unit Testing
 Integration Testing
 System Testing
Figure 61:Verification Phases
51

Figure 62:Validation Phases
52

A.C. 4.5 Explain how control mechanisms have been used in the developed relational
database system.
Control mechanisms used in a developed relational database system, they are-
 RBAC (Role Based Access Control)- In these model, the theme holds within an
organization the access to resources is ruled based. Because of the user inherits
advantage that is tied to his part RBAC is also called as non-optional Access Control.
The user cannot command the ruling that he was allocated. Advantages and
disadvantages of each of the access model have its own.
 DAC (Discretionary Access Control)- The user’s discretion is based on these access
control model. Based on his discretion the owner of the resources can give access
right on that resources to the other users. The typical examples of DAC are Access
Control Lists.
 MAC (Mandatory Access Control)- In this model, the files of MAC users and owners
are not confidential in determining who can access. With safety level, every matter
(users) and thing (resources) are classified and allocate. If the matter can allocate the
object, the safety labels of the matter and the thing along with the safety policy
control.
Figure 63: Acedemic_manager for access control mechanisms
53

Figure 64: Admin for access control mechanisms
Figure 65: college for access control mechanisms
54

Figure 66: Course for access control mechanisms
Figure 67: lecturer for access control mechanisms
Figure 68: Students for Access Control Mechanisms
55

Figure 69: Units for access control mechanisms
56

Conclusion-
Conclusion of this project is done by our team and college have faced their problems, we
have solved all the problems in database and elaborate all the data models, schema, ER
diagrams with their types and advantage and disadvantages, covered the verification and
validation topics with their example, control mechanisms developed by the relational
database system, all different types of approaches in database design and all the screen sort
of the database and their table names with example is given in this project.
57

References-
 Beynon-Davies, P. (2004). The database, Dbms and Data Model. Database Systems,
pp.30-47
 Bouneffa, M. and Boudjlida, N. (1995). Managing schema changes in object-
relationship databases. OVER '95: Object-Oriented and Entity-Relationship Modeling,
pp.113-122.
 Database Management System (DBMS). (2008). Encyclopedia of Genetics, Genomics,
Proteomics and Informatics, pp.470-470.
 Encyclopedia of GIS. (2008).
 Filax, M., Gonschorek, T. and Ortmeier, F. (2016). Correct Formalization of
Requirement Specifications: A V-Model for Building Formal Models. Reliability,
Safety, and Security of Railway Systems. Modeling, Analysis, Verification, and
Certification, pp.106-122.
 Langer, A. (2001). Documentation and Acceptance Testing. Analysis and Design of
Information Systems, pp.218-226.
 Miura, T., Matsumoto, W. and Shioya, I. (1999). Managing Meta Objects for Design
of Warehouse Data. DataWarehousing and Knowledge Discovery, pp.33-40.
 Objected-Oriented and Object-Relational DBMS. (2007). Fundamentals of Relational
Database Management Systems, pp.477-558.
 Relational Database Management Systems. (2009). Beginning Oracle Database 11g
Administration, pp.3-20.
 Schmidt, J. and Brodie, M. (1983). Analysis of Relational Database Management
Systems. Relational Database Systems, pp.49-559.
 Weik, M. (2000). entity-relationship data model. Computer Science and
Communications Dictionary, pp.526-526.
 Zdonik, S. and Wegner, P. (1988). Language and Methodology for Object-Oriented
Database Environments. Topics in Information Systems, pp.155-171.
58

Appendix
59