At a closed-door meeting of its Interoperability Customer Executive Council (ICEC), held in May, Microsoft was surrounded by the critics suggesting that it is not sincere in handling customer feedback. However two executives of the company continued to mention that these feedback helped Microsoft form a more pragmatic approach to interoperability and in understanding what their customers and programmers of computer software development really need.

Craig Shank, general manager of the interoperability group at Microsoft, mention that the discussions at the ICEC event were “robust” and after the meeting the company has started various work streams, including meetings between its product architects and those customers. He specified that there are four main areas to Microsoft’s structured approach to interoperability:

• products and standards implementations,
• collaboration,
• developer resources, and
• participation in formal standards bodies

Shank added that the company has taken steps towards rewriting Office Binary Protocol file documentation, and that there is a “high degree” of support activity through MSDN. Microsoft is also identifying how it implemented standards, and it is collaborating with the industry to do testing work for its standards implementations. Microsoft has focused on specific testing, including Plugfest testing between SAMBA and Windows Server for file and print interoperability.

- By Software Development Team, SynapseIndia [Software Development India]

Any computer software development project ideally involves proper step by step documentation of the project details. The Documentation process facilitates the maintenance and scalability of the software in the long run.

Doc-O-Matic is a single source software documentation tool for source code documentation and Help authoring. It creates documentation, source code documentation, API documentation, application documentation and user manuals in PDF, HTML, HTML Help, XML, WinHelp and RTF from a single source. It creates fully cross linked documentation systems, including both source code documentation, Online Help and user manuals in PDF, browser-based Web Help, HTML Help, MS Help 2, Windows Help, RTF and XML. Create powerful documentation for your C/C++, IDL, C++/CLI, Managed C++, Delphi/Pascal, VB.NET, C#, MATLAB, JavaScript, ASPX, JSP and Java applications and components.

Doc-O-Matic uses information about source code symbols and existing comments in source code files (any source files that support comments) and external documentation files and creates accurate documentation based on popular IDE documentation styles.Features such as a visualization and design tool for class hierarchies, a graphical documentation QA tool and a flexible report generator help you develop high-quality and well documented software.Doc-O-Matic Doc-O-Matic box Doc-O-Matic compiles your documentation into balanced and highly customizable HTML Help 1.x, MS Help 2, WinHelp, browser-based Help or transformes it into a double-side printable PDF document or an XML file.

Accordingly, companies offering custom software development services across the world tend to implement commercial documentation generators for automatically preparing fully cross-linked documentation systems for their software development projects at hand. Doc-O-Matic is one such commercial automatic documentation generator.

The documentation systems prepared by Doc-O-Matic comprise documentation of the entire source code, browser-based help, Windows help, HTML help, MS Help2, online help, user manuals in PDF format, XML and RTF.  Programmers use DOC-O-Matic across almost all programming languages, including C#, C/C++, C++/ CLI, Java, IDL, Delphi, VB. NET, MATLAB, JavaScript, ASP.NET and JSP. It also supports all main formats for project file generation.