Part A
An entity is a real-world object that has distinct and separate existence whereas an attribute defines the properties of an entity. In the given case study, following major entities and attributes identified:
Inventory entity
Employee entity
Customer entity
In this given information, it is identified that the organisation is storing sales transaction with the customers’ information. For instance, ‘purchase record’ is representing the sales transaction but it is initially identified as part of the customer entity. Data can be stored effectively after normalization process.
It is a high-level model used to define data elements and their relationship within a system. In entity-relationship model, database structure is demonstrated as a diagram and can be used to develop conceptual design for the target system. However, entity-relationship model at high-level may not normalized entities and therefore, it is useful only to develop a basic understanding how the entities are related to each other.
This model is showing three entities and their relationship. For example, customer purchases an outfit from inventory. Similarly, employee records a purchase record and customer’s information during sales. At this high-level modelling, primary keys are not given and not even assumed. However, primary key for employee is identified as their identification number (ID).
First normal form : According to this rule, a relation must contain atomic values. It also means that each record is unique. For example, all the attributes in inventory entity are atomic where it is assumed that there is a separate record if a product is considered as two or more types of the outfit. For instance, there should be two records for a product if it is considered a dress as well as night suit. For employee and customer, all the attributes are atomic except the purchase record. A customer may have one or more purchase records and therefore, separate records are required to store each purchase.
Second normal form : a relation must be in first normal form to be in second normal form and all the non-key attributes should be functionally dependent on the primary key. Note that a primary key is an attribute that can be used to identify each record uniquely in an entity. Considering this, the following entities and attributes are identified for second normal form:
Third normal form : a relationship must follow the rules of second normal form and there should not be any transitive dependency among attributes. Here, transitive dependency means the attributes belong to a different entity can be separated and access using reference keys. Assuming some common attributes for the ‘purchase record’, following entities are identified in third normal form:
Attribute |
Data type |
Data format |
Size |
Description |
Example |
ID |
Number |
NNNNN |
5 |
Unique identification number |
12345 |
Name |
Text |
- |
50 |
Full name of employee |
Jones John |
Phone |
Text |
NNNNNNNNNN |
10 |
Phone number of customers containing only digits without country code. |
0123456789 |
|
Text |
- |
100 |
Email address of the customer |
hello@gmail.com |
Customer
Attribute |
Data type |
Data format |
Size |
Description |
Example |
ID |
Number |
NNNNN |
5 |
Unique identification number |
12345 |
Name |
Text |
- |
50 |
Full name of employee |
Jones John |
Role |
Text |
- |
50 |
Role of the employee such as cashier, salesperson and inventory manager |
Cashier |
Date_of_joining |
Date |
DD/MM/YYYY |
- |
Date of joining |
01-01-2000 |
Hourly_rate |
Decimal |
00.00 |
2,2 |
Hourly rate with maximum two decimal digits. |
35.75 |
Designer
Attribute |
Data type |
Data format |
Size |
Description |
Example |
ID |
Number |
NNNNN |
5 |
Unique identification number |
12345 |
Name |
Text |
- |
50 |
Name of the designer/ firm |
Designer XYZ |
Attribute |
Data type |
Data format |
Size |
Description |
Example |
Outfit_ID |
Number |
NNNNN |
5 |
Unique identification number |
12345 |
Outfit_type |
Text |
- |
20 |
Type of the outfit such as dress, top etc. |
Skirt |
Price |
Decimal |
3,2 |
- |
Price of the outfit |
199.9 |
Designer_ID |
Number |
NNNNN |
5 |
ID of the designer for the outfit |
12345 |
Size |
Text |
- |
10 |
Size of the outfit |
Small |
Stock_status |
Number |
NNN |
3 |
Available stock units of the outfit |
50 |
Attribute |
Data type |
Data format |
Size |
Description |
Example |
RecordID |
Number |
NNNNN |
5 |
Unique identification number |
12345 |
customerID |
Number |
NNNNN |
5 |
Customer identification number |
12345 |
outfit_ID |
Number |
NNNNN |
5 |
Outfit identification number |
12345 |
quanity |
Number |
NN |
2 |
Quantities of the outfit purchased |
12 |
amount |
Decimal |
4, 2 |
- |
Total amount of transaction for a purchase |
205.49 |
purchase_date |
Date |
DD/MM/YYYY |
- |
Date of purchasing |
01-01-2000 |
employee_ID |
Number |
NNNNN |
5 |
Employee who performed transaction |
2 |
Find More of Our Work:- MIS602 File-Based Framework Assignment Sample
For Additional Information, Read Our Blog On:- How To Use Google Sites to Make and Learn Web Designing?
Find Assignment Help Here:- IT Assignment Sample
1,212,718Orders
4.9/5Rating
5,063Experts
Turnitin Report
$10.00Proofreading and Editing
$9.00Per PageConsultation with Expert
$35.00Per HourLive Session 1-on-1
$40.00Per 30 min.Quality Check
$25.00Total
FreeBonanza Offer
Get 40% Off *
on your assignment today
Doing your Assignment with our samples is simple, take Expert assistance to ensure HD Grades. Here you Go....