By the end of this chapter, you will be able to:
Mastering these skills will help you create efficient databases that truly support users and improve how information is managed in the real world.
Designing a computerized database is a critical skill for an ICT Technician in Kenya. Effective database design enables organizations across sectors such as healthcare, education, finance, and public service to manage data efficiently, supporting decision-making and operational processes. This chapter introduces fundamentals of establishing computerized databases, focusing on understanding Database Management Systems (DBMS) and gathering accurate database requirements to ensure the system meets organizational needs.
Establishing a computerized database involves selecting appropriate tools, defining the structure of data storage, and ensuring the system aligns with user needs. In Kenyan organizations like county governments or SACCOs, a well-designed database supports functions ranging from financial record-keeping to client management, thus improving service delivery and data integrity. The first step is to comprehend what a DBMS entails and then systematically gather requirements from stakeholders to build a database that reflects real-world operations and constraints.
The concept of a Database Management System (DBMS) is fundamental to computerized databases. A DBMS is software that facilitates the creation, management, and use of databases, allowing users to store, retrieve, and manipulate data efficiently. In Kenya’s banking sector, for example, DBMS enables secure transaction processing and customer data management, which are essential for operational continuity and regulatory compliance.
A DBMS is an integrated software package designed to define, create, maintain, and control access to databases. It acts as an intermediary between users and the physical database, ensuring data is consistently organized and accessible. This software handles data storage, query processing, transaction management, and security enforcement.
Gathering accurate database requirements is essential for building a system that meets the specific needs of users and stakeholders. In Kenya’s diverse organizational landscape, techniques must capture both technical and business perspectives to ensure the database supports operational workflows and reporting needs.
Interviews involve direct discussions with stakeholders such as department heads, data entry clerks, and IT staff to understand their information needs and challenges. This technique allows in-depth exploration of user expectations and uncovers implicit requirements. For instance, interviewing staff at a county health department can reveal critical data points for patient tracking and reporting.
Structured questionnaires are distributed to a larger group of users to gather quantitative data about their database needs. This method is efficient for collecting information from dispersed teams such as employees across different branches of a retail chain. Well-designed questionnaires can identify common data fields, frequency of data access, and desired reporting formats.
Reviewing existing documentation such as process manuals, forms, and reports helps analysts understand current data flows and storage methods. In a university setting, analyzing student registration forms and exam records provides insights into necessary database tables and relationships. This technique also identifies gaps and inefficiencies in current systems.
Direct observation of users performing their tasks reveals practical details that may not surface during interviews. For example, observing data entry clerks in a SACCO shows how data is captured, validated, and where errors commonly occur. This hands-on understanding informs the design of user-friendly interfaces and validation rules.
Developing a preliminary version of the database or user interface allows stakeholders to interact with the system early and provide feedback. Prototyping is especially useful in dynamic environments like hotel management systems, where requirements may evolve rapidly. It improves communication between developers and users, reducing misunderstandings.
Explain the role of a Database Management System (DBMS) in managing data within a Kenyan retail business. (5 marks)
Discuss five core functions of a DBMS and their significance in a healthcare institution. (10 marks)
Describe five techniques used in gathering database requirements and how each technique can be applied in a county government office. (15 marks)
Create a free account to open more of this chapter.
Free: practical guides, quick cards, workplace scenarios and more.
Create a free accountThis chapter explored the establishment of computerized databases by first introducing the fundamental concepts of database management systems, including key definitions, functions, applications, types, components, and architecture. It then examined techniques for gathering database requirements, emphasizing elicitation methods and the preparation of assessment reports to ensure accurate data needs capture. Various database models were discussed, highlighting relational, hierarchical, network, object-oriented, and dimensional approaches, each with distinct structures and use cases. The chapter progressed into database design, covering conceptual design through entity-relationship diagrams that define entities, attributes, and relationships with appropriate notations. Logical design was addressed by focusing on the creation of tables, identification of keys, and the process of normalization to organize data efficiently. Finally, physical design considerations were presented, including the selection of data types, implementation of indexing for performance optimization, and the enforcement of constraints to maintain data integrity. Together, these topics provide a comprehensive foundation for designing effective computerized database systems.
Type: Individual
| Tools & Equipment | Materials |
|---|---|
| Laptop with database application installed | User requirements gathering checklist |
| Interview questionnaire template | Interview questionnaire template |
| Notepad and pen | Sample database assessment report format |
| User requirements gathering checklist | |
| Sample database assessment report format |
| S/N | Item | Quantity |
|---|---|---|
| 1 | Laptop with database application installed | 1 Pc per Candidate |
| 2 | Interview questionnaire template | 1 Pc per Candidate |
| 3 | Notepad and pen | 1 Pc per Candidate |
| 4 | User requirements gathering checklist | 1 Pc per Candidate |
| 5 | Sample database assessment report format | 1 Pc per Candidate |
| Items to be Evaluated | Marks Available | Marks Obtained | Comments |
|---|---|---|---|
| TASK 1: Establish database and gather user requirements | |||
| Candidate launches the database application and creates a new database named 'ClientDB' (Award 1 mark for launching application and 1 mark for correctly naming and creating the database) | 2 | ||
| Candidate prepares and uses an interview questionnaire to gather user requirements (Award marks based on completeness and relevance of questions used for requirements gathering) | 5 | ||
| Candidate documents user requirements clearly and logically in notes or on provided templates (Award marks for clarity, organization, and completeness of requirements captured) | 4 | ||
| Candidate analyzes and organizes gathered requirements into functional and non-functional categories (Award marks for correct categorization and logical organization) | 3 | ||
| Candidate prepares a database assessment report including introduction, methodology, gathered requirements, and recommendations (Award marks for appropriate report structure, coverage of all sections, and professionalism) | 6 | ||
| Candidate saves the database file and assessment report correctly with appropriate filenames (Award 1 mark for database file and 1 mark for report file saved correctly) | 2 | ||
| Sub-Total | 22 | ||
| PRODUCT CHECKLIST | |||
| Database 'ClientDB' exists, functional and named correctly (Award marks for existence, correct naming, and ability to open without errors) | 3 | ||
| User requirements documented are complete, clear, and cover all essential database needs (Award marks for completeness and clarity of documented requirements) | 5 | ||
| Assessment report is well structured, professional, covers all required sections, and is within 4 pages (Award marks for report formatting, content quality, and adherence to length) | 5 | ||
| Sub-Total | 13 | ||
| GRAND TOTAL | 35 | ||
Type: Individual
| Tools & Equipment | Materials |
|---|---|
| Computer with DBMS software | Sample data sets for students and courses |
| Keyboard | |
| Mouse |
| S/N | Item | Quantity |
|---|---|---|
| 1 | Computer with DBMS software (e.g. MS Access or MySQL Workbench) | 1 Pc per Candidate |
| 2 | Sample data sets for students and courses | 1 Set per Candidate |
| 3 | Keyboard and mouse | 1 Set per Candidate |
| 4 | Power source and backup | 1 Pc per Candidate |
| Items to be Evaluated | Marks Available | Marks Obtained | Comments |
|---|---|---|---|
| TASK 1: Database Creation and Table Design | |||
| Launched the DBMS software and created a new database named 'CollegeDB' (Award 1 mark for launching DBMS, 1 mark for correct database name) | 2 | ||
| Created 'Students' table with fields: StudentID (Primary Key), FirstName, LastName, Gender, Department (Award 1 mark per field name, 1 mark for correct data type, 1 mark for Primary Key constraint on StudentID) | 10 | ||
| Created 'Courses' table with fields: CourseID (Primary Key), CourseName, Credits (Award 1 mark per field name, 1 mark for correct data type, 1 mark for Primary Key constraint on CourseID) | 6 | ||
| Created 'Enrollment' table with fields: EnrollmentID (Primary Key), StudentID (Foreign Key), CourseID (Foreign Key), Grade (Award 1 mark per field name, 1 mark for correct data type, 1 mark for Primary Key constraint, 1 mark each for Foreign Key constraints on StudentID and CourseID) | 12 | ||
| Sub-Total | 30 | ||
| TASK 2: Data Population and Queries | |||
| Populated 'Students', 'Courses', and 'Enrollment' tables with provided sample data (Award marks based on correct and complete data entry in all tables) | 8 | ||
| Created query listing full names and departments of all students (Award 3 marks for correct query syntax and output) | 3 | ||
| Created query displaying course names and grades for each enrolled student (Award 3 marks for correct query syntax and output) | 3 | ||
| Created query showing full names of all male students who are enrolled (Award 3 marks for correct query syntax and output) | 3 | ||
| Created query listing students who scored grades above 75 (Award 3 marks for correct query syntax and output) | 3 | ||
| Displayed student and enrollment data using table joins (Award 3 marks for correct join query and output) | 3 | ||
| Sub-Total | 23 | ||
| PRODUCT CHECKLIST | |||
| Database 'CollegeDB' saved correctly with all tables and data intact (Award 5 marks for correct saving and accessible database) | 5 | ||
| Queries run successfully with accurate and expected results (Award marks based on correctness and completeness of query outputs) | 7 | ||
| Sub-Total | 12 | ||
| GRAND TOTAL | 65 | ||
At the start of this chapter we promised you would be able to:
Tick each one you can genuinely do.
So, are you there yet?
You're competent when you can confidently do 50% or more of what this chapter promised.
Sign in to record how you're doing.