The Latest
|
The TSA and Software Quality[magazine] As evidenced by news stories relating blatant failures on the part of the Transportation Security Administration, many organizations fail to learn much from the information testing provides. What can we do to improve the quality of our measurements so we can learn valuable lessons from the results? |
||
 |
Building a Foundation for Structured Requirements: Aspect-Oriented Engineering Explained (Part 1)[magazine] Aspect-oriented requirements engineering (AORE) is a new methodology that can help us improve the analysis, structure, and cost of development of software requirements. AORE does not replace but rather complements any of the existing requirements methodologies. This two-part paper explains to software practitioners the AORE concept, illustrates how it can be applied on software projects, and discusses the benefits of AORE. Part I focuses on the AORE analysis techniques. |
Yuri Chernak
December 30, 2008 |
|
The Kanban Primer: A Cultural Evolution in Software[magazine] Kanban,a Japanese word meaning “signal card,” introduces a new way to think about software development. Through signaling, a limit is set on work in progress resulting in a system that is never overloaded. Kanban signals do not need to be based on passing physical cards; any virtual signaling mechanism will do equally well. |
||
 |
Risk-based Testing in Action[magazine] Risk-based testing allows project teams to focus their limited test efforts on the areas of the product that really matter, based on the likelihood of bugs in those areas and the impact of bugs should they exist. By using risk priority to sequence test cases and allocate test effort, test teams can also increase their chances of finding bugs in priority order and allow for risk-based test triage if necessary. |
Rex Black
December 30, 2008 |
|
Jumping to Conclusions[article] Much of our behavior is automatic. We breathe without thinking about it, and we blink without much conscious effort. We do lots of other things without an iota of thought. In this column, Naomi Karten explains how jumping to conclusions is yet another thing we do without thinking about it—for better or worse. |
||
 |
A Path to Readable Code[magazine] Test-driven development is usually presented as a developer process. On the other hand, acceptance test-driven development (ATDD) is a communication process between the customer and the developer. In ATDD, the tests provide the terminology in customer-understandable terms. The customer's terminology suggests abstract data types that make code more readable. |
|
|
Lucky and Smart[magazine] Charles Darwin was certainly a great scientist, but his career and his discoveries were also strongly influenced by serendipity and luck. What could this great explorer and scientist teach us about testing? |
||
 |
Questions You Should Ask[magazine] It's a technique children and teenagers have mastered: asking "why" until they get to an acceptable response (or until we're too tired to continue answering). Find out how Michele Sliger uses a similar approach designed by Six Sigma to drill down into the underlying cause of any problem within software projects. She then continues the inquisition with a series of other questions in order to find out how these problems affect business value and technology. Read on to learn what these questions are and how you can start using them to find out why things aren't going as planned. |
|
|
Agile Acceptance Testing Using .NET FitNesse[presentation] FitNesse is an open-source test automation tool that enables business users, developers, and testers to cooperate on agile acceptance testing. |
Gojko Adzic, Neuri Ltd.
|
|
|
Going Mobile: The New Challenges for Testers[presentation] Mobile device manufacturers face many challenges bringing quality products to market. Most testing methodologies were created for data processing, client/server, and Web products. |
Wayne Hom, Augmentum Inc.
|
|
|
Integrating Security Testing into Your Process[presentation] Software quality is a priority for most organizations, yet many are still struggling to handle the volume of testing. Unfortunately, applications are frequently released with significant security risks. |
Danny Allan, IBM Rational
|
|
|
A Modeling Framework for Scenario-Based Testing[presentation] Scenario-based testing is a powerful method for finding problems that really matter to users and other stakeholders. |
Fiona Charles, Quality Intelligence Inc.
|
|
|
STARWEST 2008: Quality Metrics for Testers: Evaluating Our Products, Evaluating Ourselves[presentation] As testers, we focus our efforts on measuring the quality of our organization's products. |
Lee Copeland, Software Quality Engineering
|
|
|
Database Locking: What Testers Should Know, Why Testers Should Care[presentation] Database locking is a complicated technical issue for some testers. |
Justin Callison, Peak Performance Technologies
|
|
|
STARWEST 2008: Automating Security Testing with cUrl and Perl[presentation] Although all teams want to test their applications for security, our plates are already full with functional tests. What if we could automate those security tests? |
Paco Hope, Cigital
|
Pages
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.