Professional Documents
Culture Documents
BITY3 - OL - Unit20 - ADBMS - July2023 - Sem2 - Task1 - Report - HussainRiyaz - 5201
BITY3 - OL - Unit20 - ADBMS - July2023 - Sem2 - Task1 - Report - HussainRiyaz - 5201
BITY3 - OL - Unit20 - ADBMS - July2023 - Sem2 - Task1 - Report - HussainRiyaz - 5201
ASSESSMENT BRIEF
Bachelor’s Degree Year 3 - IT
The student must fill the relevant parts of the following table.
Student Last Student Task Date
Student First Name Name ID No. submitted Semester
Hussain Riyaz 5201 1 23/09/2023 July 2023
Statement of authenticity
I, the above named student, hereby confirm that this assignment is my own work and not copied or
plagiarized. It has not previously been submitted as part of any assessment. All the sources, from which
information has been obtained for this assignment, have been referenced in the Harvard format. I further
confirm that I have read and understood the Maldives Business School rules and regulations about
plagiarism and copying and agree to be bound by them.
Specialization Core
Assignment type This is an individual assignment.
Tasks Submit on Do on
Task 1: Report: LO1, LO2 23rd -29th September 2023 NA
Task 2: Examination: LO3, LO4. NA 18th-26th November 2023
An extension must be applied for in writing by individual students and will only be
Extensions
granted for valid reasons. No extensions allowed for examination.
Late Late submissions will be marked for all grades but will incur a fine of MVR 250 per task.
submissions (Assignment & Exam both)
Each report resubmission will be charged MVR 100 & re-sit/retake for examination
Resubmissions
will be charged MVR 250.
Assessor(s) Dr. Saurabh Internal Verifier Prof. Sandeep Singh Sikerwar
Statement of Grades:
Marks Representative Grade Grade Interpretation
85 & Above A* Higher Distinction
75 to 84 A Distinction
65 to 74 B Merit
50 to 64 C Pass
Below 50 F Fail
Hussain Riyaz
2657 words
Abstract
A retail grocery shop named “Fresh Food Grocery” has approached me to help them
computerize a database for the shop. They are still using paper for most of their records.
They are providing copies of their paper records and a file of their current customers. Also, a
user interface is provided which hides and protects the database structure from the end
user, as well as being easy to use
ERD
1. Bill Table:
Entities:
- BNum (primary key)
- BDate
- CustID (foreign key referencing Customer Table)
- CustName
- EmpName
- Amt
Relations:
- Bill to Customer (through CustID)
- Bill to Employee (through EmpName)
Cardinality:
- Bill to Customer: Many-to-One (Many bills can belong to one customer)
- Bill to Employee: Many-to-One (Many bills can be associated with one employee)
Attributes:
- BNum (primary key)
- BDate
2. Customer Table:
Entities:
- CutsID (primary key)
- CustName
- CustAdd
- CustPhone
Relations:
- Customer to Bill (through BNum)
Cardinality:
- Customer to Bill: One-to-Many (One customer can have many bills)
Attributes:
- CutsID (primary key)
- CustName
- CustAdd
- CustPhone
3. Employee Table:
Entities:
- EmpNum (primary key)
- EmpName
- EmpAdd
- EmpDOB
- EmpPhone
- EmpPass
Relations:
- Employee to Bill (through EmpName)
Cardinality:
- Employee to Bill: One-to-Many (One employee can be associated with many bills)
Attributes:
- EmpNum (primary key)
- EmpName
- EmpAdd
- EmpDOB
- EmpPhone
- EmpPass
4. Product Table:
Entities:
- PrID (primary key)
- PrName
- PrCat
- PrQty
- PrPrice
Attributes:
- PrID (primary key)
- PrName
- PrCat
- PrQty
- PrPrice
Question 1
1. Discuss the Uses, tools and technique used in database (1.1) (12 Marks)
A. Identify the different use of database.
B. Critically evaluate Tools and techniques used in database
1. Bill Table:
Primary Key Constraint:
BNum is the primary key, which means it must be unique for each record in the Bill table.
Foreign Key Constraint:
CustID is a foreign key referencing the CustID in the Customer Table.
Not Null Constraints:
BNum, BDate, CustID, CustName, EmpName, Amt cannot be null.
2. Customer Table:
Primary Key Constraint:
CustID is the primary key, which means it must be unique for each record in the
Customer table.
Not Null Constraints:
CustID, CustName, CustAdd, CustPhone cannot be null.
3. Employee Table:
Primary Key Constraint:
EmpNum is the primary key, which means it must be unique for each record in the
Employee table.
Not Null Constraints:
EmpNum, EmpName, EmpAdd, EmpDOB, EmpPhone, EmpPass cannot be null.
4. Product Table:
Primary Key Constraint:
PrID is the primary key, which means it must be unique for each record in the Product
table.
I have chosen Microsoft SQL Server as RDBMS. Microsoft SQL Server is a robust and versatile
RDBMS that is well-suited for enterprise-level applications. Its extensive feature set, integration
capabilities, and strong support from Microsoft make it a popular choice for organizations across
various industries.
Advantages
1. Integration with Microsoft Ecosystem: Seamless integration with other Microsoft products
and technologies, making it a natural choice for organizations already using Microsoft solutions.
2. Comprehensive Feature Set: a wide range of features including advanced security options,
high availability solutions, robust backup and recovery mechanisms, and extensive support for
different data types and operations.
4. Robust Security Features: Provides robust security measures including role-based access
control, encryption, auditing, and fine-grained access permissions.
6. Enterprise-Level Support: Microsoft offers extensive support and resources for SQL Server,
including documentation, forums, and a dedicated support team.
9. Licensing Options: Offers a range of licensing options, including both on-premises and
cloud-based solutions through Microsoft Azure, providing flexibility in choosing a licensing
model that fits budget and operational requirements.
Challenges
1. Licensing Costs: Depending on the edition and deployment model, SQL Server can be
relatively expensive, especially for large-scale enterprise applications.
5. Vendor Lock-In: Choosing SQL Server can lead to a certain level of vendor lock-in,
particularly if an organization heavily relies on other Microsoft technologies.
6. Limited Community Support: there is a substantial user base and extensive Microsoft
documentation, community support may be less robust compared to open-source databases.
Question 2
2. Discuss Databases and its relationships. (1.2) (12 marks)
A. Identify and explain the different types of databases.
B. Identify and explain the different types of relationship.
Tables
• Bill Table
• Customer Table
• Employee Table
• Product Table
• I have implemented my ERD in Microsoft SQL Server using Microsoft SQL Server
Management Studio (MSSMS).
Table of Contents
1. Introduction
2. Accessing the Database
3. Database Structure
4. Managing Customer Records
5. Product Management
6. Employee Management
7. Transaction Processing
8. Backup and Maintenance
9. Troubleshooting
1. Introduction
The backend of the Fresh Food Grocery database is where all the data management operations
are performed. It allows you to handle customer, employee records, products, and transactions
effectively.
3. Database Structure
The database is structured into the following main entities:
• Customers: Contains information about the store's customers.
• Products: Stores details about the various products available.
• Transactions: Records all the sales transactions.
• Employee Records: Stores details of the employees.
Deleting a customer
5. Product Management
Adding a New Product
• Click on "Products" in the menu.
• Fill in the required fields and click "Save."
Deleting a Product
• Navigate to the product you want to delete in the product list.
• Click on the "Delete" button.
6. Employee Management
Adding a New Employee
• Click on "Employees" in the menu.
• Fill in the required fields and click "Save."
Deleting a Product
• Navigate to the employee you want to delete in the employee list.
• Click on the "Delete" button.
7. Transaction Processing
• If you encounter any issues or have questions, please contact the support team at the
hotline number 3693522
Question 4
4. Explain the Design documentation in RDBMS. (2.2) (10 marks)
A. Identify and explain different tools for Design documentation.
B. Identify and explain the validation and verification procedure.
Test Cases
Objectives of
Test Actual Test environment
S.No the test Test Name Expected results
Date results
document
Throughout the implementation, various tests were conducted to validate the constraints,
including primary keys, foreign keys, and not null constraints. These tests confirmed that the
database functions as intended, with constraints effectively preventing unauthorized or
erroneous data entry.
References