Important Reference Points
Solution Architecture Development
The debate about what is the nature and role of a software architect, what does he/she do? What is that role in life; is irrelevant. There seems to be a veritable Babylon of self congratulatory, self examinatory, back slapping, on this question. It maybe a profession in search of a raison d’etre but it won’t find an apology here. No generation has an absolutely firm handle on the definition of this deliverable and there are some things that old hands have thought through which there is no need to re-invent.
Click the picture to get the idea!
|
|
REvolution Computing |
|
|
SAP Bank Analyzer High Performance Banking Analytics |
|
|
Bank Analyzer (FS-BA) |
|
|
IBM Industry Models |
|
|
BM InfoSphere Warehouse |
|
|
IBM InfoSphere Warehouse Technical Specifications |
|
|
Enterprise Solutions Structure (ESS) IBM end2end architecture methodology (E2E) |
|
|
The Open Group Architecture Framework |
|
|
451 Group CAOS Theory |
|
|
SPRING / TOMCAT |
|
|
Relational Persistence for Java and .NET |
|
|
Rational Unified Process Best Practices for Software
|
|
|
OASIS Reference Model for Service Oriented Architecture |
|
|
The many faces of architectural descriptions
|
|
|
SMR |
|
|
HPI
|
|
|
IBM Redbooks |
|
|
SAP SDN |
|
|
INTEL FASTER FS |
|
|
REVOLUTIONS
|
|
WINDOWS HPC |
|
|
|
PRINCE2 |
|
|
SSADM |
|
|
Integrated Financial and Risk Architecture (IFRA) - Accounting for Financial Instruments (AFI) |





















