How do you confirm that user requirements are addressed in the code you are working on?

Question

The code can be perfect as well as completely useless at the same time. Proper compliance is as important as ensuring that requirements are implemented correctly.

How do you confirm that user requirements are addressed in the code you are working on?

Answer 1

You show this to users as soon as possible and more often.

Most likely, what they asked for is not really what they want, and the best way to find out is to show them what you have, even before it ends.

EDIT: And yes, this is also an approach to answering StackOverflow questions :)

Answer 2

, , , , . , , .

Answer 3

, . , , , . - , " ", . -

Answer 4

, , ?

, , " ".

- , .

, , , , .

Answer 5

• , , , .
• , .
• .
• , , .
• , , , .
• , , .

, , .

, , , , . , , .

Answer 6

, . " " .... , , , ....

Answer 7

, , . ,

testSumInvoice()
{
     // create invoice of 3 lines of $1, $2, $3 respectively
     Invoice myInvoice = new Invoice().addLine(1).addLine(2).addLine(3);
     assertTrue(myInvoice.getSum(), 6);
}

unit test , , - . , , . , , , .

, , , unit test, .

Answer 8

, . , , . , . ( ), , , . . , ( ), , .

, . , , , .

Answer 9

; , .

, , ; .

- , () .

post , .

Answer 10

, ... . , - , - , " ", " , ", " "... , , , , , , . ... , / " " (IKIWISI - Know It When See It)... .

Answer 11

AlbertoPL is right: "In most cases, even users don’t know what they want!"

And if they know, they have a solution in mind and determine the aspects of this solution, and not just talk about the problem.

And if they tell you about the problem, they may have other problems, not knowing that they are related to a common cause or a common solution.

So, before you implement the mock-ups and prototypes, go and see what the customer has or what the staff still does manually.