Assigment 1

First carefully read the initial project description in SmartSite.  What?  You find this description vague? Welcome to the real world. This assignment will illustrate the process of requirements elicitation.
 
 


------------------------------------------------------------------------
Assignment 1 involves generating test cases, and using these for clarifying the requirements. First, look at the project carefully and generate test cases. Each test case describes a typical way in which the system might be used..what does the user provide as input, and what is the expected response from the system? This will used to test the system at the end. We will cover this is more detail in the lecture shortly.
------------------------------------------------------------------------
Goal: Ride-seeking user  (RSU) accepts a trip
Initial State: User fires up WheelShare app.
Final State:  Ride seeker and Ride Offering User (ROU) are both aware of ride being acepted..

  1. RSU enters desired source, destination and departure time.
  2. (if some rides available) System displays available optional matching rides ("Matching" means within 10 minutes of stated departure time, and the same source and destination cities) with cost and departure time.)
  3. RSU Selects one ride
  4.  (Assume that there is still space availability on that ride)
    1. System asks RSU to confirm payment.
    2. If confirmed, System Updates database, reducing space available.
    3. System notifies ROU that one more rider has accepted ride.
    4. System enters Ride in to RSU's google Calendar.
  5. (Assume there is no space available on any ride, or no rides available)
    1. System responds "No space available on any ride. Save request for future offers? "
    2. User confirms. 
    3. System saves request for match against future offers for ROUs.

How many test cases should you have? Conside each different function of the user,
There is no need to have repetitive test cases. You can reuse one test case within another, just document it clearly when one test case is being
reused in another.  Also consider error cases, when the user enters bad data, etc.

A lot of questions will arise when you come up with test cases. Please keep track of the questions, and include them in your submission for Assignment 1. This will help clarify the requirements.

This assignment counts for 5% of the overall credit. Due dates etc? See the grading page.  Please submit a document with a list of use cases in raw text, html or pdf form, using version control TBA