Interesting thoughts. Technology impacts that detailed design. Sounds reasonable.
At what point, if ever, does a technology have an impact on the high- level design? The example that pops into my head, albeit probably a poor one, is a manual transmission vs. an automatic transmission in a car. Obviously at a high level the difference can be abstracted away as simply "the car will have a transmission, which transfers the engine power...." Auto vs. stick being deferred to later design phases. But I wonder if the differences between auto and manual transmission were ever at a point that they needed to be accounted for much earlier in the analysis/design? Are there any IT technologies that have a such an impact that they impact the highest levels of a design- -e.g. the architecture? Conversely, would the use of certain technologies cause some to dismiss a solution as not being "true SOA" (whatever "true SOA" is)? For example, if I choose, for whatever reason, to use flat-files, FTP and file directory interaction as the "stuff in the middle", would that be considered non-SOA? -Rob --- In [email protected], "Anne Thomas Manes" <[EMAIL PROTECTED]> wrote: > > My response is here: > http://apsblog.burtongroup.com/2007/09/when-technology.html > > Anne >
