Testing the tools

Testing the Tools
		Introduction  Sun Java Studio Creator  BEA Web Logic Workshop  Borland C# Builder  IBM WebSphere Studio  Summary

When looking at the different development tools and platforms to road test, we walked through typical RAD projects including quick and simple data-entry forms, and tied to a simple database table on the back end. Following the RAD methodology, we built prototypes with each tool, noting where a tool provided efficiencies and where it could use improvement. We also looked at the features and functionality within the IDE that supported the tenets of RAD design and suitability for the required tasks.

Microsoft Visual Studio.NET 2003
Visual Studio.NET 2003 can be used to create Web and Windows applications for the .NET framework in a variety of languages, including C#, VB.NET, C++, J#, and other supported CLR-compatible languages, as shown in Figure 1. One of the distinct advantages of Visual Studio as a RAD tool is this multi-language support, enabling developers to build applications that have components written in different languages, enabling organisations to leverage the different skills that exist within the organisation.

For the quick creation of prototypes, Visual Studio also rates highly with a number of tools and components that can be used to quickly create data-driven applications. The tight integration with SQL Server is also a bonus, although developers who need to access information held on other platforms may find it cumbersome to connect to their underlying data.

That said, there are a number of database vendors who have tools that can snap in to Visual Studio, including Oracle and DB2 that make database integration less of an issue. In addition to database support, there is also a thriving industry around third-party components for Visual Studio, enabling developers to buy components for functionality they don't have the time or skill to build.

The one major deficiency in considering Visual Studio as a RAD tool lies with the tools Microsoft has provided for teams of developers working on a single project. For versioning and source control, most Visual Studio developers will use Microsoft's Source Safe, which is difficult to use across multiple locations or work sites. In addition, Visual Studio does not have a lot of support for other developer roles (architect, tester, etc.) so you will need to employ other Microsoft or third-party tools to cater for the unique requirements of each of these roles.

Microsoft has recently announced it will bundle a number of new tools in it's release of Visual Studio 2005 for architects, unit testing, and team development, but these tools are definitely missing from the current release and with a RAD project, you may not have the time to wait.

Figure 1: Microsoft Visual Studio.NET