LT: Given That The .NET Platform Is Open to All ISVS, DOESN '的 m.? M m a a.? G g?'?
MD:. There are different levels of integration The VS.NET environment provides much more integration, and in that sense it is certainly easier to use different vendors' tools But you still face the issue of deeper semantic integration, such as data integration.. With different vendors' products, will you get, for example, common representation of use cases between your requirements management tool and your modeling tool? you benefit from deeper semantic integration, where each tool knows how the rest work.
For another example, our component test tools rely heavily on information stored in the models for test-case generation and test-stub generation. That's harder to integrate between vendors. So you can get good UI integration and control integration across vendors, but not data integration and process integration. Deep integration helps us in providing more lightweight, agile versions of lifecycle tools as well. That's why we did not just port our stuff to .NET. We rearchitected it. The fundamentals do not change with .NET, OR WITH LIFECYCLE TOOLS, But The Practicality of Using Them with a Wider Variety of Projects WILL.
LT: The Old Saw Goes, "Wait for Rev 3 of any MS Product;" That Has to Be Doubly True with a technology as vast as .net. What Would You Tell Development Managers Who Think THEY SIOULD SITOT IN THE SIDELINE AND LET OTHERS WORK WIDELINE AND LET OTHERS WORK WITHE INEVITABLE BUGS IN A First RELEASE AMBITIS?
