Wednesday, June 1, 2011


  1. Definition of Architecture.
    1. What is architecture? Excerpt from Sun Tone From this link
      The terms “system architecture” and “system design” are often used interchangeably,
      but in fact deal with two very different system engineering processes. System archi-tecture focuses primarily on the overall structure of a system, identifying major com-ponents and their relationships. The systems architect seeks to define:
      1. How the overall processing should be decomposed into component parts 
      2. How the major components should be organized with respect to one another and the mechanisms underlying shared system-wide operations such as
        communication and storage.
        1. Thus, the architect focuses on issues such as which components belong together or apart; which ones should be visible to one another; which should be replicated; how they should be distributed; how they should talk to one another; where they should be stored; and so on.
  2. Infrastructure of an Architecture.
    1. Transaction Management.
    2. Security
    3. Distribution.
    4. Communication.
      1. You provide a default method for developers to implement the above features consistently.
  3. Creating an architecture means you have created an infrastructure that addresses service level requirements.
    1. When does architecture stop and design begins, there is a never clear answer.
    2. Architecture’s focus is on what is going to be built. Design’s focus is how that architecture is going to be built.
    3. For experienced designers it is not needed to provide a detailed documentation as for less experienced ones.
  4. When creating an architecture it is important to identify the system limitations.
    1. Funds
    2. Resources
    3. Time
  5. When making decisions in the architectural process, these decisions need to be documented, so that we do not have to repeat ourself over and over again.