SRS

A collection of 2  Posts

The difference between User Stories and Software Requirements Specifications (SRS), especially for regulated systems (part 1)

It’s getting easier and easier to build unregulated software these days but it’s still pretty hard to create regulated/certified systems such as EHRs, medical device software, and government IT. To help create better systems we all know we need better user requirements; however, “heavyweight requirements” efforts have been shunned, especially in unregulated systems, over the past decade in favor of “user stories” and more agile specifications. But, are agile user stories the best way to go in regulated systems where requirements traceability and safety analysis is a must?

Because it’s so easy to build software these days we’re seeing a proliferation of healthcare apps — what’s hard to figure out is whether we’re building the right software. Abder-Rahman Ali, currently pursuing his Medical Image Analysis Ph.D. in France, has graciously agreed to give us advice on how to write good software specifications for health and medical technology solutions. Some of you are probably rolling your eyes and thinking that software requirements specifications (SRS) are old and “tired” and we should be writing agile user stories instead.

Medigy Innovation Network

Connecting innovation decision makers to authoritative information, institutions, people and insights.

Medigy Logo

The latest News, Insights & Events

Medigy accurately delivers healthcare and technology information, news and insight from around the world.

The best products, services & solutions

Medigy surfaces the world's best crowdsourced health tech offerings with social interactions and peer reviews.


© 2025 Netspective Media LLC. All Rights Reserved.

Built on Mar 12, 2025 at 5:07am