1 / 14

Presentatie titel

Software Design and Media Design – formal and non-formal tools. Presentatie titel. Geert de Haan Media Technology / Human-Centered ICT Rotterdam University of Applied Sciences g.de.haan@hro.nl. Rotterdam, 00 januari 2007.

judith
Download Presentation

Presentatie titel

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Software Design and Media Design – formal and non-formal tools Presentatie titel Geert de Haan Media Technology / Human-Centered ICT Rotterdam University of Applied Sciences g.de.haan@hro.nl Rotterdam, 00 januari 2007

  2. Contents: Software Design and Media Design – formal and non-formal tools • Overview / question • Extended Task-Action Grammar • Sources, ETAG itself, ETAG design • Advantages of formality • Media design • Tool & method requirements • current teaching tools • what our companies use • product requirements • future requirements

  3. ETAG – extended task-action grammar • formalism (Tauber, 1990) • task-action grammar (TAG) with an ontology • psychologically valid wrt user mental model • model for design specification • ... and possibly more Task-Action Grammar (TAG; Green and Payne, 1986) Task [ Direction, Unit ] -> symbol [ Direction ] + letter [ Unit ]symbol [ Direction = forward ] -> "ctrl"symbol [ Direction = backward ] -> "meta"letter [ Unit = character ] -> "C"letter [ Unit = word ] -> "W"

  4. ETAG Sources Design specification (Moran 1981) - Ontological Level- Conceptual Level- Semantic Level- Syntax Level- Lexical Level- Physical Level Psychological validity - conceptual graphs (Sowa, Klix ...) - competence model not a performance model - user mental model of a perfectly knowing user

  5. ETAG the Model [CONCEPT] ::= [OBJECT] | [VALUE] | [PLACE] | [STATE] | [EVENT] .... [EVENT] ::= [event.KILL-ON ([OBJECT], [PLACE])] | [event.MOVE-TO ([OBJECT], [PLACE])] | .... type [OBJECT > MESSAGE] themes: [HEADER], [BODY] ;relations: [place.ON-POS(1) ([MESSAGE])] for [HEADER],[place.ON-POS(1) ([MESSAGE])] for [BODY],[place.POSS-AT ([MESSAGE])] for [HEADER], [BODY] ;attributes: <SENDER>, <SENDING_DATE>, <RECEIVING_DATE>, [TASK > COPY_MESSAGES],[EVENT > COPY_MESSAGES],[MESSAGE_FILE: *z],T6[EVENT > COPY_MESSAGES][OBJECT > MESSAGE: (*x)][OBJECT > MESSAGE_FILE: *y],"copy messages from the current message file into a message file".

  6. ETAG-based Design • task analysis • functional design • conceptual design • perceptual design • implementation • one notation • most iterations within design steps & few between

  7. ETAG as a Formal Model advantages of a formal design specification: • automatic generation of programming code • generation of help text using ontology and state-history information! • calculation of usability metrics cf. complexity, efficiency, ease of use ... • a single notation throughout design only one specification language to master • formality failed for the perceptual interface we cannot generate suitable screen/physical designs

  8. Formal models and Media Design • Rotterdam University of Applied Sciences • BA-level Media Technology (engineers not scientists!) • Research group Human-Centered ICT - - which methods should we teach with respect to • optimal support for current technology (webs, cms-es ...) • future technology (ubicomp, sentient systems ...) • the companies who hire our students • Investigate: current teachings, companies, software & possible future developments

  9. Current methods and tools Media Technology products: websites, interactive webs, mobile apps, CMS-es: frontend website, backend CMS & a database, code-glue Pragmatic methodology around UCD & prototyping • design concept, design view • persona's (mood boards) • scenario's, storyboards • task lists, task descriptions (task analysis) • use cases, activity diagrams, ER diagrams • interface scetches, wireframes • (paper) prototypes, demonstrators, actual designs

  10. Companies – Pilot Inventory • ads, websites, web services, web & mobile apps • most young, small, hip, innovative • development methods • soft requirements • flexible methods for e.g. social media, new products, ubicomp • experiences with methods practice • which methods do 'our' companies use? • SE: agile, structured, ucd, XP, RAD, RUP ... • non-SE: prince II, CMM, ... • type of company or department / products / size ...

  11. Questionnaire • first inventory to set up followup research • students who work as interns for a BA thesis • name (or anonymous) • which company • type of product (cms-es, websites, mobile apps, ads ... ) • main methods (Scrum, SDM/structured, watefall ...) about 21 students, 11 respondees: almost all scrum, waterfall (xp, ad hoc, dsdm) ergo: lightweight, prototyping/incremental, with project management

  12. Software products frontend – backend systems • frontend = presentation / user interface • backend = database / functionality flexible architecture (Seeheim model; 1984) -> • 'natural' support for UCD, incremental, empirical, adaptive, prototyping-based development • even: development continues into production use ergo: formal specification are not needed, unwanted

  13. The Sentient Future from SE to html, java, cms, smartphone, html5 the future is sentient, context-sensitive, adaptive • micro-adaptive not model-based • continuously changing user wants & needs design requirements: • close(s) contact with actual users co-design (& co-creation) • facilities for quick conceptual prototyping sensor lab -> fablab • facilities for continuous fine-tuning in the field living lab (cf. sense-os)

  14. Software Design and Media Design formal and non-formal tools Geert de Haan g.de.haan@hro.nl

More Related