Imam Mohammad Ibn Saud Islamic University

College of Computer and Information Sciences

Project Title: DATA WAREHOUSE SYSTEM

Section:

Information Systems Department

Course Title: Business Requirements Analysis
Course Code: IS 230
Course Dr. Abdulaziz AlSahli,
Instructor:
Agreement:
1- I and my team members -NOT an external party- performed this project.
2- I participated with the group members to accomplish this project effectively and
equally.
3- This project is free from copying and cheating from other students' works and
projects.
4- This project is free from illegally copying of any resources and intellectual
property breaches.
Based on the above, I sign below and accept any corrective action taken if I breach or
don't fulfill the above commitments.

Student Name Student ID Signature

Spring 2022

1
Contents
List of Figures............................................................................................................3
List of Tables..............................................................................................................4
1. Introduction:...............................................................................................................4
1.1 Description:..........................................................................................................4
1.2 Scope:...................................................................................................................5
2. Business Requirements:.............................................................................................6
2.1 Background:.........................................................................................................6
2.2 Business Objectives:............................................................................................6
2.3 Vision:..................................................................................................................7
3. Stakeholders:..............................................................................................................7
4. Elicitation Techniques:...............................................................................................7
4.1  Stakeholder Analysis..........................................................................................7
4.2 Brainstorming.......................................................................................................7
4.3 Interview..............................................................................................................7
5. User requirements:.....................................................................................................8
6. Software Requirements:.............................................................................................9
6.1 Functional Requirements:....................................................................................9
6.2 Non-Functional Requirements:............................................................................9
7. Models:.....................................................................................................................10
References................................................................................................................11
Appendices...............................................................................................................11

1. Introduction:

2
1.1 Description:
A data management system called a "warehouse" was developed to support and
enable business intelligence activities, notably analytics. Data warehouses are only
intended for questions and analysis [6] and usually include a substantial amount of
historical data. Transactional software as well as application log files are two common
sources used by data warehouses.
A data warehouse is used to concentrate and combine huge amounts of information
from many sources. Organizations may use their data to generate insightful business
insights by employing their analytical capabilities to improve decision-making. Over
time, it builds a historical record that information researchers and business strategists
may benefit from. These characteristics may make a data warehouse the sole source of
truth for an organization.
1.2 Scope:
A contract describing the functions of the data warehouse, its expenses, and its
anticipated benefits is part of the data warehouse scope. It is made between end-user
management and systems development management. Several unique challenges must
be considered instead of a normal range of work when developing a data warehouse
scope of the work contract. First, note that end-user management is engaged rather
than the end-user community, which is often included in the work area for an
information system.
Top-level managers are often responsible for end-user management for a data
warehouse project. Top management could be a little disengaged from the practical
use of information technologies [2]. It's also possible that senior management is
unfamiliar with employing decision-support warehouses. The dynamic nature of the
data warehouse is another factor to consider in the scope of work. It is almost a given
that system needs will alter as the data warehouse matures. The size of the work must
contain as much information as is known at this project stage.

3
2. Business Requirements:
2.1 Background:
Business requirements are utilized to define the success criteria for a project as well as
its business need. The following is a list of the business requirements for the data
warehouse system: Platform Functions create a foundation on which the system may
run. Scalability allows for quick scaling up and down to satisfy demand Scale up
swiftly to manage unforeseen demands and scale down equally quickly to save money
and resources.
Performance requirements that effectively manage heavy workloads, make the most
effective use of limited resources and parallelly handle numerous queries, users, and
processes to improve analytics and business decisions—data visualization, which
includes the system identifying trends and patterns in data sets. Graphs, charts, scatter
grams, and other visual representations are produced as a result of it.
Analytics that analyzes data patterns and predictions about them provides insights into
your company operations. Online Analytical Processing, or OLAP, subjects large,
layered datasets to multi-dimensional analysis [5]. Document management tools make
it simple for users to send team members, investors, and others reports and
visualizations in various document formats. Decision Services are concerned with
users' actions after concluding data. Integrations provide several integrations with
various software platforms and data sources.
2.2 Business Objectives:
To increase the data analytics industry's revenue and capacity for competitive
advantage in the labor market.
To effectively drive data strategy by integrating standardized, contextual data into an
organization's business intelligence platform
To improve data quality and compliance.
To improve data analytics' efficiency and power.
To increase the scalability and security of data.
2.3 Vision:
We are utilizing the expertise of data engineers, data scientists, and intelligent
business analysts to make information more accessible and usable.

4
3. Stakeholders:
Analytics director
A firm's computational modeling and data warehousing departments are managed by
an analytics director. All data analytics technologies are under the control of the
analytics director, who also makes sure that their department is meeting the business's
aims.
Big data Programmer
The Data Warehouse Developer is responsible for managing the day-to-day supply of
data and information related to business intelligence to the company they work for.
Data Engineers
Data warehouses are enormous databases that hold information from several sources,
and data warehouse engineers are in charge of planning and constructing them.

4. Elicitation Techniques:
4.1  Stakeholder Analysis
Stakeholders include team members, clients, anybody the project will influence, and
suppliers. A stakeholder analysis is conducted to determine the stakeholders the
system will impact.
4.2 Brainstorming
This approach generates original ideas and pinpoints a problem's solution. Experts in
their respective fields and domains might be present during the brainstorming session.
4.3 Interview
Business analysts and stakeholders will develop strong connections via interview
techniques. Using this method, the interviewer addresses the interviewee directly.

5
5. User requirements:
Analytic director
The director of analytics must possess a post graduate degree in data science,
computer engineering, information systems, finance, mathematics, information
systems, advanced math, business management, or a related field (a doctorate is
recommended). The ideal applicant for this position will have at least ten years of
relevant experience working in a big data analysis or data warehousing department,
preferably as the Head of Analytics [4]. The Manager of Analytics must have
exceptional communication abilities both in writing and speaking. The Director of
Analytics must possess exceptional computer skills and be a proficient user of
Microsoft Word, Excel, and PowerPoint in order to provide visually and audibly
appealing reports and presentations.
Big Data Programmer
Programmers should have excellent computer, communication, and analytical
abilities. Understanding ETL technologies, structured query language (SQL), best
practices for business intelligence, and data warehousing and reporting strategies are
crucial. The programmer should possess superior writing and verbal communication,
extraordinary organizational abilities, and the capacity to operate independently and
in a team.
Data Engineer
Data engineers should be proficient in SQL as it is a necessary operation-related
ability. Building and using a data warehouse is a skill every data engineer must
possess. Data warehousing helps data engineers combine unstructured data that has
been gathered from many sources. Building complicated database systems for
corporations requires expertise that data engineers must possess [1]. Data operations
that deal with data in motion, data at rest, datasets, and the interaction between data-
dependent processes and applications are all part of its scope. To integrate databases
and deal with various kinds of applications, a data engineer has to possess advanced
programming abilities.

6
6. Software Requirements:
6.1 Functional Requirements:
Business Rules
Business rules are a set of guidelines that specify how particular processes should be
carried out. They offer instructions on essential tasks and how to run the data
warehouse.
Administration functions
To guarantee that the data warehouse software functions correctly, the admin user
should supervise its usage.
External Interfaces
These specifications encompass hardware interfaces (where a team describes the
equipment for which the software is designed), screen layouts, buttons, functionality
on each screen, user interface (the rationale of how software interacts with people),
and other valuable information.
 Authentication requirement
Authentication, integrity of the information, access control, and incorrect password
lockouts are all functional requirements. Nonfunctional specifications list the
characteristics a system must possess. The Director of Analytics will need to be an
adept user of Microsoft Word, Excel, and PowerPoint and have exceptional computer
skills.

6.2 Nonfunctional Requirements:

Safety and adherence
The program must contain intelligent user access restrictions, accurate information
classification, and highly secure encryption algorithms to maximize data security.
Scalability
The software must be able to handle an increase in workload without performance
degradation; it should be able to enlarge quickly.
Reliability
The software should perform without failure for a specific number of uses or amount
of time by a large percentage.

7
Data integration
Data from several sources should be able to be combined by the program into a single,
cohesive warehouse. Consequently, every department within a company may access
the data warehouse.
7. Models:
Enterprise warehouse
An enterprise warehouse is a data warehouse repository for all data pertaining to
topics across the whole company. It offers cross-functional data integration for the
whole company, often from one or more operational systems or outside information
sources. The model is illustrate in the figure 1 below.
Virtual warehouse
A collection of views over active databases makes up a virtual warehouse. Only a
small portion of the potential summary views may materialize for effective query
processing in a data warehouse system as shown in figure 2 below. Although it is
simple to create a virtual warehouse, doing so requires extra space on active database
servers.

8
 References
[1] Ramakrishnan, R., Gehrke, J., & Gehrke, J. (2003). Database management
systems (Vol. 3). New York: McGraw-Hill.

[2] Kulkarni, P., Joshi, S., & Brown, M. S. (2016). Big data analytics. PHI Learning
Pvt. Ltd..

[3] Russom, P. (2013). Managing big data. TDWI Best Practices Report, TDWI
Research, 1, 40.

[4] Zhou, H., Ren, H., Royer, P., Hou, H., & Yu, X. Y. (2022). Big Data Analytics for
Long-Term Meteorological Observations at Hanford Site. Atmosphere, 13(1),
136.

[5] Oliveira, A. C., da Silva, L. F., Eler, M. M., & Freire, A. P. (2020, November). Do
Brazilian Federal Agencies Specify Accessibility Requirements for the
Development of their Mobile Apps?. In XVI Brazilian Symposium on
Information Systems (pp. 1-8).

[6] Lessa, L., & George, A. Usability of Security Mechanisms of E-Health

Applications: Cases from Ethiopia.

9
Appendices
Appendix 1

Figure 1: Enterprise warehouse

Appendix 2

Figure 2: Virtual warehouse

10