Skip to main content

Timeline for Ambiguous program requirements

Current License: CC BY-SA 3.0

12 events
when toggle format what by license comment
Sep 5, 2012 at 6:09 review Close votes
Sep 12, 2012 at 3:02
Sep 5, 2012 at 6:06 history edited gnat CC BY-SA 3.0
added 3 characters in body
Sep 5, 2012 at 3:01 history tweeted twitter.com/#!/StackProgrammer/status/243181934723878912
Sep 5, 2012 at 2:45 comment added NoChance @JimmyHoffa, very true.
Sep 5, 2012 at 2:03 comment added Jimmy Hoffa @EmmadKareem While analysts often should and do write the spec up and define requirements, it is very important that the actual developer do their own requirements gathering from the analyst, filtering the product requirements into technical requirements, many times in this filtering process the product requirements should or must change due to technical reasons the analyst couldn't have known.
Sep 5, 2012 at 1:47 vote accept Mohamed Ahmed Nabil
Sep 5, 2012 at 0:55 comment added NoChance There is a subject that you need to know about, it is called Requirements Engineering or Requirements Management. Programmers are not the best qualified people to gather requirements anyway. In many cases this is the job for Systems Analysts or Business Analysts. Guessing is bad.
Sep 5, 2012 at 0:27 answer added akton timeline score: 2
Sep 4, 2012 at 23:06 comment added psr On average I would say clients are more ambiguous than exercises. Also, just because clients say they want something doesn't mean it's really what will make them happy.
Sep 4, 2012 at 22:59 comment added Jeff Vanzella Most clients don't know what they want. They have this grand idea in their head of what they think they want. It's up to the development team to pull it out and define it.
Sep 4, 2012 at 22:58 answer added gahooa timeline score: 17
Sep 4, 2012 at 22:56 history asked Mohamed Ahmed Nabil CC BY-SA 3.0