Win a copy of The Little Book of Impediments (e-book only) this week in the Agile and Other Processes forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

What is your view of the boundary between DESIGNERS and ARCHITECTS?

 
Scott H. Kao
Greenhorn
Posts: 23
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
It seems that an architect aims at building a robust architecture and focuses on busines domain as well. The overlapped area with respect to the class diagram is sometimes confusing. Do you think the boundary between an architect and a designer is that an architect draws only the relations between all the classes and leaves all attributes and methods out to designers? Would you think such kind of class diagram kind of week?

Any views are much appreciated!
 
ANKO NAG
Greenhorn
Posts: 9
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
An architect should perform system partitioning and define interfaces for the functional requirements. For quality attributes in the utility tree (meaning any non-functional requirements), he/she should define approaches to persistence, transactions, security; define the deployment model not only for the application but for the entire infrastructure including storage, network, replication, disaster recovery etc.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic