search

samimave / car-pool

Automatically exported from code.google.com/p/car-pool
0 stars 0 forks source link

Add Offers #6

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The task involves looking at the use cases written up and the paper 
prototype model and ensuring that the above tasks follow the structure 
that it details.

Things to note

- ensure that the database stores all the details needed when adding an 
offer or request. E.g. at the moment it doesn't accept the time field. 
Also at the moment neither the interface nor database have a place to 
store comments. 
- ensure that the database can distinguish between an offer and a request, 
perhaps through a column that stores the type of ride: request or offer
- ensure that a user can add a regular or one off ride and that the fields 
of the interface change accordingly (as explained in the use cases) and 
that the relevant details are stored in the database
- Ensure that a user can specify a return or no return trip

I would recommend two people claim this task and work together on it - one 
may do the database work and the other the relevant interface work

Estimated time: 6-10 days

Original issue reported on code.google.com by parul2...@gmail.com on 13 Aug 2008 at 3:52

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Also the locations FROM, TO, & VIA need to be prepopulated drop down boxes. I 
suggest having two drop down boxes side by side. One Region and the other 
Street. 
This region can remain Palmerston North only for now and hence the only Streets 
in 
there will be streets in Palmerston North.

Original comment by parul2...@gmail.com on 13 Aug 2008 at 4:31

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
To Jordan:

As I mentioned in the meeting, here is a list of the attributes that currently 
need 
to be added to the database -

Suburb and Occupation for User

For Ride:
-LengthOfTrip
-Via locations (these can be more than one, but we wouldn't want them 
to be stored as just in one field together...I don't know how we will store 
this 
actually. Ideas? Maybe we need a limit like you can only go via 10 places...), 
-Return trip (that accepts only Yes or No as values) and Recurrence (accepts 
only 
Regular or One-Off as values)
-Now I don't know how this is going to work in the database but if Regular is 
chosen 
then days of ride will be added while if One Off is chosen then as is happening 
currently departureDate gets added. (Ofcourse later a user will be able to add 
more 
than one DepartureDate but err lets keep things simple for now). 
-Also we need a field called TypeOfRide that accepts only Offer or Request as 
values. At the moment I am thinking we'll just have one link about Adding a 
Ride 
and on it the user chooses if that ride is an offer or request. This may change 
in 
the future...
- As for From and To ...we now need FromRegion ToRegion and FromStreet ToStreet 
(see 
comment above)

Hmm that is all I can think of that we need for now. Let me know if anything 
sounds 
confusing/wierd/infeasible etc.

Original comment by parul2...@gmail.com on 20 Aug 2008 at 8:30

GoogleCodeExporter commented 9 years ago 
Changed the fields appearing on the Add A Ride page to match the use case 
documentation. 

Functionality yet to be added: 
- Prepoplating the boxes based on prev combo box selectio.
Currently Jordan will be creating a Streets table in the carpool database and 
the 
drop down box will eventually be populated from this table where the region = 
the 
one specified in the region box before.
- changing the Timing fields depending on if Regular or One off ride was
chosen ie Days vs Dates
- Changing label to seats needed if Request is chosen.

Original comment by parul2...@gmail.com on 25 Aug 2008 at 3:44

GoogleCodeExporter commented 9 years ago 
I have begun to develop an extended ER Diagram to encompass this.

Original comment by Jordan.D...@gmail.com on 25 Aug 2008 at 9:08

GoogleCodeExporter commented 9 years ago 
Street Names are viewable now. 
Add A Ride works post database changes.

Original comment by parul2...@gmail.com on 6 Sep 2008 at 6:34

GoogleCodeExporter commented 9 years ago 
Regualar Offers to be implemented in Iteration 3. 
We have to relook at how users can specify the locations they want to travel to 
and 
from in light of advice from our manager.

Original comment by parul2...@gmail.com on 16 Sep 2008 at 3:31

GoogleCodeExporter commented 9 years ago

Original comment by parul2...@gmail.com on 18 Sep 2008 at 11:26

GoogleCodeExporter commented 9 years ago 
User should be able to specify the precise location of departure, ie we need a 
house 
number for departure street as well

Original comment by parul2...@gmail.com on 29 Sep 2008 at 9:23

GoogleCodeExporter commented 9 years ago 
we need a house number for departure street as well:

This involves modifying the database, the add ride functionality, also ride 
listing 
and other places where we need to see the end location

Original comment by parul2...@gmail.com on 30 Sep 2008 at 2:07

GoogleCodeExporter commented 9 years ago

Original comment by parul2...@gmail.com on 14 Oct 2008 at 8:57

GoogleCodeExporter commented 9 years ago

Original comment by parul2...@gmail.com on 14 Oct 2008 at 8:57