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

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

by Matt Hartley9mSeptember 3rd, 2019
Read on Terminal Reader
Read this story w/o Javascript
tldt arrow

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
Matt Hartley

Matt Hartley

@matthartley

Co-Founder @ModifyHQ

Learn More
LEARN MORE ABOUT @MATTHARTLEY'S
EXPERTISE AND PLACE ON THE INTERNET.

Share Your Thoughts

About Author

Matt Hartley HackerNoon profile picture
Matt Hartley@matthartley
Co-Founder @ModifyHQ

TOPICS

THIS ARTICLE WAS FEATURED IN...

Permanent on Arweave
Read on Terminal Reader
Read this story in a terminal
 Terminal
Read this story w/o Javascript
Read this story w/o Javascript
 Lite
L O A D I N G
. . . comments & more!