-
31
pages
-
English
-
Documents
Description
Requirements Meet Interaction DesignRequirements Meet Interaction DesignHermann KaindlInstitut fürComputertechnik Vienna University of Technology, ICTICTAustriaInstitute ofComputer Technology kaindl@ict.tuwien.ac.atSystem overviewApplication DomainSystem BorderUserSystem to be builtComposite systemInstitute of Computer Technology© Hermann Kaindl 1Requirements Meet Interaction DesignOutlineBackgroundInteraction design based on discourse modelingUse case specificationExercisesSketch of automated user-interface generationSummary and ConclusionInstitute of Computer TechnologyWhat are requirements? User wishes / needs IEEE Standard:“A condition or capacity needed by a user to solve a problem or achieve an objective.” “The shall be able to ...”- system to be built- composite system Example: “The ATM shall accept a cash card.” Requirements modelingInstitute of Computer Technology© Hermann Kaindl 2Requirements Meet Interaction DesignWhat are requirements? – In practice User requirements documents Software/system requirements documents Mostly descriptions in natural language Representation often unstructured Ad hoc process Communication problem Requirements and use cases?Institute of Computer TechnologyTraditional UI development Based on toolkits employing widgets Widgets grouped according to their graphical appearance Highly-specialized designers and programmers needed Lots of UI code ...
-
Publié par
-
Langue
English