Ce diaporama a bien été signalé.
Nous utilisons votre profil LinkedIn et vos données d’activité pour vous proposer des publicités personnalisées et pertinentes. Vous pouvez changer vos préférences de publicités à tout moment.

Domain model example

9 678 vues

Publié le

Publié dans : Business, Technologie
  • Soyez le premier à commenter

Domain model example

  1. 1. Domain Models - Part Deux
  2. 2. Vision <ul><ul><li>Network Time Server </li></ul></ul><ul><ul><li>Major Features: </li></ul></ul><ul><ul><ul><li>Gets current time for a given time zone. </li></ul></ul></ul><ul><ul><ul><li>Get all available time zones. </li></ul></ul></ul><ul><ul><ul><li>Support 600+ clients. </li></ul></ul></ul><ul><ul><ul><li>Single clock on a large network. </li></ul></ul></ul><ul><ul><ul><li>Clock isn’t necessarily the same as the wall clock. </li></ul></ul></ul><ul><ul><li>This is a real business problem! </li></ul></ul>
  3. 3. Use Case UC1: GetCurrentTime Use Case: GetCurrentTime Identifier: UC1 Description: The GetCurrentTime use case models obtaining the current time from a central clock. Actors: Client Preconditions: 1. Network time service is available on the network. Flow of events: 1. The use case starts when the Client opens a network connection to the Server. 2. The Client indicates a need for the current time. 3. The Client provides its current time zone, using the time zone name. 4. The Server provides the Client with the current time in the requested time zone. 5. The Server closes the network connection. Postconditions: 1. The Client has the current time, and the network connection is closed.
  4. 4. SSD: UC1
  5. 5. Use Case UC2: ListTimeZones Use Case: ListTimeZones Identifier: UC2 Description: The ListTimeZones use case models obtaining a description of all recognized time zones. Actors: Client Preconditions: 1. Network time service is available on the network. Flow of events: <ul><li>1. The use case starts when the Client opens a network connection to the Server. </li></ul><ul><li>2. The Client indicates a need for the complete list of all time zones. </li></ul><ul><li>3. For each recognized time zone: </li></ul><ul><ul><li>1. Server provides the time zone name. </li></ul></ul><ul><ul><li>2. Server provides the time zone offset from UTC. </li></ul></ul><ul><ul><li>3. Server provides a list of major cities which use the time zone. </li></ul></ul><ul><li>4. The Server closes the network connection. </li></ul>Postconditions: 1. The Client has been given all recognized time zones, and the network connection is closed.
  6. 6. How To Make A Domain Model <ul><ul><li>Identify Conceptual Classes </li></ul></ul>
  7. 7. Use Case UC1: GetCurrentTime Use Case: GetCurrentTime Identifier: UC1 Description: The GetCurrentTime use case models obtaining the current time from a central clock. Actors: Client Preconditions: 1. Network time service is available on the network. Flow of events: 1. The use case starts when the Client opens a network connection to the Server. 2. The Client indicates a need for the current time. 3. The Client provides its current time zone, using the time zone name. 4. The Server provides the Client with the current time in the requested time zone. 5. The Server closes the network connection. Postconditions: 1. The Client has the current time, and the network connection is closed.
  8. 8. Use Case UC1: GetCurrentTime Use Case: GetCurrentTime Identifier: UC1 Description: The GetCurrentTime use case models obtaining the current time from a central clock. Actors: Client Preconditions: 1. Network time service is available on the network . Flow of events: 1. The use case starts when the Client opens a network connection to the Server . 2. The Client indicates a need for the current time . 3. The Client provides its current time zone , using the time zone name . 4. The Server provides the Client with the current time in the requested time zone . 5. The Server closes the network connection . Postconditions: 1. The Client has the current time, and the network connection is closed.
  9. 9. Identified Conceptual Classes <ul><ul><li>Network Time Service </li></ul></ul><ul><ul><li>Network </li></ul></ul><ul><ul><li>Client </li></ul></ul><ul><ul><li>Network Connection </li></ul></ul><ul><ul><li>Server </li></ul></ul><ul><ul><li>Current Time </li></ul></ul><ul><ul><li>Current Time Zone </li></ul></ul><ul><ul><li>Time Zone Name </li></ul></ul>
  10. 10. How To Make A Domain Model (The system itself) (Probably an attribute) (Out of system boundary)
  11. 11. How To Make A Domain Model <ul><ul><li>Identify Conceptual Classes </li></ul></ul><ul><ul><li>Put them onto a picture. </li></ul></ul><ul><ul><li>Draw associations between them. </li></ul></ul>
  12. 13. How To Make A Domain Model <ul><ul><li>Identify Conceptual Classes </li></ul></ul><ul><ul><li>Put them onto a picture. </li></ul></ul><ul><ul><li>Draw associations between them. </li></ul></ul><ul><ul><li>Add attributes to fill in details. </li></ul></ul>
  13. 15. Use Case UC2: ListTimeZones Use Case: ListTimeZones Identifier: UC2 Description: The ListTimeZones use case models obtaining a description of all recognized time zones. Actors: Client Preconditions: 1. Network time service is available on the network. Flow of events: 1. The use case starts when the Client opens a network connection to the Server. 2. The Client indicates a need for the complete list of all time zones. 3. For each recognized time zone: 1. Server provides the time zone name. 2. Server provides the time zone offset from UTC. 3. Server provides a list of major cities which use the time zone. 4. The Server closes the network connection. Postconditions: 1. The Client has been given all recognized time zones, and the network connection is closed.
  14. 16. Use Case UC2: ListTimeZones Use Case: ListTimeZones Identifier: UC2 Description: The ListTimeZones use case models obtaining a description of all recognized time zones. Actors: Client Preconditions: 1. Network time service is available on the network . Flow of events: 1. The use case starts when the Client opens a network connection to the Server . 2. The Client indicates a need for the complete list of all time zones . 3. For each recognized time zone : 1. Server provides the time zone name . 2. Server provides the time zone offset from UTC . 3. Server provides a list of major cities which use the time zone . 4. The Server closes the network connection . Postconditions: 1. The Client has been given all recognized time zones , and the network connection is closed.

×