Slashdot Mirror


Getting Accurate Specifications for Software?

spiffcow asks: "I design internal software for users that are largely computer-illiterate, and obtaining accurate specs for these programs has become a huge challenge. In the most recent instance, I asked for detailed specs on what an accounting program should do (i.e. accounting rules, calculation methods, and so forth), and received a Word document mock-up of an input screen, complete with useless stickers. This seems to be the norm around here. When I asked my boss (the head Sales manager) for specs, he responded saying that it was my responsibility to determine what was needed. How do I convey to the users that, in order to develop the software they want, I need detailed, accurate specs?"

1 of 147 comments (clear)

  1. A lesson learnt by nagora · · Score: -1, Flamebait
    "Head of Sales" translates to "IQ of 40, fantastic liar". Never ask sales anything. Sales is there to be told things; they have no ability, talent or insight. If they did then they'd be actually doing something instead of selling the results of other people's skills and talent.

    TWW

    --
    "Encyclopedia" is to "Wikipedia" what "Library" is to "Some people at a bus stop"