U nified M odelling L anguage

1. بسم الله الرحمن الرحيماللهم صلي علي احمد السجايا محمد الخصال شفيع البرايا سليم النوايا صادق الاقوال

2. UnifiedModellingLanguage UML

3. Use case Diagram: • A use case diagram is “a diagram that shows the relationships among actors and use cases within a system. • The use case diagrams describe system functionality as a set of tasks that the system must carry out and actors who interact with the system to complete the tasks.

4. Use Case: • Each use case on the diagram represents a single task that the system needs to carry out. • Fro example (Buy a Product, Add Client …) One use case

5. Scenarios in use case: • A scenario is a formal description of the flow of events that occur during the execution of a use case instance. • It defines the specific sequence of events between the system and the external actors.

6. Actor : • An actor is anything outside the system that interacts with the system to complete a task. •  It could be a user or another system. • actor "uses" the use case to complete a task.

7. Relationship between use cases: 1- Include : Use the includes link to show that one use case includes the task described by another use case. Example:

8. Relationship between use cases: 2- Extend: • Use the Extends link to show that one use case extends the functionality of another use case at specific Extension Points. • Example:

9. Relationship between use cases: • Extend Example :

10. Relationship between use cases: 3 - Generalization: The generalization link is an informal way of showing that one use case is similar to another use case, but with a little bit of extra functionality.  One use case inherits the functionality represented by another use case and adds some additional behavior to it.

11. Relationship between actors: • Generalization: Generalization is a relationship between two use cases or two actors. Where A is a generalization of B, it means A describes more general behavior and B a more specific version of that behavior. Customer Employee

12. Relationship between actor and use case: • Association: The association is the link that is drawn between and actor and a use case.  It indicates which actors interact with the system to complete the various tasks.

13. System Boundary: • It is usual to display use cases as being inside the system and actors as being outside the system.

14. General Example of relationship :

15. Example :

16. Example: • The following sample shows a Use Case Diagram for an on-line CD catalog.  The system has a single actor: the on-line customer.  The customer can browse the catalog, search for a CD, add a CD to the order, view the order details, and place the order. • Both "View Order Details" and "Place Order" use "Calculate Order Total".

17. Example(cont ..)

18. UniversityRecordSystem(URS) • A University record system should keep information about its students and academic staff. • Records for all university members are to include their id number, surname, given name, email, address, date of birth, and telephone number. • Students and academic staff each have their own unique ID number: studN (students), acadN (academic employee), where N is an integer (N>0).

19. UniversityRecordSystem(ConT…) • In addition to the attributes mentioned above: • Students will also have a list of subjects they are enrolled in. A student cannot be enrolled in any more than 10 subjects. • Academic employees will have a salary, and a list of subjects they teach. An academic can teach no more than 3 subjects.

20. SomeActionsSupportedbyURS • The system should be able to handle the following commands. • Add and remove university members (students, and academic staff) • Add and Delete subjects • Assign and Un-assign subjects to students • Assign and Un-assign subjects to academic staff.

21. student UseCaseDiagramURSSystem URS add member Del member system user academic add subject del subject assg subject unass subject enrol subject unenrol subject