1. Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 19. september 2006 Assignment 3 ERD

2. Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 19. september 2006 ERD

3. Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 19. september 2006 Validation: Consistency  The diagram is consistent  we have not used absolute cardinalities, and have no circular dependencies.

4. Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 19. september 2006 Validation: Elementary sentences  A controller has one type of sport and the type of sport may have zero or one statistics.  Players exist only in our system in connection with statistics  A player can either be a handball, soccer or basketball player  The controller can have at most one connection to a website. The website can be in connection with several controllers.  The controller must have at least one buzzer

5. Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 19. september 2006 Validation: Snapshots none 6:46 away team Suspension Basketballplayer Faults = 6 Handballplayer Player 2 - 1ComputerMatch statisticsBasketball 10 - 11ComputerMatch statisticsHandball ScoreControllerStatisticType of sport  In the first snapshot, the suspension time isn’t legal in handball, but our controller doesn’t care.  In the second snapshot, the number of faults cannot exist in basketball.  We have as a constraint that the operator inputs correct information

6. Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 19. september 2006 Validation: Identification  Player must be an entity, because the system must pass information about a unique players goals, suspensions, faults etc. In addition the information in the messages are different depending on the player type. Thus, we have the entities handball player, soccer player and basket player.

7. Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 19. september 2006 Dictionary  Controller. Entity type. A controller is a program running on a computer connected to a board.  Board. Entity type. A board is large display placed at the court of the game. Can be anything capable of displaying computer graphics.  Website. Entity type. A server connected to the internet, which is responsible for providing services for handling game information.  Suspensions. Entity type. Suspension handles countdowns - by using the timer - of arbitrary length determined by the operator.  Statistics. Entity type. Statistics keeps track of the player records during a match. The statistics type is dependent on the type of the game.

8. Morten Bohøj, Jakob Dam og Brian Jensen Gruppe 2 A A R H U S U N I V E R S I T E T SoITS d. 19. september 2006 Dictionary  Time_Paused(t: Timer). State predicate. t is paused.  Time_Running(t: Timer). State predicate. t is started.  Suspension(s: suspension, t: timer). Relationship predicate. A suspension is created by the controller and given a timer indicating the suspension time.  Statistics(s: Type of Sport, p: Player). Relationship predicate. A player is associated with a type of sport. The sport of the player must match the type of sport.