ITEC 3230 Lecture Notes - Requirements Management, Domain Knowledge, Data Analysis
17 Apr 2013
School
Department
Course
Professor
Document Summary
Who the users are and what they can do. Where, under what conditions, environmental, organizational, cultural or other the system shall operate. Learnability and efficiency for a self-service airport check-in. Maintain privacy, maintain a professional image, increase. Novices and casual users want clear instructions. User characteristics: characteristics and skills, ability, background and attitude to computers, system use: novice, expert, casual, frequent, novice: step-by-step (prompted), constrained, clear information, expert: flexibility, access/power, frequent: short cuts, casual/infrequent: clear instructions, e. g. menu paths. Hierarchy, communications structure and infrastructure, relationship types (informal, formal, mutual support, competition, trust), power relationships and politics. May occur at any point during the design process: Initially when figuring out what the project is about. During early prototyping i. e. when the first models of the system are exposed to stakeholders. Understanding organization (or individual users or user population) and current processes (or habits, activities) Understanding problem with existing situation and implicit/explicit user needs and opportunities.
