1 / 9

Project Overview

Project Overview. Project Discussion. Domain: Electronic Medical Records Key areas: Polypharmacy : Data collection Data analysis Drug interactions, side effects Drug Optimization Reduce drug bloat, redundancy PDMs : Personal Drug Management Systems PMRs : Personal Medical Records.

parley
Download Presentation

Project Overview

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. Project Overview

  2. Project Discussion • Domain: Electronic Medical Records • Key areas: • Polypharmacy: • Data collection • Data analysis • Drug interactions, • side effects • Drug Optimization • Reduce drug bloat, redundancy • PDMs: Personal Drug Management Systems • PMRs: Personal Medical Records

  3. Initial Objectives • Everyone must gain understanding of domain • Articles mentioned in class and on Handouts page • Research via web • Each person on each team: • Research one example system • Identify 4 novel features • Identify 4 areas for improvement • Project manager collate into one list

  4. Website requirements • Skeletal website for each team by Nov. 3 • Top-level page: • Brief project Background • Brief project Description • Team composition, with role names, photos, links to individual web pages • Link to instructor and cse435 course page. • Links: • Original Project description (PDF) • SRS (SW Requirements Spec) • Prototype(s) • Project Wiki • Project Wiki: • Accessible by team members, instructor, and TA • Agendas and Minutes of all meetings • Milestones with internal and required deadlines • Access to intermediate drafts of deliverables • Discussion forum between team members. • Questions/Answers with customers and other resources

  5. Project Requirements • Requirements Doc • Identify preliminary set of requirements • Compile list of questions/clarifications for customer • Web-based prototype • Prototype 1: interface • Prototype 2: working version of system • High-Level Design Doc • System architecture • Subsystems and their interactions • Include product line elements (core and variations) • Constraints: must be compatible with companion systems • Oral Presentation/Demonstration

  6. Team Composition • Project Manager • Assign tasks • Responsible for deliverable submission • Project Facilitator • Setup and run meetings (agendas/minutes cc to Instructor/TA) • Post minutes on website • Domain Expert/Customer Liaison • Specialized domain knowledge • Interface with customer • Artifacts Manager • Configuration management • Web master • [Assurance/Security Manager]

  7. Meeting Requirements • Agenda • Leader • Action list • With assignments so we know who is doing what. • Timelines so we know when it’s to get done. • Summary • Something happened or there would not have been a meeting. Record it briefly.

  8. Project Issue List • Every issue goes on the list • Date and brief description • Make assignment to get it resolved • Put resolution on list. • “Close” issue. • 1st version usually generated on 1st read of problem statement. • And then, back to the customer...

  9. Interviewing • Have a list of things you want to know. • Listen. • Listen. • Ask open-ended questions. • Don’t express (show, say) opinions on answers. Just record, and think. • Listen. • Ask questions more than one way.

More Related