Compartmenting stages inhibits the development of a development-process-related overview such that
the risks inherent in transforming a requirement into a design, test or manual, and a design into code
will only be appreciated by the design authority (if then). The persons with a stake in exposing the risks
(the users and testers) will be excluded.
None of this however relieves developers of the responsibility for writing and executing their own
unit tests.
9.3.2 Specialization-Related
Some organizations employ specialists who alone are able to take requirements and design decisions on
some feature. In this case it is widely-recognized that validation and verification needs the reinforcement
of comparable expertise. This is the basis of the appointment of the Independent Safety Advisor to many
safety-critical projects.
Many organizations have a test group. The better ones involve that group at all stages of a system??™s
development from contract negotiation to retirement.
9.3.3 Feature-Related
To minimize compartmentization, some organizations have split their development teams into feature teams
each of which consists of up to 4 programmers, two testers (a senior and a junior), and a technical author.
(One or two of) the developers write the specifications and feed them back to marketing, the technical
author, and the testers.
The teams then develop and the technical author writes up the feature for the manuals.
Pages:
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368