Better Software Articles
Instead of wading through requirements documents, try drawing them instead. Learn about three simple diagrams and how to turn them quickly into valuable models. The diagrams presented here represent the most commonly used types for each of the three software dimension perspectives: data flow diagrams for function, class diagrams for information, and state transition diagrams for behavior.
It's not easy to know the ways that a product might fail, determine how important the failures would be if they occurred, and then develop and excuse tests to discover whether or not the product would indeed fail in those ways. Renowned tester James Bach shares some of his tips for dealing with common risk-based testing obstacles.
Think you’re ready to launch your new metrics program? Think again. Find out how conducting a trial measurement program on yourself first can give you valuable insights and understanding. Learn about the value and limits of measurement, gain knowledge into why many software measurement efforts fail, and prepare yourself for launching a successful program.
Sometimes TDD (Test-Driven Development) doesn't get used because it can be cost prohibitive to a testing budget. Read on as Joel Spolsky laments the limited real-life usefulness of test-driven development and discusses some common roadblocks to using this testing technique.
This article details interview behavior basics you should follow before, during, and after the interview. Jonathan Bach shares the secrets of putting your best foot forward when you're the one being tested.
Borrowing ideas from Robot, Rational's RobotJ focuses on automating a specific class of applications: Java and Web (HTML). RobotJ's scripts are based on a commom language (Java2), instead of yet another scripting language specific to yet another automation tool. Tom Arnold takes a look at test automation with Rational's RobotJ.
When you file a bug report, you become a bug advocate. It's your job to follow up to see that the bug is addressed one way or another. The way you write your report influences whether the application's behavior is changed. In this issue's "Bug Report," Danny Faught gives tips on writing successful bug reports.
Risk Management can be divided into three general types: risk management and decision-making, the process and mechanics of IT risk management, and the practice of risk management. In this issue's "Reference Point," Bob Charette recommends some useful resources on risk management.
People tend to gravitate toward what they feel comfortable with. This is also true when it's time to choose a testing methodology. Is a particular personality more suited to software testing than another? In this issue's "Technically Speaking," Brian Marick explores this possibility.
When is a year of experience not a year of experience? When that experience doesn’t match your needs. Assembling the right mix of people for your software team can have a tremendous impact on productivity and quality. Find out how to discern whether a potential candidate will make the grade.
Recommended Web Seminars
Agile Connection is one of the growing communities of the TechWell network.
|Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery. Join the conversation now!|