Object-oriented analysis and design(OOAD) UML Slides. for more slides refer www.scmGalaxy.com.

2. Most essential and commonly used steps in OOAD Define use cases Define conceptual model Define collaboration diagrams Define design class diagrams System Behavior diagram Analysis Design

4. Expanded Usecase: Alternate path to 2a : the total is 7 then the player looses the game SI No Actors Action SI No System Response 1 This use case begins when the Player starts the game by picking up the dice and then player rolls the the dice 2 2a Die Game will collect face value of each dice and then adds up to give the sum of the face value( total ) for a particular roll. If the dice total is 7 then system will indicate the player that he win’s , and request the player to continue the game.

5. Usecase Diagram

7. Conceptual model of the Dice game The conceptual model is not a description of software components; it represents concepts in the real – world problem domain .

9. Defining Collaboration Diagrams Illustrating messages between software objects For example, assume that a simulation in software of the dice game is desired. This collaboration diagram in Figure illustrates the essential step of playing by sending messages to instances of the Player and die classes.

11. Design class diagram of software components . For example, in the dice game, an inspection of the collaboration diagram leads to the following design class diagram. In contrast to the conceptual model, this diagram does not illustrate real – world concepts; it describes software components