Document Choreography of an EDI Purchase
Wednesday, February 10th, 2010
Keeping a copy of all of the documentation you create is a pretty general benifit. It helps you in three major ways;
I have never regretted keeping a personal copy of documentation. But I have always regretted knowing that I didn’t keep one when I could have used it.
Monday, January 18th, 2010
One of the things that I advocate is keeping a copy of the documentation you produce, and the documentation that you encounter and use. Over a short period of time, this can become a large amount of stuff. If you are just throwing it all in your MyDocuments folder, it can quickly get out of hand. To help out in this ongoing task and fight against the chaos, I am going to share some basic approaches that can help keep the sanity and utility in your documentation collection. (more…)
Tuesday, October 13th, 2009
One of the things that Integration Engineers are asked to do is create documentation. But as we all know, many times documentation is the last and poorest part of a project. Developers and programmers don’t generally like writing documentation, and are generally considered the most qualified.
In comes the Integration Engineer to make the system work. Producing effective documentation at this point is important. We want to make the system work, and then hand if off to the team that will support it. If we don’t create effective documentation, this last step can never happen, and we will be unable to undertake new integration work because we are still supporting the first one. And if we are a contractor, we need this even more. (more…)
Monday, May 11th, 2009
© 2010, The Integration Engineer. All Rights Reserved.
WP theme by TheIntegrationEngineer.com