Details, responsibilities and due dates for the final project.
Responsibilities: All team members are responsible for carbon copying all teams members, other involved parties, and the instructor, on any official team business, such as scheduling of meetings, project specifications, interface specifications, assignments to be turned-in, contracts agreed upon, etc. Each team member is responsible for certain tasks (to be agreed upon by the team). Each team member should have at least one programming task.
Tasks common to most projects: (some of these may be explained in more detail below)
For projects in which multiple interfaces are to be developed and contrasted there are also
Assignment #6 -- By Monday March 3rd of this week, schedule a meeting with me and all team members. Send me email (very soon) suggesting a list of possible times. The scheduling should be done early for a meeting to take place sometime this week or early next week. If it is not possible to meet outside of class hours, please send an explanation of why as a part of your scheduling e-mail. The assignment is done when you send me a second email message (replying to mine) confirming an agreed upon time. Remember to cc all members of your group.
Assignment #7 --March 21st. Determine how the work on you project will be divided among team members. If you assign yourself too little work, your grade may suffer. If your team cannot come to agreement that seems fair to all members, then let Dr. Dailey know and he will assign responsibilities. You should send e-mail to Dr. Dailey describing the official responsibilities (tasks) assigned to each member. For certain projects, client-side programming may have to be divided into different functions or categories.
Assignment #8 -- March 21st.. Produce (and e-mail to me) a list of all interface issues appropriate to the literature review required of Assignment #10. While the Team is ultimately responsible for creating this list, it should have the prior approval of the person doing the literature review who should e-mail an acknowledgment of approval (cc: dailey).
Assignment #9 --March 21st.. Customer specifications. Based on your meeting with me write the customer specifications of your final project. In detail, what exactly will be accomplished? Provide a sample screen mapping the active elements and their event handlers (see feature analysis of interface). What is the time frame for completion of each step of the project? Specifically, How will authentication be handled? When will testing begin? By what date will you know what training materials will be required? What are your needs for graphics? When will those be done? Are there copyright or citations issues? How will those be handled? How will data analysis, be it statistical or real-time, be handled? What will be done on the server-side, in what language(s), by what date, and by whom? Which projects will be contracted out?
Assignment #10 -- March 21st.. Programming Agenda. Write and e-mail me the programming agenda for the project. What are the various functions that need to be written in JavaScript, and when will they be done and by whom? What needs to be done on the server-side?
Assignment #11 --TBA. Literature review. Conduct a literature review of any and all articles reflecting on the basic interface design issues your team is likely to encounter. Summarize your findings and produce a bibliography.
Assignment #12-- TBA. Written progress report (remember to use sentences). All programs and design elements for the final project should be in working order. Testing, evaluation, and data collection should be in progress.
Assignment #13 -- Last week of classes. Class presentations: each team shall make a ten minute presentation, with approximately six minutes devoted to discussion of issues of user-interface: how does the project work? what design decisions were and why? what could be improved? Approximately four minutes should be used to describe the project from a programming perspective. What pieces of code are involved and what do they do?
Assignment #14 (Team). Time reserved for final exam : Final report on the project is due at the beginning of class. The final report should contain the a review of literature germane to design decisions, the design decisions made and their rationale, complete instructions on how to use the software, complete source code and documentation, statistical analysis, if any. A list of all contributions made by each member of the class as well as any outside contributions should be included as well as a bibliography.