Fall2005.CSCI380Homework2 History

Hide minor edits - Show changes to output

Changed lines 27-28 from:
# ''Friday, Oct. 21, noon'': Create a hierarchical task analysis (HTA) for this system. \\
[-(Note: No late days for this deliverable. Failure to submit by deadline, will result in loss of points for the whole team.)-]
to:
# ''Friday, Oct. 21, 11pm'': Create a hierarchical task analysis (HTA) for this system.
Changed line 27 from:
# ''Thursday, Oct. 20, noon'': Create a hierarchical task analysis (HTA) for this system. \\
to:
# ''Friday, Oct. 21, noon'': Create a hierarchical task analysis (HTA) for this system. \\
Changed line 24 from:
## [[Fall2005/CSCI380_Homework2_Team3 | Jonathan Tindall, Michal Baker]]
to:
## [[Fall2005/CSCI380_Homework2_Team3 | Jonathan Tindall, Michael Baker, Christopher Evans]]
Added lines 27-36:
# ''Thursday, Oct. 20, noon'': Create a hierarchical task analysis (HTA) for this system. \\
[-(Note: No late days for this deliverable. Failure to submit by deadline, will result in loss of points for the whole team.)-]
(:note Note: |Homework 3 has been posted.:)

## [[Fall2005/CSCI380_Homework3_Team1 | Jason Trinklein, Evelena Leung, Matt Rice]]
## [[Fall2005/CSCI380_Homework3_Team2 | Peter Hearn, Chris Singleton, Bryan Peterson]]
## [[Fall2005/CSCI380_Homework3_Team3 | Jonathan Tindall, Michael Baker, Christopher Evans]]
## [[Fall2005/CSCI380_Homework3_Team4 | West Crosby, Charlie Phillips, Hector Mojica]]
Deleted line 40:
* Task analysis (HTA)
Changed lines 17-18 from:
# ''Thursday, Oct. 13, noon'': Create a user profile from this system. Create three user personas (with photos) for system users. [-(Note: No late days for this deliverable. Failure to submit by deadline, will result in loss of points for the whole team.)-]
to:
# ''Thursday, Oct. 13, noon'': \\
(
a) Create a user profile for this system. \\
(b)
Create three user personas (with photos) for system users. \\
[-(Note: No late days for this deliverable. Failure to submit by deadline, will result in loss of points for the whole team.)-]
Changed lines 19-23 from:
to:
## [[Fall2005/CSCI380_Homework2_Team1 | Jason Trinklein, Evelena Leung, Matt Rice]]
## [[Fall2005/CSCI380_Homework2_Team2 | Peter Hearn, Chris Singleton, Bryan Peterson]]
## [[Fall2005/CSCI380_Homework2_Team3 | Jonathan Tindall, Michal Baker]]
## [[Fall2005/CSCI380_Homework2_Team4 | West Crosby, Charlie Phillips, Hector Mojica]]
Added lines 1-59:
'''Assigned Date''': Thursday, Oct. 6, 2005 \\
'''Due Date''': ?? \\
'''Due Time''': Noon

Last modified on {$LastModified} (see [[http://www.cs.cofc.edu/~manaris/index.php/Fall2005/CSCI380Homework2?action=diff&source=n&minor=n | updates]])

You will work in teams of two or three students. See course collaboration policy for details.

!!!Purpose

You are to develop a user interface for a genetic-programming music phrase generator program, called ''StochasticMotifGenerator''.

!!!Deliverables

# ''Friday, Oct. 7, noon'': Send email with the names and email addresses of all people on your team (one email per team). [-(Note: No late days for this deliverable. Failure to submit by deadline, will result in loss of points for the whole team.)-]

# ''Thursday, Oct. 13, noon'': Create a user profile from this system. Create three user personas (with photos) for system users. [-(Note: No late days for this deliverable. Failure to submit by deadline, will result in loss of points for the whole team.)-]


!!! Future Deliverables

Project phases include (dates to be announced):

* Task analysis (HTA)
* Paper prototypes (three-levels-deep)
* State-transition diagrams
* Hi-Fi prototypes
* Demos


!!!Notes

* Your report should have sections that follow the above outline. Include figures and illustrations that give '''substantive''' help to the reader in understanding the user interface, the usability breakdown, and your analysis. You are encouraged to '''use screen snapshots''' and other graphics (e.g., diagrams) for elucidation. However, '''avoid decorative graphics/pictures'''.

* As per course collaboration policy, there should be no discussion of any kind about this assignment (and possible solutions) with any person other than the instructor. '''You are not allowed to discuss/look at someone else’s solution (including material in books and the Internet) or show your solution to someone else other than the instructor'''.

* At the bottom of your report, include a certificate of authenticity using this format:


Certification of Authenticity:

I certify that this submission is entirely my own work,
as per course collaboration policy.


Name: ________________________ Date: ___________


* Include '''references''' on materials (other than the textbooks and handouts) you consulted to do the assignment.

!!!Grading

Grading will be based on your ability to carefully and succinctly identify the key points.
* Work for clarity, succinctness, and effectiveness.
* ''Hint'': It might help to think of your report as a (meta) user interface, and your classmates as your end-users. What are the tasks they would want to accomplish with your report?

!!!Submissions

Student submissions [- (require password) -]: [- ''pending'' -]