Survey Automation Report and Workshop Proceedings (2003) / Chapter Skim
Currently Skimming:
Practitioner Needs and Reactions to Computer Science Approaches
Practitioner Needs and Reactions to Computer Science Approaches
Pages 174-182
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 174... ...
But some of the things we test for in computer-assisted interviewing certainly, valid values and flow, but also the hard edits, the soft edits and the computations. But then I have a whole second slide, and there's a reason I have a first slide and a second slide.
|
From page 175... ...
* In multiple languages · Sample selection · Multimedia display and play · Data are correct · Navigation Non-linear navigation Ad hoc navigation · Pop-up help screens · Interviewer understanding and usability NOTES: Items from the first slide are more mechanical in nature and more readily suited to automated testing, while items from the second slide are context- and interface-specific features that may require human interaction for testing.
|
From page 176... ...
There is now more formal version control and build procedures; we have pop-up GUI error reporting dialogs from within our instruments, we're using tracking databases. And we're getting better at it.
|
From page 177... ...
And then there's something called a state table; we've heard a lot about O , 1 1 1 state tables but, basically, here's your state you begin at, here's your action, and here's the expected result. The state table can be hundreds, thousands of lines deep.
|
From page 178... ...
So if flow testing is OIL then look at the hard edit testing, and the idea is to cut down on the number of tests using the flow as the constraints. And remember the number of pairwise combinations was 613.
|
From page 179... ...
I've seen projects where the specification might be a Word document, a narrative document. But the exercise of coming up with scenarios that would provide a test can work off a Word document as well.
|
From page 180... ...
We have a lot of teams that are light on budget, and their refrain is, "we can't afford to do that." And our response has been, "you can't afford not to." Because what they're doing is, it looks lilac they're saving money up front but they'll actually be paying for it later on. PIERZCHALA: Let me just say, one of my jobs this afternoon, as given to me, was to sort of pull everybody back to earth.
|
From page 181... ...
Now the cost of those errors multiplies if you don't catch them earlier, so you're catching very expensive errors early. That's the good news.
|
From page 182... ...
And the beauty of that is the requirements specification and the test specification were the same. So what would happen is that the agencies would develop DFDs as a specification, and we would derive a test based on that.
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.