1 / 17

Agile Test Design & Automation of A Life-critical Medical Device

Agile Test Design & Automation of A Life-critical Medical Device. A Presentation. About us. Project summary. 700 Man years Over 11300 pages of specifications/plans Over xxx pages of test documentation. The process. TEST. Challanges. Stringent Validation and Verification criteria

Download Presentation

Agile Test Design & Automation of A Life-critical Medical Device

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. Agile Test Design & Automation of A Life-critical Medical Device A Presentation

  2. About us

  3. Project summary • 700 Man years • Over 11300 pages of specifications/plans • Over xxx pages of test documentation

  4. The process TEST

  5. Challanges • Stringent Validation and Verification criteria • Constantly changing specifications • Regular releases • Complex application • Small testing team

  6. The structure of the app • The application is structured acc. to a number of functional areas (subsystems) e.g. sms/contacts/dialing/set date/set alarm/ snooze alarm etc. • Each subsystem has own requirements

  7. Tooling • ReqPro • CQ • CC • HP QC • Excel

  8. Process • Req in QC – Req module • TD in QC – Req module • Linked Req+TD • TD using primitives • TC in QC using primitives • Linked TD+TC • Automated TC using same primitives

  9. Proces 2 • Supported structured test w. exploratory for each release

  10. The trick • From the TD to aTC – think in primitives • Tracing between Req-TD-mTC-aTC

  11. A live example of using the prims • Locally installed QC example - LIVE • Change 2 reqs • Change 3-4 TDs – mTCs, - aTCs

  12. What it solved • Tracing tells you what to change • Primitives make the test suite flexible

  13. What it did not solve • There is no quick fix for the analysis – change in req – requires re-analysis of the req and redesign of TD.

More Related