White Paper: The DODAF standard defines a number of work products, some of which are identified as requirements for a system to be compliant, others are identified as supporting products that are recommended but not required. 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.
The opinions and positions expressed within these guest posts are those of the author alone and do not represent those of the TechWell Community Sites. Guest authors represent that they have the right to distribute this content and that such content is not violating the legal rights of others. If you would like to contribute content to a TechWell Community Site, email [email protected].
CMCrossroads is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.