|
||||
|
|
|||
|
 |
 |
Behind the Scenes: Assembling an Enterprise Tool
PDC, October 28, 2003
Microsoft discussed its vision of the future, and the future of enterprise computing, on the first day of this year's Professional Developers Conference in Los Angeles. It focused primarily on the tools that will enable developers to make that vision happen. Such toolsets aren't created in a vacuum. Yes, there is the ongoing parade of software design reviews with seemingly endless tweaks and adjustments, but creating enterprise-level frameworks and tools that meet real-world business needs requires getting your hands dirty. Microsoft has assembled a little-known team called the Microsoft .NET Enterprise Architecture Team (.NEAT) to test and improve its enterprise tools. This team has two important responsibilities: developing real-world architectures for difficult business problems with enterprise-level partners, and sharing the lessons learned to the various Microsoft product teams. Companies that have participated in this program include Citigroup, Reuters, the Swiss Stock Exchange, and Volkswagen. The group concentrates on finding projects of architectural significance that haven't been done before or presenting logistical issues in implementing a solution. Microsoft isn't providing free labor and doing all the work for companies, however. A key requirement for participating in this project is that you must devote your own resources to the project. Simon Guest, a member of Microsoft's .NEAT group who specializes in enterprise interoperability and integration, described how the project typically works. Microsoft pays a potential client an on-site visit to ascertain what kind of project is involved. Microsoft usually mandates that the project itself—which usually lasts about three months—be executed in Redmond. It's important that the customers involved demonstrate a commitment to these projects. Microsoft requires these companies to send their top software designers and architects. Companies must pay their employees' travel and other expenses. Additionally, Microsoft tries to involve a system integrator in the project, preferably one the company works with already. In return, Microsoft supplies one or two people from its architecture team and loops in Microsoft Consulting Services where appropriate. The assembled team lives in Redmond for three months as it scopes out the project, analyzes the business requirements, and designs a solution. On some projects, Microsoft invites select business analysts up to Redmond to discuss the business issues. Both Microsoft and the participating company are free to use the code and implementation worked out in these projects. Microsoft owns the license to the work, but the customer has license rights to implement it and adapt it as necessary. Once a project is finished, the real work begins. The company Microsoft worked with heads off to implement the described solution, and Microsoft's .NEAT team is tasked with analyzing the just-finished project and making recommendations for how to take better advantage of Microsoft's existing enterprise tools, as well as how to improve them. The lessons learned aren't shared only with various Microsoft development teams, but with other clients and potential customers as well. They are also shared in books, magazine articles, and at an annual event called the Software Architect Forum (SAF). Microsoft invites roughly 250 software architects to this event to discuss issues it has encountered on such projects, as well as other issues related to creating scalable and usable architectures for enterprise systems. The Microsoft .NEAT initiative shows the company's commitment to continual improvement of enterprise tools. Working directly with enterprise teams in this way offers significant benefits for both Microsoft and its clients, and should continue to help fulfill Microsoft's visions for the future. About the Author |
|
|||||||||||
