- May 07, 2008
Concurrent programs loom as a major developer and tester challenge as multicore processors grow in use. A dynamic analysis tool for Java from Coverity may automatically detect multithreading deadlocks and race conditions, while incurring low ...
- April 11, 2008
Not properly signing off on a software project's requirements limits the quality assurance (QA) team's ability to ensure that the software does as it's intended.
- March 07, 2008
According to a recent Info-Tech report, six types of functional tests can be used to ensure the quality of the end product. Those tests are unit tests, functional tests, systems tests, regression tests, system integration tests and acceptance tests.
- March 05, 2008
When offshore testers partner with the client's user acceptance testing (UAT) team, they can be better assured that the business's needs are met and that bugs are found early.
- February 06, 2008
A Forrester study found that problem resolution is inefficient at most organizations. By automating the process companies can solve problems faster and cut costs, Doug Laney says.
- December 17, 2007
The Coverty Prevent SQS static code analyzer helps developers identify race conditions and other concurrency defects in multi-threaded applications earlier in the development cycle.
- December 03, 2007
The terms iteration and increment are often used interchangeably. The problem is, however, they don't mean the same thing. Kevlin Henney explains the differences, as well as how to use iterative development to improve your development process and ...
- November 01, 2007
It's tempting to consider use case diagrams as context diagrams because they do show context. But having one diagram for both will result in an unreadable cloud of bubbles.
- October 08, 2007
Bypassing requirements testing can lead to software that doesn't do what users expected, costly software changes and often project failure.
- September 24, 2007
Putting too much into a use case diagram can often render the otherwise useful technique of use cases almost useless. Kevlin Henney recommends a more balanced and restrained approach in order to not lose readers in a myriad of bubbles and ...
- August 16, 2007
Software quality suffers when IT managers poorly communicate with their team and make decisions based on their own self-serving interests.
- August 01, 2007
While still early in the adoption curve, software development and IT groups are finding Six Sigma, often combined with other process improvement efforts such as Lean and CMMI, helps to reduce defects and improve quality.
- July 25, 2007
By doing unit testing, programmers can catch bugs early before they cause significant problems or delays. It's important, however, that programmers feel comfortable testing and not be scared off by extreme testing practices. Alberto Savoia explains ...
- July 23, 2007
Software testing and QA groups already pushed to the limit face even more challenges with SOA applications. Automation through modeling can help monitor and test such applications.
- July 18, 2007
Ideally use cases capture the functional requirements of a system in terms of identifiable and testable goals. The trick is writing and documenting them so that they offer value not just for requirements gathering but also for software design and ...
- June 04, 2007
The changing face of application lifecycle management (ALM) has application development organizations looking to tools and technologies that help them collaborate across functional silos, work across large geographic distances and work more ...
- May 21, 2007
Alistair Cockburn, a signatory on The Manifesto for Agile Software Development, talks about the agile landscape, what has changed and where his methodology, Crystal, fits in.
- April 18, 2007
AccuRev founder and CTO Damon Poole has developed a methodology he calls Hyper Agile. Recently he talked with SearchSoftwareQuality.com about the benefits of Hyper Agile, how it differs from other agile methodologies and how it helped in the ...
- February 20, 2007
Software testing is uselss if it isn't complete. Statement and branch coverage can uncover glaring problems in unexecuted blocks of code, but they often miss bugs in the logic of your code. Path coverage, however, is a more comprehensive technique ...