Database design (entity attribute and its types) unit 2 part 4

Sep 4, 2019Download as PPTX, PDF2 likes357 views

This document discusses database design and different types of attributes. It explains that each entity is described by a set of attributes. There are several types of attributes: simple attributes which are single-valued, composite attributes which are hierarchies of other attributes, multivalued attributes which can have multiple values per entity, and derived attributes which are calculated from other stored attributes. The document provides examples of each type of attribute from an employee entity to illustrate the different attribute types.

Unit -2
DATABASE DESIGN (ENTITY (OBJECT), ENTITY SET, ENTITY TYPE -
PART 3
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 1

Database Design (Attributes)
Attributes
Each entity is described by a set of attributes
(e.g., Employee = (Name, Address, Birthdate (Age), Salary).
Each attribute has a name, and is associated with an entity and a
domain of legal values. However, the information about attribute
domain is not presented on the Entity Relationship Diagram.
In the entity relationship diagram, shown in Figure, each attribute is
represented by an oval with a name inside.
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 2

Database Design (Attributes)
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 3
Employee
Name Salary Birthdate Address

Database Design (Attributes)
Types of Attributes
There are a few types of attributes you need to be familiar with.
Some of these are to be left as is, but some need to be adjusted to
facilitate representation in the relational model. This first section will
discuss the types of attributes.
◦ Simple Attributes
◦ Composite Attributes
◦ Multivalued Attributes
◦ Derived Attributes
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 4

Database Design
(Attributes)
Simple attributes
Simple attributes are
those drawn from the
atomic value domains;
they are also called
single-valued attributes.
In the COMPANY
database, an example of
this would be:
Name = {Ram} ;
Salary = {4141}
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 5
Employee
Name Salary Birthdate Address
Simple Attributes

Database Design
(Attributes)
Composite attributes
are those that consist
of a hierarchy of
attributes. Using our
database example,
and shown in Figure
Address may consist
of Number, Lane and
Area. So this would be
written as →
Address = {A - 11 +
‘Lane 3’ + ‘Shatabdi
Puram, Gwalior’}
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 6
Employee
Name Address Birthdate Salary
Number Lane Area
Composite Attributes

Database Design
(Attributes)
Multivalued attributes
Multivalued attributes
are attributes that have
a set of values for each
entity. An example of a
multivalued attribute
from the COMPANY
database, as seen in
Figure, are the degrees
of an employee: BSc,
MIT, PhD.
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 7
Employee
Degree
Name Address Birthdate
Salary

Database Design
(Attributes)
Derived attributes
Derived attributes are
attributes that contain
values calculated from
other attributes. An
example of this can be
seen in Figure. Age can
be derived from the
attribute Birthdate. In
this situation, Birthdate is
called a stored attribute,
which is physically saved
to the database.
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 8
Employee
Name
Address Birthdate Salary
Age

References
1. https://resources.saylor.org/wwwresources/archived/site/wp-
content/uploads/2014/12/CS403-1.10-Database-Design-2nd-Edition-CCBY.pdf
2. Database System Concepts 6th edition by korth and Sudarshan
9/4/2019 DATABASE DESIGN (ENTITY - ATTRIBUTES AND ITS TYPES) -UNIT 2 PART 4- BY RAM K PALIWAL 9

The document outlines the content of a Tableau course, including topics such as data warehousing concepts, SQL, business intelligence, Tableau desktop fundamentals, filtering and sorting data, creating charts and maps, calculated fields, dashboards, data blending, migration, administration, and integration with R. It also describes three live projects using Tableau as a business intelligence reporting tool in the insurance, banking, and retail domains.

Case Problem: Frame.xlsxViscKand

Jeri Carbone owns Frame Financial, a small financial consulting firm. She maintains Excel workbooks with information on companies and their stock market activity. She asks you to complete a workbook with information on Harriman Scientific by adding charts describing the company's financial status and stock performance. You are instructed to add a pie chart showing the company's shareholders, add data bars to values in one range, and move a 3D clustered column chart of revenue and expenses to a different worksheet.

Microsoft excelJismy James

The document provides an overview of the Insert menu in Microsoft Excel. It describes various options for inserting tables, illustrations like pictures and clip art, different types of charts including column, line, pie, and bar charts, hyperlinks, text boxes, headers and footers, word art, signature lines, objects, and symbols. Pivot tables and tables are mentioned as ways to arrange, summarize, sort, and filter complicated data. A variety of chart types are listed and described for visualizing different types of data.

Chapter-3 Data Modeling Using the Entity-Relationship ModelRaj vardhan

The document describes conceptual database design using the entity-relationship (ER) model. It discusses key concepts of the ER model including entities, attributes, relationships, and relationship constraints. An example ER diagram is presented for a COMPANY database with entities for employees, departments, and projects. Relationships include employees working for departments and departments controlling projects. The summary provides an overview of the important concepts and examples covered in the document related to conceptual database design using the ER model.

Data Modeling Using the Entity-Relationship (ER) Model.pptMutwakilElsadig

3 data modeling using the entity-relationship (er) modelKumar

This document provides an overview of the key concepts in entity-relationship (ER) modeling for database design. It begins with an outline of the database design process and an example database application for a company (COMPANY). It then defines the core components of ER modeling, including entities, attributes, relationships, relationship types, and ER diagrams. The document presents the initial ER design for the COMPANY database and refines it by introducing relationships. It also covers additional concepts like weak entity types, constraints, and recursive relationships. The overall summary provides a high-level introduction to ER modeling concepts and how they are applied to design a sample database schema.

assigAssignment 2.docxAssignment 2 LASA 1 Designing a Human.docxfredharris32

assig/Assignment 2.docx Assignment 2: LASA 1: Designing a Human Resources Database Description of LASA: For this assignment, you will design a basic human resources database for a fictional software company. Scenario: You are a freelance database designer who has just been contacted by a small software development company named Altair Software. The president of the company has asked you to create a database that will house employee information. The company currently has eight employees and comprises one president, two vice presidents, three programmers, and two sales representatives. The company wants you to create a scalable database that will grow as the company grows. They want to store the following information within the database: Information Required Maximum Value Employee ID 6 integers Employee Last Name 30 characters Employee First Name 30 characters Street Address 60 characters City 30 characters State 2 characters ZIP Code 5 integers Department 30 characters Manager 60 characters Position 30 characters Salary 8 integers The president of the company has given you a document that contains all of the above information for each employee. Click here to view the document having employee information. Tasks: You need to create spreadsheets in Microsoft Excel that accomplish the following: 1. Display a database table in first normal form that will store all of the information listed above. Identify a field or fields to act as the primary key bybolding that field name. Enter all of the provided information into the table in the spreadsheet. Save your spreadsheet as M3_A2_Lastname_Firstname_FirstNormalForm.xls. 2. Decompose the table you created in Step 1 to second normal form. Place each table in its own sheet within the spreadsheet. Identify a field or fields to act as the primary key in each table by bolding that field name. You may insert a new field to act as the primary key if you feel it is warranted. Enter all of the provided information into the appropriate table in the spreadsheet. Save your spreadsheet as M3_A2_Lastname_Firstname_SecondNormalForm.xls. 3. Decompose the table or tables you created in Step 2 to third normal form. Place each table in its own sheet within the spreadsheet. Identify a field or fields to act as the primary key in each table by bolding that field name. You may insert a new field to act as the primary key if you feel it is warranted. Enter all of the provided information into the appropriate table in the spreadsheet. Save your spreadsheet as M3_A2_Lastname_Firstname_ThirdNormalForm.xls. In addition, in a 2- to 3-page Microsoft Word document, you need to: · Share your planning strategy to complete the database. · Create an entity-relationship diagram from the tables that you designed above using crow's foot notation. Be sure to note the cardinality and modality for each relationship. · Explain why you selected the links between each of the database tables. Write in a clear, concise, and organized manner; demon ...

3. R- list and data framekrishna singh

Preparing for BIT – IT2301 Database Management Systems 2001dGihan Wikramanayake

Data Modeling Using the EntityRelationship (ER) Modelsontumax

The document provides an overview of entity-relationship (ER) modeling and the ER diagram notation. It discusses key ER modeling concepts like entities, attributes, relationships, and relationship constraints. An example database schema for a company is used to illustrate these concepts. The example requirements are analyzed to identify entity types, relationship types, and refine the initial design. Notation for displaying entity types, relationships, and constraints in ER diagrams is also described.

ikd312-03-designAnung Ariwibowo

The document discusses concepts related to entity relationship (ER) modeling, including: - It provides an example database application for a company to illustrate ER concepts. - It describes key ER modeling concepts such as entities, attributes, relationships, relationship types, and weak entities. - It explains ER diagram notation for representing entities, attributes, relationships, and cardinalities. - It shows an ER diagram for the example company database schema.

Sql Server 2000Om Vikram Thapa

Chapter03 database system in computer.pptubaidullah75790

Chapter03 (2).pptabhilashbachu5

This document discusses conceptual database design using the Entity-Relationship (ER) model. It provides an overview of the database design process and introduces an example database application for a company. The key concepts of the ER model are explained, including entities, attributes, relationships and relationship types. Finally, an ER diagram is shown modeling the entity types and relationships for the example company database application.

Written by Dr. Preiser 1 CIS 3100 MS Access Assignment .docxtroutmanboris

Written by Dr. Preiser 1 CIS 3100 MS Access Assignment Database Design and Implementation Project Health Care Benefits Database for Irrigation Equipment Specialists Inc. 50 points This assignment is worth 10% of your grade. DUE DATE: See Course Schedule Academic Integrity This is an individual assignment. Collaboration with another student is not allowed. Any sharing of work or factual data between students constitutes academic dishonesty as defined in the University Catalog. All work must be original for this project in this quarter. You may not use work from other classes or courses to fulfill this assignment. Failure to adhere to this requirement will result in an “F” grade for the class. Project Objectives: This project is designed to give you a better understanding of how data can be organized into a relational database and then used to provide answers to management queries and to extract information for reports. The software we will be using this assignment is Microsoft Access 2010, 2013 or 2016. If you use a Mac, you must save the file as a Windows Access file before submittal.  Note: CPP email servers block Access files so don’t email files to instructor or TA. Project Background: Irrigation Equipment Specialists employs 100 employees who specialize in purchasing parts and supplies (inbound logistics), shipping products to customers (outbound logistics), order fulfillment (sales and marketing), product support (service), and the administrative functions of information technology infrastructure / systems development, planning, research and development, human resources, and financial management. IES’s management recognizes that its employees have different health care needs, and thus, provides them with a flexible benefits plan. For medical insurance, an employee must enroll with either a preferred provider organization (PPO) or a health maintenance organization (HMO). IES currently pays the monthly medical premiums for its employees. However, if an employee enrolls in a dental or vision plan, the employee must pay a small monthly premium for the optional plan. An employee may carry, medical, dental, and/or vision coverage for one or more of its family members. In order to carry insurance on a family member, the employee must carry the same coverage for himself/herself. For example, to carry a vision insurance on a child (or a spouse), the employee must also carry vision insurance on himself/herself. In the past, the Human Resources Department of IES administered health benefits enrollment and analysis functions manually, with a minimal support of Excel spreadsheets and Word documents. The manual process was time-consuming, error prone, and inefficient. Written by Dr. Preiser 2 The health benefits enrollment process at IES will begin in several months, and Mr. David Andrews, the Human Resource Director of IES, has hired you, as a database consultant, to design, d.

Description of dataJohnna Mae Yodico

This document describes different types of data and data structures. It discusses numeric data types like integers and reals, and non-numeric types like character strings and logical values. Common data structures include arrays, tables, files with records and fields, and static versus dynamic structures. Arrays allow grouping of related data elements and tables are multi-dimensional arrays. Records contain grouped fields of related data items. Files are collections of logically related records.

Chapter03Reham Maher El-Safarini

This document discusses the entity-relationship (ER) model for data modeling. It provides an overview of the database design process and introduces an example database schema for a company. The key concepts of the ER model are explained, including entities, attributes, entity types, keys, relationships, relationship types, and ER diagrams. For the example company database, initial entity types and relationships are identified from the requirements. The design is then refined by introducing additional relationships. Constraints for relationships and weak entity types are also covered.

ch03-Data Modeling Using the Entity-Relationship (ER) Model.pptkizza6

Chapter03.pdfHughMungus22

This document provides an overview of entity-relationship (ER) modeling and its application to conceptual database design. It discusses key ER concepts like entities, attributes, relationships and relationship types. An example database application for a company is used to demonstrate how these concepts are identified and modeled. The initial ER design for this example captures entity types for departments, projects, employees and dependents along with some of their attributes. The design is then refined by introducing relationship types to fully represent the requirements.

Dbms ii mca-ch3-er-model-2013Prosanta Ghosh

The document discusses the process of conceptual database design using an Entity-Relationship (ER) model. It begins by outlining the main steps: 1) requirements collection and analysis, 2) creating a conceptual schema using a high-level data model, 3) logical design mapping the conceptual schema to a implementation data model, and 4) physical design specifying storage structures. It then provides an example database for a company, describing the key entities, attributes, and relationships between employees, departments, projects, and dependents. Finally, it introduces some basic concepts of ER modeling including entities, attributes, relationships, cardinalities, and weak entities.

SAP E Recruitment - ERec600_SystemArchitecture.pdfSureshKumar820241

E r modelsantoshsaini22

"Comprehensive Guide to Effective Database Design PrinciplesEliasZerabruk

May Woo Bi Portfoliomaywoo

Conceptual Data Modelling Using ER-modelsShailaja Jayaprakash

The document discusses conceptual data modeling using entity-relationship (ER) models. It defines key concepts in ER modeling such as entities, attributes, relationships, cardinalities, and participation constraints. Entities can have attributes and relationships with other entities. Relationships have cardinality constraints that specify how many entities can participate in a relationship, such as one-to-one, one-to-many, or many-to-many. Participation constraints specify whether an entity's participation in a relationship is mandatory or optional. Together, cardinalities and participation constraints specify the structural constraints of relationships in an ER model.

ch03-Data Modeling Using the Entity-Relationship (ER) Model.pdfRounakSaha34

Mis classification By Ram K PaliwalRam Paliwal

The document categorizes information systems as either operations support systems or management support systems. Operations support systems process transactional data to support daily business operations, including transaction processing systems, process control systems, and office automation systems. Management support systems provide information and decision support, including management information systems, decision support systems, executive support systems, and enterprise systems which integrate business functions across an organization.

Management inofrmation system basics by ram k paliwalRam Paliwal

This document defines information systems and describes their key components. It provides several definitions of information systems that focus on the technological components (hardware, software, data) that make up information systems and their role in supporting organizational processes and decision-making. The document outlines the five core components of information systems: hardware, software, data, people, and processes. It provides a brief description of each component, emphasizing that while technology is important, people and processes are what truly define information systems.

Database design (entity, entity set and entity type) unit 2 part 3Ram Paliwal

The document discusses database design concepts including entities, entity sets, and entity types. An entity is an object in the real world that can be differentiated from other objects. An entity set is a collection of similar entities at a point in time. The document also describes different types of entities such as independent entities, dependent entities, and characteristic entities. Independent entities are the core tables in a database, while dependent entities rely on other tables and characteristic entities provide additional details about other entities.

Database design (conceptual, logical and physical design) unit 2 part 2Ram Paliwal

More Related Content

Similar to Database design (entity attribute and its types) unit 2 part 4 (18)

Preparing for BIT – IT2301 Database Management Systems 2001dGihan Wikramanayake

Data Modeling Using the EntityRelationship (ER) Modelsontumax

ikd312-03-designAnung Ariwibowo

Sql Server 2000Om Vikram Thapa

Chapter03 database system in computer.pptubaidullah75790

Chapter03 (2).pptabhilashbachu5

Written by Dr. Preiser 1 CIS 3100 MS Access Assignment .docxtroutmanboris

Description of dataJohnna Mae Yodico

Chapter03Reham Maher El-Safarini

ch03-Data Modeling Using the Entity-Relationship (ER) Model.pptkizza6

Chapter03.pdfHughMungus22

Dbms ii mca-ch3-er-model-2013Prosanta Ghosh

SAP E Recruitment - ERec600_SystemArchitecture.pdfSureshKumar820241

E r modelsantoshsaini22

"Comprehensive Guide to Effective Database Design PrinciplesEliasZerabruk

May Woo Bi Portfoliomaywoo

Conceptual Data Modelling Using ER-modelsShailaja Jayaprakash

ch03-Data Modeling Using the Entity-Relationship (ER) Model.pdfRounakSaha34

Preparing for BIT – IT2301 Database Management Systems 2001dGihan Wikramanayake

Data Modeling Using the EntityRelationship (ER) Modelsontumax

ikd312-03-designAnung Ariwibowo

Sql Server 2000Om Vikram Thapa

Chapter03 database system in computer.pptubaidullah75790

Chapter03 (2).pptabhilashbachu5

Written by Dr. Preiser 1 CIS 3100 MS Access Assignment .docxtroutmanboris

Description of dataJohnna Mae Yodico

Chapter03Reham Maher El-Safarini

ch03-Data Modeling Using the Entity-Relationship (ER) Model.pptkizza6

Chapter03.pdfHughMungus22

Dbms ii mca-ch3-er-model-2013Prosanta Ghosh

SAP E Recruitment - ERec600_SystemArchitecture.pdfSureshKumar820241

E r modelsantoshsaini22

"Comprehensive Guide to Effective Database Design PrinciplesEliasZerabruk

May Woo Bi Portfoliomaywoo

Conceptual Data Modelling Using ER-modelsShailaja Jayaprakash

ch03-Data Modeling Using the Entity-Relationship (ER) Model.pdfRounakSaha34

More from Ram Paliwal (20)

Mis classification By Ram K PaliwalRam Paliwal

Management inofrmation system basics by ram k paliwalRam Paliwal

Database design (entity, entity set and entity type) unit 2 part 3Ram Paliwal

Database design (conceptual, logical and physical design) unit 2 part 2Ram Paliwal

Database development life cycle unit 2 part 1Ram Paliwal

The document discusses the database development life cycle (DDLC), which is a six-phase process for designing, implementing, and maintaining a database system to meet an organization's information needs. The six phases are: 1) database initial study, 2) database design, 3) implementation and loading, 4) testing and evaluation, 5) operation, and 6) maintenance and evolution. Each phase is described in detail, from analyzing requirements in the initial study to ongoing maintenance activities once the database is operational.

Memory hierarchy unit 2 by ram k paliwalRam Paliwal

Cpu register, instruction exucution and interrupts unit 1 by ram k paliwalRam Paliwal

System component and system calls unit 1 by ram k paliwalRam Paliwal

The document discusses the components and system calls of the Windows operating system. It describes the main layers as the hardware abstraction layer, kernel, and executive which run in kernel mode. User-mode subsystems include environmental and protection subsystems. The main system call types are process control, file manipulation, device manipulation, information maintenance, and communications. Process control calls include creating and terminating processes while file manipulation calls involve opening, reading and writing files.

Sdlc spiral model in software engineering basics by ram k paliwalRam Paliwal

The document discusses software process models and the spiral model in particular. It notes that prescriptive process models brought order to software development but work remains complex. The spiral model is an evolutionary model that combines iterative prototyping with controlled aspects of waterfall. With spiral, software is developed through a series of evolutionary releases from initial prototypes to more complete versions. Each pass through the planning phase allows for adjustments to the project plan based on customer feedback.

Types of operating system unit 1 by Ram K PaliwalRam Paliwal

The document discusses the main types of operating systems: serial processing, batch processing, time-sharing, real-time, and multi-user/multi-tasking network operating systems. Serial processing operating systems execute instructions sequentially without user interaction. Batch processing groups similar jobs into batches to be processed when the computer is idle. Time-sharing operating systems allow multiple users or programs to share resources by rapidly switching between tasks. Real-time operating systems are used for systems like robots where response time is critical. Network operating systems manage shared resources, users, security, and applications over a private network.

Software project planning in software engineering by ram k paliwal unit 2Ram Paliwal

Software reuirement elicitation in software engineering basics by ram k paliwalRam Paliwal

Srs (software requirement specification) in software engineering basics by ra...Ram Paliwal

The document discusses software requirement specification (SRS), which defines the necessary functional and non-functional requirements for a software system from the user's perspective. An SRS is developed through an agreement between the customer and contractors. It should have characteristics like correctness, completeness, consistency, unambiguity, modifiability, verifiability and testability. The SRS is used to guide software development and testing.

Sdlc process models in software engineering basics by ram k paliwalRam Paliwal

Database models unit 1 part 2Ram Paliwal

Database overview unit 4 part 1Ram Paliwal

Database development life cycle unit 2 part 1Ram Paliwal

The database development life cycle (DDLC) is a six-phase process for designing, implementing, and maintaining a database system to meet an organization's information needs. The six phases are: 1) initial study, 2) design, 3) implementation and loading, 4) testing and evaluation, 5) operation, and 6) maintenance and evolution. In the initial study phase, the current system is examined to analyze problems, define objectives and scope. The design phase focuses on creating the database model. In implementation, the design is executed by installing the DBMS, creating databases, and loading data. Testing and evaluation ensures the database performs as expected. During operation, the completed system is used. Maintenance involves routine activities like backups

Operating system basics function of os unit 1 by ram k paliwal part 1Ram Paliwal

The document discusses the basics of operating systems and computer systems. It defines an operating system as a program that manages a computer's hardware and acts as an intermediary between the user and computer. A computer system consists of hardware components like the CPU and memory, an operating system, application programs, and users. The operating system controls hardware usage and coordinates application programs for users. It describes functions of the operating system like memory management, device management, processor management, file management, and security.

Software process in software engineering basics by ram k paliwal part 2Ram Paliwal

Software and software engineering basics by ram k paliwalRam Paliwal