Object planning or user thread planning - what should be the first?

Question

When starting a new piece of software, do you find it more useful to plan the interface and use cases in the first place, or to outline the objects that will need to be built?

I can see the argument for the first one in that you need to know where you are going before you can get there. But when I say “interface usage examples”, I mean a VERY SPECIFIC application stream. Basically, all software is on paper.

Secondly, planning a big picture software can help you understand potential development bottlenecks. It also helps to understand the flow of applications and can slightly change user interaction.

In your impressions, what is the best use of time ahead?

Answer 1

I see false alternatives in this matter.

Some systems do not even have a user interface! Therefore, you cannot reasonably expect a single, universal answer to this question.

Many systems actually have separate object models for the Business Logic layer and the user interface layer, and indeed, there can be more than one user interface. For example, the client user interface is provided in the browser and the Thick Client application for the customer support team.

- . : " , , Wibble". . " , ...".

, , , , -. . , , : ", Wibbles? Zetules? Wibble Zetule?, ! , Wibbles? , Blue Zetules ?"

, . . .

: - . . - . , . , , UI, . , .

Answer 2

: . , ( ), , .

Answer 3

, , , , . / . , , , , , .

Answer 4

.

.

. , , . , , .

, , .