When you create a SoDA document you must determine what information will act as sources to the document. SoDA extracts information using special programs called domains. Each domain understands a single source of information, such as Rational Rose and the File System.
Embedded in each domain is the knowledge of how information is modeled by that source, in terms of classes, attributes and relationships. For instance, the Rose domain understands that a class category has attributes of name and documentation, and contains relationships to classes, and has import relationships to other packages. This domain-specific knowledge enables you to retrieve exactly the information you want to document.
One of the benefits of SoDA is that it can support multiple domains, even within the same document. This means that project team members need to use (and learn) just one documentation tool throughout the software lifecycle, rather than using a different tool unique to design, coding, or testing.
Some domains, most notably ClearQuest and RequisitePro, are dynamic domains. Both of these domains have a small number of default objects. As these products are implemented, additional site-specific, dynamic, objects are added—database specific objects for ClearQuest and project-specific objects for RequisitePro. When you design templates, these custom objects become available for reporting.
Next
Parent topic
See also