Visually developing enterprise applications by using domain modeling diagrams

You can use domain modeling diagrams to represent and analyze an existing system to identify its components and interrelationships and create representations of the system in another form. You can use domain modeling diagrams to automatically abstract the system's structural information from code to a new form at a higher abstraction level. You can redesign the system for better maintainability or to produce a copy of a system without access to the design from which it was originally developed. You can also modify the target system or develop and generate new systems.

A domain modeling class diagram depicts some or all of the components or elements in an application. You can use class diagrams to understand and design the structures and relationships for EJB enterprise beans. You can create your own context to understand, collaborate, and develop an application by using a subset of its classes. You can also develop enterprise beans directly from class diagrams and test enterprise beans on a server.

In Rational® Software Architect, you can use sequence diagrams to visually represent and develop behaviors and interactions of enterprise beans. You can also use temporary, non-editable browse diagrams to create quick static views and explore existing relationships in applications, and use non-editable topic diagrams to create dynamic views of applications based on context and queries.