HND - 60 Aung Khin Sint

Little baby shop

DataBase Assignment Report

Aung khin sint

HND-60
Pearson ID: SJ-53742
1
HND - 60 Aung Khin Sint

Table of Contents

Introduction...........................................................................................3
About Databases....................................................................................3
What is a Database?................................................................................................ 3
Why do we use it?................................................................................................... 3
Why is it important?................................................................................................ 4
Database Design....................................................................................4
Requirement Analysis.............................................................................5
Importance of Requirement Analysis.......................................................................5
Conceptual Design.................................................................................6
What is the process?............................................................................................... 6
Logical Design.......................................................................................8
What is the process?............................................................................................... 9
Normalization.......................................................................................................... 9
Importance of Logical Design................................................................................ 11
Physical Design....................................................................................11
What is the process?............................................................................................. 11
Importance of Physical Design.............................................................................. 12
Implementation....................................................................................19
User Guide............................................................................................................. 19
Effectiveness of Database Design..........................................................22
Conclusion...........................................................................................22
References...........................................................................................23

2
HND - 60 Aung Khin Sint

Introduction
My name is Aung Khin Sint. I work as a database developer for a large IT
Consultancy Company. The company accepted a commission by a small retail business
called “Little Baby Shop”. The commission requires the company to create software to
help with their business. The project manager tasked me with the database software. The
business owner told us that they have had a database before. It was designed by a college
student 5 years ago; they were okay with the amateur database that he designed for them
since they were a small business. But since then, the business has started to grow rapidly.
Their old database has started to show some of its flaws. Therefore, they requested a new
up-to-date database that contains newer technology and newer systems to help their rapidly
growing business. Before I get to explaining my process, it is important to understand what a
database is and why its so crucial to a business.

About Databases

What is a Database?
A database is a systematic collection of information or data that is usually saved
electronically in a computer system. A database management system (DBMS) is typically
required to manage a database. Data in databases is often structured in rows and columns
in a series of tables to make processing and data querying efficient. The data may then be
readily accessed, managed, amended, updated, controlled, and arranged. Most databases
write and use query data using structured query language (SQL).

Why do we use it?

A database is essential for business to store and manage large amounts of
information. Especially for small retail businesses such as this one, they absolutely need a
database to manage their inventory. A database enables ease of use in the storing,
updating, and tracking of information. Multiple people can access the database, allowing it
to be consistent and accurate. This allows for many solutions to many problems, such as
when a customer complains about receiving the wrong order; they may check the database
under the client's ID to see if they received the correct order or not. Since databases contain
confidential information, they can enable strict access and additional security safeguards to
protect and preserve your data.

3
HND - 60 Aung Khin Sint

Why is it important?
A database is an important part of a business for a multitude of reasons such as:

• Scalability: When businesses grow and change, they generally collect a lot more
data. Databases are built to help with this growing process, allowing companies to
grow their data store and working skills successfully. This freedom helps companies
change to changing market situations and user needs while still keeping functionality
and speed.
• Data security: Databases have different tools and ways that help keep data
security. These involve validation rules, limits, and transaction management that
cooperate to ensure the truth, reliability, and consistency of information over time.
Being constant is really important today because data-driven insights can greatly
affect business plans, how we connect with customers, and the ease of processes
overall.
• Decision-Making: Databases help build logical skills that are really important for
making good decisions in businesses. Databases let users pull out useful insights that
can help businesses measure trends and spot patterns, allowing them to make data-
driven choices that match with their goals. This not only helps business performance,
but it also supports creativity and success in the market.
• Backup and Recovery: Databases help keep important information safe, which is
super important for businesses nowadays. These systems make copies of data,
ensuring that information is saved quickly and correctly in the event of unexpected
loss, corruption, or unforeseen disasters. By adopting such robust backup strategies,
businesses can lessen the risk of working downtime or data loss, both of which can
have significant financial and social effects.

Database Design
Database Design can be defined as a set of procedures or collection of tasks involving
various steps taken to implement a database. It helps you get the right information when
you need it. When creating a database, having a well-structured database design is
important. A poorly designed database can lead to numerous problems such as slower
performance, scalability issues, data inconsistency, security risks, and may need increased
maintenance costs and time. To create a good database design, we need to break down the
steps of designing a database. There are multiple stages to database design:

 Requirement Analysis
 Logical Design

4
HND - 60 Aung Khin Sint

 Physical Design
 Implementation
 Testing

Let’s go in depth with each and one of the following.

Requirement Analysis
The initial step in database design is requirement analysis, which includes gathering
and studying needs. The goal is to examine the client's wants and expectations to properly
plan and implement solutions. This is the longest and most important step. If the research is
not done properly, the entire database design may need to be rebuilt, resulting in higher
development costs. A competent requirement analysis requires careful study and analysis of
the client's demands, as well as a written report outlining the key requirements.

Importance of Requirement Analysis

A great requirement analysis is key to making a working database. When made from a
great base, a variety of benefits can be gained such as:

• Clarified goals: Requirement analysis is an important process for exactly stating a

project's goals and results. By meeting with partners to gather feedback and
understand their goals, this method creates a thorough framework for what success
looks like. This shared knowledge among developers, project managers, and clients
not only improves communication but also lowers misunderstanding and mistaken
goals throughout the project lifetime.
• Prevention of Scope Creep: Scope creep refers to the needless addition of the
project’s needs, often leading to additional features and jobs being added without
thought. This can cause unexpected needs emerging during the job. Requirement
analysis combats this by recording all required requirements, ensuring clarity and
agreement amongst everyone. This helps keep the project focused on its original
goals, avoiding detours.
• Reduction of Development Expenses: One of the key benefits of great
requirement analysis is its ability to lower development costs greatly. By finding and
handling possible problems during this phase, teams can escape expensive fixes that
can come up in late-stage changes. This allows resource sharing to be improved,
eventually leading to a more organized development process that is both time-
efficient and cost-effective.

5
HND - 60 Aung Khin Sint

• Enhanced Communication: Requirement analysis enables better communication

among all groups involved in the project. By fully knowing and recording criteria,
everyone may return to a uniform set of rules and standards. This thorough
paperwork works as a shared language that increases teamwork, decreases doubt,
and reduces mistakes or misinterpretations that might negatively affect the project.
• Quality: A full requirement analysis is crucial in ensuring that the result meets with
user wants and standards. By focusing on having clear and reasonable goals, teams
may create solutions that are not only helpful but also user-friendly and trustworthy.
The process leads to a higher-quality product that meets or beats user pleasure,
hence boosting the value offered for both the company and its customers.

Conceptual Design
Conceptual design is the process of finding important data items, connections, and
limitations in a data model. The conceptual design stage is the second step in database
design, preceding the logical and physical design stages. The main goal of conceptual
design is to build a high-level data model that fits business requirements while also giving a
complete understanding of the data items, connections, and limits involved. This data model
is the ground for mental and physical planning methods.

What is the process?

Conceptual design is an important stage in the database design process, concentrating on
identifying and defining major data pieces, their interrelationships, and the constraints that
govern them. The key objectives of conceptual database design are as follows –

 Identify the entities and their attributes − Entities are objects or concepts that
exist in the real world and can be distinguished from each other. Attributes are the
properties or characteristics of the entities. The first objective of conceptual database
design is to identify the entities and their attributes that are relevant to the
organization's business requirements.

 Define the relationships − Relationships are the associations between entities.

The second objective of conceptual database design is to define the relationships
between the identified entities. Relationships can be one-to-one, one-to-many, or
many-to-many.

 Establish the constraints − Constraints are the rules that govern the relationships
between entities. The third objective of conceptual database design is to establish
the constraints between entities, which ensure data consistency and integrity.

6
HND - 60 Aung Khin Sint

Most conceptual designs commonly use something called an Entity-Relationship Diagram

(ERD). These are diagrams used to visualize the conceptual design. These diagrams differ in
visuals for entities, attributes, relationships, and constraints to differentiate them and
provide a better understanding of the database design.

Fig. 1- Entity-Relationship Diagram

Here’s my rendition of the conceptual design for ‘Little Baby Shop’. In this diagram there are
a total of six different entities. Each entity has its own attributes, Attributes are the defining
characteristics of the entities. Here are all the entities and their attributes:

 Customer: Customer_ID, Name, Email, Phone No., Address

 Order: Order_No., OrderDate, ShippingAddress, Discount, Tax, Delivery, Total
 Order Detail: SubTotal, Qty, Amount
 Item: Item_Code, Description, UnitPrice, Age, StockQty
 Staff: Staff_ID, Staff Name
 Branch: Branch_ID, Branch Name, Email, Phone No., Address

Some attributes can hold multiple values at the same time. These are referred to as
multivalued attributes; some of which are in my ERD such as:

7
HND - 60 Aung Khin Sint

 Address: No., Street, Township

 Name: FirstName, LastName
 Date: Day, Month, Year

Each entity is connected to each other with a relationship. There are three types of linkage
in relationships:

 One-to-One relationship: When one entity can be uniquely associated with another
entity.
 One-to-Many relationship: When one entity can be associated with multiple
instances another entity (Example: Customer-Order)
 Many-to-Many relationship: When an entity can be associated with multiple
instances another entity and vice versa (Example: Order-Item)

According to the model, a customer can place several orders. An order can contain many
items, and one item can appear in multiple orders. Each order is accepted by a staff
member, although the same staff member can accept many orders. Each staff member is
allocated to a certain branch.

After evaluation, we can observe that this ERD is well-structured, providing a simple view
into the structure of the database. This aids in data management by fostering smooth
contact between consumers, orders, employees, and items in the company without causing
any confusion during the process.

Logical Design
The third phase in database design is Logical Design. Logical design is the process of
transforming a conceptual model into a logical schema or model that structures data by
defining tables, fields, the primary and foreign keys, and relationships.

What is the process?

When beginning the logical design process, we must first transform the entities from
the conceptual design into tables. Each table has columns derived from the attributes of the
entities in the conceptual design. Each table must define its use of primary and foreign keys.
The relationship between the tables must also be specified. Normalization marks the end of
the logical design process. Normalization should be used to eliminate data redundancy,
inconsistency, and dependency issues.

8
HND - 60 Aung Khin Sint

Normalization
Normalization refers to the process of structuring data in a database.
It is used to reduce the redundancy of a relationship or group of connections. It is also used
to remove unwanted traits such as Insertion, Update, and Deletion Anomalies.
Normalization separates the larger table into smaller ones and connects them through
relationships. The normal forms are used to eliminate data redundancy in the database
table. There are three normal forms in normalization. They are:

 First Normal Form (1NF)- Remove repeated groups on individual tables. Make a
separate table for each collection of related data. Use a primary key to identify each
collection of linked data.
 Second Normal Form (2NF)- Create distinct tables for collections of values that are
common to several entries. Connect these tables with a foreign key.
 Third Normal Form (3NF)- Eliminate fields that don't depend on the primary key.

Let’s examine why each form is required to apply to your logical design. We can start with
the first normal form; the first normal form needs each column to hold an atomic/unique
value. This removes repeated values and lowers possible mistakes, making it easier to query
and handle data. The second normal form follows the first, needing all non-key attributes to
be reliant on the primary key. This stops attributes from being loosely or wrongly paired with
parts of the primary key, which could cause data integrity problems. The third normal form
demands that a non-key attribute be dependent solely on the primary key. If a non-key
attribute depends on another non-key attribute, 3NF moves such attributes to different
tables. This means that non-key attributes are only based on the primary.

My rendition of normalization follows the same principles as mentioned above. This ensures
an efficient database structure that maintains integrity, minimizes redundancy, and
enhances performance.

Fig. 1- First Normal Form (1NF)

9
HND - 60 Aung Khin Sint

Fig. 2- Second Normal Form (2NF)

Order
Order No(PK) CustomerID(FK) Staff_ID(FK) Branch_ID(FK) OrderDate SubTotal Discount% Tax Delivery Total
LBS-00023 S-005 IDN-003 LBB-03 15/10/2024 760000 45600 15200 0 729600

OrderDetails Staff
Composite PrimaryKey Staff_ID(PK) StaffName
Order_No(FK) Item_ID(FK) Qty Amount IDN-003 Kyu Kyu
LBS-00023 LB-C45 15 105000
LBS-00023 LB-C46 20 460000 Branch
LBS-00023 LB-C93 1 45000 Branch_ID(PK) BranchName StoreAddress ContactNumber ContactEmail
LBS-00023 LB-C22 2 150000 LBB-03 Mingalardon Branch No12, Mingalardon, Yangon 01-223344 [email protected]

Item
Item_ID(PK) Description Age UnitPrice Customer
LB-C45 MoLo Pink Dress 2 Years 7000 CustomerID(PK) CustomerName Phone Email Address
No20(A), AungChan Thar,
LB-C46 MoLo Blue Dress 23000 S-005 Aye Thiri 09-5401244 [email protected]
4 Years Mandalay
LB-C93 BabyCar Seat 3 Years 45000
LB-C22 BabyStrollers 75000

Order OrderDetails
1 M
1 1
One Many

OrderDetails Item
1 1
M 1
Many One

Order Customer
1 1
M 1
Many One

Order Staff
1 1
M 1
Many One

Order Branch
1 1
M 1
Many One

Fig.3 - Third Normal Form (3NF)

Importance of Logical Design

Going through the process of logical design is important for numerous reasons such as:

• Establishes a Clear Data Structure- Logical design offers a structured basis for
data by describing entities, characteristics, and connections in an organized and
consistent way. This style makes data easy to store, access, and control inside the
system.
• Ensures Data Integrity and Accuracy- Logical design finds key connections and
dependencies among data, helping to apply limits that keep data accuracy and

10
HND - 60 Aung Khin Sint

consistency across the system. The careful design of tables and connections ensures
that the system works with reliable, correct data.
• Reduces Data Redundancy and Optimizes Storage- A well-designed logical
model removes redundancy by organizing data and ensures that the data is only
stored in one place, avoiding any unnecessary duplicates. This improves storage
effectiveness and lowers the chance of errors.
• Serves as a Blueprint for Physical Design- Logical design provides a basis that
guides the physical design, where implementation details such as data types and
storage settings are defined. A well-defined logical design makes the shift to physical
design more efficient and effective.
• Facilitates Future Scalability and Maintenance- Logical design considers current
and future data needs, making it easier to scale the database as the company grows.
It also improves upkeep and debugging because the data format is well-organized
and easy to navigate.

Physical Design
Physical Design is the last step of the database design process. Physical Design
defines the actual database architecture, based on the logical model, to be implemented on
a specific database management system. This includes how the data in each column must
be stored, what constraints are applied, and the purpose of the data stored in the column.

What is the process?

In the physical design phase, tables derived from the third normal form (3NF) of the
logical model are transformed into actual tables, with columns representing the properties of
each attribute. For each table, it is essential to define the data type of all attributes, along
with specifying primary and foreign keys, additional constraints, how the data is stored and
the intended purpose of each attribute.

Importance of Physical Design

Physical Design is a crucial part of the database in improving the database structure
even further bringing abundant benefits such as:

 Optimizes Data Storage and Retrieval- Physical design involves strategies for
data storage, file organization, and indexing, which enhance retrieval speed and
efficiency. Well-planned indexing reduces query time and saves disk space, crucial for
large applications.

11
HND - 60 Aung Khin Sint

 Ensures High Performance and Scalability- By accounting for data volume and
access frequency, physical design allows for performance optimization. Techniques
like partitioning and data distribution help manage higher loads and scale as data
grows.
 Supports Security and Data Integrity- Security measures such as access controls
and encryption are established during physical design, protecting sensitive data. It
also sets constraints and triggers to maintain data integrity and prevent corruption.
 Enables Efficient Query Processing- Physical design enhances query speed
through indexing, materialized views, and caching, leading to improved user
experience and application performance.
 Allows Flexibility for Future Changes- It considers current and future
requirements, facilitating easier adaptability to changing data volumes or access
patterns without major redesigns. Modular design approaches help in system
upgrades.
 Facilitates Backup and Recovery- Establishing a reliable backup and recovery
strategy is integral to physical design, minimizing data loss and downtime through
defined storage areas, backups, and transaction logs.
 Enhances Data Transfer and Communication Efficiency- Physical design
optimizes data transfer between the database and applications, addressing network
constraints and minimizing latency through strategies like data denormalization.
 Ensures Compatibility with the Chosen DBMS- It aligns the logical design with
the specific features and limitations of the selected DBMS, maximizing efficiency and
leveraging the system's strengths.

My rendition of Physical Design reflects the benefits mentioned above. Having such an
effective physical design improves the performance of the database system under heavy
operating loads and ensures speedy data retrieval.

Physical Design

‘Order’ Table

Null or
Column Constrain
Data Type Not Description
Name t
Null

Order_No. VARCHAR (9) NOT Primary  Order No. will be stored in

this column.
NULL

12
HND - 60 Aung Khin Sint

key  Primary key constraint is

applied to store unique
Check
data.
 Format is LBS-00001. Check
constraint is applied to this
column. Check constraint is
‘LBS-[0-9] [0-9] [0-9] [0-9]
[0-9]’.

Customer_ID VARCHAR (5) NOT Foreign Key  Customer ID will be stored

in this column.
NULL Check
 Foreign key constraint is
applied to link
‘Customer_ID’ from the
‘Customer’ table to the
‘Order’ table.
 Format is S-001. Check
constraint is applied to this
column. Check constraint is
‘S-[0-9] [0-9] [0-9]’.

Staff_ID VARCHAR (7) NOT Foreign Key  Staff ID will be stored in this
column.
NULL Check
 Foreign key constraint is
applied to link ‘Staff_ID’
from the ‘Staff’ table to the
‘Order’ table.
 Format is IDN-001. Check
constraint is applied to this
column. Check constraint is
‘IDN-[0-9] [0-9] [0-9]’.

Branch_ID VARCHAR (6) NOT Foreign Key  Branch ID will be stored in

this column.
NULL Check
 Foreign key constraint is
applied to link ‘Branch_ID’
from the ‘Branch’ table to
the ‘Order’ table.
 Format is LBB-01. Check
constraint is applied to this
column. Check constraint is
‘LBB-[0-9] [0-9]’.

OrderDate DATE NOT Default  Order date will be stored in

this column.
NULL Check
 Default constraint is applied
to this column. If there’s no
input value, Default value is
set to ‘current date’.
 Check constraint is applied

13
HND - 60 Aung Khin Sint

to this column. Format is

‘dd/mm/yy’.

SubTotal MONEY NOT Check  The sum of all items before

any deduction will be stored
NULL
in this column.
 Check constraint is applied
to not allow any negative
value. Check constraint is
‘SubTotal’ >=0.
 ‘SubTotal’ is calculated by
summing all the values in
the ‘Amount’ column of the
‘Order_Details’ table.

Discount MONEY NULL Default  Discount will be stored in

this column.
Check
 Default constraint is applied
to this column. Default
value is ‘0’.
 Check constraint is applied
to not allow any negative
value. Check constraint is
‘Discount’ >=0.
 Discount is calculated from
‘SubTotal’ column. If
‘SubTotal’ > 200,000 then
‘Discount’ would be 4%. If
‘SubTotal’ > 500,000 then
‘Discount’ would be 6%.

Tax MONEY NULL Default  Tax will be stored in this

column.
Check
 Check constraint is applied
to not allow any negative
value. Check constraint is
‘Tax’ >=0.
 Default constraint is applied
to this column. Default
value is 0.02.

Delivery MONEY NULL Check  Delivery charge will be

stored in this column.
 Check constraint is applied
to not allow any negative
value. Check constraint is
‘Delivery’ >=0.
 If the ‘Address’ column
contains ‘Yangon’, charge
would be 3000. Else, charge

14
HND - 60 Aung Khin Sint

is 1500.
 If ‘SubTotal’ column >
500,000 then charge is 0.

Total MONEY NOT  Total calculated amount is

stored in this column.
NULL
 ‘Total’ is calculated by
subtracting [‘Discount’ +
‘Tax’ + ‘Delivery’] from
‘SubTotal’ column.

‘Order_Details’ table

Column Null or
Data Type Constraint Description
Name Not Null

Order_No. VARCHAR (9) NOT Foreign Key  Order No. will be stored in
this column.
NULL Check
 Foreign key constraint is
applied to link ‘Order_No’
from the ‘Order’ table to
the ‘Order_Details’ table.
 Format is LBS-00001.
Check constraint is applied
to this column. Check
constraint is ‘LBS-[0-9] [0-
9] [0-9] [0-9] [0-9]’.

Item_ID VARCHAR (6) NOT Foreign Key  Item ID will be stored in

this column.
NULL Check
 Foreign key constraint is
applied to link ‘Item_ID’
from the ‘Item’ table to the
‘Order_Details’ table.
 Format is LB-C01. Check
constraint is applied to this
column. Check constraint
is ‘LB-C [0-9] [0-9]’.

Qty INT NOT  Quantity will be stored in

this column.
NULL

Amount MONEY NOT  Total Amount of an item is

stored in this column.
NULL
 ‘Amount’ is calculated by
multiplying the values in

15
HND - 60 Aung Khin Sint

the ‘Quantity’ and ‘Price’

columns from the ‘Item’
table.

‘Item’ table

Column Null or
Data Type Constraint Description
Name Not Null

Item_ID VARCHAR (6) NOT Primary Key  Item ID will be stored in

this column.
NULL Check
 Primary key constraint is
applied to store unique
data.
 Format is LB-C01. Check
constraint is applied to this
column. Check constraint
is ‘LB-C [0-9] [0-9]’.

Description VARCHAR (50) NOT Unique  Description will be stored

in this column.
NULL
 Unique constraint is
applied to this column.

Age INT NULL Check  Age will be stored in this

column.
 Check constraint is applied
to not allow negative
value. Check constraint is
‘Age’ >=0.

UnitPrice MONEY NOT Check  Unit Price will be stored in

this column.
NULL
 Check constraint is applied
to not allow negative
value. Check constraint is
‘UnitPrice’ >=0.

‘Staff’ table

Column Null or
Data Type Constraint Description
Name Not Null

16
HND - 60 Aung Khin Sint

Staff_ID VARCHAR (7) NOT Primary Key  Staff ID will be stored in

this column.
NULL Check
 Primary key constraint is
applied to store unique
data.
 Format is IDN-001. Check
constraint is applied to this
column. Check constraint
is ‘IDN-[0-9] [0-9] [0-9]’.
StaffName VARCHAR (50) NOT  Staff names will be stored
in this column.
NULL

‘Branch’ table

Column Null or
Data Type Constraint Description
Name Not Null

Branch_ID VARCHAR (6) NOT Primary Key  Branch ID will be stored in

this column.
NULL Check
 Primary key constraint is
applied to store unique
data.
 Format is LBB-01. Check
constraint is applied to this
column. Check constraint
is ‘LBB-[0-9] [0-9]’.

BranchName VARCHAR (50) NOT  Branch name will be

stored in this column.
NULL

Address VARCHAR (50) NOT  Store address will be

stored in this column.
NULL

Number VARCHAR (12) NOT Check  Contact numbers will be

stored in this column.
NULL
 Format is 09-123456789
Check constraint is applied
to this column. Check key
constraint is ‘[0-9][0-9]-[0-
9][09][0-9][0-9][0-9][0-9]
[0-9][0-9][0-9]’.

Email VARCHAR (50) NOT Check  Contact email will be

stored in this column.
NULL
 Check constraint is applied

17
HND - 60 Aung Khin Sint

to this column. Check key

constraint is ‘Email’ like
'%_@__%.__%'.

‘Customer’ table

Column Null or
Data Type Constraint Description
Name Not Null

Customer_ID VARCHAR (5) NOT Primary Key  Customer ID will be stored

in this column.
NULL Check
 Primary key constraint is
applied to store unique
data.
 Format is S-001. Check
constraint is applied to
this column. Check
constraint is ‘S-[0-9] [0-9]
[0-9]’.

CuName VARCHAR (50) NOT  Customer name will be

stored in this column.
NULL

CuAddress VARCHAR (50) NOT  Customer address will be

stored in this column.
NULL

CuNumber VARCHAR (12) NOT Check  Contact numbers will be

stored in this column.
NULL
 Format is 09-123456789
Check constraint is
applied to this column.
Check key constraint is
‘[0-9][0-9]-[0-9][09][0-9]
[0-9][0-9][0-9][0-9][0-9][0-
9]’.

CuEmail VARCHAR (50) NOT Check  Contact email will be

stored in this column.
NULL
 Check constraint is
applied to this column.
Check key constraint is
‘CuEmail’ like '%_@__%.__
%'.

18
HND - 60 Aung Khin Sint

Implementation

User Guide
To translate the design concepts into a working database, we need reliable software to
build the database on. There are various great selections to choose from, such as MySQL,
SQLite, and Microsoft SQL server. After great evaluation, Microsoft SQL server is the perfect
software for building a database for small retail businesses such as this one. Some reasons
include:

 Low costs
 User-friendly
 Freedom of customization

The latest version, Microsoft SQL server 2022, is recommended as it’s always the safest
option. Having up-to-date software provides many benefits such as having quality-of-life
features that make managing a database more convenient. There’re many other reasons
such as:

 Better data security

 New features in
o Analytics
o Availability
o Security
o Performance
o Query Store and intelligent query processing
o Management
o Platform
o Language
 Future proof
 Improved optimization and performance

Before we install the software, we first need to check if we have a reliable operating system
and a powerful enough computer for the database to run on. Any operating system is
compatible and optimized for in Microsoft SQL server. However, it is recommended to use
either Windows or macOS for smaller business such as this. As for specification
requirements, Microsoft SQL server needs:

Minimum requirements

 2 CPU cores x64 Processor 1.4 GHz

 1 Gb RAM
 6 Gb Hard Drive Space
 Windows 10 or 11

19
HND - 60 Aung Khin Sint

Recommended requirements

 4 CPU cores x64 Processor 2.0 GHz

 8 Gb RAM or more
 10 Gb Hard Drive Space
 Windows 10 or 11

For installation, head to https://www.microsoft.com/en/sql-server/sql-server-downloads and

download either the developer or express versions for a free specialized edition.

Next, run the .exe file and a pop-up will show. Choose the Basic installation type and accept
the terms and conditions next choose the file location and install the file.

20
HND - 60 Aung Khin Sint

Once the installation is successful, click Install SSMS to install the Server Manager.

For the database to function properly, we should build the tables in an order based on
dependencies between tables, starting with tables that don’t have any foreign key
dependencies. This ensures that there won’t be any errors while building tables that
reference other tables. Here’s the recommended order for building the tables in your
database:

1. Branch Table (Parent)

2. Staff Table (Parent)
3. Customer Table (Parent)
4. Item Table (Child)
5. Order Table (Parent)
6. Order Details Table (Child)

By building the tables following this order, each table can reference the necessary foreign
keys without any errors. Once all the tables have been created, the database has essentially
been finished.

Effectiveness of Database Design

To determine the effectiveness of the database's design, it has to satisfy the
business’s requirements for data integrity, performance, scalability and so on. To ensure
data integrity and accuracy, we have enforced constraints to maintain consistency with the
data. Applying normalization reduces the redundancy of the data while maintaining

21
HND - 60 Aung Khin Sint

performance. Physical design helps with faster queries and data retrievals. Logical data
model and physical design takes account for scalability and data growth ensuring smooth
expansion for the business. By testing these requirements with appropriate methods, we can
ensure that the database has met the business’s requirements.

Conclusion
The current database design intended for ‘Little Baby Shop’ has satisfied the
requirements for a small retail business. The database is designed methodically, with
structured tables for items, customers, orders, and inventories, which improves data
administration and makes essential business information more accessible. This architectural
style encourages smooth transaction processing, enables effective inventory management,
and provides a simple system for tracking client orders. The installation of this database will
lay a solid platform for everyday operations, improve managerial practices, and greatly
contribute to the business’s future growth. This development is will be of great
improvements for the ‘Little Baby Shop’ business.

22
HND - 60 Aung Khin Sint

References
Anand, A. (no date) Importance of database design in DBMS, Analytics Steps. Available at:
https://www.analyticssteps.com/blogs/importance-database-design-dbms (Accessed: 09
November 2024).

Co., H.T. (1970) Database design fundamentals, SpringerLink. Available at:

https://link.springer.com/chapter/10.1007/978-981-19-3032-4_7#:~:text=The%20main
%20goal%20of%20the,used%20for%20the%20next%20system. (Accessed: 09 November
2024).

Conceptual database design (no date) Tutorialspoint. Available at:

https://www.tutorialspoint.com/conceptual-database-design (Accessed: 09 November 2024).

GeeksforGeeks (2024a) Database design fundamentals, GeeksforGeeks. Available at:

https://www.geeksforgeeks.org/database-design-fundamentals/ (Accessed: 09 November
2024).

GeeksforGeeks (2024b) Database design in DBMS, GeeksforGeeks. Available at:

https://www.geeksforgeeks.org/database-design-in-dbms/ (Accessed: 09 November 2024).

23