0% found this document useful (0 votes)
41 views11 pages

Dubai Property

The document provides a comprehensive overview of database types, focusing on relational and non-relational databases, their features, and user/system requirements. It discusses the importance of data normalization, security measures, and the role of databases in various sectors such as customer relationship management and data recovery. Additionally, it includes technical aspects such as data dictionaries, interface diagrams, and examples of normalization processes.

Uploaded by

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

Dubai Property

The document provides a comprehensive overview of database types, focusing on relational and non-relational databases, their features, and user/system requirements. It discusses the importance of data normalization, security measures, and the role of databases in various sectors such as customer relationship management and data recovery. Additionally, it includes technical aspects such as data dictionaries, interface diagrams, and examples of normalization processes.

Uploaded by

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

Dubai Properties

1
Contents
Dubai Properties...........................................................................................................1
General introduction about database:...........................................................................3
Types Of Data Base:.....................................................................................................4
Explanation for Relational Data Base:.........................................................................4
Features Of Relational DBMS:....................................................................................4
Explanation for Non- Relational Data Base:................................................................5
User Requirements:......................................................................................................5
System Requirements:..................................................................................................6
Data Dictionary:...........................................................................................................6
Interface Diagram:........................................................................................................6
Identifying The Requirement:......................................................................................7
SMART DRAW DIAGRAM:......................................................................................7
Normalization:..............................................................................................................8
Design For Fully – Functional System:......................................................................11
Security of System and Maintenance of Data Base:..................................................12
Extraction of data form query tool:............................................................................13
Examining The Requirement as per their needs:........................................................14
Advice For Improvement:..........................................................................................15

2
General introduction about database:
In computer data base in an organized collection of data or a type of data stored based on
the use of data base management system. MS Access consists of two type of data base the
first type data base is flat file data base which is used to store data in plain text and does
not accept multiple tables. The second type data base is relational data base, and the use
of this data base is to store data in forms that relate to each other. The main purpose of
data base is to provide access to multiple and manipulate the data simultaneously.

3
Types Of Data Base:
The different type of data base are as follows:

1) Relational Data Base


2) Non – Relational Data Base

Explanation for Relational Data Base:


In relational database, the data is organized into a table, also known as relation. To
relate a table in a database key feature is used, and its main purpose is to identify the
relationship between the tables. The relational database provides the user with some
benefits which include flexibility, data security and data integrity etc.

Example:
Costumer
Full Name
Address

Emirates ID

In this table the relational database is SQL (Structured Query Language). In relational
database design it consists of rows and columns. When new data is added then new
records are added into the existing table. Relationships can then be made between two
or more tables. Relational database works when data they contain does not change very
often.

Features Of Relational DBMS:


General information for data base used in different sectors:

Data base security refers to the range of tools which are used to design. Data base
security is used to prevent vulnerabilities used to secure threats. It is the element that
compromised in most data breaches.

The role of data base in different sectors are as follows:

1) Computer Security
2) Data Recovery
3) Customer Relationship management
4) Data Storage
5) Data Transformation

Explanation for the role in different sector:


 Computer Security: In this role any organization can store and manage data or
information and it can be used to support wide range of activity including data storage
data base has the capacity to organize and collect information that is stored and
controlled by data base management system (DBMS).
 Data Recovery: The key role of data base is to recover data, make sure that data
integrity and prevent data loss.

4
1) Roll back.
2) Commit
 Roll back: The idea behind this is to reverse the impact of information that was left
unfinished due to a system malfunction.
 Commit/Redo Recovery Technique: This is the method to use the records and the
changes made by the users and restore the data in its original position.

Explanation for Non- Relational Data Base:


Non-relational data sources are various from relational data sources because they save
their information in a non-relational data source. In a non - organized type non-
relational will certainly be based upon based upon information framework like record.
This is utilized to make as well as arrange numerous details plus it is adaptable than
relational data source.
Features of Non–Relational Data Base: Some features of non – relational data base
offers a range of features that are applicable to modern applications the main key
feature is that it allows user to change any business requirements and can be flexible.
They can capture large amounts of data or information.

User Requirements:
 User friendly interface: It is a user-friendly interface in which the user can easily
understand and can navigate through any applications, and it is a very effective and
efficient way to for self-explanation and does not require user to put much
information. And it helps to manage “IT” queries.
 Efficient Query Logging: The users should be allowed to log in to their IT queries
easily and include the information they provide. Such as caller details, name,
helpdesk operator information and time of call.
 Problem Categorization: The system should allow users to help desk operator to
categorize problems correctly and efficiently which is selected from any lists of
problem type.
 Caller Information Retrieval: The users should be able to collect or retrieve any
type of information they are provided with such as information that is provided in
name, ID, job title and department.
 Problem Reference System: The user should easily refer any type of problem to any
specialist suggesting the correct solution. And the expert should solve any problem
based on the nature of the issue.
 Workload Management: The operator should be able to solve problems and view
the workload of the specialist finding the number of on-going problems for each
expert.
 Resolution Recording: The user should be able to monitor the date and time and
resolution detail once the problem is resolved so that the record issue is solved.

System Requirements:
 Relational Database System: The system must be constructed using a relational
database model to guarantee data is stored in a structured and organized manner.

 Optimization: The database system needs to be designed for optimal performance to


ensure fast access and handling of data.

5
 Security Measures: Place strong security measures to safeguard sensitive data,
making sure that only authorized individuals can access and alter information.

 Scalability: The system should be designed with scalability in mind to cater for the
company's projected growth and a rising number of IT inquiries.

 Backup and Recovery: Dubai property company should emphasize the need to set
up consistent backup practices and a dependable recovery system. This is crucial in
protecting against data loss and ensuring easy restoration of systems when necessary.
 Documentation and Training: Ensure that the company offers system
documentation and training materials to users enabling them to grasp and make the
most of the system efficiently.

Data Dictionary:
A data dictionary is a collection of data with name, definition and attributes that
contain data elements that can be used or stored in a database, information system, or
any part of a research project. A data dictionary includes spreadsheets, web
applications and other example are as follows:

 Data Validation
 Data Relationships
 Primary Key
 Foreign Key

Interface Diagram:

What is the meaning of ERD (Entity Relationship Diagram): An Entity relationship


diagram (ERD) that is also referred to as an entity relationship model is a graphical pictorial
of relationships among people, objects, places, concepts, or events within the information
technology (IT) system. An ERD is built on techniques of data modeling and that will allow
business logic definition and participating as a binary. It tells the user and other people the
relationship between the “Entity”, “Fields” and the “Relationship” that are present in it. It

6
consists of different shapes that represent different connections and picture two valuable
information which include “Entity” and the second thing is “Inter – relationship” that is
among the entities.
 Entity: They are objects that have the concept of representing valuable information and
data. They are nouns such as product, customer name, location etc. There are three types of
Entity that are commonly used witch are as follows:
1. Strong Entity
2. Weak Entity
3. Associative Entity
 Relationship: It is utilized in such a way to identify interplay between two objects or
parameters. Relationship is therefore concerning the real and understandable information to
describe and explain the relationship between two entities.
 Attributes: They are the kind if entity that help users to understand database better
Attributes are included in detailed in the diagram bellow. With an example.

Identifying The Requirement:


After identifying the requirement, we can easily identify the entity that are mentioned
below.
Caller Detail: This include caller ID, Caller Name, Job Title, Department.
Specialist: This include Specialist Name, Specialist Department, Problem.
Help Desk Operator: This include Help Desk ID, Help Desk Department.
Problem: This include Problem ID, Problem Type, Problem Number.
Equipment: Equipment ID, Valid License, Operating System.

SMART DRAW DIAGRAM:

We use the Smart Draw tool that allow us to design ERD and more than that it is simple to
use and understandable as well. Like that it gives us templates in which we input data by
ourselves. And there could be yet disparate approaches of tailored design smart draw based
on user's choice.

• Data Normalization:

Not only does normality ends up terminating data but also maintaining data is another benefit
of normalization.

7
• Assessment of Design:

1. Abide by simplicity in the role of help desk operator.

2. The traced solutions: resolved problems.

3. Gathers and verifies complete information.

4. Adaptable for future income volatility.

Therefore, this executive design intends to setup a comprehensive, yet efficient, data structure
that will now be used to accomplish a structured approach in their IT Helpdesk operations.
Such were the modifications that always referred to the appliance of preferred technology and
special equipment matching the organization.

Roll Number Name Address Phone Number


1 Ali Karachi 054-145699-0, 055-749514-0

2 Sameer India 050-789104-8, 054-736541-7

Normalization:
It is the proves in which we remove unwanted things and rearranging it according to
user requirement in database, it includes tables and making the relationship that is
between the two tables this enable user to reduce any data to enable data redundancy
and data inconsistent.

Category of Normalization:

 1NF: It stand for “First Normal Form” this is the first step that is done the feature of
1NF is that it cannot hold multiple values or data. It can only hold single value.

Consider a random example for 1NF.

Scenario 1: Consider a relation student which include Roll number, Name, Address and
Phone Number.

In the above table we can clearly see that the data is not repeated but the issue is that the
“Phone Number” is the only thing that it has more then one attributes it means that it is
having many numbers for a single user.

8
If we make the same table that is above but we will creating new row for “Phone
Number”

Roll Number Name Address Phone Number


1 Sameer Lahore 050-789104-8
1 Sameer Lahore 050-789104-8
2 Ali Panjab 054-145699-0
2 Ali Panjab 054-145699-0

Now in the above table we can see that it contain more than one data which is due to
“Phone Number.” And because of this we did repeat all the information that are related
to student so to fix this issue we have to separate Phone attribute from the above table.
To do that we have to divide the above table let us say “Group 1 and Group 2” be the
two parts of the tables and this concept is called “Normalization”.

If we divide the table into two group, then let’s us consider Group 1 and Group 2.

Group 1: Roll Number, Repeating Data


Group 2: Roll Number, Address and Nam
Table Of Group 1:

Roll Number Phone Number


1 050-789104-8
1 050-789104-8
2 054-145699-0
2 054-145699-0

Now we will make the table of Group 2:


Roll Number Name Address
1 Khazer Lahore
2 Adeel Karachi

Group 1 and Group 2 are in 1NF.

Key of Group 1 = Roll Number

Key of Group 2 = Roll Number, Phone Number.

 2NF: When the table is said to be in 1NF but has no non – prime attributes. A Relational
non – prime attributes refers to that kind of attributes which has subset in their relations. A
non – prime attributes always refers to that kind of attributes that is not a prat of the table
with means that data is unique and cannot be found in another table. 2NF partially depends
on primary keys.

Consider an example of school:

Scenario 1: Consider a school which stores information of teacher which includes subject,
teacher’s ID, and teacher’s Age.

9
Teacher ID Subject Teacher Age
50 Math 30
50 Computer 30
47 Biology 35
82 Chemistry 38
82 English 38

In the above table there are violation of 2NF in which non – prime attributes with is
“Teacher Age” depends on “Teacher ID” and it is a proper subset of candidate key.

To convert the given table into 2NF we divide the tables into two Groups.

Group 1 table for “Teacher Details”:

Teacher ID Teacher Age


25 30

47 35

82 38

Now we make the table for Group 2 for “Teacher’s Subject.”

Teacher’s ID Subject
25 Chemistry
25 Biology
47 Math
82 English
82 Computer

Group 1 and Group 2 are in 2NF.


Key of Group 1 = Teacher’s ID
Key of Group 2 = Teacher’s ID and Subject.

 3NF: In 3NF there is no data duplication. It is used to achieve data integrity there is not non – prime
attributes then only the table is said to be in 3NF.

Example: If we take one example to make the concept clear for 3NF is that

10
Scenario 1: If we take a scenario of an “Employee” that is working in a random company and now
we must create a table for that.
Employee ID Employee Name Employee Zip Codes Employee State Employee City
221 Ali 201313 Paris Taxis

331 Haris 57145 Dublin Ohio

441 Adeel 635987 Milan Michigan

554 Hamza 65210 Warsaw Indiana

662 Aliyan 32679 Landon Kentucky

The primary key in this table is “Employee ID.”

The non – prime attributes are all that are mentioned in the table except “Employee ID.”

In the above table “Employee State” and “Employee City” is violating the rule of 3NF so must
move them in a new table “Employee”.
Employee Zip Code Employee State Employee City
201313 Paris Taxis
57145 Dublin Ohio
635987 Milan Michigan

65210 Warsaw Indiana


32679 Landon Kentucky

11

You might also like