cm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agoJunior Prompt Engineeringlemmy.mlimagemessage-square52fedilinkarrow-up1725arrow-down18cross-posted to: programmerhumor@lemmy.ml
arrow-up1717arrow-down1imageJunior Prompt Engineeringlemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agomessage-square52fedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up18·edit-22 days agoWhat, like some kind of design requirements? Heresy!
minus-squareBjörn Tantau@swg-empire.delinkfedilinkarrow-up8arrow-down1·2 days agoDesign requirements are too ambiguous.
minus-squarepsud@aussie.zonelinkfedilinkEnglisharrow-up2·1 day agoI’m a systems analyst, or in agile terminology “a designer” as I’m responsible for “design artifacts” Our designs are usually unambiguous
minus-squaresnooggums@lemmy.worldlinkfedilinkEnglisharrow-up10·2 days agoDesign requirements are what it should do, not how it does it.
minus-squareheavydust@sh.itjust.workslinkfedilinkarrow-up5·2 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.
What, like some kind of design requirements?
Heresy!
Design requirements are too ambiguous.
I’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 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.