Matakuliah
Tahun
Versi
: A0194/Pengendalian Rekayasa Ulang
Informasi
: 2005
: 1/5
Pertemuan 14
The Ballpark View of data
Architecture
1
Learning Outcomes
Pada akhir pertemuan ini, diharapkan mahasiswa
akan mampu :
• Menjelaskan the ballpark view of the data
architecture
• Menunjukkan kebutuhan kontrol pada the
ballpark view of the data architecture
2
Outline Materi
• The Importance of Class Membership
• Classification Difficulties
• Global Data Class Event
3
The Importance of Class Membership
The entire process of classification assumes that there can
be no overlap between groups.
If there is, the classification scheme is wrong.
A human is a member of species Homo sapiens and no
other.
The basic characteristics of a wheel cannot belong to two
different classes.
However, a wheel can play the role of product or part or
both.
4
The Importance of Class Membership
• Class membership must be precisely
defined.
• The entire process classification assumes
that there can be no overlap between
groups.
5
Classification Difficulties
Classification can sometimes be difficult.
For example, determining the criteria for class
membership can be difficult.
If there is limited or incomplete knowledge about a
particular area, (limited specimens is scientific
terms), it is hard to come up with a stable
classification scheme.
See Figure 5-15 p. 95, Figure 5-16 p. 96, Figure 517 p. 97
6
Classification Difficulties
• Determining the criteria for class
membership can be difficult if there is
limited or incomplete knowledge about
particular area.
• It so important to examine the entire
enterprise when designing the business
views of the architecture.
7
Global Data Class Event
Not all the events have something in common.
However, it seems there are several likely groups of events that do
have something in common.
For example, leads and sales deals are initial stages of a customer
need, a need that sometimes continues on to customer purchase
order, sales order, shipment and invoice.
We’ll group those entities together for now in Figure 5-18 p. 98
Continuing on down the list of Event entities, purchase orders are
internal orders from vendors typically for material.
8
Global Data Class Event
Therefore, we’ll group purchase orders with
the role of vendors in Figure 5-19 p. 98
9
Global Data Class Event
Service contracts and service deliveries are
much like the idea of customer orders and
shipments but, because they are people
oriented versus thing oriented, we’ll put
them in a separate class in figure 5-20 p.
99
10
Global Data Class Event
Budgets, forecasts and quotas all have to do with
planning for costs and revenues.
We’ll put them in their own group for now and we’ll
also put revenues, costs and compensation (a
form of costs) in a group in Figure 5-21 p. 99
We now have a first – pass list of global data
classes, so we’ll remove our higher – level
generalizations of People, Place, Thing and
Event.
11
Global Data Class Event
There are several likely groups of events
that do have something in common. For
example: Leads, and sales deals are initial
stages of a customer need,  customer
purchase order, sales order, shipment, and
invoice.
12
The End
13