{"id":82,"date":"2013-06-19T14:45:01","date_gmt":"2013-06-19T18:45:01","guid":{"rendered":"http:\/\/localhost\/cs4760\/2014\/?page_id=82"},"modified":"2019-01-07T13:46:59","modified_gmt":"2019-01-07T18:46:59","slug":"project","status":"publish","type":"page","link":"http:\/\/cs4760.csl.mtu.edu\/2020\/assignments\/cs4760-assignments\/project\/","title":{"rendered":"Project"},"content":{"rendered":"

The user interface (UI) project is a semester long team project designing and implementing an Web Application.<\/p>\n

Designing<\/h2>\n

You and your team\u00a0will learn a design process. The design process will involve several design changes, in other word it will evolve as your team improves the design. You will implement enough of the design so that graduate students can design a usability test and assist you in the testing.<\/p>\n

Design process steps:<\/h4>\n
    \n
  1. The project begins with forming your team and selecting potential applications (apps) to design. I will assign the apps to the teams based on your preference.<\/li>\n
  2. After receiving your app assignment, your team will meet with the scientist. From information that you gather from the interviews with the scientist, your team will make a website and design the interaction.<\/li>\n
  3. Your team will receive an interaction and stakeholder analysis from the graduate student. You use these design documents and your interaction design documents to make paper prototypes for your app. Your team will present the paper prototype during the walkthrough.<\/li>\n
  4. The graduate students will send your team a heuristic evaluation after the walkthrough. Using the results of the heuristic evaluation, your team will refine the paper prototype. Your team will meet with me in the design review to present your refined design.<\/li>\n
  5. \u00a0After beginning the implementation of the app design, your team will present to the class your final design. This is another walkthrough, which the class on the whole can delineate potential usability problems.<\/li>\n
  6. \u00a0Finally, after helping the grad students conduct the usability tests, your team will meet with me to discuss your implementation and recommend design changes.<\/li>\n<\/ol>\n

    Team Coordination<\/h2>\n

    The team size should be about 5 or 6 CS students and 2 or 3 HU students.\u00a0CS and HU students work as a team to plan and design the apps.\u00a0After designing the app, the CS undergraduate students will primarily be responsible for implementing the app.\u00a0\u00a0STC students will do the technical writing for the app and insure that the technical content for apps are\u00a0implemented. Students from both disciplines should work together to complete the app including documenting their work and conducting usability tests.<\/p>\n

    While choosing teams consider schedules, jobs, where prospective members live and work, and anything else that might impact how well the team will function. You should schedule meetings well in advance to ensure participation of all team members. During your meetings, take notes on your design decisions and how you reached your decision, so that you can use the notes in preparing your reports.<\/p>\n

    This project is a team activity. When you send e-mail to me about your project send it from your team email list and copy the list so that all team members will receive my reply and the original email.<\/p>\n

    Try to divide the project among team members so that every member of the team has experience in each phase of this process.<\/p>\n

    Team Meeting Documents<\/h2>\n

    For team meetings to effective, two meeting documents should be written and posted and the team websites.<\/p>\n

    Meeting Agenda<\/h3>\n

    The meeting agenda is short documented written before the meeting listing the topics that will be discussed and decided during the team meetings. This documents allows all team members to prepare for the meeting. It should emailed via the team email list before the meeting. Post the meeting agenda on the website as an historical record of the purpose of the meeting.<\/p>\n

    Meeting Minutes<\/h3>\n

    Meeting minutes are written by the team. They are not individual note taking. They record who attended the meeting, what team member will do, what decisions where made, and what will be discussed in the next meeting. The outline of the meeting minutes is<\/p>\n