List any four factors a database designer should consider when selecting a DBMS systemin your organization. [4 Marks]b) Wanguru Company Limited intends to introduce a new computerized system in order themanagement of its employee’s records. Outline FOUR good features you would want tosee in the implemented Wanguru database system. [4 Marks]c) KCA University uses the Database approach instead of a manual systems approach for keepingrecords. Explain any four disadvantages of using manual database approach. [4 Marks]d) Discuss FOUR components of a database management system (DBMS). [4 Marks]e) Explain FOUR classifications of relationships based on Degree. [4Marks]QUESTION TWO [15 MARKS]a) Describe the following attributes and give an example in each case:i. Derived Attributeii. Key Attributeiii. Composite Attributeiv. Single-Valued Attributev. Optional Attribute [5 Marks]b) List three types of users associated with the database implementation [3 Marks]c) Describe the following classes of database integrity and explain how they are enforced.i). Entity integrityii). Referential integrityiii). User defined Integrity [3 Marks]d) Write a simple SQL statement that can be used to insert students details into the database[4 Marks]

a) When selecting a DBMS system for an organization, the database designer should consider the following four factors:

1. Scalability: The DBMS should be able to handle the organization's current data needs and also have the capability to scale up as the data grows over time.

2. Performance: The system should be able to efficiently process and retrieve data, ensuring that the response time is acceptable for the organization's requirements.

3. Security: The DBMS should have robust security features to protect the organization's data from unauthorized access, ensuring data confidentiality and integrity.

4. Compatibility: The system should be compatible with the organization's existing hardware and software infrastructure, minimizing the need for additional investments or complex integration processes.

b) In the implemented Wanguru database system, the following four good features would be desirable:

1. User-friendly interface: The system should have an intuitive and easy-to-use interface, allowing employees to navigate and interact with the system without extensive training.

2. Data backup and recovery: The system should have built-in mechanisms for regular data backups and the ability to restore data in case of any system failures or data loss.

3. Data security: The system should have robust security measures in place to protect employee records from unauthorized access or data breaches.

4. Reporting and analytics: The system should provide comprehensive reporting and analytics capabilities, allowing management to generate meaningful insights and make informed decisions based on the employee data.

c) Using a manual database approach in KCA University can have the following four disadvantages:

1. Data redundancy and inconsistency: Manual systems are prone to data duplication and inconsistencies, leading to data integrity issues and difficulties in maintaining data accuracy.

2. Limited accessibility: Manual systems restrict access to data, making it difficult for multiple users to simultaneously access and update the database.

3. Lack of data security: Manual systems lack the security features provided by DBMS, making the data vulnerable to unauthorized access or accidental loss.

4. Limited scalability: Manual systems have limitations in terms of data storage capacity and processing capabilities, making it challenging to handle large volumes of data or accommodate future growth.

d) The four components of a database management system (DBMS) are:

1. Data Definition Language (DDL): This component is responsible for defining the database structure, including creating tables, specifying data types, and setting constraints.

2. Data Manipulation Language (DML): This component allows users to interact with the database by performing operations such as inserting, updating, deleting, and retrieving data.

3. Data Control Language (DCL): This component manages user access and permissions to the database, ensuring data security and enforcing data integrity rules.

4. Database Administrator (DBA): The DBA is responsible for managing and maintaining the DBMS, including tasks such as database design, performance tuning, backup and recovery, and security management.

e) Relationships in a database can be classified based on their degree into the following four categories:

1. One-to-One (1:1) relationship: In this type of relationship, one record in a table is associated with only one record in another table. For example, a person and their passport information can have a one-to-one relationship.

2. One-to-Many (1:N) relationship: In this type of relationship, one record in a table is associated with multiple records in another table. For example, a customer can have multiple orders in an e-commerce system.

3. Many-to-One (N:1) relationship: In this type of relationship, multiple records in a table are associated with a single record in another table. For example, multiple students can be enrolled in a single course.

4. Many-to-Many (N:N) relationship: In this type of relationship, multiple records in one table are associated with multiple records in another table. For example, a student can be enrolled in multiple courses, and a course can have multiple students.

QUESTION TWO:

a) The following attributes can be described as:

i. Derived Attribute: An attribute that is calculated or derived from other attributes in the database. For example, the age of a person can be derived from their date of birth.

ii. Key Attribute: An attribute that uniquely identifies a record in a table. For example, a student ID can be a key attribute in a student table.

iii. Composite Attribute: An attribute that is composed of multiple sub-attributes. For example, an address attribute can have sub-attributes like street, city, and postal code.

iv. Single-Valued Attribute: An attribute that can have only one value for each record. For example, the date of birth of a person is a single-valued attribute.

v. Optional Attribute: An attribute that is not mandatory and can have a null or empty value. For example, the middle name of a person can be an optional attribute.

b) The three types of users associated with database implementation are:

1. End Users: These are the individuals who directly interact with the database system to perform day-to-day operations, such as entering data, retrieving information, and generating reports.

2. Database Administrators (DBAs): DBAs are responsible for managing and maintaining the database system. They perform tasks like database design, security management, performance tuning, and backup and recovery.

3. Application Programmers: These users develop and maintain the software applications that interact with the database. They write code to perform database operations and ensure the smooth functioning of the applications.

c) The classes of database integrity and how they are enforced are:

i. Entity integrity: This ensures that each record in a table has a unique identifier (primary key) and that it cannot be null or empty. It is enforced by defining primary key constraints on the table.

ii. Referential integrity: This ensures that relationships between tables are maintained, and foreign key values in one table correspond to the primary key values in another table. It is enforced by defining foreign key constraints and using cascading actions like ON DELETE CASCADE or ON UPDATE CASCADE.

iii. User-defined integrity: This allows the database designer to define additional integrity rules specific to the organization's requirements. These rules can be enforced using triggers, stored procedures, or application-level validations.

d) A simple SQL statement to insert student details into the database could be:

INSERT INTO students (student_id, student_name, student_age, student_major) VALUES (1, 'John Doe', 20, 'Computer Science');

This statement inserts a new record into the "students" table with the specified values for the "student_id", "student_name", "student_age", and "student_major" attributes.

a) When selecting a DBMS system for an organization, the database designer should consider the following four factors:

1. Scalability: The DBMS should be able to handle the organization's current data needs and also have the capability to scale up as the data grows over time.

2. Performance: The system should be able to efficiently process and retrieve data, ensuring that the organization's operations are not slowed down.

3. Security: The DBMS should have robust security features to protect the organization's data from unauthorized access, ensuring data confidentiality and integrity.

4. Compatibility: The system should be compatible with the organization's existing hardware and software infrastructure, minimizing the need for additional investments and ensuring smooth integration.

b) In the implemented Wanguru database system, the following four good features would be desirable:

1. User-friendly interface: The system should have an intuitive and easy-to-use interface, allowing employees to navigate and interact with the system without extensive training.

2. Data backup and recovery: The system should have a reliable backup and recovery mechanism to ensure that employee records are protected and can be restored in case of data loss or system failure.

3. Data security: The system should have robust security measures in place to protect employee records from unauthorized access or data breaches.

4. Reporting and analytics: The system should have built-in reporting and analytics capabilities, allowing management to generate meaningful insights and make informed decisions based on employee data.

c) Using a manual database approach in KCA University can have the following four disadvantages:

1. Data redundancy and inconsistency: Manual systems are prone to errors, leading to duplicate or inconsistent data entries, which can affect data accuracy and reliability.

2. Limited accessibility: Manual systems require physical access to records, making it difficult to share and access data remotely or by multiple users simultaneously.

3. Lack of data integrity: Manual systems rely on human input, increasing the risk of data entry errors, omissions, or unauthorized modifications, compromising data integrity.

4. Time-consuming and inefficient: Manual systems involve manual data entry, retrieval, and processing, which can be time-consuming and prone to delays, affecting operational efficiency.

d) The four components of a database management system (DBMS) are:

1. Data Definition Language (DDL): This component is responsible for defining the database structure, including creating tables, specifying data types, and setting constraints.

2. Data Manipulation Language (DML): This component allows users to interact with the database by performing operations such as inserting, updating, deleting, and retrieving data.

3. Data Control Language (DCL): This component manages user access and permissions to the database, ensuring data security and enforcing data integrity rules.

4. Database Administrator (DBA): The DBA is responsible for managing and maintaining the database system, including tasks such as performance tuning, backup and recovery, and security management.

e) Relationships in a database can be classified based on their degree, which refers to the number of entities involved. The four classifications are:

1. One-to-One (1:1) relationship: In this type of relationship, each entity in one table is associated with exactly one entity in another table. For example, a person and their passport information.

2. One-to-Many (1:N) relationship: In this type of relationship, an entity in one table is associated with multiple entities in another table. For example, a customer and their orders.

3. Many-to-One (N:1) relationship: In this type of relationship, multiple entities in one table are associated with a single entity in another table. For example, multiple students enrolled in a single course.

4. Many-to-Many (N:N) relationship: In this type of relationship, multiple entities in one table are associated with multiple entities in another table. For example, students and courses, where a student can be enrolled in multiple courses, and a course can have multiple students.

QUESTION TWO:

a) Attributes and examples:

i. Derived Attribute: An attribute that can be calculated or derived from other attributes. For example, the age of a person can be derived from their date of birth.

ii. Key Attribute: An attribute that uniquely identifies each entity in a table. For example, the student ID in a student table.

iii. Composite Attribute: An attribute that is composed of multiple sub-attributes. For example, the address attribute can have sub-attributes like street, city, and postal code.

iv. Single-Valued Attribute: An attribute that can have only one value for each entity. For example, the date of birth of a person.

v. Optional Attribute: An attribute that is not mandatory and can have a null value. For example, the middle name of a person.

b) The three types of users associated with database implementation are:

1. End Users: These are the individuals who directly interact with the database system to perform day-to-day operations, such as entering data, retrieving information, and generating reports.

2. Database Administrators (DBAs): DBAs are responsible for managing and maintaining the database system. They perform tasks like database design, security management, performance tuning, and backup and recovery.

3. Application Programmers: These users develop and maintain the applications that interact with the database system. They write code to perform operations like data insertion, retrieval, and manipulation.

c) Classes of database integrity and their enforcement:

i. Entity integrity: This ensures that each entity in a table has a unique identifier (primary key) and that the primary key value is not null. It is enforced by defining primary key constraints on the table.

ii. Referential integrity: This ensures that relationships between tables are maintained, and foreign key values in one table correspond to primary key values in another table. It is enforced by defining foreign key constraints and using cascading actions like ON DELETE and ON UPDATE.

iii. User-defined integrity: This refers to additional business rules or constraints that are specific to the organization's requirements. It is enforced by defining custom constraints or triggers in the database.

d) A simple SQL statement to insert student details into the database:

INSERT INTO students (student_id, student_name, student_age, student_major) VALUES (1, 'John Doe', 20, 'Computer Science');