SWEN 444: Human Centered Requirements and Design
SWEN444 Human Centered Requirements and Design
Yasmine El-Glaly: (ynevse@ rit.edu)
Robert Kuehl: (rbkvse@ rit.edu)
El-Glaly: Tuesday 11:00 - 12:30 PM, Thursday 11:00 - 12:30 PM (and by appointment), Room 1573
Kuehl: Monday, Wednesday, Friday 11:00 -11:30 AM (and by appointment), Room 3450
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.
4010- 262 (Engineering of Software Subsystems); 1016-351
(Probability & Statistics) or 1016-314
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.
Required: (Note: Both are available at Books 24x7. There should be a plentiful supply of used copies if you would like a print copy.)
Come to class. You owe it to yourself. You owe it to your
teammates. Most sessions contain project team work that
requires all team members to be present to gain full
You are allowed one unexcused absence (car trouble, etc.) with no consequences. After that the following scale applies for additional absences:
Also, you will miss credit for activities that took place during classes that you were absent. If you need to be absent because of a job interview, illness, or other significant personal issue, please let me know so we can determine if it should be an excused absence.
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.
Participation Policy: Your participation is imperative for your success in this course. The participation portion of your overall grade focuses on attendance, completion and timely submission of in-class activities and assignments, your meaningful contribution to classroom discussions, and especially your individual contribution to the team project/activities.
Classroom discussions: Demonstrate critical thinking by asking challenging questions, reflecting on and articulating your personal opinions, and critiquing the ideas of others. Initiate class discussion by offering and explaining your ideas and opinions, and providing relevant examples and anecdotes.
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 bi-weekly
project reporting mechanism, anecdotal peer reporting, and
at least one formal team peer review survey. Team
participation impacts your overall course participation
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.
A final course grade is a combination of your grades on exams, assignments, class activities, participation, and a team project.
|Component||Percentage of Final Grade|
|Quizzes, Class Activities and Participation
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.
* Please be aware that the myCourses grade-book feature will be used to communicate “raw” grades to you, but is NOT used for calculating final grades.
At the end of the course, your final grade is assigned in the following manner:
|Grade||Percentage of Final Grade|
|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%|