π Lecture 1 β Module-01: Introduction to Data & Information
π Overview: This foundational lecture establishes the critical distinction between data and information, demonstrating how raw facts are transformed into decision-useful content. It introduces the concept of a database as an organized repository of data and explains why a Database Management System (DBMS) is essential for managing, retrieving, and controlling that data efficiently, contrasting this with manual data handling.
ποΈ Topics Covered
This lecture begins by defining data as raw material and information as processed, context-relevant data, using concrete examples like a telephone directory and student records. It contrasts life with and without databases, highlighting benefits such as reduced redundancy and easier access. The lecture explains why we have databases (not "information bases"), distinguishes a database from a DBMS, and finally breaks down the five core components of a DBMS: data, users, hardware, software, and procedures.
π Lecture Summary
A. Definition of Data
Data can be referred to as raw material from which we can draw conclusions after analysis, or the facts from which we can infer new facts. Data has nothing to do with decision making, but it lays down the foundation for decision making. Data is collected and further analyzed to convert it into information suitable for decision making. Data and information are two separate things and are not to be confused with each other.
π Definition β Data: Raw material or facts from which we can draw conclusions after analysis or infer new facts. It has nothing to do with decision making but provides the foundation for it.
B. Examples of Data
The following are examples of data:
- Telephone Directory: a huge collection of data, with an internal structure of representation i.e., name, telephone number, city or address. Facts with structures are also termed as data.
- Student Record on Computer: a file on a computer containing data of ten thousand students is also data. This data too has an internal structure in the form of Student ID, Student Name, CGPA, and the like.
C. Definition of Information
Information can be defined as processed or organized data presented in a given context so as to make it useful related to the problem in hand. When a specific set of data is analyzed or interpreted, it becomes information that is more suitable for decision making. Simply stating, data becomes information when it becomes relevant to the decision problem.
π Definition β Information: Processed or organized data presented in a given context to make it useful for the problem at hand. Data becomes information when it becomes relevant to the decision problem.
π‘ Why this matters: This distinction is the core of why we build databasesβto store raw data efficiently so we can later retrieve and process it into information for a specific purpose.
D. Examples of Information
The following are examples of information:
- Telephone Directory: as stated above, the telephone directory is a huge set of data, and when we process this set of data to get the telephone number of a specific dentist or a colleague, it becomes information.
- Student Record on Computer: a file on a computer containing data of ten thousand students is again a huge set of data, which converts into information when processed to get a list of students with a CGPA greater than three.
E. Comparison of Data & Information
Data and information are often considered to be synonyms of each other, but the truth is that there is nothing in common between them. Both have different meanings and characteristics. Information is a subset of data, typically the required set of data. Data leads to information, so information is considered to be dependent on data.
F. Example to Elaborate the Difference Between Data and Information
Consider a file storing flight routes from one city to another. Data is structured in the form of Flight ID, Origin, Destination, Date of Departure, Time of Departure, etc. The file contains two thousand routes. This file qualifies to be called data because it's a huge set of structured data. This huge data turns into information when processed or filtered to get details about a flight for a specific destination, for example, from Lahore to Karachi on April 15th.
π Example: A flight schedule file with 2,000 records is data. Filtering it to find flights "from Lahore to Karachi on April 15th" produces information.
G. Life With & Without Database
A database is organized data with digital procedures, which is able to handle different sets of data with a very large capacity. A database is a huge repository of data that comes with ease to manage. Therefore, databases have become a substitute for the manual handling of lots of files, which come with very high risks and chances of data loss. Access to data has become easy and less time-consuming due to databases.
H. Benefits of Using Databases
As mentioned above, the advantages of using databases are enormous. Benefits of using databases vary from reducing redundancy in data to getting rid of unnecessary sets of data. Without databases, loads of data are handled manually with many potential risks and are difficult to access. With databases, it's easy to access large sets of data when required. The example of a Driving License and Passport serves as a good example in which the profile data is the same but it is repeated over again, highlighting the problem of redundancy that databases solve.
I. Why Database, Not Information Base?
Databases deal with the storage or organization of data, and the main focus of databases is to optimize data storage. On the other hand, information β as it is a subset of data β is all about the retrieval of specific data for different purposes. As information is dependent on data, databases are the basic requirements for information, which can then be used for multiple purposes.
π‘ Why this matters: The term "database" focuses on the storage mechanism. If we called it an "information base," we would miss the crucial first step of efficiently storing and organizing the raw data before it can be turned into information.
J. Difference Between Database and Database Management System (DBMS)
A database is all about the design and structure of the data, and a DBMS works as a tool to manipulate or analyze the data inside the database. A DBMS is a whole system to manage a digital database, its storage, creation, and retrieval (of information). Differentiating between these two terms: a database is a huge set of data, while a DBMS is a tool to manage or control that data in a database, with the major function of data retrieval.
π Definition β Database vs. DBMS:
- Database: The design and structure of the data (e.g., Employee Records Columns).
- DBMS (Database Management System): A tool/system to manage the digital database, its storage, creation, and retrieval (e.g., Oracle).
K. Example of Database and DBMS
- Example 01:
- Database: Employee Records Column with Employee ID, Name, Qualification, Date of Joining, etc.
- DBMS: Oracle to create and load employee records.
- Example 02:
- Database: Individual files on Hard Disk.
- DBMS: Operating System to read the file from Hard Disk.
L. Components of Database Management System
A DBMS is the aggregate of the following components:
- Data: The data inside the database which is to be processed, organized, retrieved, or updated.
- User: The people who manage the databases and perform different operations on them. They can be end users, database administrators, or application programmers.
- Hardware: A set of physical electronic devices such as computers (together with associated I/O devices like disk drives), storage devices, and I/O channels that make the interface between computers and the real world systems.
- Software: The set of programs used to handle the database and to control and manage the overall computerized database.
- Procedures: Instructions and rules that help to design the database and to use the DBMS.
β Key Takeaways
The single most critical understanding from this lecture is the clear, operational distinction between data (raw, unprocessed facts) and information (processed data relevant to a decision). A database is a structured repository for the former, while a DBMS is the system of software, hardware, users, data, and procedures used to manage it. The primary goal of a database is to optimize data storage, making it a prerequisite for extracting information. Finally, the core components of a DBMS are the five interdependent parts: data, users, hardware, software, and procedures.
π§ Quick Revision Questions
- What is the fundamental difference between data and information in the context of decision making?
- If you have a spreadsheet of all student names and their final exam scores, is it data or information? What would make it information?
- Why is it called a "Database" and not an "Information Base"?
- What is the difference between a database and a Database Management System (DBMS)? Give an example of each.
- List the five core components of a DBMS and briefly describe the role of one of them.
π Lecture 2 β Data Storage Mechanism
π Overview: This lecture explains the foundational data models used in database design, starting from the basic architectural unit of a data model through various historical models. It covers flat file, hierarchical, and network database models, detailing how each stores, organizes, and retrieves data, and why understanding these models is crucial for designing efficient modern databases.
ποΈ Topics Covered
The lecture begins with the definition and importance of a data model as the architectural unit of a database. It then explains the flat file database model, including how it works with columns, rows, and duplication issues. Next, the hierarchical database model is introduced as a tree-like structure based on one-to-many parent-child relationships. Finally, the network database model is covered as a flexible alternative that allows multiple parents and many-to-many relationships.
π Lecture Summary
A. Data Model Basics
A data model is the basic architectural unit of a database, determining the structure, organization, and storage of data. It defines the connections, processing, and storage of data in a system. The data model organizes data and determines how data elements relate to each other. It acts as the map or design of the database and is difficult to change once data is inserted.
M. Flat File Basics
A flat file is a database stored on its host computer system as an ordinary file, requiring the complete file to be read into memory for processing or performing operations. This database contains one record per line and prefers plain text (word or notepad) or ASCII File format. The flat file database design puts all data around a single table, and data has no interrelationships.
N. How Flat File Works
Data in a flat file is stored in columns and rows, with each row separated by a comma or tab. Each line of text holds one record and contains many fields, often with duplicate data. There is no relation between data, and as more records are added, the chances of data duplication increase. This redundancy results in reduced integrity of data, making it more unreliable. Additionally, duplication makes it difficult to update records because there are non-unique records in the database.
π Example: In a flat file storing customer orders, each line might contain "John,New York,Order1,Order2" where John's name and city are repeated for every order, creating duplicate data.
O. Hierarchical Database Basics
The hierarchical database is one of the two main data models proposed by IBM's IMS System. It is a data model in which data is stored in a tree-like structure. Data is stored as records (combination of rows and columns), and these records are connected through links. The Hierarchical Data Model organizes a database with multiple one-to-many relationships. The structure is based on the rule that one parent can have many children, but children are allowed only one parent. To retrieve data from a hierarchical database, the whole tree must be traversed starting from the root node.
π Definition β Root Node: The topmost node in a hierarchical database tree from which traversal begins to retrieve data.
π Formula: One-to-many relationship β One parent record can link to many child records, but each child has exactly one parent.
π Example: An organizational chart where one manager (parent) oversees multiple employees (children), but each employee reports to only one manager.
P. How Hierarchical Database Works
In the hierarchical data model, data is retrieved using traversal β meaning visiting the root node and navigating through its children. There is a one-to-many relationship between root and its child nodes. Each parent record stores the address of its child records, and every child record acts as a parent record for its next level.
π‘ Why this matters: This structure makes hierarchical databases fast for accessing data from a known root but inefficient for finding data that requires starting from a middle or leaf node.
Q. Network Database Basics
Opposite to the hierarchical model, the network model allows each record to have multiple parents and child records. This structure forms a generalized graph structure, and this model can be seen as an upside-down tree. This model is considered a very flexible way of representing objects and their relationships with each other. The network database model is easy to navigate because of the linkages between the information and many-to-many relationships.
π Definition β Many-to-many relationships: A relationship where multiple records can be linked to multiple other records, unlike the one-to-many restriction of hierarchical models.
π Example: In a university database, a student can enroll in multiple courses, and each course can have multiple students β a many-to-many relationship.
R. How Network Database Works
There is no concept of parent-child relationship in this type of data model. Each record stores the addresses of all the referencing records. As it supports many-to-many relationships between root and child nodes, any record can be linked to any record, and thus there is no hierarchy in this type of data model.
π Example: A database of books and authors where one book can have multiple authors, and each author can write multiple books β each record stores pointers to all related records.
β Key Takeaways
The data model is the fundamental architectural unit determining database structure and storage, and it is difficult to change after data insertion. Flat files store data in a single unstructured table with no relationships, leading to data duplication, reduced integrity, and update difficulties. Hierarchical databases use a tree structure with one-to-many relationships where each child has one parent, requiring traversal from the root for data retrieval. Network databases overcome hierarchical limitations by allowing many-to-many relationships where any record can connect to any other record, creating a flexible graph structure. The evolution from flat files to network models shows increasing flexibility in representing data relationships, which is essential knowledge for understanding relational and modern database designs.
π§ Quick Revision Questions
- What is a data model and why is it difficult to change after data is inserted?
- How does data duplication in flat files affect data integrity and update operations?
- What is the key rule about parent-child relationships in a hierarchical database model?
- How does the network database model differ from the hierarchical model in terms of relationship types?
- In the network model, why is there no concept of parent-child relationship?
π Lecture 3 β Three-Tier Architecture
π Overview: This lecture introduces the Three-Tier Architecture as a solution for managing application complexity and enterprise scalability. It explains how dividing an application into three independent tiersβPresentation, Business Logic, and Dataβenables modular development, fault tolerance, and easier maintenance. The lecture also covers roles in DBMS, client-server architecture, and distributed processing.
ποΈ Topics Covered
The lecture defines tiers as logically related but physically independent components, introduces the rationale for 3-Tier architecture, and explains each of the three tiers: External Level (Client Interface), Conceptual Level (Business Logic), and Internal Level (Data Tier). It emphasizes layer independence with illustrative examples, then moves to roles in database management (Application Programmer, End User, DBA, System Analyst), client-server architecture with a chat example, and finally distributed processing.
π Lecture Summary
A. Introduction to 3-Tier Architecture
Tiers are defined as the collection of logically related but physically independent components of an application. In this architecture, the application is divided into 3 tiers, where each tier has its own boundary. Each tier contributes to the whole, and several tiers join to make something complete. By segregating an application into various tiers, developers acquire the option of modifying or adding a specific layer, instead of reworking the entire application.
π Definition β Tier: a collection of logically related but physically independent components of an application
S. Rationale for 3-Tier Architecture
3-Tier architecture emerged as a solution to application complexity and enterprise scalability. This new architecture proposes three layers, allowing different teams to work on different layers simultaneously, thus making the development process easier. Dividing an application into 3-Tiers helps avoid a single point of failureβfailure of one tier does not cause the whole application to crash.
T. External Level (Client Interface)
This is the top-most layer of 3-Tier architecture, also known as the Presentation Layer. This tier manages the input/output data and their display. In other words, it displays what clients view. This tier is responsible for formatting the input/output data into a presentable form. It can communicate one tier below with the application tier to display information. In simple words, it is a tier that users can access directly, such as mobile applications, browsers, and forms.
U. Conceptual Level (Business Logic)
This tierβalso referred to as the application tierβis the middle tier that bridges the gap between the user interface and the underlying database. This tier consists of business and data rules. In this tier, the logic of the business is encapsulated (e.g., Programming, Class Diagram, ERD). This tier receives requests from the presentation tier only, interprets or processes the requests according to the defined rules, and sends back the results to the presentation tier only. It can receive requests and send responses to the presentation tier only, and it can send requests to only the below tier, i.e., Internal Level (Data Tier).
V. Internal Level (Data Tier)
This tier is responsible for storing information and data needed for the system and for optimizing data access. Data needed by the application logic layer are retrieved from the database, and the computation results produced by the application logic layer are stored back in the database. This tier can receive requests from the Conceptual Level (logic tier) only and can send responses to that tier only. All decisions related to data storage are kept here, and these storage mechanisms are independent of other tiers.
W. Layer Independence
The tiers mentioned above have no interdependence and work exclusively. Every tier is totally unaware of the internal working or the logics of other tiers, and the decisions made by the tiers are also independent. In simple words:
- Data layer is not aware of the internal working of the logic layer
- Logic layer is not concerned about the workings of the data layer
- Presentation layer works in total independence from other layers
π‘ Why this matters: This independence means changes can be made to one tier (e.g., changing the database) without affecting the other tiers, making the system highly flexible and maintainable.
X. Example β Presentation Layer Independence
Consider the following situation: Query: Get Total Sales. A manager of a company needs to run a sales query to find out the list of all sales made last year. He will use the presentation tier (client interface) to send this request to the application tier. Suppose this is done using a form, browser, or mobile app. The way the request is made cannot affect the way the data is retrieved. All other tiers will work in total independence. Similarly, all other tiers cannot affect the way data is presented in the presentation tier.
Y. Example β Logical Layer Independence
Continuing with the same example: Query: Get List of all Sales made last year. The structure or the workings of this tier are also exclusive to the logical tier. Using if-then, while, or any other structure (i.e., how the query is made) is internal to this tier only and cannot affect the way data is displayed.
Z. Example β Data Layer Independence
As shown in the figure, the application tier will send the query to the data tier, and it will respond to the application tier only with the requested results. What logic the application has used or will use is not the concern of the data tier; it will just provide the required results. The application tier will perform the activity as it is programmed to do and will forward the results to the presentation layer, which will display the results to the end user. None of the mentioned tiers can affect the working or processes of the other tiers.
AA. Roles in Database Management System (DBMS)
There are the following roles in a database environment:
- Application Programmer: develops the application that provides the required functionality for the end user.
- End User: the 'clients' for the database, which has been designed, implemented, and maintained to serve their information needs.
- Database Administrator (DBA): responsible for the physical realization of the database, including physical database design and implementation, security and integrity control, maintenance of the operational system, and ensuring satisfactory performance of the applications for users.
- System Analyst: a person who uses analysis and design techniques to solve business problems using information technology.
BB. Client Server Architecture
Client-server architecture is an architecture of a computer network in which many clients (remote processors) request and receive service from a centralized server (host computer). Client computers provide an interface to allow a computer user to request services of the server and to display the results the server returns. Servers wait for requests to arrive from clients and then respond to them. The server is powerful in terms of processing (e.g., file server, printer server, email server). The client is connected to the server via a communication link. The client interacts with the server when it requires access to any additional functionality that does not exist in its own system.
CC. Example β Client Server Architecture
The client-server architecture is best illustrated with the example of chatting over the internet, where communication takes place between multiple clients with multiple clients. The chat clients send the user-typed message to the server; the server then aggregates typing from all the clients and forwards it to all the clients. User's clients on the other side display the aggregated typing from the chat server.
DD. Distributed Processing
A distributed system is a combination of multiple components located on a network, and these components communicate and coordinate their actions by passing messages. These components interact with each other to achieve a common goal. The processing is divided into multiple systems, increasing the processing power. In distributed computing, a problem is divided into many tasks, each of which is solved by one or more computers, which communicate with each other by message passing.
EE. Example of Distributed Processing
(To be done by Sheraz SB)
β Key Takeaways
The most critical concepts from this lecture are: (1) The Three-Tier Architecture separates an application into Presentation, Business Logic, and Data tiers, providing modularity and fault tolerance. (2) Layer independence means each tier is unaware of the internal workings of other tiers, allowing changes to one tier without affecting others. (3) The database environment involves four key roles: Application Programmer, End User, Database Administrator, and System Analyst. (4) Client-server architecture involves clients requesting services from a centralized server, as illustrated by the chat example. (5) Distributed processing divides a problem into tasks solved by multiple computers communicating via message passing.
π§ Quick Revision Questions
- What are the three tiers in the Three-Tier Architecture, and what is the primary responsibility of each?
- Explain why layer independence is important for application maintenance and scalability.
- Describe the four roles in a DBMS environment and their key responsibilities.
- Using the chat example, explain how client-server architecture works in terms of request and response.
- How does distributed processing differ from client-server architecture in terms of task execution and communication?
π Lecture 4 β Fact Finding Technique
π Overview: This lecture introduces the essential fact-finding techniques used in database development to gather accurate requirements. It covers multiple methods including document examination, interviews, observation, research, and questionnaires, explaining how each technique contributes to understanding the current system and identifying data needs for the new database.
ποΈ Topics Covered
The lecture covers six main fact-finding techniques: examining documents basics and the importance of documenting existing systems, conducting interviews with their types (unstructured and structured with open-ended and close-ended questions), observing enterprise operations with best practices, researching existing solutions, and using questionnaires with free-format and fixed-format questions. Each technique includes practical examples and guidelines for effective implementation.
π Lecture Summary
A. Examine Document Basics
Examine documents is the first step in database development that reveals how the need for a database arose and what symptoms and problems in the current system led to this decision. This technique is critical for studying the current system and identifying the affected part of the organization. It is also valuable for identifying the data to be collected and reported by the system.
π Definition β Examine documents technique: A fact-finding technique where existing documents are reviewed to understand how the need for a database arose and to study the current system.
GG. Documenting the Examine Document
Documenting the existing systems leads to identifying the type of data coming in and out of the system, laying the foundation for database requirements. This documentation identifies the data being handled and the relationship between the data, explaining how data flows from one part to another, thus creating a better and more efficient system. The lecture illustrates this with a figure showing data about customers and services requested, where problems are categorized into two categories, demonstrating how examining documents reveals information flows among different stakeholders.
HH. Conducting Interviews Basics
Interviewing is the most commonly used and normally most useful technique for fact finding, where the business analyst gathers information through face-to-face interaction. The objectives of interviews include fact finding or verifying facts, getting more diverse ideas and information, gathering requirements, involving the end user to generate enthusiasm, and making them feel engaged in the whole project.
π Definition β Interviewing: A fact-finding technique where the business analyst gathers information by having face-to-face interaction with stakeholders.
II. Types of Interview
There are two types of interviews:
- Unstructured Interviews: These interviews are conducted with a general goal in mind with very few specific questions. The interviewer lets the interviewee drive the discussion and provide direction to the interview.
- Structured Interviews: In this type, the interviewer has a specific set of questions which can be further divided into two categories:
- Open-ended Questions: These let the interviewee respond in any way that seems appropriate with no specific options to choose.
- Close-ended Questions: These restrict the answers to either a specific choice or very short answers.
JJ. Example of Type of Interviews
π Example 01 β Unstructured Interview: A researcher asks a caregiver "What kinds of illnesses do children in this village get?" The caregiver freely responds about diarrhea, cough, cold, measles, fever, typhoid. The researcher then follows with "Are there any other during cold and hot weather?" and the caregiver adds pneumonia and whooping cough. The conversation continues naturally about measles symptoms and transmission.
π Example 02 β Structured Interview: The interviewer asks specific questions like "Could you tell me the tasks you do to prepare salaries per month?" and "How do you know person monthly salary?"
KK. Observing the Enterprise in Operations
Observation is one of the most effective fact-finding techniques as it gives the analyst a chance to participate in or watch the person perform the activity, resulting in deep understanding of the system. This technique is particularly useful when the validity of data collected through other methods is a serious concern or when the system is too complex for the end user to explain properly. To ensure success, it is necessary to know as much about the individual and activity as possible, including when low, normal, and peak periods occur for the activity being observed.
π Definition β Observation: A fact-finding technique where the analyst participates in or watches a person perform an activity to gain deep understanding of the system.
LL. Have and Have Not's for Observing
The observation should be recorded immediately or in parallel with the observation. The observer must not wait until the observation ends to write the complete process; rather, notes should be taken in bullet form during the observation to avoid losing any point. The observer must not interrupt or ask too many questions from the end user while they are performing the activity, as this would temper the activity and prevent the observer from getting real information.
MM. Research
Research is valuable for solving the problem in hand. Internet, journals, and reference books are good sources of information about how others have solved related problems or what solutions are available. Research can save a lot of time as ready-to-deploy solutions can be found to fulfill requirements. It is also helpful in validating information gathered through observation, as there are chances that the actual execution of the activity differs from what was observed.
NN. Questionnaire
Questionnaires are specific purpose documents used to gather information from a large number of people while maintaining some control over the responses. There are two types of questions:
- Free-Format Questions: These offer greater freedom to respondents as they answer in the space provided after the question. Responses are more subjective in nature and difficult to tabulate.
- Fixed-Format Questions: These require specific responses where individuals choose from available options. Responses are more specific and easier to tabulate, but the disadvantage is that the researcher doesn't get additional information that might be worth knowing.
π Definition β Questionnaire: A specific purpose document used to gather information from a large number of people while maintaining some control over the responses.
OO. Example of Questionnaire
π Example: Given the requirement "What are current trends among students in terms of interest in media programs?", the lecture shows a sample questionnaire in Figure 1. The questionnaire includes a title "Student Media Interest Survey" and contains questions about age, gender, preferred media programs, time spent, and reasons for interest, using both free-format and fixed-format questions.
β Key Takeaways
The lecture presents six essential fact-finding techniques for database development: examining documents, conducting interviews (both unstructured and structured with open-ended and close-ended questions), observing enterprise operations, researching existing solutions, and using questionnaires. Each technique has specific advantages and best practices β interviews are most commonly used, observation provides deep understanding but requires immediate note-taking without interruption, and questionnaires are best for gathering information from large numbers of people. Document examination is the critical first step that reveals data flows and relationships within the organization. The choice of technique depends on the complexity of the system, the number of stakeholders involved, and the need for validation of collected data.
π§ Quick Revision Questions
- What are the six fact-finding techniques covered in this lecture?
- What is the difference between unstructured and structured interviews?
- Why should notes be taken during observation rather than after it ends?
- What are the advantages and disadvantages of fixed-format questions in questionnaires?
- How can research help in validating information gathered through observation?
π Lecture 5 β Implementing Fact Finding Techniques
π Overview: This lecture covers the critical transition from fact-finding activities to formal requirement writing in the database design cycle. It provides practical examples of translating interview and questionnaire responses into structured requirements, and explains how to derive a system definition from those requirements to guide the entire development process.
ποΈ Topics Covered
The lecture explains the process of converting fact-finding results into written requirements, using detailed examples from a rental system interview and a restaurant questionnaire. It then defines how to create a comprehensive system definition from these requirements, including concept definition and the System-of-Interest (SoI), followed by a step-by-step extraction process and a list of essential database features.
π Lecture Summary
A. From Fact-finding to Requirement Writing
Requirement writing is the immediate next step after fact-finding in the cycle of database design and development. The requirements defining the systems are to be converted into written format. Along with the system definition, it also contains and explains the data flow in the system and the relationships between the data. The requirement or the specification document describes in detail the data to be held in the database and how the data is to be used (i.e., the processes and the relationships). These requirements are specific and measurable in nature. The system requirement, like how fast a transaction must run or how many transactions must be processed in a specific interval of time, form the basis of a number of decisions in database design and development.
π‘ Why this matters: Without precise, written requirements, the database design will be based on assumptions and may fail to meet stakeholder needs. Measurable requirements ensure the final system can be tested and verified.
PP. Example of Translating Interview to Requirements
Consider the following example in which the interviewer asks questions to get the requirements for a high-level database for a rental system of a certain plaza. Following the interview are the requirements gathered through the interview.
Interview:
- Interviewer: How many building types are there for rent? Interviewee: Primarily Apartments, some Offices and few Shops
- Interviewer: How many are total apartments, total offices and total shops? Interviewee: Ahhhh... yes 15 Apartments, 5 offices and 3 shops
- Interviewer: How many floors are there in the plaza? Interviewee: 6 floors but we have apartments only on 3 floors and on remaining floors we have shops and offices
- Interviewer: Do we have fix rent for each apartment or does it vary from Floor to Floor? Interviewee: Rent varies from Floor to Floor of apartment.
- Interviewer: Did you send rent bill / receipt at the end of month? Interviewee: We usually send bill for two-months but receive installments on monthly basis also.
- Interviewer: Can you tell me specific data you store about customer into the system? Interviewee: We usually ask for name, address and phone no.
- Interviewer: Did you assign any number to customer? Interviewee: Yes, I miss out.
- Interviewer: If multiple apartments / shops / offices are rented to same customer, then do we have same contract no and customer no? Interviewee: Good question, let me think....pause, we usually assign different contract no but one bill to such case.
Requirements (derived from interview): In a plaza renting system, there are three types of buildings primarily: apartment, offices and shops. There are multiple floors in a plaza and for 3 floors apartments are allocated but for remaining there can be a mix of shops and offices. When a customer is registered, usually customer id, name, phone and address is stored as profile and a bill is generated for the rent on bi-monthly basis but customer has an opportunity to pay the bill on monthly basis. Contract is signed and uploaded against every building type. Contract id is assigned to every contract. It is possible that a customer may rent multiple building types; in this case, a different contract no is assigned to same customer. One Bill is generated for customers with multiple building types.
π Example: From the interview, the requirement "Rent varies from Floor to Floor of apartment" is captured. The requirement "One Bill is generated for customers with multiple building types" translates the specific business rule discovered in question 8.
QQ. Example of Translating Questionnaire in Requirements
Following is a sample questionnaire to elaborate the translation of data gathered through questionnaires into requirements.
Questionnaire:
- What is price (per person) range of food offered?
- 500-1000
- 700-1200 (checked)
- 1000-1500
- Is cost of dish calculated on the basis of?
- Cost of ingredient only (checked)
- Cost of ingredient and electricity also
- Cost of ingredient plus % of profit
- Is % of Profit?
- 20% (checked)
- 15%
- 10%
- None of the Above
- Are ingredients and Quantity mentioned in?
- Menu
- Recipe (checked)
- Restaurant Manual
Requirements (derived from questionnaire): In a restaurant management system, there are many dishes offered either as individual serving or buffet. Price range between 700-1200 is targeted which will include drinks and taxes also. Cost of every dish is calculated individually depending on ingredients involved only. Each ingredient is listed in recipe and quantity is also mentioned. Cost is calculated as per market rate of ingredient with 20% profit to cater for management and miscellaneous cost.
π Definition β Questionnaire Translation: The process of converting structured, closed-ended questionnaire responses into clear, actionable system requirements by interpreting the checked options and implied business rules.
π Example: The checked option "Cost of ingredient only" translates to the requirement: "Cost of every dish is calculated individually depending on ingredients involved only." The checked option "20%" translates to: "Cost is calculated... with 20% profit."
RR. Defining System Definition from Requirements
System definition is defined by listing down the details of the whole system. These details, when properly concluded, form the basis of decisions regarding the scope and the boundaries, the architecture and the design of the system to be developed. Concept definition artifact lays down the foundation of system definition; concept definitions are activities in which the needs and the requirements of all the stakeholders are closely examined before defining the system. The concept definition is the articulation of System-of-Interest (SoI) β the model of system on the basis of needs and requirement β which is a collective set of all elements of any system being considered by the lifecycle.
π Definition β System Definition: A document that details the scope, boundaries, architecture, and design of the system to be developed, derived from the requirements and stakeholder needs. π Definition β Concept Definition Artifact: The foundation activity that examines stakeholder needs and requirements before defining the system. π Definition β System-of-Interest (SoI): The model of the system created from the needs and requirements, representing the collective set of all elements of the system under consideration.
SS. Process of Extracting System Definition
System definition is based on the concept definition, a deep understanding of concepts, needs, expectations and stakeholders' requirements. System is further divided into subsystems through top-down decomposition of system-of-interest in order to reach the exact destination. This same model is shown in Figure 13 (see text). The needs and the concepts along with the stakeholder requirements are gathered to form a system-of-interest, and this is further divided into subsystems to fulfill the desired requirements.
The system should list all the important features for a database system and these should include the following:
- Initial database size
- Database rate of growth
- The types and average number of record searches
- Performance
- Security
- Backup and recovery
- Legal issues etc.
π Definition β Top-Down Decomposition: The process of breaking a system-of-interest into smaller, more manageable subsystems to reach the specific design destination.
π Formula/Model: Needs + Concepts + Stakeholder Requirements β System-of-Interest (SoI) β Subsystems β Fulfilled Requirements.
β Key Takeaways
The most critical lesson is that fact-finding is useless without proper translation into precise, written requirements. You must master converting open-ended interview answers and structured questionnaire responses into formal requirement statements, preserving all business rules and constraints like "one bill for multiple contracts" or "20% profit on ingredient cost." The system definition then synthesizes these requirements into a comprehensive blueprint that determines the scope, architecture, and design of the database, further decomposing into subsystems via top-down analysis. Essential database features like initial size, growth rate, performance, security, backup, and legal issues must be explicitly documented. For the exam, remember the direct line from fact-finding technique β requirement β system definition β database design.
π§ Quick Revision Questions
- What is the immediate next step after fact-finding in the database design cycle?
- In the plaza rental system example, what business rule was discovered about billing when a customer rents multiple building types?
- In the restaurant questionnaire example, what is the profit percentage applied, and on what cost basis?
- What is a System-of-Interest (SoI), and how does it relate to concept definition?
- List four of the seven essential features a database system definition must include.