1. 1 System Analysis and Design Using UML INSTRUCTOR: Jesmin Akhter Lecturer, IIT, JU

2. 2 What is UML? 4 It is a Unified Modeling Language, which is mainly a collection of graphical notation that methods use to express the designs. 4 The UML is language for visualizing, specifying, constructing and documenting the artifacts of software system. 4 UML is visual modeling language for modeling systems.

3. 3 UML refers to: 4 UML things: Class, component, node, relationship, package etc.. 4 UML diagrams: Use case diagram, interaction diagram, class diagram, State diagram, deployment diagram

4. 4 UML diagrams: 1. Use case diagram 2. Class Diagram 3. Behavioral diagrams - State chart diagrams - Object diagram - Activity diagrams - Interaction diagrams - Sequence diagrams - Collaboration diagrams 4. Implementation diagrams - Component diagram - Deployment diagram

5. 5 Semantics of Diagrams: ò Use case diagrams represent the functions of a system from the user’s point of view. ò Sequence diagrams are a temporal representation of objects and their interactions. ò Collaboration diagrams are a spatial representation of objects, links, and interactions. ò Object diagrams represent objects and their relationships, and correspond to simplified collaboration diagrams that do not represent message broadcasts. ò Class diagrams represent the static structure in terms of classes and relationships.

6. 6 Semantics of Diagrams: Contd... ò State chart diagrams represent the behavior of a class in terms of states ò Activity diagrams are to represent the parallel behavior of an operation as a set of actions. ò Component diagrams represent the logical components of an application. ò Deployment diagrams represent the deployment of components on particular pieces of hardware.

7. 7 What is USE CASE diagram? 4 A use case diagram establish the capability of the system as a whole. 4 Components of use case diagram: Actor Use case System boundary Relationship Actor relationship 4 Semantic of the components is followed.

8. 8 ACTOR: What is an actor? 4 An actor is some one or something that must interact with the system under development 4 UML notation for actor is stickman, shown below. Customer Manager Cashier

9. 9 ACTOR: More about an actor: 4 It is role a user plays with respect to system. 4 Actors are not part of the system they represent anyone or anything that must interact with the system. 4 Actors carry out use cases and a single actor may perform more than one use cases. 4 Actors are determined by observing the direct uses of the system,

10. 10 ACTOR: Contd… 4 Those are responsible for its use and maintain as well as other systems that interact with the developed system. 4 An actor may - input information to the system. - receive information from the system. - input to and out from the system.

11. 11 ACTOR: How do we find the actor? 4 Ask following questions to find the actors: –Who uses the system? –Who installs the system? –Who Starts up the system? –What other systems use this system? –Who gets the information from the system? –Who provides information to the system? 4 Actor is always external to the system. They are never part of the system to be developed.

12. 12 ACTOR: 4-Categories of an actor: 4 Principle: Who uses the main system functions. 4 Secondary: Who takes care of administration & maintenance. 4 External h/w: The h/w devices which are part of application domain and must be used. 4 Other system: The other system with which the system must interact.

13. 13 USE CASE: What is USE case? 4 A use case is a pattern of behavior, the system exhibits 4 Each use case is a sequence of related transactions performed by an actor and the system in dialogue. 4 USE CASE is dialogue between an actor and the system. 4 Examples: Open new account Withdrawal of cash from ATM

14. 14 USE CASE: Contd… 4 A use case must deliver something of value to an actor. 4 The use cases may be decomposed into other use cases. 4 Use cases also present a good vehicle for project planning.

15. 15 USE CASE: USE CASE documentation example:  The following use case describes the process of opening a new account in the bank. Use case: Open new account Actors: Customer, Cashier, Manager Purpose: Like to have new saving account. Description: A customer arrives in the bank to open the new account. Customer requests for the new account form, fill the same and submits, along with the minimal deposit. At the end of complete successful process customer receives the passbook. Type: Primary use case.

16. 16 SYSTEM BOUNDARY: What is System Boundary? 4 It is shown as a rectangle. 4 It helps to identify what is external verses internal, and what the responsibilities of the system are. 4 The external environment is represented only by actors.

17. 17 RELATIONSHIP What is Relationship? 4 Relationship between use case and actor. Communicates 4 Relationship between two use cases Extends Uses 4 Notation used to show the relationships: >

18. 18 RELATIONSHIP : 4 Relationship between use case and actor is often referred as “communicates”. 4 Relationship between two use cases is refereed as either uses or extends. USES: 4 - Multiple use cases share a piece of same functionality. 4 - This functionality is placed in a separate use case rather than documenting in every use case that needs it.

19. 19 RELATIONSHIP: Contd... 4 A uses relationship shows behavior that is common to one or more use cases. EXTENDS: 4 It is used to show optional behavior, which is required only under certain condition.

20. 20 USE CASE diagram: Use case diagram for the shown functionality. Balance status report Withdraw cash Validation uses Customer Clerk Manager extends ATM

21. Use case diagram for ATM 21