Parking App Group 1
Visit an App Preview - https://user-images.githubusercontent.com/70823359/111871887-ce8bc980-8962-11eb-9ca4-6717f0526adf.mov
- Zoom meeting discussion about the flow of the app.
- Pinal made the following app flow sketches:
Before dividing functionalities: Make a data model and mvc architecture together, so there is no conflict.
- Sign-up page
- Sign-in page
- Home-page(View parking -> see below) + Sign-out button
- update profile Screen (add delete account facility on this page)
- Account entity + user entity record:
- Name attribute
- Email attribute
- Password attribute
- contact number attribute
- car plate number attribute
- Profile picture (bonus feature)
- “Add Parking” form
- Create a new Parking record/entity with the following information:
- Building code (exactly 5 alphanumeric)
- No. of hours intended to park (1-hour or less, 4-hour, 12-hour, 24-hour)
- Car Plate Number (min 2, max 8 alphanumeric)
- Suit no. of host (min 2, max 5 alphanumeric)
- Parking location (street address, lat and lng)
- date and time of parking (use system date)
- User can input the parking location with street name [obtain location coordinates using geocoding]
- User can input the parking location with current location [ use reverse geocoding to obtain street address ]
- Accept and verifying all information when user adds parking
- Save parking record to the database when use adds parking ( in CoreData)
- When adding the parking information in the database, make sure that you associate the record with the currently logged in user.
- Appropriately design the relationship between the user and parking entities.
- list of all the parking they have made (most recent parking first)
- detail view of each parking when the user taps on any item of the list, display all the information about the parking in appropriate format.
- In the detail view of parking, allow the user to open the parking location on map and display the route to the parking location from the current location of the device.
