Dr. Dobb's Journal - February 2009 - (Page 25)

• Support for heterogeneous environments, so teams can have flexibility across the organization, based on specific project requirements. • Adaptive to current workflows and tools. Developers and QA engineers want to stay in familiar environments. • Access to complementary tools and configurations across the development lifecycle. Time Boxing Time boxing involves splitting projects into separate time periods of 2–6 weeks, each with their own deadline and budget. Deadlines are fixed but deliverables are adjusted. To meet the fast turnaround times and project splitting, engineering must allocate and configure systems quickly. If constrained by access to these systems or incorrect configurations, short iterations are impacted. On-demand cloud management server pools can mitigate this.) LEADTOOLS v.16 – .NET, WPF, C API, C++ Class Lib, COM & more! Microsoft, HP, Sony, Canon, Kodak, GE, Siemens, US Air Force Veterans Affairs Hospitals. For instance, CUBiT (CollabNet’s Cloud Management for Development Services) can be configured to manage a virtual private cloud with your own corporate computing resources, expanding to a public cloud such as Amazon EC2 if desired. This type of capability is key for automating any development environment. With such automation, overhead for software teams to obtain and manage computing resources is reduced with the Development Build and Test Services previously described. New systems can be provisioned from the predefined profiles within minutes while maintaining corporate security, auditability, and traceability. Design goals for the cloud environment include: • Teams must have autonomy over their own resources, and must have minimal delay in provisioning their own systems. • Strict access controls so that resources are dedicated to project teams or to a dedicated purpose (such as build or test). • Charge back for resources used. Even if the organization doesn’t charge back, teams can begin to understand the resource costs associated with their projects. • Using agile processes such as continuous integration (CI). • Automated build and test. Figure 3 illustrates how CUBiT manages development clouds of build and test services—combinations of physical and virtual machines with profiles. Software developers within their own projects have access to their own dedicated systems that are dynamically sharable among project members. CUBiT management features include visibility of all system resources within cloud, auditing, capacity monitoring, rolebased access, and accounting with charge back. Profile management enables version Image Formats: Image Compression: control and traceability for configuring predefined development stacks within minutes. Step 1: Configuring a virtual private cloud. Using CUBiT, you can configure multiple clouds for different use cases, and have the ability to control the usage of those clouds. For example, we could create clouds for continuous integration build systems and assign them as an exclusive resource to that project, or share it among any number of projects. Step 2: Giving developers easy access to cloud resources through their IDEs. CollabNet provides a free plug-in to IDEs such as Eclipse and Visual Studio that lets you seamlessly access the source-code management tool, collaboration platform, and development services (Subversion, SourceForge Enterprise, and CUBiT, respectively) without having to leave your IDE. From the IDE, you can browse all system resources within a cloud or CUBiT domain, physical or virtual systems. The management interface can be viewed directly from within the IDE; in addition, the systems can be securely accessed. Step 3: Creating reusable profiles for ondemand build and test services. By creating reusable predefined configurations explained as profiles earlier, systems can be consistently provisioned on demand, hence the concept of build and test services. Profiles are defined in an XML format and are maintained in a Subversion repository under version control, so systems can be restored exactly to a previous state if needed. Example 1 shows how a continuous integration build system can be provisioned from CUBiT. This example installs Java SDK, CruiseControl, Display Controls: Image Processing: OCR/ICR/OMR: Barcode: Forms Recognition and Processing: Document Cleanup/Preprocessing: PDF and PDF/A: Annotations: Grayscale Imaging: Medical Web Viewer Framework: Medical Image Viewer: DIC OM : DICOM Communications: WPF (XAML): AJAX JPIP Scanning: DVD: Multimedia: (866) 530-3418 Free 60 Day Eval! www.leadtools.com/dobbs LEADTOOLS SDKs feature LEAD’s iCompress™ Technologies. February 2009 l www.ddj.com l Dr. Dobb’s Journal 25 http://www.leadtools.com/dobbs http://www.leadtools.com/dobbs http://www.ddj.com

Table of Contents Feed for the Digital Edition of Dr. Dobb's Journal - February 2009

Dr. Dobb's Journal - February 2009 Contents Friday Night Fish Fry Alia Vox Developer Diaries Conversations Computing in the Clouds Software Development in the Cloud Videos and Oracle Forms 10g Parallel LINQ Decoupling C Header Files Effective Concurrency Disciplined Agility Swaine’s Flames

Dr. Dobb's Journal - February 2009

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.