120 likes | 158 Views
Understand and compare various lifecycle models for Interaction Design and Web 2.0, such as Waterfall, Spiral, JAD/RAD, and Agile, to enhance project management efficiency and user-centered design. See how activities are interrelated!
E N D
Lifecycle models For more info on these models – see text Specific References are in notes view Present the model you think is most appropriate for IXD and Web 2.0 processes
Lifecycle models • Show how activities are related to each other • Lifecycle models are: • management tools • simplified versions of reality • Many lifecycle models exist, for example: • From software engineering: waterfall, spiral, JAD/RAD, Microsoft • from HCI: Star, usability engineering
A simple interaction design model Identify needs/ establish requirements (Re)Design Evaluate Build an interactive version Final product Exemplifies a user-centered design approach
From software engineering Traditional ‘waterfall’ lifecycle Requirements analysis Design Code Test Maintenance
From software engineering Spiral model (Barry Boehm) • Important features: • Risk analysis • Prototyping • Iterative framework so ideas can be checked and evaluated • Explicitly encourages considering alternatives • Good for large and complex projects but not simple ones
From software engineering Spiral model (Barry Boehm) From cctr.umkc.edu/~kennethjuwng/spiral.htm
From software engineering A Lifecycle for RAD (Rapid Applications Development) Project set-up JAD workshops Iterative design and build Engineer and test final prototype Implementation review
From software engineering DSDM lifecycle model
From Human Computer Interaction The Star lifecycle model Implementation task/functional analysis Requirements specification Prototyping Evaluation Conceptual/ formal design
From Human Computer Interaction Usability engineering lifecycle model • Reported by Deborah Mayhew • Important features: • Holistic view of usability engineering • Provides links to software engineering approaches, e.g. OOSE • Stages of identifying requirements, designing, evaluating, prototyping • Can be scaled down for small projects • Uses a style guide to capture a set of usability goals