Project 4: Refining your Project 2
Due
New executable (tested in AVW 1120) needs to be e-mailed to
me at
eg434022@wam.umd.edu
before 2:00pm on Monday, Decemeber 15th.
Additionally, the portfolio needs to be brought to my office by 2:00pm
on Monday December 15th. I will post a list of times that I will be in my
office on Friday December 12th and Monday December 15th.
Description
Since the time that you turned in project 2, you will have had new
feedback about your application. This has taken the form of the
report given to you by another team in the class, comments and
questions during your presentations and the project 2 grading
report that you will receive by December 8th.
You may also have had things that you planned to complete but did not.
Additionally, you have hopefully reviewed your project 2; you may have
discovered issues in that way.
For this assignment, you will continue to work on your project 2
implementation. Your final
executable should have all of your current vertical tasks and the
top-level visual design refined and polished. In the case of vertical
tasks, make sure that you have populated any tables, charts, etc.
enough so that we can get a more representative view of how things
will look in actual use (eg: if something might end up scrolling,
there should be enough data provided to demonstrate how things will
appear when scrolling is required).
In addition to your new executable, your group will deliver a report.
This report needs to address the concerns raised in the reports delivered
to your group. For each concern raised, either explain how you addressed
that concern in your modified application or explain how you would address
it if you had additional time. Your description should be detailed enough
for us to be able to bring it back to the person who raised the concern
and convince them that your solution would address that concern. Feel free
to use a picture to show how you would change things.
Please note that it is expected that you will address a significant number
of the points raised to you in your new executable. In
addition to
the description of changes made and change to-be-made, include a timetable
for the changes to-be-made, as well as a brief explanation of how you
prioritized modifications.
Just as with project 2, I would like a public "who did what" statement
from each team. Private reports can be e-mailed to me if there is
something in the public report that you did not agree with but
did not want to argue about when writing the public report.
Check this page and the class home page for clarifications...
12/11 - As mentioned in class yesterday, the best way to turn in the
written portion of project 4 is probably to add it to the back of the
portfolio from Projects 1 and 2. You should use the previous written
reports as a model for how to organize your project 4 report. Be sure
to read the above description carefully for the level of detail and
information we expect in the report.
Web Accessibility