Bottom Up vs Top Down
From: e. (e.d_at_nowhere.com)
Date: 06/03/04
- Next message: Harold Halbleib: "Re: Simple UML Sketch Tool"
- Previous message: Michael Feathers: "Re: Is Modularity a Useful Concept?"
- Next in thread: Phlip: "Re: Bottom Up vs Top Down"
- Reply: Phlip: "Re: Bottom Up vs Top Down"
- Reply: Topmind: "Re: Bottom Up vs Top Down"
- Reply: Robert C. Martin: "Re: Bottom Up vs Top Down"
- Reply: SP: "Re: Bottom Up vs Top Down"
- Reply: H. S. Lahman: "Re: Bottom Up vs Top Down"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 3 Jun 2004 16:44:30 +0200
It seems to me that most of the software projects starts from the database
(the data model), then after the database is almost ready the developers
begin with the DAL, then the BIZ layer and so on until the interface.
I start to think that is better begin the project from the interface to
build a better customer oriented software.
In bottom up method we think too much at the object model, we think in terms
of classes and methods. The customer, think in terms of functionalities and
user interfaces, instead.
So often the developer team ends up we a big number of small classess that
do not abstract the application.
The top down method starts with the "interaction model", the way the user
interact with the system, so, I think, the software can be more user
oriented.
What do you think?
Emanuele
PS I hope you understand me! :-)
- Next message: Harold Halbleib: "Re: Simple UML Sketch Tool"
- Previous message: Michael Feathers: "Re: Is Modularity a Useful Concept?"
- Next in thread: Phlip: "Re: Bottom Up vs Top Down"
- Reply: Phlip: "Re: Bottom Up vs Top Down"
- Reply: Topmind: "Re: Bottom Up vs Top Down"
- Reply: Robert C. Martin: "Re: Bottom Up vs Top Down"
- Reply: SP: "Re: Bottom Up vs Top Down"
- Reply: H. S. Lahman: "Re: Bottom Up vs Top Down"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|