@[email protected] to Programmer [email protected] • 9 days agoJunior Prompt Engineeringlemmy.mlimagemessage-square54fedilinkarrow-up1752cross-posted to: [email protected]
arrow-up1752imageJunior Prompt Engineeringlemmy.ml@[email protected] to Programmer [email protected] • 9 days agomessage-square54fedilinkcross-posted to: [email protected]
minus-squaresnooggumslinkfedilinkEnglish10•9 days agoDesign requirements are what it should do, not how it does it.
minus-square@[email protected]linkfedilink5•9 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@[email protected]linkfedilinkEnglish2•8 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