Traceability Model in Layered Architecture

UPDATED WIKI: Home

joycsc — Tue, 16 Sep 2008 14:18:39 GMT

Resource Page Description
Traceability in layered architecture lets software architects to define, utilize, reuse and re-engineer existing, current and future application architecture in more structured way. This resource provides guidelines and template documents to trace multi-layer architectures easily.

Quicklink

Download guideline:
http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=tmla&DownloadId=1685
Download blank template:
http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=tmla&DownloadId=1686
Code project article:
http://www.codeproject.com/KB/architecture/tmlarc.aspx

UPDATED RELEASE: v1.1 (Apr 15, 2008)

Wed, 16 Apr 2008 07:19:28 GMT

Multi layer architecture is one of the most popular and proven model in the current trend of software development. It lets software designers and developers to easily isolate user interface, business logic and data access logic.

In last few years I have worked on several projects done by other developers to be improved and/or enhanced. Also, I see lots of starter kits, sample projects are available in web, and where from a beginner to expert can improve their ideas regarding latest best practices in layered architecture.

However, while reviewing source codes of projects done by other developers, always I miss a simple document by which I can easily grab the core ideas of the layering, and can update any part along with my own point of view. No matter how big the application or how complex the application architecture is, having a traceability structure helps the future developers for a given project, quickly understand the existing layering model, and/or utilizing/updating existing structure with considering appropriate design and requirements context.

Traceability model considering the logical layers is a very basic document which addresses several common questions, answers and view points of any current or future application architecture.

The resource documents provided in this release explores some of the common question and explanation point which will help us to form our own traceability model.

UPDATED RELEASE: v1.1 (Apr 15, 2008)

Tue, 15 Apr 2008 07:46:17 GMT

Multi layer architecture is one of the most popular and proven model in the current trend of software development. It lets software designers and developers to easily isolate user interface, business logic and data access logic.
In last few years I have worked on several projects done by other developers to be improved and/or enhanced. Also, I see lots of starter kits, sample projects are available in web, and where from a beginner to expert can improve their ideas regarding latest best practices in layered architecture.
However, while reviewing source codes of projects done by other developers, always I miss a simple document by which I can easily grab the core ideas of the layering, and can update any part along with my own point of view. No matter how big the application or how complex the application architecture is, having a traceability structure helps the future developers for a given project, quickly understand the existing layering model, and/or utilizing/updating existing structure with considering appropriate design and requirements context.

Traceability model considering the logical layers is a very basic document which addresses several common questions, answers and view points of any current or future application architecture.

The resource documents provided in this release explores some of the common question and explanation point which will help us to form our own traceability model.

CREATED RELEASE: v1.1 (Apr 15, 2008)

Tue, 15 Apr 2008 07:03:53 GMT

Multi layer architecture is one of the most popular and proven model in the current trend of software development. It lets software designers and developers to easily isolate user interface, business logic and data access logic.
In last few years I have worked on several projects done by other developers to be improved and/or enhanced. Also, I see lots of starter kits, sample projects are available in web, and where from a beginner to expert can improve their ideas regarding latest best practices in layered architecture.
However, while reviewing source codes of projects done by other developers, always I miss a simple document by which I can easily grab the core ideas of the layering, and can update any part along with my own point of view. No matter how big the application or how complex the application architecture is, having a traceability structure helps the future developers for a given project, quickly understand the existing layering model, and/or utilizing/updating existing structure with considering appropriate design and requirements context.

Traceability model considering the logical layers is a very basic document which addresses several common questions, answers and view points of any current or future application architecture.

The resource documents provided in this release explores some of the common question and explanation point which will help us to form our own traceability model.

UPDATED WIKI: Home

joycsc — Tue, 15 Apr 2008 07:00:28 GMT