The DODAF standard defines a number of work products, some of which are identified as required for a system to be compliant, others are identified as supporting and are recommended but not required. The 1997 C4ISR standard came out at about the same time as the UML standard and therefore doesn’t take advantage of the rich semantics and clear notation provided by the UML. Since then, the UML has been widely adopted in the specification of software and systems within the DoD and other environments. Additionally, the new DODAF standard provides recommended representations of the DODAF products using UML notation and semantics. This paper discusses each product required by the DODAF and shows how standard UML views and semantics can be used to represent them. Clearly, the unifying nature of the UML meets the needs of the DODAF very well, now and into the future.