Ansis 8 - Use Case Diagram
•Télécharger en tant que PPT, PDF•
5 j'aime•12,157 vues
Dokumen tersebut menjelaskan tentang diagram use case yang digunakan untuk menggambarkan fungsionalitas sistem dari sudut pandang pengguna, terdiri dari use case, actor, dan hubungan antara keduanya.
![USE CASE DIAGRAM ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommandé
Contenu connexe
Tendances
Tendances (20)
En vedette
En vedette (20)
Similaire à Ansis 8 - Use Case Diagram
Similaire à Ansis 8 - Use Case Diagram (20)
Plus de Lia Rusdyana Dewi
Plus de Lia Rusdyana Dewi (13)
Dernier
Dernier (20)
Ansis 8 - Use Case Diagram
- 15. ACTIVITY DIAGRAM
- 18. CONTOH ACTIVITY DIAGRAM Penarikan Uang dari Account Bank Melalui ATM
- 23. CLASS DIAGRAM
Notes de l'éditeur
- For each role you can specify the multiplicity of its class, how many objects of the class can be associated with one object of the other class. Multiplicity is indicated by a text expression on the role. The expression is a comma-separated list of integer ranges. A range is indicated by an integer (the lower value), two dots, and an integer (the upper value). A single integer is a valid range. During analysis, assume a multiplicity of 0..* (zero to many) unless there is some clear evidence of something else. A multiplicity of zero implies that the association is optional; make sure you mean this; if an object might not be there, operations which use the association will have to adjust accordingly. Narrower limits for multiplicity may be specified (such as 2..4). Within multiplicity ranges, probabilities may be specified. Thus, if the multiplicity is 0..*, is expected to be between 10 and 20 in 85% of the cases, make note of it; this information will be of great importance during design. For example, if persistent storage is to be implemented using a relational database, narrower limits will help better organize the database tables. Specification of multiplicity flushes out business rules and assumptions. The lower bound is critical, as the lower bound is what determines whether or not the relationship is optional (e.g., a lower bound of 0 indicates that the relationship is optional). Multiplicity is needed on both ends of a relationship, even if you can only navigate in one direction. Even though there is no need to navigate in that direction, the multiplicity still provides valuable business information. Sometimes navigation decisions are made for performance reasons, which may change over time. The multiplicity should reflect the requirements. Navigation is discussed on later slides. The use of ‘N’ instead of ‘*’ is Booch, not UML (e.g., the use of “0..N” and ‘N’ is not UML).