I would like to add something to this conversation: 1) The International Association of Software Architects is currently working on a standard definition of those terms. How could you describe the role of Software Architect if it is not possible to agree on what an architecture is. Seems stupid but fundamental. Check what they are doing at http://www.iasahome.org
2) My personal experience with that is the following: a Software Architecture does not detail all the possible architecture views for all use cases. The Software Architecture is made taking into consideration the most specific use cases without detailing everything . For me, Design is more an exhaustive kind of work where all the use cases are taken into consideration and the result of the design is a ready to be implemented set of diagrams while Architecture is not. Whenever you are Architect on a project and are building complete, exhaustive diagrams for further development of an application or a system, then you are doing Design and not Architecture. In small projects, the 2 roles are merged. Robin --- In [email protected], "Alexander Johannesen" <[EMAIL PROTECTED]> wrote: > > On 3/10/06, Jerry Zhu <[EMAIL PROTECTED]> wrote: > > > > Architecture is not designed but defined. > > > > I think you'll find that architecture is used as a word describing how > something is designed, again, pointing back to design being something an > architect does. > > But anyways, if you look up the definitions for architecture, there are as > many definitions as there are people trying to define it. There is no one > answer to this, and I assert that the word itself should be erased from > serious computer language. :) > > > Alex Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
