BMI+211+01.12.10

BMI+211+01.12.10 - Effective Design in Clinical Informatics...

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

View Full Document Right Arrow Icon
Effective Design in Clinical Informatics BMI 211/CS 271 Amar Das Assistant Professor Medicine (Biomedical Informatics)
Background image of page 1

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

View Full DocumentRight Arrow Icon
Announcements First homework out on January 15 and due January 22 Groups should be finalized this week and a project area selected
Background image of page 2
Course Lectures Week 2: Requirements analysis Week 3: Functional specification and design Week 4-6: System architecture Week 7-8: Human-system interaction Week 10: Industry perspectives
Background image of page 3

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

View Full DocumentRight Arrow Icon
System Design Technical Model User Model System Interface
Background image of page 4
Requirements Analysis What is the problem to be solved? The what rather than the how What methods exist? Why is it hard?
Background image of page 5

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

View Full DocumentRight Arrow Icon
Background image of page 6
Approaches Personal experience Software requirements Focus group or user survey Task analysis Field study
Background image of page 7

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

View Full DocumentRight Arrow Icon
Approaches Personal experience Software requirements Focus group or user survey Task analysis Field study
Background image of page 8
Software Requirements Problem Needs Features Software Requirements Problem Domain (What) Solution Domain (How) Use Case Modeling, Bittner & Spence, 2003
Background image of page 9

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

View Full DocumentRight Arrow Icon
Software Requirements Functional (behavioral requirements) Actions that a system must be able to perform Specify the inputs and outputs of the system Nonfunctional (developmental quality) Related to the ‘ilities’ of the system: usability, reliability, and maintainability
Background image of page 10
Involving Stakeholders Identify the stakeholders “An individual who is materially affected by the outcome of the system” Identify the stakeholder types Organizational roles Ambassador user vs. executive sponsor Technology adopters vs. standard users
Background image of page 11

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

View Full DocumentRight Arrow Icon
Involving Stakeholders Stating the problem (simplified) The problem of what [describe problem] Affects [stakeholders] The result of which is [impact of problem] A solution would [key benefits] Use this approach for first project presentation
Background image of page 12
Limitations of Approach Eliciting a complete set of requirements from users is challenging Decomposing the problem and organizing the information Communicating the problem Resolving conflicting needs Knowing when to stop
Background image of page 13

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

View Full DocumentRight Arrow Icon
Why is Requirements Analysis Hard? Different types of requirements to address (needs vs. features) Requirements are constantly changing Often the requirements of the context of use is missed
Background image of page 14
Approaches Personal experience Software requirements Focus group or user survey Task analysis Field study
Background image of page 15

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

View Full DocumentRight Arrow Icon
User Survey Study (Stevens et al., 2001) Working biologists (experts) in academia and industry General questionnaire and interviews What tasks do you commonly perform?
Background image of page 16
Image of page 17
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 05/26/2010 for the course CS 271 taught by Professor Das during the Winter '10 term at Stanford.

Page1 / 63

BMI+211+01.12.10 - Effective Design in Clinical Informatics...

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

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