inspections
|
Weekend Engagement In "Growing Your Career in Tough Times," Fiona Charles writes about some of the free and low-cost things testers can do for professional development when money isn't available for courses and conferences. In this column, she describes two examples of the amazing things some testers get up to on the weekend to practice their craft, develop their skills and knowledge, and have a great deal of fun.
|
|
|
Don't Believe Everything You Read! There are volumes of written material covering just about every aspect of software engineering. Books, articles, magazines, conference proceedings, Web sites, and other rich sources of information are readily available to those learning about our profession. However, based on personal experience and observation, Ed Weller is compelled to ask how much of this information is actually misinformation. Anytime you collect data you must proceed with caution! In this article, we'll find out why Ed questions validity and accuracy and what you can do next time you're faced with questionable material.
|
|
|
Design and Code Inspection Metrics In this study, historical inspection data from large real-time embedded systems were analyzed with the intention of improving the current review process.
|
|
|
The Seven Habits of Highly Insecure Software Severe functional bugs usually have pretty overt symptoms: an application crash, corrupt data, and screen corruption. Security bugs, though, usually have more subtle symptoms and habits. This article discusses the most common and difficult-to-notice symptoms of insecure software to help you track down these bugs during testing.
|
|
|
Prepare to Succeed Another pair of eyes will find bugs, but code reviews are traditionally time consuming and painful. Learn how modern, lightweight techniques make code reviews effective and practical.
|
|
|
Adapting Inspections to the Twenty-first Century How do you adapt inspections to a twenty-first century distributed workforce? A key part of the inspection process is the team meeting, which provides peer pressure to participate and consensus on defects. Teams working in multiple time zones have limited opportunities for the team meeting. A list of requirements and the functions needed to solve this problem based on real-world experiences should help anyone faced with this problem.
|
|
|
Rising Above the 7 Percent Rule Afraid of what you're missing by testing only 7 percent of your code? Forget your formal code inspections; Jason Cohen enlightens us on the merits of bringing lightweight code inspection to your organization.
|
|
|
Support for Testing, Testing for Support Where supportability and testability fit in the Quality Criteria dimension of the Heuristic Test Strategy Model.
|
|
|
Software Inspections: Key Elements of Success Inspections have over thirty years of history improving software quality and productivity. Numerous studies have shown inspection is the most effective process for discovering defects. Yet today, inspections are not widely used in the software industry. Why are they not more prevalent? Ed Weller knows that successful implementation of inspections requires a thorough understanding of
the process as well as the cultural and organizational roadblocks to implementation. Knowing when to apply inspections, or other defect identification techniques, also requires a cost-benefit analysis. Measuring and improving inspections requires an understanding of inspection process metrics and appropriate corrective actions. Ed discusses the inspection process, measurement, common pitfalls, and how to implement a successful program in your organization.
- Learn what makes inspections different from other types of reviews
|
Edward Weller, Software Technology Transition
|
Visit Our Other Communities
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.