Presentation Requirements for Dec. 9:
Remember, you'll be presenting on site so you won't have a projector for PowerPoint. Practice presenting without one, and make handouts to summarize or explain complex ideas.
1) Summarize the reasons and the thinking behind the project:
1a) What is this project?
1b) What makes it appropriate to the Parsons/New School campus and community and/or to this location?
1c) How will it change the way we relate to each other or exchange information at this site, or on campus more generally?
2) How does it work?
2a) An overview of the technologies you are using and how they work together. (You can walk through your system diagram if you'd like, but you need to make it clear to a non-technical person.)
2b) What equipment do users bring to it? (Laptops? WLAN cards?)
2c) What knowledge must users have? (Do they need to know how to use a Wi-Fi network?)
2d) What equipment and systems must the school provide to implement it?
3) Live demonstration
3a) Demonstrate the initial or default state of your project: what it looks and feels like before anyone interacts with it.
3b) Demonstrate how one or more people interact with it, and what happens when they do. (If possible, you should demonstrate the actual process by which your project will accept and react to user data--e.g. logon information from the 10th floor access point, HTTP requests to your web pages, activity of users with RFID badges, etc.)
3c) If it's necessary to get your idea across, demonstrate the full/busy state of your project: what it will look and feel like when many people are interacting with it.
3d) If you have designed a means of promoting or explaining your project to the community, such as paper handouts, be sure to show these and explain how they will be used.
Documentation Requirements (Ideally you should post this to the website on Dec. 9, but you have to have it to me by Dec. 16.):
1) Text project description, two or three paragraphs. (You can adapt this from parts one and two of your Dec. 9 presentation.)
2) Complete hardware and software requirements list and diagram.
3) System administration requirements: What would a sysadmin need to do to keep the project running? How often would they need to do it? Is a human editor or reviewer needed to keep an eye on what users add to or do with the system?
4) Website or QuickTime movie showing your project's display or user interface in its full/busy state.
5) On site photographs or composite images showing what your project looks like on site.