Professional Documents
Culture Documents
Information Sheet ITAp 313-7
Information Sheet ITAp 313-7
List of Modules
No. MODULE
MODULE TITLE
CODE
TOPICS:
1. Business Benefits of High-Quality Information
2. Storing Information sing a Relational Database Management System
3. Using a Relational Database for Business Advantages
4. Case Study
ASSESSMENT METHOD/S:
• Written Quizzes and Assignments on PDF sent through FB Messaging or
email
• Oral recitation or Demonstrative Exercises via Google Meet
REFERENCE/S:
Laudon, K.C., and Laudon, J.P. (2014). Management Information Systems:
Managing the Digital Firm 13th Global Edition. Essex: Pearson Education Limited.
Post, G.V. (2012). Management Information Systems Cases.
Stair, R.M., and Reynolds G.W. (2013). Principles of Information Systems: a
Managerial Approach 6th Edition.
Learning Objectives:
After reading this INFORMATION SHEET, YOU MUST be able to:
1. Explain the four primary traits that determine the value of information;
2. Describe a database, a database management system, and the relational
database model;
3. Identify the business advantages of a relational database; and
4. Explain the business benefits of a data-driven website.
Introduction:
Welcome back, and congratulations on completing the midterm exams.
In this module, we go back and build on the concepts of data and databases; then in the next
module, we will revisit data warehousing.
Interesting stuff, but thankfully this module is also quite short. So let us begin.
Data quality is crucial – it assesses whether information can serve its purpose in a particular
context (such as data analysis, for example). So, how do you determine the quality of a given set
of information? There are data quality characteristics of which you should be aware.
There are five traits that you’ll find within data quality:
Source: https://www.precisely.com/blog/data-quality/5-characteristics-of-data-quality,
downloaded on 29 July 2020.
There are hundreds of transactions that go through organizations every day. The result of these
transactions is transactional information. Transactional information is all the information
contained within a business unit. The primary purpose of transactional information is to
support the day-to-day operations of the unit. Examples of transactional information include
sales receipt, packing slip, purchase confirmation, etc. So transactional information is the result
of performing daily operating tasks.
Databases that can handle transactions are known as transactional databases. The main
purpose of a database is to ensure the accuracy and integrity of information. That’s why it is
extremely important that when a transaction takes place, it is recorded in a database accurately
and consistently. To illustrate this point, let’s look at an example of a double-entry accounting
system where we use debits and credits. Any transaction involves a debit and a credit so a
transactional system will record both debit and credit or a transaction cannot take place. This
way, you cannot have a transaction involving a debit or a credit only. So integrity and consistency
of information are ensured.
Source: http://www.computerbusinessresearch.com/Home/database/transactional-
information, downloaded on 29 July 2020.
Information Governance
The goal of a holistic approach to information governance is to make information assets available
to those who need it while streamlining management, reducing storage costs, and
ensuring compliance. This, in turn, allows the company to reduce the legal risks associated with
unmanaged or inconsistently managed information and be more agile in response to a changing
marketplace.
Source: https://searchcompliance.techtarget.com/definition/information-governance,
downloaded on 29 July 2020.
A relational database organizes data into tables that can be linked—or related—based on data
common to each. This capability enables you to retrieve an entirely new table from data in one
or more tables with a single query. It also allows you and your business to better understand
the relationships among all available data and gain new insights for making better decisions or
identifying new opportunities.
For example, imagine your company maintains a customer table that contains company data
about each customer account and one or more transaction tables that contain data describing
individual transactions.
The columns (or fields) for the customer table might be Customer ID, Company Name, Company
Address, etc.; the columns for a transaction table might be Transaction Date, Customer
ID, Transaction Amount, Payment Method, etc. The tables can be related based on the
common Customer ID field. You can, therefore, query the table to produce valuable reports, such
as a consolidated customer statement.
Report generators take these queries and run them on demand to create formal reports. Many of
the documents businesses run to track inventory, sales, finance, or even perform financial
projections come from a relational database operating behind the scenes.
You can communicate with relational databases using Structured Query Language (SQL), the
standard language for interacting with management systems. SQL allows the joining of tables
using a few lines of code, with a structure most non-technical employees can learn quickly.
With SQL, analysts do not need to know where the order table resides on disk, how to perform
the lookup to find a specific order, or how to connect the order and customer tables. The database
compiles the query and figures out the correct data points.
Those features make the relational approach the single most popular query tool in business
today.
Flexibility
SQL has its built-in language for creating tables called Data Definition Language (DDL). DDL
allows you to add new columns, add new tables, rename relations, and make other changes even
while the database is running and while queries are happening. This allows you to change the
schema or how you model data on the fly.
Reduced redundancy
Relational databases eliminate data redundancy. The information for a single customer appears
in one place—a single entry in the customer table. The order table only needs to store a link to
the customer table. The practice of separating the data to avoid redundancy is called
normalization. Progressional database designers make sure the tables normalize during the
design process.
Relational databases are transactional—they guarantee the state of the entire system is
consistent at any moment. Most relational databases offer easy to export and import options,
making backup and restore trivial. These exports can happen even while the database is running,
making restore on failure easy. Modern, cloud-based relational databases can do continuous
mirroring, making the loss of data on restore measured in seconds or less. Most cloud-managed
services allow you to create Read Replicas, like in IBM Cloud Databases for PostgreSQL. These
Read Replicas enable you to store a read-only copy of your data in a cloud data center. Replicas
can be promoted to Read/Write instances for disaster recovery as well.
Supplies/Materials : -- N/A --
Steps/Procedure:
1. Open the file MIS Case - FedEx.pdf you previously
downloaded from
https://drive.google.com/drive/u/1/folders/1eZeoJ
IPZpJuO2ZGnWL8zLfOnD5UA8rSy
2. Read the section “FedEx”; then answer the guide
questions. You may need to research additional
information on the internet.
3. Submit to the professor the answers to the guide
questions upon completion of this module at the end
of the week.
Assessment Method:
Once the student submits the written answers to the professor, the following
rubrics will be used to grade the output:
1. Gleaning information from the case study and using that information to
answer the guide questions directly – 5 points.
2. Searching for additional information about the topic not mentioned and
using that additional information as further arguments to answer the
guide questions – 5 points.
3. Adding personal insights and substantiating these insights based on 1
and 2 above – 10 points.
4. TOTAL Points: 20 points.