Hi All,

I have to start an EAI integration project. What are the standards i
have to follow to make Integration Design Document. This document will
be provided to managers and  Biztalk developer team to develope the
integration system.

Any suggestion ???


Thanks

[ Post a follow-up to this message ]

>
> I have to start an EAI integration project. What are the standards i
> have to follow to make Integration Design Document. This document will
> be provided to managers and  Biztalk developer team to develope the
> integration system.

I think it depends a lot on your situation. Personally, I've had good
success by separating the documentation in two categories:

- An Architecture document, explaining the core patterns and rationality of
the solution. This also presents the basic functionality and non-functional
requirements that should be part of the solution and how the proposed
architecture addresses those.
- A set of functional specifications detailing specific parts of the
solution. I also complement this sometimes with prototiping things like maps
in Excel documents, for example.


--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Hi Restrepo,

Thanks for response.
Do you have any sample document to share with me ?



Tomas Restrepo (MVP) wrote: 
>
> I think it depends a lot on your situation. Personally, I've had good
> success by separating the documentation in two categories:
>
> - An Architecture document, explaining the core patterns and rationality o
f
> the solution. This also presents the basic functionality and non-functiona
l
> requirements that should be part of the solution and how the proposed
> architecture addresses those.
> - A set of functional specifications detailing specific parts of the
> solution. I also complement this sometimes with prototiping things like ma
ps
> in Excel documents, for example.
>
>
> --
> Tomas Restrepo
> tomasr@mvps.org
> http://www.winterdom.com/

[ Post a follow-up to this message ]

> Thanks for response.
> Do you have any sample document to share with me ?

Unfortunately, no, sorry, those I have are confidential.

That said, here's more or less how I tend to outline these kinds of
documents:

- Architecture:
- Architectural Principles
- Conceptual Architecture: High-level Problem description, high-level
solution concept, interfaces list, core data and work flows.
- Technical/Logical Architecture: Technical details of interfacing with
each source/target system/datastore/applications, security considerations,
identification of required components/artifacts, project conventions
- Deployment architecture


- Functional integration documents:
- Detailed information on the business scenario. Especial attention is
dedicated to events/actions that trigger the scenario, as well as value
derived from it and it's purpose
- Workflows deriving from the business scenario
- Document/Message especification (initially are just list of data
structures/entities and relevant fields, later can grow to accomodate more
detailed information)
- Identification of necessary mappings across applications (usually
especified with tables or in an Excel workbook)
-

There is probably stuff I'm missing, but this seems to me to be the core
information needed.

--
Tomas Restrepo
tomasr@mvps.org
http://www.winterdom.com/

[ Post a follow-up to this message ]

Thanks alot, now i have good idea about the documentation.

[ Post a follow-up to this message ]