2 Replies Latest reply on Feb 17, 2005 6:45 PM by ccrouch

    Basic flow of Use Case 4(Create a DataSource) Complete

    ccrouch
    ccrouch Feb 15, 2005 11:30 AM

      The basic flow of Use Case 4(Create a DataSource) has been completed. See below for details. Extension point 4.1 (Test DataSource) will be implemented as part of use case 1 (View list of Datasources).
      The Alternate flows A4.x (validation and cancel create) are still to be implemented.




      Basic Description
      An administrator uses the system to add a DataSource to a particular instance of a JBoss
      server.
      Preconditions
      It is assumed that Use Case 1 will already have been executed and the user has indicated
      which type of DataSource they are going to create.
      Goal
      A DataSource is successfully created.
      Basic flow of events
      1. The user indicates to the system that they wish to create a new DataSource.
      2. The system displays a DataSource attribute fields for the user to fill in.
      3. The user fills in the fields and indicates to the system to create a DataSource with
      the given settings.
      4. The system takes the information entered by the user, validates it and creates a
      new DataSource.
      5. The system indicates to the user that the DataSource was successfully created.
      6. The use case ends.

      • 10522 Views
      • Tags:
        • 1. Re: Basic flow of Use Case 4(Create a DataSource) Complete
          ccrouch
          ccrouch Feb 17, 2005 6:37 PM (in response to ccrouch)

          The Alternate flows A4.x (validation and cancel create) have been completed.

            • Actions
          • 2. Re: Basic flow of Use Case 4(Create a DataSource) Complete
            ccrouch
            ccrouch Feb 17, 2005 6:45 PM (in response to ccrouch)

            Alternate Flows

            A4.1: Information validation fails, DataSource not created
            During step 4) of the Basic Flow:
            1. The system finds a problem with the information the user submitted, see
            variations below.
            2. The system displays the information the user submitted and indicates to the user
            which piece(s) of information caused the problem.
            3. The use case ends.
            Possible validation errors are:
            a) The uploaded driver is not a valid jar file.
            b) A security domain is specified at the same time as specifying application managed
            security.
            c) Invalid value given for Blocking timeout.
            d) Invalid value given for idle timeout.
            e) Invalid value given for Prepared statement cache size.

            A4.2: Information validation fails, user fixes problem
            After step 2) of Alternative Flow A1.1:
            1. The user updates the pieces of information which the system indicated had caused
            the problem and indicates to the system to create the DataSource.
            2. The system takes the information entered by the user, validates it and creates the
            DataSource.
            3. The system indicates to the user that the DataSource was successfully created.
            4. The use case ends.

            A4.3: User cancels creation
            During step 3) of the Basic Flow:
            1. The user indicates to the system that they want to cancel the creation of the
            DataSource.
            2. The system does not attempt to create a DataSource. The system displays the page
            the user was on before attempting to create the DataSource.
            3. The use case ends.

              • Actions