ASSIGNMENT OF UNIT 1

Question-1 what is the difference between File management and Database management.
Answer – file management system

A file management system is a collection of programs that manage and store data in files and folders in a computer hard
disk. A file management system manages the way of reading and writing data to the hard disk. It is also known as
conventional file system.
This system actually stores data in the isolated files which have their own physical location on the drive, and users
manually go to these locations to access these files. It is the easiest way to store the data like text, videos, images,
audios, etc. in general files. Data redundancy is high in file management system, and it cannot be controlled easily. Data
consistency is not met, and the integration of data is hard to achieve.
Operating System such as Linux and Windows has its own file system.
For example, NTFS is the Windows file system, and EXT is the Linux file system.
These operating systems provide less security to these files where they have options such as hide files, locks, and sharing
on files.

Database management system

 The Database Management System or DBMS is an effective or easy way to store the data, mainly when data
maintenance and security are the primary concern of the user.
 The database management system stores the data or information in the form of interrelated tables and files.
 In this type of system, data security is maximized using encryption/decryption, password protection, granting
authorized access and others.
 DBMS helps users to easily retrieve, insert, and manipulate data in a database.
 It also helps to perform data recovery, transactions, and many more.
Handling DBMS is difficult than the file system, but it provides more advantages than a file system.

Question -2 : explain data models and its types.

Answer: Data Model
Data Model gives us an idea that how the final system will look like after its complete implementation. It defines
the data elements and the relationships between the data elements. Data Models are used to show how data is
stored, connected, accessed and updated in the database management system. Here, we use a set of symbols and
text to represent the information so that members of the organisation can communicate and understand it.
Though there are many data models being used nowadays but the Relational model is the most widely used
model. Apart from the Relational model, there are many other types of data models about which we will study in
details in this blog. Some of the Data Models in DBMS are:

1. Hierarchical Model
2. Network Model
3. Entity-Relationship Model
4. Relational Model
5. Object-Oriented Data Model
6. Object-Relational Data Model
7. Flat Data Model
8. Semi-Structured Data Model
9. Associative Data Model
 10. Context Data Model
Question -3: explain architecture of database.
Answer: The design of a DBMS depends on its architecture. It can be centralized or decentralized or hierarchical.
The architecture of a DBMS can be seen as either single tier or multi-tier. An n-tier architecture divides the whole
system into related but independent n modules, which can be independently modified, altered, changed, or
replaced.
In 1-tier architecture, the DBMS is the only entity where the user directly sits on the DBMS and uses it. Any
changes done here will directly be done on the DBMS itself. It does not provide handy tools for end-users.
Database designers and programmers normally prefer to use single-tier architecture.
If the architecture of DBMS is 2-tier, then it must have an application through which the DBMS can be accessed.
Programmers use 2-tier architecture where they access the DBMS by means of an application. Here the
application tier is entirely independent of the database in terms of operation, design, and programming.
3-tier Architecture
A 3-tier architecture separates its tiers from each other based on the complexity of the users and how they use the
data present in the database. It is the most widely used architecture to design a DBMS.

 Database (Data) Tier − At this tier, the database resides along with its query processing languages. We
also have the relations that define the data and their constraints at this level.
 Application (Middle) Tier − At this tier reside the application server and the programs that access the
database. For a user, this application tier presents an abstracted view of the database. End-users are
unaware of any existence of the database beyond the application. At the other end, the database tier is not
aware of any other user beyond the application tier. Hence, the application layer sits in the middle and acts
as a mediator between the end-user and the database.
 User (Presentation) Tier − End-users operate on this tier and they know nothing about any existence of
the database beyond this layer. At this layer, multiple views of the database can be provided by the
application. All views are generated by applications that reside in the application tier.
Multiple-tier database architecture is highly modifiable, as almost all its components are independent and can be
changed independently.
Question -4: explain entity, Relationship and attributes with example.
Answer: Entity: Entity in DBMS can be a real-world object with an existence, For example, in
a College database, the entities can be Professor, Students, Courses, etc.
Entities has attributes, which can be considered as properties describing it, for example, for Professor entity, the
attributes are  Professor_Name, Professor_Address, Professor_Salary, etc. The attribute value gets stored in
the database.

Relationship: One-to-One Relationship

Under One-to-One (1:1) relationship, an instance of entity P is related to instance of entity Q and an instance of
entity Q is related to instance of entity P.
Let us see an example −
A person can have only one passport, and a passport is assigned to a single person.

One-to-Many Relationship
Under One-to-Many (1:N) relationship, an instance of entity P is related to more than one instance of entity Q and
an instance of entity Q is related to more than one instance of entity P.
Let us see an example −
A Person can have more than one Bank Accounts but a bank account can have at most one person as account
holder.

Many-to-Many Relationship
Under Many-to-Many (N:N) relationship, more than one instance of entity P is related to more than one instance of
entity Q. For more than one instance of entity Q is related to more than one instance of entity P.
Let us see an example −
A person can have more than one skills. More than one person can attain a skill.
Attributes
In RDBMS, a table organizes data in rows and columns. The columns are known as attributes whereas
the rows are known as records.

Example: A school maintains the data of students in a table named “student”. Suppose the data they
store in table is student id, student name & student age. To do this they have had three columns in the
table: student_id, student_age, student_name. The table looks like this:

student_id student_age student_name

101 12 Jon

102 13 Arya

103 12 Sansa

Here student_id, student_age and student_name are the attributes.