Analysis

Articles

Big data Big Data’s Relationship with Business Intelligence and Data Warehousing

You’ve probably heard the buzz about big data and business intelligence data warehouses. Both deal with collecting information for analysis, but how are they different? When should you use one or the other? This article explains these two data solutions in a user-friendly way with real-world examples.

Nels Hoenig
Clock: adding value How Testers Can Add Value Earlier in the Development Lifecycle

Before you can achieve continuous delivery, you need to first start implementing continuous integration. Some say CI is just for developers, but testers also play their own important roles. This article describes solutions that will help you add value to the development lifecycle—whether you work in an agile, DevOps, or traditional context.

Antoin Boerboom
Help keyboard button Overcoming Cognitive Friction to Engineer Better Software

The problems customers face are difficult to anticipate while developing software. However, looking at support issues can give a clearer idea about how to look for defects in the future. Sometimes users don’t know how to find certain information; other times, software doesn’t work as expected. In both cases, cognitive friction is at play.

Nilanjan Bhattacharya
Analysts Craft How Analysts Can Show Craftsmanship in Their Work

A craftsman could be defined by having enough experience to anticipate and prevent clients' problems before they even know they are going to have them. How might craftsmanship be manifested in analysis work? Terry Wiegmann captured some practices analysts can employ to demonstrate craftsmanship to their customers.

Terry Wiegmann
Risk Identification Awareness of Risk Identification in Software Testing

When testing software, most of us identify risk seemingly effortlessly. But do we really understand the process we’ve undertaken? Do we know what methods we’ve called upon? Are we aware of how we’re identifying risks? And therefore, are we identifying all the important risks? David Greenlees uses models to assess these questions.

David Greenlees
Testing Wins Should Come through Mastery, Not Luck

Bonnie Bailey writes that as testers, some of our track record will be pure luck—for better or for worse. We should, however, strive to test well enough that users must be crafty to cripple the software we stamp.

Bonnie Bailey
What Are Your Metrics Trying to Tell You? What Are Your Metrics Trying to Tell You?

Joanne Perold writes that you cannot just look at the numbers; the context behind the data is often far more valuable. Metrics can tell a compelling story or provide meaningful information to anyone who wants to pay attention, but when the focus is only on the number, it can be a disaster.

Joanne Perold
 Four Solutions Compared How to Test Your Website on Multiple Browsers: Four Solutions Compared

Robbie Bridgewater writes on the difficulty in finding bugs during testing since no single computer can run all of the major browsers—not to mention the added challenge of testing various mobile operating systems. In this article, Robbie compares four possible solutions to this dilemma.

Erle Bridgewater
What to Review If You Can’t Review Everything

Payson Hall shares with us a useful list of review criteria via a case study of a troubled software development project. Reviews can be messy. Sometimes it’s hard to know where to start, particularly when you are in triage mode and can only review a small sample.

Payson Hall
Writing Test Rules to Verify Stakeholder Requirements

Some organizations employ business analysts who are very good at specifying requirements at the beginning of a software project. The advantage of this step is the reduction in ambiguity for the developer and tester of what should be delivered.

Brendan Quinn

Pages

StickyMinds is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.