By the end of this chapter, you will be able to:
These skills will help you build strong, efficient database systems that make managing information easier and more reliable in any workplace.
Establishing database requirements is the initial and arguably most crucial phase in database system design. In Kenya’s dynamic software development landscape, gathering precise requirements from diverse sectors such as banking, healthcare, and government agencies ensures the database aligns with operational realities and compliance standards. This process involves comprehending the data to be managed, user interactions, and performance expectations, which collectively inform the database schema and architecture.
The Database Management System (DBMS) is the software that facilitates the creation, management, and use of databases. It acts as an intermediary between users and the physical data, providing tools to define, manipulate, and secure data. In Kenya, organizations ranging from microfinance institutions to county government offices rely on DBMS solutions to maintain data integrity and support decision-making.
Gathering database requirements is a collaborative process that involves stakeholders to ensure the database system reflects real-world needs. In Kenya's software development projects, especially those serving sectors like education and healthcare, thorough requirements gathering prevents costly redesigns and enhances user satisfaction.
Conducting structured interviews with end-users, managers, and IT staff uncovers detailed insights into data usage patterns, reporting needs, and pain points. For example, interviewing hospital administrators at a county referral hospital reveals specific patient data tracking requirements that inform the database schema.
Distributing questionnaires to a broad user base captures quantitative data on user expectations and frequency of database interactions. SACCOs use surveys to understand member data management needs, guiding the design of member databases.
Direct observation of daily workflows and data handling practices helps identify implicit requirements that users might not articulate. Shadowing clerks at a retail business exposes how sales data is recorded, influencing real-time inventory tracking features.
Reviewing existing documentation such as business process manuals, legacy system reports, and regulatory guidelines provides context and constraints. For instance, analyzing Kenya Revenue Authority’s data policies ensures the database design complies with taxation data standards.
Developing a preliminary database model and obtaining feedback from users enables iterative refinement of requirements. At a university, prototyping student registration data structures helps align the system with academic administrative needs.
Explain the main functions of a Database Management System and their significance in a banking application. (10 marks)
Compare and contrast the relational and hierarchical DBMS models with examples relevant to Kenyan organizations. (12 marks)
Discuss five different techniques used for gathering database requirements and illustrate how each can be applied in a healthcare setting. (15 marks)
Describe the role of transaction management in a DBMS and its importance in multi-user environments such as a SACCO. (8 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 provides a comprehensive overview of designing a database system, beginning with the establishment of database requirements through understanding the fundamental concepts of database management systems. It explains key terms, outlines the core functions of database systems, explores various applications, and distinguishes between different types of database management systems while detailing the major components and architectures involved. The process of gathering accurate database requirements is emphasized using appropriate techniques. The chapter then examines various database models including relational, hierarchical, network, object-oriented, and dimensional models, highlighting their distinct structures and uses. In the design phase, it covers conceptual design with a focus on entity-relationship diagrams, followed by the application of the relational model. Logical design is presented as the step where the conceptual model is translated into a logical structure, and physical design is discussed as the final phase that optimizes performance and storage. Together, these topics form a detailed framework for creating effective and efficient computerized database systems.
Type: Individual
| Tools & Equipment | Materials |
|---|---|
| Relational Database Management System (MySQL, PostgreSQL, MS SQL Server etc.) | |
| Data Modelling Tool (Lucidchart, EdrawMax, Draw.io etc.) | |
| Notebook and Pen for notes |
| S/N | Item | Quantity |
|---|---|---|
| 1 | Relational Database Management System (MySQL, PostgreSQL, MS SQL Server etc.) | 1 Pc per Candidate |
| 2 | Data Modelling Tool (Lucidchart, EdrawMax, Draw.io etc.) | 1 Pc per Candidate |
| 3 | Notebook and Pen for notes | 1 Pc per Candidate |
| Items to be Evaluated | Marks Available | Marks Obtained | Comments |
|---|---|---|---|
| TASK 1: Requirements Gathering | |||
| Candidate uses appropriate database requirements gathering techniques (interviews, questionnaires, observation) (Award 1 mark for each technique correctly applied) | 3 | ||
| Candidate identifies and lists at least six relevant entities for the school management system (Award 1 mark for each correctly identified entity, max 4) | 4 | ||
| Candidate specifies relevant attributes for each identified entity (Award 1 mark for each entity with at least 2 appropriate attributes) | 6 | ||
| Candidate defines appropriate relationships between entities with cardinalities (Award 1 mark for each correctly defined relationship with cardinality, max 4) | 4 | ||
| Candidate documents primary keys for each entity (Award 1 mark for each entity with correctly specified primary key, max 3) | 3 | ||
| Candidate presents the gathered requirements clearly and logically using the data modelling tool (Award 3 marks for clear, well-structured documentation and diagrams) | 3 | ||
| Sub-Total | 23 | ||
| PRODUCT CHECKLIST | |||
| Complete and clear database requirements documentation including entities, attributes, primary keys, and relationships with cardinalities (Award 7 marks for completeness, clarity, and accuracy of the documented requirements) | 7 | ||
| Sub-Total | 7 | ||
| GRAND TOTAL | 30 | ||
Type: Individual
| Tools & Equipment | Materials |
|---|---|
| Relational Database Management System (MySQL 8.0 or PostgreSQL 13) | integer |
| Data Modelling Tool (Draw.io or Lucidchart) | varchar |
| Rewritable Compact Disc (CD-RW) | date/time |
| S/N | Item | Quantity |
|---|---|---|
| 1 | Relational Database Management System (MySQL 8.0 or PostgreSQL 13) | 1 Instance per Candidate |
| 2 | Data Modelling Tool (Draw.io or Lucidchart) | 1 License per Candidate |
| 3 | Rewritable Compact Disc (CD-RW) | 1 Pc per Candidate |
| Items to be Evaluated | Marks Available | Marks Obtained | Comments |
|---|---|---|---|
| TASK 1: Explain DBMS Fundamentals | |||
| Candidate defines DBMS and explains its purpose (Award 1 mark for each correct aspect: definition, purpose, example) | 3 | ||
| Candidate correctly defines key terms: database, DBMS, schema, instance (Award 1 mark for each term correctly defined) | 4 | ||
| Candidate explains at least four main functions of a DBMS (Award 1 mark for each function clearly explained: storage, retrieval, security, backup) | 4 | ||
| Candidate demonstrates use of the RDBMS tool to create a sample database schema with at least two tables (Award marks for correct creation of schema, tables, attributes, and primary keys) | 5 | ||
| Candidate uses Data Modelling Tool to diagrammatically represent the database schema (Award marks for clear, correct ER diagram with entities, attributes, and relationships) | 3 | ||
| Sub-Total | 19 | ||
| TASK 2: Document and Present Findings | |||
| Candidate prepares a clear, concise written report explaining DBMS fundamentals (Award marks for clarity, completeness, and correct terminology) | 5 | ||
| Candidate saves the report and ER diagram on the CD-RW and demonstrates retrieval (Award marks for correct saving, naming, and retrieval of files) | 3 | ||
| Candidate answers assessor's questions on DBMS concepts confidently (Award marks for accurate, clear verbal responses) | 3 | ||
| Sub-Total | 11 | ||
| PRODUCT CHECKLIST | |||
| Written report is well structured, minimum 3 pages, with correct DBMS fundamentals and terminology (Award marks for content accuracy, structure, and language) | 5 | ||
| Database schema created in RDBMS with at least two tables and primary keys correctly defined (Award marks for correct schema creation and attribute specification) | 5 | ||
| ER diagram correctly drawn showing entities, attributes, and relationships (Award marks for completeness and clarity) | 5 | ||
| Report and ER diagram saved and retrieved successfully from CD-RW (Award marks for file management and demonstration) | 4 | ||
| Sub-Total | 19 | ||
| GRAND TOTAL | 49 | ||
At the start of this chapter we promised you would be able to:
Tick each one you can genuinely do.
Sample simulation — try how the simulator works. A version built for this chapter's practical is coming.
Prepare Kenyan PilauLocked ▸Free: practical guides, quick cards, workplace scenarios and more.
Now — 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.