This week's giveaway is in the Spring forum.
We're giving away four copies of REST with Spring (video course) and have Eugen Paraschiv on-line!
See this thread for details.
The moose likes Architect Certification (SCEA/OCMJEA) and the fly likes System vs Reference Architecture Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login

Win a copy of REST with Spring (video course) this week in the Spring forum!
JavaRanch » Java Forums » Certification » Architect Certification (SCEA/OCMJEA)
Bookmark "System vs Reference Architecture" Watch "System vs Reference Architecture" New topic

System vs Reference Architecture

ankur rathi
Ranch Hand

Joined: Oct 11, 2004
Posts: 3830
What I understood from the study guide is:

System Architecture is product and Reference Architecture is process. System Architecture is the output of Reference Architecture.

Is that the only difference?

Ricardo Ferreira
Ranch Hand

Joined: Feb 13, 2006
Posts: 156
A reference architecture is a resource containing a consistent set of architectural best practices for use by all the teams in your organization.

Many projects I encounter spend an inordinate amount of time researching, investigating, and pondering architectural decisions. This is especially unsettling when it's clear that if prior project teams had taken the time to document their experiences and build up a reference architecture, they could have spared the new project teams much of this research and decisionmaking.

In fact, the inability to learn from a cumulative project "history" probably puts a new project's timetable at greater risk than all other factors combined. A project that proceeds without reference information will not necessarily fail; it will just require considerable effort on the part of the project team that could be spent better elsewhere. Organizations can hope to get software into the hands of clients sooner only through realizing tried and true repeatable processes.

The RUP suggests that a reference architecture should be defined along different levels of abstraction, or "views," thereby providing more flexibility in how it can be used. Ideally, these views map to the 4+1 Views of software architecture outlined in the RUP and embodied in the RUP's Software Architecture Document.


Ricardo Ferreira,<br /> <br />Sun Certified Enterprise Architect<br />IBM Certified SOA Solution Designer<br />IBM Certified RUP v7.0 Solution Designer<br />IBM Certified Specialist for RUP v2003
Consider Paul's rocket mass heater.
subject: System vs Reference Architecture
It's not a secret anymore!