|
Iribe Center "Lobby" Kiosk
You must design a stand-alone kiosk application that is intended to sit in a "lobby" space of the Iribe Center. We put "lobby" in quotes because there are a variety of places on the ground floor (or even the first floor) of the Iribe Center (the atrium, the cafe seating area, the area outside of the Antonov auditorium, the large area at the top of the winding staircase, etc) where people might want to be able to access a "lobby" kiosk. It should assist anyone who has a reason to be in the building, even if that reason is to try to find a different destination on campus - remember, this building is at the "front door" of campus! You will need to undertake steps such as identifying who might be coming to the Iribe building to potentially use the kiosk, and learn what type of information they might want or require. For example, it should at least include information about the departments with offices there, classes taught in there or in CSIC, student events, how to get to CSIC or other likely destinations, etc. The actual list is actually quite long... Even though you are potential users, you should not think that all users are like you. Since the building will be used by more than just CMSC and the building is not the only building on campus, you should consider having some secondary information that other visitors to the building might need. The ESJ building could be worth visiting to see what another such open layout is like, to see what their kiosks do (or don't do), to determine aspects of that building that could be helped by a better kiosk system in Iribe, but in the end it's not really needed. Be sure to reacquaint yourself with Iribe to have a good sense of that space. Your goal should be to create a system that could actually be used in the building (if you make something impressive, who knows, we might pitch to get one fully implemented and installed). Your job is to design and prototype a system that could actually be used by the department. Your kiosk can have an Internet connection if you so choose, but you do need to consider what we wouldn't want people doing at this kiosk in addition to what we would want them doing. The kiosk can have a microphone and speakers if so desired, but again the motivation for the use of these in the context of the location of the kiosk is important. See the hardware rules for details on the course standard touchscreen specifications. Note that this will not have a camera or a microphone. Also, we are not being futuristic (no AI or ML) and we are in an HCI course (so the focus cannot be on things that AI or machine learning would do, this is about direct human interactions). It will be important that you do not drift into other domains (ie: this should not be an office hours reservation system) and that you think about how this type of kiosk application will differ from what might appear on a smartphone app or a website viewed through a laptop/desktop. Another important point to note is that you will be prototyping the kiosk application to serve the needs of the the person physically in front of the kiosk, rather than the back end users. Once the kiosk design itself was ready for full implementation, we would then also work on prototyping and implementing the software with which admins or people creating content for the kiosk would work. . Some example bare-minimum requirements When building your prototype you will need to populate the system with a wide variety of real information in order for us to fully evaluate your system. Some potential resources are floorplans (UMD login required, and you might need to re-click this URL after logging in) and a partial directory from 2019 when the building opened and in case any of these end up as useful... Ground Floor PNG, First Floor PNG, Generic Upper Floor PNG, First Floor wall map PNG This page may be updated with additional guidelines within the next few days... |