CloudShare’s Development and Testing Offer Meets the Requirements of Modern Software Prototyping Best Practices
Many enterprise IT organizations, and their peers in the public and not-for-profit sectors have embraced software prototyping. A review of the components of an industry-standard software prototyping procedure can provide decision-makers with the qualifiers they need to choose the right solution for their specific needs. A handy guide, in PowerPoint form, can be found in a presentation by Vishnu Chaitanya reddy Nara, Software Prototyping, which is published by Louisiana Tech University.
CloudShare’s Development and Testing offer meets, or exceeds the basic requirements of an industry standard software prototyping process, as it is described in Vishnu Chaitanya reddy Nara’s presentation.
The presentation summarizes three different approaches to software prototyping:
- Throw Away Prototyping
- Evolutionary Prototyping
- and Operational Prototyping
Vishnu Chaitanya reddy Nara writes about “Throw Away Prototyping”: “Throw away prototyping is one type of approach where an initial prototype is built mainly focusing on the poorly understood requirements” (quoted from a PowerPoint Slide Deck published on the web site of Louisiana Tech University. A download link for the slide deck has been provided in the paragraph above). Early stage Independent Software Vendors (ISVs) are prime candidates for “Throw Away Prototyping”. Their “ready, fire, aim” approach to software product development must be built with as close to a self destruct mechanism for concepts as possible.
Certainly there is no better method of rapidly assembling development tools, operating systems environments, and hardware infrastructure, than to make use of virtual computing resources for this purpose. CloudShare has the features required to make this type of prototyping not only possible, but profitable, when the annual cost of $2400.00 for a TeamLabs subscription (permits 3+ users to access a virtual development environment) is compared to the cost of acquiring disposable hardware, and software for a similar effort, albeit one handled on premises .
The foundation plank of a successful “Evolutionary Prototyping” method, the second of three noted above in our bullet list, Vishnu Chaitanya reddy Nara writes, is a set of ” . . . well understood requirements.” (ibid). If we look at this approach, from the perspective, once again, of an early stage ISV, we see a need for “Evolutionary Prototyping” once our “ready, fire, aim” method has revealed a bonafide product development opportunity for an enterprise computing market.
Recent quarterly earnings reports from some of the leading mature ISVs (Microsoft®, Oracle®, and IBM®, to name three) have indicated strong market demand from enterprise users for Software Defined Data Centers (SDDCs). SDDC, one can argue, is a safer step along a path to reliance on cloud computing resources for the kind of large communities of computing uers typical of enterprise business, etc. Of course, the underlying assumption powering SDDC is a combination of on premise computing for data communications of company proprietary information , with cloud Infrastructure as a Service (IaaS) resources.
Once again, CloudShare’s TeamLabs offer can certainly be used in an Evolutionary Prototyping approach to an SDDC system.
Perhaps the final variant presented by Vishnu Chaitanya reddy Nara, “Operational Prototyping”, represents the most promising method of the three, at least for CloudShare’s offer. This approach requires the user to be able to implement “Throw Away Prototyping” and its “Evolutionary” sibling, as required. Certainly it will be substantially less expensive for an early stage ISV to use the TeamLabs subscription offer to deliver, over the long term, for enterprise customers in need of an “Operational Prototyping” model for further systems development than would otherwise be the case with an on premises computing approach.
© IMB Enterprises, Inc. & Ira Michael Blonder, 2014 All Rights Reserved