• A model of the application domain is built
• Using well known object-oriented modeling principles
• Main concern is to capture the domain semantics, with very little concern for the types of users and tasks
• The product is a class schema built out of Sub-systems, Classes and Relationships.
• Further depending on application types:
     – Read-only application
        • Design source for the navigation and interface models
    – Dynamic Web-applications
        • An object model to be implemented
    – The model being data containers
            • Can also be implemented in a relational database
            • Usually found in commercial Web applications