@cm0002@lemmy.world to Programmer Humor@programming.dev • 19 days agoJunior Prompt Engineeringlemmy.mlimagemessage-square54fedilinkarrow-up1764arrow-down18cross-posted to: programmerhumor@lemmy.ml
arrow-up1756arrow-down1imageJunior Prompt Engineeringlemmy.ml@cm0002@lemmy.world to Programmer Humor@programming.dev • 19 days agomessage-square54fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squaresnooggumslinkfedilinkEnglish10•19 days agoDesign requirements are what it should do, not how it does it.
minus-square@heavydust@sh.itjust.workslinkfedilink5•19 days agoThat’s why you must negotiate or clarify what is being asked. Once it has been accepted, it is not ambiguous anymore as long as you respect it.
minus-square@psud@aussie.zonelinkfedilinkEnglish2•19 days agoI’m a systems analyst, or in agile terminology “a designer” as I’m responsible for “design artifacts” Our designs are usually unambiguous
Design requirements are too ambiguous.
Design requirements are what it should do, not how it does it.
That’s why you must negotiate or clarify what is being asked. Once it has been accepted, it is not ambiguous anymore as long as you respect it.
I’m a systems analyst, or in agile terminology “a designer” as I’m responsible for “design artifacts”
Our designs are usually unambiguous