ELEC5620-TUT-06

.pdf

School

The University of Sydney *

*We aren’t endorsed by this school

Course

5620

Subject

Electrical Engineering

Date

Oct 30, 2023

Type

pdf

Pages

Uploaded by MateCaribou3742

7he 8niversity of 6ydney 3Dge $ +,E23L+,E)*C°±²³ ´ Tutorial ±

7he 8niversity of 6ydney 3Dge % Tutorials – Use )*Case Specification – +,Example – )*Components – 56Object *+Diagram – 7Purpose – )*Components – +,Example – 56Object *+Diagram vs )*Class *+Diagram – Sequence *+Diagram – 8Qµ'(

7he 8niversity of 6ydney 3Dge & Use Case Specification '( typical use case specification should encompass elements such as name ¶ goal ¶ level ¶ precondition ¶ success condition ¶ failure condition ¶ and trigger · These components collaboratively form a comprehensive portrayal of a use case¶ aiding in the clarification of its intent¶ range¶ prerequisites¶ and anticipated results· 45Name -.Goal 23Level 7Precondition Success condition ,-Failure )*Condition Trigger Withdraw case '(llow the customer to withdraw cash from their bank account *+Detailed The customer must have a valid bank account and a sufficient balance· The requested amount is dispensed¶ and the customer¸s account balance is updated· If the customer enters an invalid 7PI45N or exceeds the withdrawal limit¶ the transaction fails¶ and no money is dispensed· The customer inserts their '(T34M card and enters the 7PI45N·

7he 8niversity of 6ydney 3Dge ' Use Case Specification – 45Name – This is the name of the use case¶ which should be a clear and concise description of what the use case represents· – +,Example¹ 45Name¹ ºWithdraw )*Cashº – -.Goal – The goal describes the purpose or objective of the use case¶ explaining what the system aims to achieve when this use case is executed· – +,Example¹ -.Goal¹ º'(llow the customer to withdraw cash from their bank account·º – 23Level – The level specifies the scope or level of detail of the use case· It can indicate whether the use case is a high´level or detailed use case· – +,Example¹ 23Level¹ º*+Detailedº

7he 8niversity of 6ydney 3Dge ( Use Case Specification – 7Precondition – This element describes the conditions or prerequisites that must be satisfied before the use case can be executed· – +,Example¹ 7Precondition¹ ºThe customer must have a valid bank account and a sufficient balance·º – Success )*Condition – The success condition outlines the expected outcome or result when the use case is successfully completed· – +,Example¹ Success )*Condition¹ ºThe requested amount is dispensed¶ and the customer¸s account balance is updated·º – ,-Failure )*Condition – The failure condition describes what happens if the use case encounters an error or fails to achieve its goal· – +,Example¹ ,-Failure )*Condition¹ ºIf the customer enters an invalid 7PI45N or exceeds the withdrawal limit¶ the transaction fails¶ and no money is dispensed·º

7he 8niversity of 6ydney 3Dge ) Use Case Specification – Trigger – The trigger indicates what initiates or triggers the use case· It can be an event or an action that starts the use case· – +,Example¹ Trigger¹ ºThe customer inserts their '(T34M card and enters the 7PI45N·º

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version