Why 

Informational systems are different from the traditional operational

systems? Give at least 3 point examples

Information systems differ from traditional operational systems. Operational systems are not intended
to hold strategic information. The wheels of business are turned by operational systems. They assist the
company's core business procedures. When it comes to data content, operational systems utilize current
values, whereas informational systems use archived, derived, and summarized values. Operational
systems are geared for transactions, but informational systems are optimized for complex inquiries.
Operational systems responded in sub-seconds, but informational systems required many seconds to
minutes. As a result, we discover that in order to offer strategic information, we must construct
informational systems distinct from the operational systems we have been developing to operate the
fundamental company.

6.A data warehouse is an environment, not a product. Discuss.

A data warehouse is not a single piece of software or hardware product that you purchase to
furnish strategic information. It is, instead, a computer environment in which users may obtain
strategic information, an environment in which users are immediately connected to the data they
require to make better decisions. It is an information system architectural construct that offers
users with current and historical decision support information that is difficult to access or present
in the standard operational data store. It is a user-friendly environment. This computer
environment has the following characteristics: It is an appropriate environment for data analysis
and decision support. Fluid, adaptable, and engaging. It is completely user-driven. Give people
the capacity to find answers to complicated and unanticipated problems. And very sensitive and
receptive to the ask–answer–ask again pattern. In addition to a relational database, a data
warehouse environment includes an extraction, transportation, transformation, and loading (ETL)
solution, an online analytical processing (OLAP) engine, client analysis tools, and other
applications that manage the process of gathering data and delivering it to business users. A data
warehouse is subject oriented since it offers information on a specific topic rather than about the
organization's current activities. These issues might include a product, customers, suppliers,
sales, income, and so forth. A data warehouse does not focus on ongoing operations, but rather
on data modeling and analysis for decision making.

PART 1: Site a business that is within your city or near-by place  that collets huge
volumes of data through its operational systems (may it be in finance, retail,
school, manufacturing etc..).
Philippine National Bank San Pedro Branch. It is an institution that provides financial services to
consumers, businesses, and governments and was established as a government-owned
banking institution. PNB's principal commercial banking activities include deposit-taking, lending, bills
discounting, trade finance, foreign exchange dealings, fund transfers, remittance servicing, asset
management, a full range of retail banking and trust services, and treasury operations. PNB is ready to
go ahead, backed by a heritage of service excellence, to become a more dynamic, creative, and
customer-focused bank – a trustworthy financial partner that delivers stability and security to Filipinos all
over the world.

11.Why is data integration required in a data warehouse, more so than in an

operational application?

Data across separate sources needs to be aligned and harmonized, and standardized. The
need for data cleansing and data quality control is significant. This is why integration work and
scope in data warehousing is higher than in operational systems. The data in the data
warehouse comes from several operational systems. Source data reside in different databases, files, and
data segments. These are disparate applications, so the operational platforms and operating systems
could be different. The file layouts, character code representations, and field naming conventions all
could be different Before the data from various disparate sources can be usefully stored in a data
warehouse, you have to remove the inconsistencies. You have to standardize the various data elements
and make sure of the meanings of data names in each source application. Before moving the data into
the data warehouse, you have to go through a process of transformation, consolidation, and integration
of the source data.

The data in the data warehouse comes from a variety of operating systems. The source data is available
in a number of databases, directories, and data components. Because these are distinct applications, the
operational frameworks and operating systems will differ. There may be differences in file formats,
character code representations, and field naming conventions. In order for data from different disparate
sources to be usefully processed in a data warehouse, inconsistencies must be removed. In each source
application, you must standardize the different data elements and verify the definitions of data names.
You must convert, consolidate, and integrate the source data before bringing it into the data
warehouse. Data from various sources must be synchronized, harmonized, and standardized. The
importance of data cleansing and data quality control cannot be overstated. This is why the complexity
and amount of integration work in data warehousing is greater than in operating systems.
 Why is the a need for a data structure in the data warehouse should contain time
element. Why?
A data warehouse, because of the very nature of its purpose, has to contain historical data, not just
current values. Data is stored as snapshots over past and current periods. Changes to data are tracked
and recorded so that, if necessary, reports can be produced to show changes over time. Every data
structure in the data warehouse contains the time element. You will find historical snapshots of the
operational data in the data warehouse. This aspect of the data warehouse is quite significant for both
the design and the implementation phases. Data inconsistencies are removed; data from diverse
operational applications is integrated. FOR example, in a data warehouse containing units of sale, the
quantity stored in each file record or table row relates to a specific time element. Depending on the
level of the details in the data warehouse, the sales quantity in a record may relate to a specific date,
week, month, or quarter.

Because of the nature of its role, a data warehouse must hold both historical and current values. Data is
stored in snapshots from the past and present. Data changes are monitored and documented so that
reports can be generated to display changes over time if appropriate. The time element is present in
every data structure in the data warehouse. You will find historical snapshots of the operational data in
the data warehouse. This aspect of the data warehouse is quite significant for both the design and the
implementation phases. Data inconsistencies are removed; data from diverse operational applications is
integrated. The quantity contained in each file record or table row in a data warehouse containing units
of sale, for example, corresponds to a particular time factor. The sales quantity in a record may refer to a
particular day, week, month, or quarter, depending on the degree of detail in the data warehouse. The
time-variant nature of the data in a data warehouse allows for analysis of the past, relates information
to the present and enables forecasts for the future

13.PART 2: Using the business you have sighted earlier.

 Banking operations are the legal transactions executed by a bank in its daily business
depending on the focus and size of the bank. It includes loans, mortgages, and investments.
Every day, PNB generates many thousands of Deposit or withdraw funds using an ATM,
Online Banking, Lending of Funds, Clearing of Cheques and Remittance of Funds.

 Acceptance of Deposits.
 Lending of Funds.
 Clearing of Cheques.
 Remittance of Funds.
 Lockers & Safe Deposits.
 Bill Payment Services.
 Online Banking.
 Credit & Debit Cards.

Explain the difference between the top-down and bottom-up approaches for
building data warehouses. Do you have a preference? If so, why?

Top-Down Approach

Bill Inmon is a major supporter of the top-down method. A data warehouse, according to him, is a
centralized repository for the whole company. The data in the data warehouse is stored at the lowest
degree of granularity possible using this technique, which is based on a normalized data model. The CIF
is driven by data from business activities. The centralized data warehouse would provide data to the
dependent data marts, which may be built on a dimensional data model. This is the big-picture method
to building the overall, large, enterprise-wide data warehouse. You are not dealing with a jumbled
collection of information islands. The data warehouse is extensive and well-integrated. This method, on
the other hand, would take longer to develop and has a high failure rate. This technique might be
dangerous if you do not have seasoned specialists on your team. Furthermore, selling this strategy to
top management and sponsors would be challenging. They are unlikely to see benefits in a timely
manner. The benefits of this strategy include: a really corporate endeavor, an enterprise perspective of
data that is intrinsically architected, rather than a collection of fragmented data marts, Data regarding
the material is stored in a single, central location. Finally, centralized rules and control may yield rapid
outcomes if applied through iterations. The drawbacks are as follows: it takes longer to develop, even
when using an iterative technique; There is a high risk of failure. Requires a high level of cross-functional
expertise and Expensive outlay in the absence of proof of concept.

Ralph Kimball, another renowned author and experienced practitioner in data warehousing, is a
proponent of the bottom-up approach. According to Kimball (1996), the corporate data warehouse is
envisioned as a collection of conformed data marts. The primary consideration is the alignment of the
dimensions across the various data marts. Data marts are built initially in this method to give analytical
and reporting capabilities for certain business subjects based on the dimensional data model. Data
marts include data at the most detailed degree of granularity as well as summaries based on the
demands for analysis. By matching the dimensions, these data marts are linked or "unioned" together.
You create your departmental data marts one by one using this bottom-up method. To select which data
marts to develop first, you would create a priority scheme. The most serious disadvantage of this
method is data fragmentation. Each isolated data mart will be oblivious to the broader needs of the
company. The benefits of this strategy include: faster and simpler deployment of manageable chunks,
favorable return on investment and proof of concept, reduced risk of failure, naturally incremental; the
ability to schedule critical data marts first, and the ability for the project team to learn and develop.

I think that in order to develop a strategy for your business, we must first determine what it wants.
Although both the top-down and bottom-up techniques have advantages and disadvantages, a
compromise strategy that incorporates both perspectives looks to be feasible. We don't lose sight of the
broad picture for the entire company when we take this strategy. This overarching large picture serves
as the foundation for our planning. This is a result of the top-down strategy. Then, using the bottom-up
method, we construct the conforming data marts based on a priority system. The key to this strategy is
to begin planning at the corporate level. You collect needs on a broad scale. You create the architecture
for the entire warehouse.

27.What do you consider to be a core set of team roles for a data warehouse
project? Describe the responsibilities of three roles from your set

A data warehouse is a subset of an organization's data that contains just information that is
critical to achieving strategic goals. This is frequently kept as raw data that has been arranged
in a way that allows for rapid retrieval and analysis. Building a data warehouse is a difficult
and time-consuming operation, with the difficulty directly proportional to the size of the
company and the amount of data that must be managed. A data warehouse project team
should be comprised of specialists that are familiar with the organization and its data. Team
roles are not to be assigned arbitrarily; the roles must reflect the needs of each individual data
warehouse project to fit into the roles and discharge the responsibilities, the selected persons must
have the right abilities. They should possess suitable skills and the proper work experience. You will have
to reexamine the goals and objectives. During the development phases, you will need to determine
which areas require extra attention. Then, with specialized responsibilities, support that function. After
you've identified the broad classes, you may focus on the specific jobs inside each categorization. There
is no such thing as a standard set. If you like conventional methods, stick to management and
development classifications.

Project Manager- The perceived strength of data warehousing inside a company is the sum of the
Project Managers' strengths. Project managers must keep promises and deliver on schedule. They will
accomplish this through utilizing resources from within the data warehouse team as well as consulting
when needed, as well as forming collaborations with other internal support organizations needed to
support a data warehouse iteration. The project manager is in charge of the project budget as well as
the team. He must also be aware of the project scope and manage it in accordance with the project
timeline. This role is also responsible for removing roadblocks for the project team and
ensuring that they have what they need to do the job. 

Database Administrator- The DBA or data warehouse professional should be well-versed in

data warehouse technology and principles. His/her duty is to create the data warehouse
model and construct test cases to ensure the data's authenticity. In addition, the specialist
must give technical and business support to data warehouse developers. Finally, the DBA
must maintain the data warehouse to ensure availability and usability of the warehouse.

Executive Sponsor- The Data Warehouse requires high-level and long-term sponsorship. The Executive
Sponsor must be politically viable and capable of obtaining and retaining enough resources for the Data
Warehouse's construction and maintenance. The Executive Sponsor, as the responsible executive for the
success or failure of the Data Warehouse, should be able to articulate and quantify the value of the Data
Warehouse program.
“In a data warehouse, business requirements of the users form the single and
most powerful driving force.” Do you agree? If you do, state four reasons why. If
not, is there any other such driving force?

Yes, in a data warehouse, business requirements of the users form the single and most powerful driving
force.

 Every task that is performed in every phase in the development of the data warehouse is
determined by the requirements. Business requirements strongly influence the
information delivery mechanism. Requirements define how, when, and where the
users will receive information from the data warehouse.

 Every choice made during the design process, whether it is the data design, the architectural
design, the infrastructure configuration, or the scheme of the information delivery methods, is
heavily impacted by the requirements.

 Because requirements are the major motivator for each step of the development process, you
must ensure that your requirements definition has sufficient specifics to support each phase.

 When gathering business needs and creating the requirements definition document, keep in
mind that what you accomplish in this phase of the project is critical to the rest of the project.
Please pay close attention to your requirements specification because it will drive every aspect
of the project.

Name five architectural components that are strongly impacted by business

requirements.
Explain the impact of business requirements on any one of those five
components.
Five architectural components that are strongly impacted by business
requirements are source data, data staging, management and control, data
storage and information delivery.
The influence of business requirements on a data warehouse's information delivery method is
straightforward. Users tell you what information they want from the data warehouse during the
requirements formulation process. These criteria are documented in the requirements definition paper.
Then, in the information delivery component, you provide all of the needed features and content.
Although the impact looks to be easy and uncomplicated, there are a number of considerations to
consider. Many distinct components of the criteria have varied effects on various sections of the
information delivery component. The information delivery strategy is influenced by the user group that
is anticipated to consume the data warehouse's business intelligence. The information strategy should
therefore be geared on offering powerful analysis capabilities. The information delivery component's
query and reporting capabilities must then be improved. Queries and reports, types of analysis,
information dissemination, real-time information delivery, decision support applications, and growth
and extension are the main areas of the information delivery component that are directly influenced by
business requirements.

Five architectural components that are strongly impacted by business

requirements are source data, data staging, management and control, data
storage and information delivery. The influence of business requirements on a
data warehouse's information delivery method is straightforward. Users tell you
what information they want from the data warehouse during the requirements
formulation process. These criteria are documented in the requirements
definition paper. Then, in the information delivery component, you provide all of
the needed features and content. Although the impact looks to be easy and
uncomplicated, there are a number of considerations to consider. Many distinct
components of the criteria have varied effects on various sections of the
information delivery component. The information delivery strategy is influenced
by the user group that is anticipated to consume the data warehouse's business
intelligence. The information strategy should therefore be geared on offering
powerful analysis capabilities. The information delivery component's query and
reporting capabilities must then be improved. Queries and reports, types of
analysis, information dissemination, real-time information delivery, decision
support applications, and growth and extension are the main areas of the
information delivery component that are directly influenced by business
requirements.