Software Engineering D7025E

State diagrams vs Flowchart A state machine (a) performs actions in response to explicit events A flowchart (b) does not need explicit events but rather transitions from note to node in its graph automatically upon completion of activities

Top tips Don’t goldplate things Don’t underestimate the time it takes to do things Don’t overwork yourself (power of saying no) Always save something for a rainy day Always have something to show Look after your own interests, but be a team player Don’t ”blackmail” the company by making sure only you can read the code

Home Exam 2012 Hand in before 2/11, 17:00 As PDF, by e-mail to josef.hallberg@ltu.se Use ”D7025E: Home Exam” in the subject Label each page with name and your social security number (person-nummer) http://www.sm.luth.se/courses/d7025e/homeexam/D7025E_2012_HomeExam.pdf

Rapid Prototyping

Problem User reaction is difficult to predict

What is Rapid Prototyping? User Centric (User Centered) Experimental and partial design Testing design ideas Something to do early on

Why rapid prototyping? Test early Implementation is expensive Get feedback early Implementation is expensive Rapid prototypes are cheap Traditionally users lack the ability to envisage desigs conceptually

Prototyping tools GUI design Functionality Mockingbird Balsamiq Pen and paper, Powerpoint Functionality Powerpoint Wizard of Oz Pen and Paper, Post-it notes, Storyboards Video Simple code

Powerpoint prototypes Add ”functionality” by Insert Hyperlink / Action Place in document, Last slide viewed, First slide, etc.

Wizard of Oz Some examples User >Blurb blurb >Do this >Why?

The Nursing Home Prototype

How? Purpose? Target user? Remove inessential elements When, Where, How, Experience, etc. Target user? Remove inessential elements Avoid unnecessary design Remove unnecessary features Evaluate early