1. Software Engineering D7025E

2. 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

3. 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

4. Home Exam 2012 Hand in before 2/11, 17:00
As PDF, by to
Use ”D7025E: Home Exam” in the subject
Label each page with name and your social security number (person-nummer)

5. Rapid Prototyping

6. Problem
User reaction is difficult to predict

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

8. 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

9. 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

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

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

12. The Nursing Home Prototype

13. 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