Designing computerized databases is a critical skill for ICT technicians tasked with developing robust, efficient, and scalable data management systems. In Kenya, organizations across sectors such as banking, healthcare, and county governments increasingly rely on computerized databases to store and manage vast amounts of information securely and accessibly. This chapter focuses on establishing the requirements for computerized database systems, starting with understanding the fundamentals of database management systems (DBMS) and effective techniques for gathering precise database requirements. Mastery of these topics ensures that ICT technicians can design databases that meet organizational needs while supporting data integrity, security, and ease of access.

1.1 Establishing computerized database requirements

Establishing database requirements is the foundational step in designing any computerized database system. It involves understanding the organization's data needs, workflows, and user expectations to create a system that supports operational efficiency and decision-making. In Kenya's dynamic ICT environment, clear and thorough requirements gathering prevents costly redesigns and ensures the database aligns with regulatory standards such as the Data Protection Act 2019. This section breaks down key concepts starting with the nature and role of DBMS, followed by practical techniques to gather accurate requirements.

1.1.1 Introduction to DBMS

The term Database Management System (DBMS) refers to software designed to define, create, manage, and control access to databases. It acts as an intermediary between users and the physical data, enabling efficient data retrieval, storage, and manipulation. For ICT technicians in Kenya, understanding DBMS is essential when working with systems in sectors like healthcare, where patient records require secure and reliable management.

Purpose of a DBMS

The primary purpose of a DBMS is to provide a systematic and organized way of storing, retrieving, and managing data. This includes:

• Data abstraction: Hiding complex data structures from users to simplify access.
• Data security: Controlling user access to sensitive data, critical in institutions like county health departments.
• Data integrity: Ensuring accuracy and consistency of data through constraints and validation.
• Data concurrency: Allowing multiple users to access data simultaneously without conflicts.
• Backup and recovery: Providing mechanisms to restore data after failures, important for financial institutions like banks.

Types of DBMS

DBMSs can be categorized based on data models and architecture, relevant to different organizational needs:

• Hierarchical DBMS: Organizes data in a tree-like structure; suitable for applications with one-to-many relationships.
• Network DBMS: Uses a graph structure supporting many-to-many relationships.
• Relational DBMS (RDBMS): Most common; represents data in tables with rows and columns, facilitating SQL queries.
• Object-oriented DBMS: Stores data as objects, useful in complex applications such as multimedia databases.
• NoSQL DBMS: Designed for unstructured data and big data applications, increasingly adopted in fintech startups.

Components of a DBMS

Understanding DBMS components helps ICT technicians manage and troubleshoot database systems effectively:

• Database Engine: Core service for storage, processing, and security of data.
• Database Schema: Defines the structure of the database including tables and relationships.
• Query Processor: Interprets and executes database queries.
• Transaction Manager: Ensures database transactions are processed reliably and adhere to ACID properties.
• Storage Manager: Handles data storage and access on physical media.

Advantages of Using a DBMS

Implementing a DBMS offers several benefits to organizations:

• Improved data sharing: Facilitates authorized access to data across departments, vital for county government offices.
• Minimized data redundancy: Eliminates duplication, saving storage and reducing inconsistencies.
• Enhanced data security: Implements access controls and encryption.
• Data consistency: Maintains uniformity through constraints.
• Efficient data access: Enables complex queries and reporting for decision support.

1.1.2 Database requirements gathering techniques

Gathering accurate database requirements is essential to designing systems that meet user needs and organizational objectives. In Kenya, where ICT projects often involve multiple stakeholders with diverse needs, effective techniques ensure clear communication and comprehensive data capture.

Interviews

Interviews involve direct interaction with stakeholders to collect detailed information about their data needs and workflows. This technique allows ICT technicians to clarify ambiguous points and explore requirements deeply.

• Structured interviews: Use predefined questions to ensure consistency.
• Unstructured interviews: Allow open-ended discussions to discover unanticipated needs.
• Group interviews: Facilitate discussion among multiple stakeholders for consensus building.

Interviews with hospital administration and staff, for instance, can reveal specific data fields necessary for patient management and reporting.

Questionnaires and Surveys

Questionnaires provide a cost-effective way to collect data from a larger user base, such as employees across county government departments.

• Closed-ended questions: Offer quantitative data for easy analysis.
• Open-ended questions: Capture qualitative insights on user preferences.
• Online surveys: Enable rapid distribution and collection, suitable for retail businesses with dispersed branches.

Careful questionnaire design is critical to avoid ambiguity and ensure relevant data is gathered.

Observation

Direct observation involves watching users perform their tasks to understand data flows and system interactions. This technique uncovers implicit requirements that users may not articulate.

• Workplace shadowing: Following users during routine activities.
• Process mapping: Documenting workflows and data exchanges.
• System usage monitoring: Analyzing current system logs to identify usage patterns.

At a SACCO, observing loan processing workflows can highlight data dependencies and timing requirements for database transactions.

Document Analysis

Reviewing existing documentation such as reports, forms, and manuals helps identify current data structures and requirements.

• Existing database schemas: Provide a starting point for enhancements.
• Business process documents: Outline data input and output needs.
• Policy manuals: Define data security and compliance requirements.

Prototyping

Creating preliminary database models or mock-ups allows stakeholders to visualize the system and provide feedback early.

• Low-fidelity prototypes: Simple sketches or diagrams to discuss structure.
• High-fidelity prototypes: Interactive models using DBMS tools.
• Iterative refinement: Incorporating feedback to improve the design.

This technique is effective in education institutions where administrators and lecturers validate student information systems.

Chapter Summary

This chapter provides a comprehensive overview of designing computerized database systems, beginning with the establishment of database requirements by exploring the fundamental concepts of database management systems, their functions, applications, types, components, and architecture. It emphasizes the importance of effective requirement gathering techniques, including elicitation and assessment to ensure the database meets user needs. Various database models are examined, such as relational, hierarchical, network, object-oriented, and dimensional models, each offering distinct approaches to organizing data. The chapter then delves into database design, starting with conceptual design where entity-relationship diagrams are used to represent entities, attributes, and relationships with their respective notations. It further explains the relational model and progresses to logical design, covering the definition of tables, keys, and the normalization process to eliminate redundancy. Finally, physical design aspects are addressed, focusing on the selection of appropriate data types, indexing strategies, and constraints to optimize database performance and integrity.