Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Use-cases are a scenario based technique in the UML which identify the actors in an interaction and which describe the interaction itself. A set of use cases should describe all possible interactions with the system. Sequence diagrams may be used to add detail to usecases by showing the sequence of event processing in the system. A use case diagram is an excellent way to communicate to management, customers, and other non-development people what a system will do when it is completed.
Use cases
They model the dynamic aspects of the system. Provides a users perspective of the system.
The role of actor may change based on the functionality active may become passive and vise versa
5
Administrator
add member
academic
del member
add subject
del subject
assg subject
unass subject
student
enrol subject
10
unenrol subject
Student
View grades
Academic
Administrator
Scenarios
Each scenario has a sequence of steps. Scenario 1 : Student is enrolled for the subject. Student chooses the enroll subject action. Check the student has enrolled in less than 10 subjects. Check if the subject is valid. Assign the subject to the student.
13
Scenarios
Each scenario has a sequence of steps. Scenario 2 : Enrolling fails since the student is already enrolled in 10 subjects. Student chooses the enroll subject action. Check the student has enrolled in less than 10 subjects. Return an error message to the student.
14
Special 15 Actor
Buy a product
customer
Collect Money
Self service machine
Collector
Restock
Supplier
16
<<includes>>
Close Machine
Close Machine
Close Machine
18
Use Case Example (self service machine generalize relationship): Actor-to-Actor relationship
generalized actor
Supplier Agent
specialized actor
Restocker
19
Collector
customer
Restock
<<includes> Restock according to sales >
Open Machine
Close Machine
supplier
20
<<includes>>
Close Machine
21
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). 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.
23
24
1
*
1 has
has *
Subject
UniversityMember
010
0..3
AcademicStaff
25
Student
takes teaches
Requirements of ATM
Requirements of ATM
Use cases
Identify the actor Actors are entities that interact with the system under design Customer: customers need to perform banking transactions using ATM machine Bank: The bank serving the ATM Operator
MVC (Model , View and Control) high level Design of the System:
Class Diagram
Indirect
Interactor
Domain
Library manager
Finance
Ar ticle providers
Users
Library staff
UI standards
Classification sy stem
Students
Staff
External
Sy stem managers
Cataloguers
client
reserve
employee
Order title
Fine payment
supervisor
37
A Library System.
Reader Af filiation
Object aggregation
Thank You