Solution to Assignment #2

This is one (of many) solutions to the second assignment. The solution does not include the task network. It also does not trace all of the components back to the Use Cases, Use Case Scenarios and Requirements as required by the Assignment. This solution is the one that will be used in the third assignment.

Initial Subsystem Analysis

The substems were initially chosen to conform to a closed system architecture in three layers.

SubsystemDescriptionServices Provided
IDVTCS InterfaceInterface between the application level and the IDVTCS
  1. Provide the current location.
  2. Provide the current local environment.
  3. Provide information stored in node databases.
  4. A vehicle can request that a resource be reserved.
  5. A resource can be asked to reserve a resource.
EnvironmentManages information about the vehicle and its local environment.
  1. Manage the current location.
  2. Manage the current local environment.
  3. Manage information stored in the local database.
  4. Retrieve information from remote databases and store it locally.
ReservationNegotiates reservations for resources
  1. Reserve a specified resource.
  2. Manage negotiation for shared resources.
Database ManagementLocal database management system
  1. Retrieve location.
  2. Store location.
  3. Retrieve environment.
  4. Update environment.
  5. Retrieve information.
  6. Store information.
SensorsDevices and system for tracking objects in the local environment
  1. Get obstacles in the local environment.
  2. Identify obstacles in the local environment.
Positioning SystemDevice and system for determining vehicle position
  1. Get the current location.
Communication ManagerDevice and system for communicating with other IDVTCS nodes
  1. Request information from another database.
  2. Request a reservation for a shared resource.

SubsystemUse Cases
IDVTCS InterfaceAll
EnvironmentRequest Information, Sense and Locate
Database ManagementRequest Information, Sense and Locate
Positioning SystemLocate
Communication ManagerRequest Information and Negotiate

Sequence Diagrams

The following are the classes. These are analysis classes not design classes. The classes were not placed in subsystems and no associations are shown.

The following are the sequence diagrams. Each sequence diagram arises from a use case.

  1. Determine Location Use Case

  2. Sense Use Case

  3. Request Information Use Case

    The first sequence diagram illustrates a request for locally available information. The second illustrates a request for information that is not available locally.

  4. Negotiate Use Case

    This is one example of many that could be given here. In this sequence diagram, a second request can be made by the Negotiator of either the Resource IDVTCS or the Vehicle IDVTCS.