In my opinion Zachman Framework is one of the most comprehensive classification methods for enterprise architecture. This framework was first designed introduced by John Zachman in 80s while working for IBM.
Using this methodology has helped me in tackling requirements/design for large scale implementations.
The Core
The base questions which need to be answer in this framework are: Why, What, Where, Who, How and When. These questions have to be answered by different groups: Planner, Owner, Designer, Builder, Programmer and User.
The intersection of these two sets creates a matrix of design artifacts and documents and application.
I highly recommend reading more about this framework and using it.
Some Papers
Zachman Poster
The Zachman Framework For Enterprise Architecture
Top Four EA Methodologies
Books:
Enterprise Architecture Using the Zachman Framework (MIS)
Friday, March 2, 2012
Thursday, March 1, 2012
Representational state transfer (REST)
Roy Fielding in year 2000 for the first time introduced the term Representational state transfer (REST) to the software world. This is an architectural practice used for distributed hypermedia, while the largest implementation being the World Wide Web.
The Core
In essence the REST Architecture consists of three parts:
In this architecture state of the client constantly in transformation as it progresses in its requests. The server in response has many states to consider in a given time since it can be responding to many clients at a given time, in essence the sever is stateless.
This architecture is a great bases for a well designed browser based application.
Below you'll find links for several good resources for REST:
Short papers or Presentations:
Roy Thomas Fielding: Architectural Styles and the Design of Network-based Software Architectures
RESTful Web services
Rest of REST
What is REST
SOA with REST
RESTful Web Services for Java
RESTful Java with JAX-RS
RESTfulWeb Services Developer'sGuide
Books:
RESTful Web Service
RESTful Java with JAX-RS
Service Design Patterns: Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services
The Core
In essence the REST Architecture consists of three parts:
- Client: This is where all the request get initiated.
- Server: Where the respond to a request is processed which can be in different forms.
- Network: This is the means through which the client and server correspond. (Usually not mentions as a part of the Architecture)
In this architecture state of the client constantly in transformation as it progresses in its requests. The server in response has many states to consider in a given time since it can be responding to many clients at a given time, in essence the sever is stateless.
This architecture is a great bases for a well designed browser based application.
Below you'll find links for several good resources for REST:
Short papers or Presentations:
Roy Thomas Fielding: Architectural Styles and the Design of Network-based Software Architectures
RESTful Web services
Rest of REST
What is REST
SOA with REST
RESTful Web Services for Java
RESTful Java with JAX-RS
RESTfulWeb Services Developer'sGuide
Books:
RESTful Web Service
RESTful Java with JAX-RS
Service Design Patterns: Fundamental Design Solutions for SOAP/WSDL and RESTful Web Services
Subscribe to:
Posts (Atom)