| slovo | definícia |
bottomup
(mass) | bottom-up
- zdola hore |
bottom-up
(encz) | bottom-up,převrácený adj: Zdeněk Brož |
bottom-up
(gcide) | bottom-up \bottom-up\ adj. (Computers)
planning or building the smallest parts first; as, bottom-up
programming. Opposite of top-down.
[WordNet 1.5] Bottony |
bottom-up
(wn) | bottom-up
adj 1: of an approach to a problem that begins with details and
works up to the highest conceptual level; "bottom-up
parser"; "a bottom-up model of the reading process" [ant:
top-down] |
| | podobné slovo | definícia |
bottomup
(mass) | bottom-up
- zdola hore |
bottom-up mechanisms
(encz) | bottom-up mechanisms,mechanismy zdola nahoru [eko.] RNDr. Pavel Piskač |
bottom-up implementation
(foldoc) | bottom-up implementation
The opposite of top-down design. It is now
received wisdom in most programming cultures that it is best
to design from higher levels of abstraction down to lower,
specifying sequences of action in increasing detail until you
get to actual code. Hackers often find (especially in
exploratory designs that cannot be closely specified in
advance) that it works best to *build* things in the opposite
order, by writing and testing a clean set of primitive
operations and then knitting them together.
[Jargon File]
(1996-05-10)
|
bottom-up model
(foldoc) | bottom-up model
A method for estimating the cost of a complete
software project by combining estimates for each component.
(1996-05-28)
|
bottom-up testing
(foldoc) | bottom-up testing
An integration testing technique that tests the
low-level components first using test drivers for those
components that have not yet been developed to call the
low-level components for test.
Compare bottom-up implementation.
(1996-05-10)
|
bottom-up implementation
(jargon) | bottom-up implementation
n.
Hackish opposite of the techspeak term top-down design. It has been
received wisdom in most programming cultures that it is best to design from
higher levels of abstraction down to lower, specifying sequences of action
in increasing detail until you get to actual code. Hackers often find
(especially in exploratory designs that cannot be closely specified in
advance) that it works best to build things in the opposite order, by
writing and testing a clean set of primitive operations and then knitting
them together. Naively applied, this leads to hacked-together bottom-up
implementations; a more sophisticated response is middle-out implementation
, in which scratch code within primitives at the mid-level of the system is
gradually replaced with a more polished version of the lowest level at the
same time the structure above the midlevel is being built.
|
|