Global Sources
EE Times-India
Stay in touch with EE Times India
 
EE Times-India > Embedded
 
 
Embedded  

Employ agile methods in medical device devt

Posted: 22 Oct 2012     Print Version  Bookmark and Share

Keywords:relay race  Test Driven Development  Traceability 

For more than a decade, software teams have taken advantage of agile development methods, where solutions evolve through iterative and incremental delivery using self-organising, cross-functional teams of generalizing specialist. The generalizing specialist is someone with one or more technical specialties (e.g. developer, tester, requirements engineer, etc.) who actively seek to gain new skills in these existing specialties and in other areas. Agile promotes adaptive planning, time-boxing, evolutionary architecture, high quality, and encourages rapid and flexible response to change. Everyone on the team does whatever it takes to develop the solution, crossing traditional functional boundaries. Agile teams avoid using specialist who focuses solely on one discipline to prevent what has become to be known as "waiting on a specialist".

Traditional, non-agile approaches typically follow a "relay race" paradigm with one group of specialist passing the "baton" to the next group of specialist. Under this approach, the project goes sequentially from phase to phase: concept, feasibility, design, development, implementation and production. This is known as the "waterfall" approach. Under this method, functions are specialised and segmented. Testing and integration are typically performed only in the later phases of the project so that problems are frequently discovered late. This makes products late and also adds to the expense of fixing the issues. In medical device development, the advantage of traditional approaches is to allow requirements to be developed up front, which helps regulatory agencies sign off before development is done. This article will discuss how medical device companies can use new techniques and still meet regulatory needs.

In order to understand how to meet regulatory needs you have to first understand what the regulators are looking for. The FDA and other regulatory agencies fundamentally want to see that your product has safety in mind. To do so, they require complete traceability through the hardware and software. There is even a fairly new standard, IEC 62304, adopted worldwide that is wholly focused on software traceability from requirements through architecture to tests. These requirements and others mean we need traceability and reporting we typically only see in heavy weight processes like waterfall.

Medical devices companies are going primarily agile to respond to change and effectively manage technical complexity by collaboratively building solutions with their partners and customers to ultimately deliver what the customer wants before the competition does.

Using agile methods, the team builds features iteratively using small chunks of functionality (Stories) that are implemented during each iteration. Traceability is manageable since requirements, functional specs and designs are developed iteratively. Compliance documentation and artifacts are continually revised and kept up to date as the system evolves. Agile engineering techniques such as Test Driven Development (TDD) and Behavioural Driven Development (BDD) turn requirements and design into tests that enforces clarity, reveals implied requirements. Traceability and quality is built in.

This works well when updating an application that goes on a webpage but how can you achieve this when building a physical device that had a long regulatory process for each release?

One way to do this is to demo the new functionality created after each iteration to your customers, using web-based meets. Using these tools enables you to get immediate feedback from your customers throughout the project. Continuous customer feedback reduces the risk of building the wrong solution. The fact is in most cases you can't make the release cycle more frequent since it includes giving tests to regulatory agencies. This is a tedious process that makes sure the device is safe. Doing the whole release cycle more frequently can be way too time consuming.

1 • 2 Next Page Last Page



Comment on "Employ agile methods in medical devi..."
Comments:  
*  You can enter [0] more charecters.
*Verify code:
 
 
Webinars

Seminars

Visit Asia Webinars to learn about the latest in technology and get practical design tips.

 

Go to top             Connect on Facebook      Follow us on Twitter      Follow us on Orkut

 
Back to Top