3 lectures per week, 50 minutes each (3-0-3) Designation: Required
Designation: Required Course
Course Level: Undergraduate
Prerequisite(s) by Topic:
ICS 201 and SWE 205
Requirements engineering process. Methods, tools and techniques for eliciting, organizing and documenting software requirements. Analysis and validation techniques, including need, goal, and use case analysis. Requirements documentation standards. Traceability. Requirements management. Handling requirements changes. Students participate in a group project on software requirements.
Designing the User Interface, Ben Shneiderman and Catherine Plaisant, 4th edition, 2005, Addison-Wesley, ISBN 0-321-19786-0
Handouts or links regarding various topics will be provided on the course website
- Create a vision statement for a system and identify stakeholders.
- Apply different requirements elicitation techniques such as: storyboarding, interviewing, and brainstorming.
- Verify and validate software requirements.
- Prioritize and manage requirements; and resolve conflicting requirements.
- Develop software requirements specifications based on stakeholders needs.
- Use appropriate case tools for documenting software requirements.
- Create a number of UML models such as use cases, sequence diagrams and class diagrams.
- Be an effective member in software requirements team.
- Usability of Interactive Systems
- Guidelines, Principles, and Theories
- Evaluating User Interface Designs
- Software Tools for Interface Design I
- Software Tools for Interface Design II
- Direct Manipulation and Virtual Environment
- Menu Selection, Form, and Dialogue Boxes
- Command and Natural Languages
- Interaction Devices
- Software Tools for Interface Design III
- Quality of Services, Function & Fashion
- User Manuals, Online Help, and Tutorials
- Information Search and Visualization