Usha's Page

As most know, when evaluating or developing software, putting it through its paces under real-world conditions is a critical yet often overlooked step. The key phrase here being "real-world conditions." Many times, testing plans are developed and implemented but do not take into account the size or technical savvy of the intended user community.



We were once called in to help solve a bug that the software developer simply could not track down. This bug only occurred in the user… Continue

During the software development life cycle (SDLC), time and resources need to be committed to application testing. This is the testing that is done by the testing group, (i.e., the black box testers.) The allocation of time and resources is always a problem, as some organizations aren't quite sure how much should be assigned.



Where does testing belong? Some say at the beginning, others say at the end. Some even say nowhere, as it doesn't really add anything to the product's… Continue

IEEE 829 standard for software testing documentation



One of the challenges facing software testers has been the availability of an agreed set of document standards and templates for testing. The IEEE 829 provides an internationally recognised set of standards for test planning documentation.



IEEE 829 has been developed specifically with software testing in mind and is applicable to each stage of the testing life cycle including system and acceptance… Continue

The benefits of open source depends largely on the open source product itself. Indeed, there are many open source projects that enjoy very few of these benefits.



In the remainder of this blog posting, I will look at how the nature of a particular open source product often determines the ability to realize the general advertised benefits of open source associated with that product.



Business Flexibility:



It has been argued that an advantage of open… Continue