UC: Initiate New Enquiry - evomimic/regen-choice GitHub Wiki

Description: This use case enables a Human Agent to initiate a new Enquiry. At the conclusion of the (main flow) of this use case a Connection will have been proposed. Different alternate flows leave the Enquiry in other states.

Actor: Requesting Agent -- the Human Agent who is specifying their perspective on the connection they seek.

Preconditions:

  1. The initiating Actor has authenticated themselves to the system and navigated to the Regen Match Home Page.

Post-conditions:

Assumptions:

Main Flow

  1. This use case starts when the Requesting Agent selects the Initiate New Enquiry action from the Regen Match Home Page.

  2. The system responds by presenting the Select Enquiry Type dialog that presents the set of Enquiry Types available within the system and prompts them to select the desired Enquiry Type_. Examples of Enquiry Types_ include:

    • sharing including dating/relationships, interests, activities
    • collaborating in business partnerships, collectives, ventures, etc.
    • living arrangements: communities, communes, co-housing projects, ecovillages, etc.
    • individuals helping or serving other individuals, including trades and many other services
    • people joining groups, such as clubs, associations, religious bodies
    • employment of people by organisations, usually paid, sometimes unpaid
    • playing
  3. The Requesting Agent selects the desired Enquiry Type

  4. If only one role is defined for the selected Enquiry Type, skip to step 6. Otherwise, the system responds by presenting the Roles defined for the specified Enquiry Type and prompts the agent to select the role they will be playing in this connection.

  5. The Requesting Agent selects the Role they will be playing in this connection.

  6. The system responds by presenting the Enquiry Details Form for the selected Enquiry Type and Role. This form contains a Requirements section that is used to specify required characteristics of the other role(s) involved in this connection. The set of possible attribute types and requirement types depends upon Enquiry Type and Role. A given Enquiry Type / Role combination may require that values be supplied for some attributes or requirements. Other values may be optional.

  7. The Requesting Agent supplies values for requirements and Submits the form.

  8. The system then searches for open enquiries and determines whether they are Matches or Possibles and presents the results on the Candidate Matching Form. Matches are shown as Matches (count). If there are any Possibles, the Candidate Matching Form also presents a rank-ordered list of questions with a count of the number of Candidate Matches that are potential matches if that question is answered. This form offers the option to proceed to View Matches and Propose Connection or .

  9. The Requesting Agent selects their desire option.

  10. If the Requesting Agent selected Answer More Questions include Use Case: Answer Questions. Otherwise (agent selected View Matches and Propose Connection), the system presents the View Candidate Matches Form.

  11. This use case ends.

Alternate Flows

Alternate Flow: Provide Required Attributes

The system will update the Requesting Agent's profile with values for any attributes not previously stored

Wireframes

For each of the following, provide an image that illustrates what information is displayed and what actions/options are being offered.

Regen Match Home Page:

Select Enquiry Type dialog

Interface provides outline info on the different type of enquiry, and how many the user currently has of each type. User chooses which type of enquiry they want to

Enquiries of a particular type

Enquiry Details Form (single enquiry)

View Candidate Matches Form

Issues

Implementation Notes

  • The actions hierarchy for the Canvas Tool Bar is shown in the following figure:

!image

image