1 / 17

Testing Process: Tools, Responsibilities, Connectathon

Testing Process: Tools, Responsibilities, Connectathon. Steve Moore Mallinckrodt Institute of Radiology. Technical Project Management. HIMSS/RSNA contracts with the Mallinckrodt Institute of Radiology (MIR) MIR provides a point person for continuity and other team members for specific tasks

Download Presentation

Testing Process: Tools, Responsibilities, Connectathon

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. Testing Process: Tools, Responsibilities, Connectathon Steve Moore Mallinckrodt Institute of Radiology

  2. Technical Project Management • HIMSS/RSNA contracts with the Mallinckrodt Institute of Radiology (MIR) • MIR provides a point person for continuity and other team members for specific tasks • Software development • Hall monitors at the Connectathon Vendor Workshop, April 2003

  3. Vendor Workshop, April 2003

  4. Participant Responsibilities • MESA tests • Documentation and other • Connectathon Vendor Workshop, April 2003

  5. MESA Tools • Medical Enterprise Simulators and Analyzers • A set of binary applications (C++) and perl scripts that lead each actor through test cases • All source code, except TLS, provided • Tools run on Windows NT, 2000, Solaris, Linux, other Unix Vendor Workshop, April 2003

  6. Why Test With MESA Tools? • These tools help your engineers prepare for the Connectathon • This is a fairness issue for all participants • This is a requirement of participation Vendor Workshop, April 2003

  7. Software Support • Private web server for participants with software and test data • Separate “bugzilla” web system for tracking MESA bug reports • We answer e-mail as quickly as possible Vendor Workshop, April 2003

  8. MESA Changes for Y5 • Table driven approach for SWF tests should make those scripts more stable • SWF tests allow users to select new patient names and generate different identifiers • New test cases for new Integration Profiles Vendor Workshop, April 2003

  9. Participant Responsibilities (May-July) • Application & Registration • Register with the RSNA for Year 5 • Software registration form • Describes to MIR staff what you are testing • Conference calls, week of 6/30 • Replace the July participant workshop • DICOM Conformance Statements Vendor Workshop, April 2003

  10. Participant Responsibilities (Aug-Sept) • Power/space requirements (RSNA) • Software/network configuration (MIR) • MESA test results (MIR) • Be prepared for Connectathon • Ask the Project Manager if you are unsure about anything Vendor Workshop, April 2003

  11. IHE Year 5 Connectathon • RSNA arranges network, power and tables in their basement for testing • Testing begins Oct 6, 12:00 • Supervised testing ends Oct 10, 13:00 • Informal testing can continue on Friday • All equipment must be operational and staffed until closing time on Friday Vendor Workshop, April 2003

  12. Connectathon Setup and Staffing • Setup must be complete by 12:00 noon on Monday, 10/6 • Vendor responsibility to make early arrangements (Friday, Sunday) • Equipment must be staffed and ready for testing for the entire day • Lunch breaks are scheduled • Other short breaks as needed Vendor Workshop, April 2003

  13. Vendor Workshop, April 2003

  14. Connectathon Test Schedule • IHE Europe has developed a web-based tool that allows participants to find test partners and log test results • Test periods • Scheduled for multiple systems (SWF) • Open for point to point tests • Some new connectathon tests to be added in Y5 based on Y4 experiences Vendor Workshop, April 2003

  15. Testing Expectations • The week goes quickly • Prepared teams get the most out of the week • Order Fillers are in high demand • Participants need to be pro-active and contact test partners Vendor Workshop, April 2003

  16. How Do I Succeed at the Connectathon? • Each actor must test with a minimum of N (usually 3) peers for all defined tests • MIR staff members will observe test results and use web system to post scoreboard • You should know before you arrive how many tests you need to run and the composition of those tests Vendor Workshop, April 2003

  17. Contact Information • Dave Maffitt • maffittd@mir.wustl.edu • (V) 314.362.6965 • (F) 314.362.6971 Vendor Workshop, April 2003

More Related