There is a very thin line between Architecture and Design activity. IMHO the design is built on the top of architecture. The architecture is the blueprint of the system as in where all the different parts or subsystems lie and how they interact. Design goes one (or more) level deeper and specifies how the small components which make a subsystem interact with each other.
e.g. Architecture can specify the different servers and apps which need to interact but how the underlying implementation will work and how the logic / data flows within each of the component falls in design activity.
My 2.2 Cents (including GST).
Cheers :)
Samir Kumar Mishra
Tel: +61-403-747-809
Email: [EMAIL PROTECTED]
Home: http://samirmishra.tripod.com/
My Attitude in life is best described by my Blood Group… B +ve
On 3/10/06, Alexander Johannesen <[EMAIL PROTECTED]> wrote:
On 3/10/06, Gregg Wonderly < [EMAIL PROTECTED]> wrote:While I wholeheartedly agree with the premise of architecture before design,--
Damn, and here I was thinking architecture was a holistic design process. :) Seriously, though, what is your definition of design? It is a dangerous word to throw about, and I want to ask that because I cannot agree with "architecture before design".
Alex
"Ultimately, all things are known because you want to believe you know."
- Frank Herbert
__ http://shelter.nu/ __________________________________________________
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
