10 Formal methods process model
Start
Outline requirements
Detailed requirements
Formal definitions
Formal proofs
System design
System
Test specifications
and tests
Define outline
requirements
Refine requirements
Detailed requirements
Detailed requirements
Formal definitions
System Test system
Create test
specifications
and tests
Stop
Create formal
definitions
Prove formal
definitions
Design and
build system
56 Manage Software Testing
??? Developers need to be highly-motivated, responsible, and competent, taking the requisite time to
document what they are doing. Typically they are supposed to document requirements as soon
as these are stable. Check for airborne pigs.
??? Since it relies on the customer??™s ability to write ???user stories??? and if customers narrate their stories
with their usual level of precision (and no one checks), then the integration phase will be problematic,
and acceptance testing will be distinguished by the number of snapped pencils, gritted
teeth, and people crying in corners.
System testing (sometimes mis-referred to as acceptance testing by agile methods promoters) remains as
agile as the persons doing it. For system testing to match the agility of other phases of development, it
is essential that the requirements are captured as they evolve, and that the testers write tests as features
are built rather than at the end. One way of capturing evolving requirements is to write them down as
notes in the test cases.
Pages:
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182