The procedures describe in detail how
to perform the steps in the process.
Table 15.1 shows an example of a process for Requirements Management. This
template was created by an organization that did not depend on a lot of verbiage
in its documentation. It wanted just the facts, short and sweet. Even though the
information looks short, if there are many steps to a process, this can get quite
complicated.
Table 15.2 shows another example of the same process by the same organization
when it decided to add more text to explain the process. Included in the text
were the supporting procedures. The exhibit is simply the table of contents for the
process. The complete process was 20 pages long. Even though it was called the
Requirements Management Process, it only concentrated on creating the Requirements
Specification, the Requirements Traceability Matrix, and changes to the
requirements document itself.
198 n Interpreting the CMMI
Another way of documenting processes is by using a flowchart. Figure 15.2 is
an example of a graphical representation called a Swimlane Process Flowchart.
Pages:
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444