When developing something in OO

.. where do you start?

As a basis for any design - for example, a package - where you start the developer.

I start by defining requirements and breaking them down into subcategories and from these objects and methods.

It usually takes some time before I start drawing it by hand - then this goes through several versions. But I always have a basic feeling that I never finished, and that could be better. How can I overcome this?

And as soon as I have my own design ideas, I never know how to include design templates in it.

How much time is rightly spent on designing an OO? (obviously, it depends on the project)

+3
source share
8

, - - , , , , / . , ...

+4

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

, / . .

, , , , .

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

+2

: 2 .

  • (, readUserInput())
  • , ( AGILE methode, . KISS)

, , , , . , , DRY.

- - . . , , , .

+2

, , .

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

, , . , , , , . , .

, . , , . .

+1

, , . , , . , , , .

- , , , , . , .

OO, , , , OO. .

0

. - . , , , , .

- OO ( ++, OO), , :

  • , / . - , " OO, , ". , - , , , . , . , , , , , . , , , , . . , .
  • / OO - , . - ++, Booch, , OO- , . , , , , , .
  • OO.
0

: . " ", :

, .

See a brief introduction by Martin Fowler or a longer article by Scott Ambler (www.agiledata.org/essays/tdd.html) at the beginning if this approach seems interesting to you. It helped me with a good design.

0
source

Source: https://habr.com/ru/post/1772132/


All Articles