The class diagram is the main building block in object oriented modeling. They are being used both for general conceptual modeling of the systematics of the application, and for detailed modeling translating the models into programming code. The classes in a class diagram represent both the main objects and or interactions in the application and the objects to be programmed. Identify classes from the use cases and sequence diagrams. Following are the 3 classifications of classes. 1. User Service Classes (Form level objects) 2. Business Service Classes (Control level objects) 3. Data Service Classes (Entity level objects) Below are some techniques for identifying classes. The first level is called as Analysis level classes. 1. 3 classes for each use case, 2. 1 class each for external actors, 3. 1 class each for alternate & exception flows. Now after these, we have to exclude classes on following rules... 1. Exclude classes which don'...