Question

Least two application (other than social-networking) you have used that most likely employed a database system to store data for each application list:

- Some tables that you think were used in the application. So a total of 6 tables, 3 tables for each application.

- Some attributes for each table. At least 4 attributes per table, so a grand total of 24 attributes.

Answer 1

1. The application that i have used which contains use of databases system to store data for each application list :

• Play store  
• Some tables used in it may be tables such as : table for storing user account information , table for storing list of apps , table for storing list of free apps ,paid apps etc... , table for storing list of newly released apps.
• table for storing user account information has attributes like : username , password ,email , date of joining ,user id etc.
• table for storing list of apps has attributes like : app_name , category , developer_of_app ,app_release_date , number_of_downloads etc..
• table for storing list of free apps has attributes like : app_name , category pr, developer_of_apps , app_release_date , number_of_downloads
• paid apps table may contain attributes like : app_name , app_release_date , developer_of_app,price_of_app,number_of_installs,
• Antivirus Apps :
• It may contain tables like : It contains table to store list_of_all_apps( it has attributes like app_name,app_installed_date,permissions_used, running_or_not etc..)
• Table for storing recent scan results ( it has attributes like scan_date ,number_of_files_scanned, scan_finished_time, scan_results etc..)
• Table for storing performance of apps (it has attributes like app_name ,app_start_time ,app_end_time,memory_used_by_app etc..)
• Table for storing notifications (it has attributes like notification_id,notification_date,notification_data,notification_seen_or_not etc....)

Answer 2

Application 1: E-commerce Platform

1. Product Table:

• ProductID (Primary Key)

• ProductName

• Price

• Category

• Description

• StockQuantity

2. Order Table:

• OrderID (Primary Key)

• CustomerID (Foreign Key)

• OrderDate

• TotalAmount

• PaymentStatus

3. Customer Table:

• CustomerID (Primary Key)

• FirstName

• LastName

• Email

• Address

• Phone

Application 2: Banking System

1. Account Table:

• AccountNumber (Primary Key)

• CustomerID (Foreign Key)

• AccountType

• Balance

• OpenDate

• Status

2. Transaction Table:

• TransactionID (Primary Key)

• AccountNumber (Foreign Key)

• TransactionType

• Amount

• TransactionDate

• Description

3. Customer Table:

• CustomerID (Primary Key)

• FirstName

• LastName

• DateOfBirth

• Address

• Phone

Please note that the table structures mentioned above are just examples and may not represent the actual schema of specific applications. The attributes listed are also just examples, and there may be additional attributes based on the requirements of the application.