Process Overview
Each step in the process
Design justifications
Designed from a birds eye because it allows the user to see the layout of the lot easily, as the lots provide multiple spots and vary in organization. Color coding will allow for greater detail, especially in the case of permits and time constraints. More interactive as it provided a better map of campus and naming system for the lots, so users could see the relative locations of the lots to their desired destination
During my design process, I realized the importance of breadcrumbs. As each step built on the previous, the need to change preferences is key to the process. This is one reason for the change in format seen in my storyboard sketches from my original sketches. Additionally, the use of pop-ups were helpful in explaining the confirmation as well as the time constraint with the use of breadcrumbs.
Unknown number of users to other users because people may look on different machines, or people may use for a friend, but they themselves are not drivers but able to reserve if need be due to access to internet, and therefore do not have to register. These features may be potential features in the future, but adding these features in the initial implementation adds unnecessary steps in using the interface. Additionally, these features assume the user base is large, meaning the system is successful in fulfilling drivers needs.
I did not include the issue of when individuals do not follow the system as it can be implemented in the lots rather than the interface. However, once an individual reserves the spot, they park in said spot and go to the machines, much like the ones in the Bartels lot to pay for parking, and indicate which spot you parked in. If you tell the system you parked in a spot that is currently reserved, it will bring you to a confirmation page of your identity through a confirmation number given to you in the last screen seen, right after confirmation. (As indicated on the last screen of the mockup).
Designed from a birds eye because it allows the user to see the layout of the lot easily, as the lots provide multiple spots and vary in organization. Color coding will allow for greater detail, especially in the case of permits and time constraints. More interactive as it provided a better map of campus and naming system for the lots, so users could see the relative locations of the lots to their desired destination
During my design process, I realized the importance of breadcrumbs. As each step built on the previous, the need to change preferences is key to the process. This is one reason for the change in format seen in my storyboard sketches from my original sketches. Additionally, the use of pop-ups were helpful in explaining the confirmation as well as the time constraint with the use of breadcrumbs.
Unknown number of users to other users because people may look on different machines, or people may use for a friend, but they themselves are not drivers but able to reserve if need be due to access to internet, and therefore do not have to register. These features may be potential features in the future, but adding these features in the initial implementation adds unnecessary steps in using the interface. Additionally, these features assume the user base is large, meaning the system is successful in fulfilling drivers needs.
I did not include the issue of when individuals do not follow the system as it can be implemented in the lots rather than the interface. However, once an individual reserves the spot, they park in said spot and go to the machines, much like the ones in the Bartels lot to pay for parking, and indicate which spot you parked in. If you tell the system you parked in a spot that is currently reserved, it will bring you to a confirmation page of your identity through a confirmation number given to you in the last screen seen, right after confirmation. (As indicated on the last screen of the mockup).
