• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • paul wheaton
  • Ron McLeod
  • Devaka Cooray
Sheriffs:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Carey Brown
  • Piet Souris
Bartenders:

System Design & System Architecture

 
Ranch Hand
Posts: 527
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Difference between System Design & System Architecture?
 
(instanceof Sidekick)
Posts: 8791
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I like "architecture is an aspect of design that can be used in more than one application." Here are some Definitions of Architecture with links to even better ones.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
And I like http://www.martinfowler.com/ieeeSoftware/whoNeedsArchitect.pdf
 
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Anil Vupputuri:
Difference between System Design & System Architecture?


Here is my 2c:
System architecture transforms requirements into components.
System design transforms components into classes.
Nalla
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Nalla Senthilnathan:

System architecture transforms requirements into components.
System design transforms components into classes.


How does that fit into the usage of the terms as a result instead of an activity? ("Let's discuss the systems architecture." or "The system has a brittle design.")
 
Nalla Senthilnathan
Ranch Hand
Posts: 40
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Ilja Preuss:

How does that fit into the usage of the terms as a result instead of an activity? ("Let's discuss the systems architecture." or "The system has a brittle design.")


Hi Ilja,
Here is my interpretation of the usage of the terms:
"Let's discuss the systems architecture." - you are discussing about the set of components involved in the system, their dependencies and their deployment issues.
"The system has a brittle design." - the implementing classes are poorly designed (disregarding patterns and other oo principles).
Regards,
Nalla
 
reply
    Bookmark Topic Watch Topic
  • New Topic