Part 1: Why Software Requirements In The Real World Are Hardby@matthartley
5,945 reads

Part 1: Why Software Requirements In The Real World Are Hard

tldt arrow
Read on Terminal Reader
Read this story w/o Javascript

Too Long; Didn't Read

This is the first in a series of posts about my experiences developing software in healthcare with my team over the last few years. I outline different views of requirements - objective, ideal, real world, constructive and yours. The real world view describes the challenges my team and I have experienced doing requirements over the years. The constructive view is a rough model we developed to deal with them that you can use for your own requirements. Have you worked on a project that failed because of poor requirements? Do you have ideas on how this could have been avoided?

Company Mentioned

Mention Thumbnail

Coin Mentioned

Mention Thumbnail
featured image - Part 1: Why Software Requirements In The Real World Are Hard
Matt Hartley HackerNoon profile picture

@matthartley

Matt Hartley

Co-Founder @ModifyHQ


Receive Stories from @matthartley

react to story with heart

RELATED STORIES

L O A D I N G
. . . comments & more!