2-methodology

2-methodology - Design Methodology CSCI 264 Basic...

Info iconThis preview shows pages 1–9. Sign up to view the full content.

View Full Document Right Arrow Icon
Design Methodology CSCI 264
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Basic Methodology • Task Analysis • User Definition • Conceptual Design • Semantic Design • Dialogue Design • Syntactic Design • Lexical Design
Background image of page 2
Basic Methodology (cont.) • Working Environment Design • Documentation Design • Design Review • Prototyping • Implementation • Software Debugging • User Interface Debugging
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Basic Methodology (cont.) • Steps are not all sequential • At each step in design, consider multiple alternatives, then choose the one which best matches user characteristics, design objectives, and functional requirements • Consider alternative designs • Each area will be discussed throughout the semester
Background image of page 4
What is Being Designed? • A communication protocol • Two languages: – user computer – computer user • What is the product of the design? – A complete design document or prototype for all aspects of user-computer interface – Use formal definition tools (e.g. UML) and prototyping
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Defining the Requirements Thoroughly research the job to be done – Determine which parts are best done with computer, but not necessarily "how" (yet) – Best done by team of subject/computer specialists – Total immersion ("know thy user") – Ask and observe – Use SADT, use-case diagrams, other formal tools People skills are crucial – Hard for technologists to see from user's perspective – Hard for people from one application domain to completely understand another
Background image of page 6
Defining the Requirements (cont.) Design objectives – Functional requirements – Learning time – Speed of use – Error rates – User satisfaction – Market appeal Design constraints – Existing equipment – Compatibility with other computer systems – Implementation time and resources
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
• User characteristics – Personality – Knowledge – Work environment – Morale – Adaptability to change • Training approaches – On the job – Formal
Background image of page 8
Image of page 9
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 25

2-methodology - Design Methodology CSCI 264 Basic...

This preview shows document pages 1 - 9. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online