SWEN 444: Human Centered Requirements and Design |
SWEN444 Human Centered Requirements and Design
SPRING 2024 (2235)
3
Sophia Sandhu spsvse@rit.edu
Monday, Wednesday Noon to 1:30 PM
Tuesday, Thursday 2:00PM - 3:30 PM
This course introduces quantitative models and techniques of human-computer interface analysis, design and evaluation, which are relevant to the Software Engineering approach of software development. Contemporary Human Computer Interaction (HCI) techniques are surveyed, with a focus on when and where they are applicable in the software development process. Students will deliver usable software systems derived from an engineering approach to the application of scientific theory and modeling. Other topics may include: usability evaluation planning, methods of evaluation, data analysis, social and ethical impacts of usability, economic justification, prototyping and tools.
* Please spend some time reading this document, as it
contains vital information about the texts, course policies
and grading.
The course will encompass a variety of concepts and topics, among them are the following:
After this course, you will be able to:
Course will combine lecture and in-class activities. Students will collaborate inside and outside of class in support of activities and project deliverables. Assignments will include selected readings, project write-ups, as well as activities focused in supporting the materials reviewed in class. Students will also author a short UX critique paper with a selected web or desktop application
Suggested for additional insights:
This is an in-person class. Zoom participation and records are available for when you cannot or should not be in class.
Absences: I have no specific policy other than support your team!
Make up exams will only be granted for very good reasons (job interviews known in advance, documented sickness, family emergencies, etc.) Heavy workload in other (maybe to you more important) courses is typically not a very good reason.
Late Submissions: Late submissions may be accepted with a valid excuse within a week of the due date. There will be a penalty point reduction.
Conduct: Be professional. Since a key
component in this course involves working with people
including users, teammates, and classmates, and your
instructor, it is expected that you will conduct yourself in
a professional manner.
Class Behavior: It is expected that during class, you are participating in class, including adhering to the departmental policy about appropriate use of classroom/team room computers, personal laptops, and smartphones.
Project: You will be organized into teams to develop a working evolutionary prototype with an emphasis on the user interface design. Usability testing will be conducted. A final presentation of the prototype will be required in class. Read about project details in the Project page.
Project Participation Policy: The intent
for the course project is to enable you to apply the
concepts covered in class to a semester-long project. In
order for you to get anything out of it you must participate
in the creation of all project artifacts and the software
development that is non-trivial. If it is found that you
have not participated in a project deliverable/phase at all
(e.g. no coding or no artifacts) then you will receive a 0
for that deliverable/phase. If you only participate at
a trivial/limited level, your project grade will incur a
proportional deliverable score penalty. Individual
participation will be monitored through the weekly
project reporting mechanism, anecdotal peer reporting, and
at least one formal team peer review survey. Team
participation impacts your overall course participation
score.
Individual Assignments: In addition to group work, there will be a set of individual assignments that will enable you to explore various concepts and techniques presented in class. Please read the instructions and note the due dates (and times) for each assignment.
Original Student work All student work is required to be their own. While we encourage research and reuse, all submissions must be your own, original creation. Copying/ Plagiarism is NOT tolerated. This is standard policy. This applies to ALL work, be it code related or written/ essay style submission.
Use of GPT/ AIAgain, all work is required to be your original creation. In situations where use of online resources is prohibited, this includes prohibition of GPT/ AI. In situations where it is not prohibited (unless otherwise stated), you may use online search for reference, but the output you create must be your own. This includes situations where you may use GPT or other AI tools for searching and/ or reference, with the following provisos: If you use GPT (ChatGPT or other, similar tools) you must also do the following:
A final course grade is a combination of your grades on exams, team project, and individual assignment(s).
Component | Percentage of Final Grade |
---|---|
Exam 1 | 12% |
Exam 2 | 12% |
Final Exam | 24% |
Team Project | 42% |
UX Critique |
10% |
Note: The individual project grades may be adjusted in either direction from the team grade based on the assessment of your contribution by the instructor and your colleagues on the team.
At the end of the course, your final grade is assigned in the following manner:
Grade | Percentage of Final Grade |
---|---|
A | >= 93% |
A- | 90% <= n < 93%% |
B+ | 87%<= n < 90% |
B | 83% <= n < 87% |
B- | 80% <= n < 83% |
C+ | 77% <= n < 80% |
C | 73% <= n < 77%% |
C- | 70% <= n < 73% |
D | 60% <= n < 70% |
F | < 60% |