The following is a basic description of one of the
project options available this term.

The general phase 1 rules and hardware rules apply to whichever specific project option you choose.


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 have to learn what information people require and who might be coming to this space that wouldn't have been in the old AVW building or be in CSIC (for example), but you might imagine it should include at least 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 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.

If any members of your team happen to be on campus, 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 and you've been in Iribe over the past year so hopefully 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.

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 will differ from what might appear on a smartphone app.

Some example bare-minimum requirements
  • the kiosk touchscreen can be used to enter search queries where appropriate
  • a building map / directions system needs to be a part of this so think about the types of people and places that people coming into the building might want to find
  • things that appear on the kiosk that mention rooms should make it easy to get directions to those rooms
  • user personas need to include CS majors as well as other type of users (faculty, other majors, visitors, etc)
  • it cannot have a keyboard or mouse or any other similar peripheral

    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 or floorplans (UMD login an return load required) 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...












  • Web Accessibility