note
Velaki
<p>
From a design perspective, I prefer to adhere to the following:
<ol>
<li>Identification of Desired Goals
<li>Notation of Behavioral Interfaces
<li>Description of Modular Functions
<li>Instantiation of Components & Methods
<li>Creation of Functionally Decomposed Methods
</ol>
</p>
<p>
The first item covers working with business analysts, but the remainder are programming activities, which encompass both the OO realm and the FD style of programming. It's very Top-Down, but once you're defined a well-behaed interface, you code back tot he blackboxes from there.
</p>
<p>
For new programmers, I like to start at the bottom, and teach functional decomposition, so they can wrap their heads around the basic syntax of the language they are trying to learn.
</p>
-v
<!-- Node text goes above. Div tags should contain sig only -->
<div class="pmsig"><div class="pmsig-322786">
"Perl. There is no substitute."
</div></div>
379168
379168