Horse Race Meeting Use Case, Class Diagrams And State Diagram

Use Case Diagram for Horse Race Meeting

1. Horse Race Meeting Use Case?

2. Horse Race Meeting Class Diagrams?

3. Horse Meeting State Diagram?

1. Use case diagram shows overview of the usage requirements of a system that represent the system properties.

Use case diagram depicts the usage of the system by the system stakeholders and the management. These are referred to as the use case actors whose usage is shown using use case diagrams (Phillips & Nagle, 2011).

Horse race meeting shows how the horse race system will be used by the system stakeholders or actors who include the jockey owner and operator. The horses are not part in the system since they cannot access the system. Their uses are conjoined with the jockey since they cannot work alone. They only work when jockey is present. Also they cannot login into system and do something such as choosing a jockey or a race. But a jockey can login and choose a horse and a race.

During Analysis of the system requirements the following use case where found to be present.

1. Schedule race meeting.
2. Schedule race
3. Enter horse race
4. Assign horse to stable
5. Conducting of barrier draw
6 .Assign horse to stable
7. Produce schedule for the jockey
8. Produce schedule for the jockey
9. Change jockey

Scheduling of meeting is done by the system operator.  However the meeting should have meeting of each stakeholder, meaning it needs approval of all. This ensures the agreed time of meeting everybody is available.

So scheduling a meeting involves get approval from owner as the manager as well as ask availability of jockeys

 

Figure 1: schedule a race meeting use case

From the diagram its clear that the scheduling of horse race meeting is the work of the operators but input of the stake holders is needed.

The operators need approval of the owner of the horse race meeting. Sometimes it is even the owner who instruct the operator to arrange a meeting at a specific day and time.

The meeting incorporates jockeys who ride the horses. Their availability is important since they are core to the whole operation. There before a meeting is planned there is need to ensure there availability to attend the meeting.

Once a meeting has been planned and attended a race is planned during the meeting. This meeting it a decision making use case where the race to be schedule the jockey is selected and notified. Also the horse and jockey available are confirmed so as to ensure they work within their resources.

Classes in Horse Race Meeting System

So scheduling of horse race meeting involeves confirmation of participation of jockeys, and availability of horses, confirmation of available time.

 After planning of races a list of races is produced with times of each race showing time and participants of each race.

 

Once everything is done the jockey can get the horses assigned during meeting. Also the horse could have been changed after race scheduling meaning the jockey needs tpo confirm which horse is available to him/her.

During scheduling for the jockey, it usually illustrates all race details. These include time for race, horse to be used and place of the race. It also indicates the name and distance to be covered during the race. all the planned duration for each race is also indicated.  Once all details are ok. The jockey enters the race.

 

Figure 2: use case diagrams for horse race meeting

Change jockey, conduct barrier draw, assign horse to stable as well as get schedule for the owner. The draw determine the race to be entered by jockey who takes the horse assigned and enters the race. The receives schedule by the operator which includes schedule race meeting. The race meeting shows all scheduled races.

2. Class diagrams are static object oriented analysis and design that shows classes of a system and how they relate to each other. The relationship can be various types such as inheritance, aggregation and association. Classes are usually depicted using attributes of an object, location or place and people. The properties of these objects make the class objects. Then these attributes are captured using methods also known as operations (Schader & Korthaus, 2012).

Classes show the static view of an application

Class name

+attrbutes

-methods

The UML class diagrams show the conceptual, design modelling and domain modeling. Horse race meeting has the folowing classes

1. Meeting class

The meeting class will have attributes and methods that will  capture its operations and characterstics.

The attributes are:’

Attributes                              datatype

2. Meeting_id                        varchar (30)

3. Meeting duration                varchar (30)

4. Meeting start time:             date/time

5. Meeting end time:               date/time

The above attributes will collected using the methods below

+schedule meeting ()

+invite participants ()

+remind participants ()

6. Race class

The race class as discussed in use case diagram in question 1 will have race details.

The details are

1. Attribute              datetype

2. Meeting id :           varchar (30)

3. Race id:                varchar (30)

4. Race start time:     date/time

5. Race end time:       date/time

6. Jockey id:              varchar (30)

7. Horse id:               varchar (30)

Its methods are

+calculateraceduratuion ()

+getracewinner()

+getraceendtime()

+rankallracejockeys()

8. Users

The user of the system include owner, jockey and operator. The attributes username, password, their id, names, email, contacts

Relationships in Horse Race Meeting System

Attributes                                            data types     

-Username                                             varchar (30)

-Password                                               varchar (30)

-id                                                           varchar (30)

-phonenumber                                       varchar (30)

-email                                                    varchar (30)

methods include

+get phonenumber()

+get email()

+get names()

+get username()

+ register()

+login()

+verify()

The classes above are connected using the relationships discussed below

Relationships

Classes are connected to each other through relationships. For instance operator is connected to draw class since he/she the one who conducts draws to determine the classes. UML dependency is usually a less formal relationship between objects of a class that reveal end of a relationship as well as it origin. The end of relationship is indicated with arrow head while the tail shows the beginning of a relationship.

From the figure above it can be interpreted to mean that class A depends on class B in some way

Horse race meeting will be investigated to find if the following relationships exists

1. association
2. direct association

• reflexive association

1. multiplicity
2. aggregation
3. composition

• inheritance
• realization

Association between two classes exist if the classes are related in any way. For classes are linked to each other thus person class, company class and employment class have association relationship (Haugen, Reed and Gotzhein).

Association exists when two classes are linked to each other in any way.

Multiplicity is a logical relationship when the cardinality on an object with another one is shown. For example a company can have several people(person).

Directed association exist when classes are bidirectional which can be shown by flow of utilization using a directed association. The arrow head of the association shows the container contained relationship.

Aggregation relationship exists when a class is formed by collection of other several classes. It is said to have “has a” relationship. Composition relationship is a variant of aggregation that show strong life cycle between classes. Another relationship knows as inheritance also referred to as “is a relationship” shows the reusable elements of a class diagram. The subclasses reuse the attributes and operations of the parent class.  Sometimes one entity, class or an interface determines the set of functionalities as a contract while the other classes implements the contract functionality. This is called realization relationship.  using the relationships discussed above horse race meeting class diagram will be as shown below:

3. State diagram describes the behavior of horse race meeting system. It has states represented as either active or passive. The first state is called initial stage while the last state is called final state. A state is associated with one or more actions which can control controller actions.

The horse racing meeting wills a state diagram that will have the following states.

State 1: meeting

State 2: conduct draws

State 3: meeting  

State 4:  sent schedules to jockey and owner 

 State 5: conduct race and attending of races by owner and jockeys

Figure 3: horse race meeting state diagram

The horse race meeting starts by conducting meeting where the decisions of race are made. So the operators, jockeys, owner enter into the meeting at initial state. Here race resources are discussed. The available time, jockeys and horses are recorded. Once all details have been confirmed a draw is conducted in the second state based on available horses, jockeys and times. During this stage a jockey may request horse change or assigning of specific horse for race. All details about the assignment of horses and races are conducted in this phase.

Once draws have been conducted, the schedules for each race have been drawn. The race against any time with its participants, time and location make up the schedule.

Reference

Phillips, C. & Nagle, H. (2011). Digital control system analysis and design (1st ed.). Englewood Cliffs, N.J.: Prentice-Hall.

Schader, M. & Korthaus, A. (2012). The Unified modeling language (1st ed.). Heidelburg: Physical-Verlag.