Sustainability of early product releases

Question

Context is as follows: enterprise software is developed without sufficient direct customer involvement. We did not develop this software for a specific client, but to fill the market gap. We worked on the basic requirements only with the main customers, now more customers. Mandatory deadlines, changing requirements, little time for development. Fun time! :)

We released the first issue out of the door. Then we got the second issue at the door (fortunately, more organized)

Most of the problems facing both versions of support are what they call "design errors," rather than old, old code defects. In general, these "design errors" are such that the function or part of the function behaves as it was designed, but this behavior is not what some customers want the product to do. The point is not that all clients have such problems - each client is different, but what is enough for one, not for the other.

It makes me think about a few things, and I could really use y'all's insight with a lot of experience.

Here are some esoteric questions :

• How common do you think this is in the life of the product?

• How do you think the context contributed to this?

• / ?

Answer 1

, .

:

1) - , . , Word - , , , , , .

2) - , . , . ( ​​, ..) -. , , , - .

3) (, // ) - , , . , , . , , ( ) .

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

, , ( ), , .

- , . , . , - . , , , , , , .

: . / , ( ) (, ), , ( , ).

Answer 2

,

• . , , , , , .

, , ?

• , .

/ ?

, , , , , , . , - , , , , , , , , . , , , .

Answer 3

, : , / .

, 1991 2003 ; , :

• TSR DOS, (, ) - .
• NT, .

, ; , , ( ) , O/S, ..

Answer 4

API. , vb/java . , .

. . , - , , 1000 , . , , , , - , , . , .

Answer 5

When you send something that the customer did not want, you have not fulfilled the technical specification . Since this is the first stage of software development, and based on it design, coding and testing are based, errors in requirements are the most difficult and expensive to fix.