The Latest

Pat Wegerson recommends software configuration management resources AntiPatterns and Patterns in Software Configuration Management and the online CM Yellow Pages.

Testing applications on Pocket PCs requires a special strategy and plan. It's different from testing normal client/server or Web-based application. Testing applications for Pocket PCs is like a mixture of strategies applied for testing client/server and Web-based applications. The test strategies applied for testing client/server applications like compatibility on different platforms, different hardware and software considerations, user interface and the strategies adopted for testing web applications like compatibility on different browsers (if it's a Web application for Pocket PC or PDA), security (authentication, authorization, data confidentiality) should be taken into consideration.

Apart from the above, there are few more issues that we need to address while testing applications for Pocket PCs.

Software is often seen as different from other products that seem more tangible and less flexible. In this article, Gerold Keefer points out that the perception of flexibility is not always a positive perception, and approaching software as a product that should be "done right the first time" can improve quality. Gerold also illustrates a number of tangible-product metaphors common in the software industry.

This article is intended to throw some light on the characteristics or traits that a software testing professional should have to be a successful testing professional.

The communication of functional requirements and specifications is the most difficult, critical, and error-prone task in IT projects. Research has shown that projects that proceed to the construction and coding phase with missing or wrong functional requirements and specifications are almost certain to fail. To avoid missing or misunderstanding the requirements for a solution, and to avoid the development of systems to incorrect specifications, we need a systematic approach to capturing, organizing, and validating the functional requirements and specifications. In this article, Bill Walton offers such an approach.

Including a testing/QA component early in a software project necessarily prolongs the schedule, right? Not so, according to Ross Collard. In this, the third of a three-part series, Collard explains how to anticipate risks and to aggressively manage the process to prevent disaster.