Vighnesh Bendre - MS technologies

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'...

We can also describe requirements in other ways. Use cases may contain secondary paths or alternative scenarios, which are variations on the main theme. Exceptions, or what happens when things go wrong at the system level, may also be described, not using the alternative paths section but in a section of their own. Alternative paths make use of the numbering of the basic course of events to show at which point they differ from the basic scenario, and, if appropriate, where they rejoin. 1. Alternate Path (Flow) 2. Pre Condition 3. Post Condition 4. Exception Flow. There are 3 major categories in sequence diagram. 1. Form Level – User Interface 2. Control Level – Business Logic 3. Entity Level – Data Interaction We will take Sign up to teach as a sample for demonstrating how to turn use cases into sequence diagram. This sequence diagram gives a rough idea to the end user (in our case its developers/managers) about the flow of the information. Use cases are generally not ...

Part 1 – Identifying Use Cases – Use Case Diagrams Recently I went through OOAD and UML training. The OOAD and UML tutorial was very impressive and I decided to share it with you. Object Oriented Analysis & Design and Unified Modelling Language is very important in a life cycle of a project. Previously I was involved in project requirement study and technical design. But this time, I learned the tricks of the trade. I discovered different tips for identifying Use Cases, Actors and Classes . In this series of posts, I am planning to take you through the process of involvement of UML in Requirement analysis and Design phase. This series will include 3 parts... Part 1. Identifying Use Cases – Use Case Diagrams Part 2. Realizing Use Cases – Sequence Diagrams Part 3. Identifying Classes – Class Diagrams For this purpose we will take commonly available sample requirement – Student Registration process. From this requirement we will identify the ACTORS and US...