Page 163 -

148 NGUYEN AND DILLON
• Gymnasts and Clubs. For each gymnast, we record an ID (unique), a name, a date of birth,
and a gender. Each gymnast belongs to one club. Each club has a name (unique), an address,
and a phone number.
• Meets, Competitions, and Events. The season’s competitions are organized in a series of
meets. Each meet is held in the course of one day. Each meet consists of several competi-
tions. Each competition consists of a series of events run on different equipment. Figure 9.3
shows a sample of the result of a competition in a meet. Each meet is identified by a name
and has the date on which it is held. A competition within a meet is identified by its name.
The competition names come from a small set of standard names. Thus, a competition within
a meet is identified across the system by the combination of the meet name and the competi-
tion name.
• Teams in Competitions. When a club enters a meet, the club enters some subset of its members
in a competition. This subset is a team. When a team is in a competition, it must enter all
the events of that competition. A team must have the same set of members entered for each
event within a competition (White, 1994, p. 34). Thus, a team is identified by the name of
the club that it represents and the competition that it enters.
• Scoring. Each event in a meet has a judging panel assigned to it. These people are qualified
to give scores for this event. Each judge rates each gymnast on his/her performance in the
event. The highest and lowest scores will be thrown out, and the rest are averaged to produce
the gymnast’s score for the event. The event score of a team for an event is the sum of all
its members’ scores for the event. The competition score of a team (which is also its meet
score) is the sum of its event scores.
• System Operations. The Gymnastics System is used to prepare the schedule of meets for the
season, to ensure that qualified judges are assigned, to register teams and gymnasts, to run
the meets, and to publish the results in various forms. Its main system operations include: (1)
registering a club in a meet; (2) registering a team in a competition; (3) assigning a judge to
an event; (4) scoring trials, events, and competitions; and (5) mailing competition schedules
to gymnasts and judges, and so forth.
• Note: The system in the original version maintains information about several leagues for
several seasons. Because the information about one league for one season is largely inde-
pendent of the rest, without loss of generality, we confine the scope to one season and one
league.

THE ORTHODOX DOMAIN ANALYSIS PROCESS

In the treatment given in White (1994), the first model to be built is the domain model and the first
task for its construction is to find the candidate classes. Below is part of the analysis presented by
the author in Chapter 4 of the book, which is displayed in extracts, followed by our comments,
some of which contain comparisons with ORM.
We are about to model a gymnastics scoring system. Our mission is to automate the defini-
tion, registration, scoring, and record keeping of a gymnastics season. (p. 33)

Comment 1. This is the opening paragraph of the problem statement. The nouns are italicized as
candidates for further analysis. Note that the approach is highly sensitive to the way the problem
statement, the interview scripts, and other documents are written.