February 3rd, 2001
The Renaissance World Gate Hotel
Orlando, Florida
Fusedoc Documentation Standard
Fusedoc Documentation Standard
A Fusedoc outlines responsibilities, customizations, and expectations of fuses, and is unique to each fuse
No fuse can assume the existence of any variable unless it is noted in the Fusedoc for that fuse
Once completed, a Fusedoc should provide all the information needed to code the fuse – no interaction with application architects or previous specifications should be needed
A Fusecard contains the following elements:
Name of the file
Responsibilities (non-technical, plain English, derived from the application design/fUseML)
Author / coder
Variables list (incoming, outgoing, and persistent)