Rabu, 23 Oktober 2013
Kamis, 17 Oktober 2013
Usecase
1.1 Actor
Basically the actor is not a part of the use case diagram , but to be able tothe creation of a use case diagram needed some actor . the Actorpresenting someone or something ( such as devices , other systems ) that interactwith the system . An actor may only provide information on the system input ,only receive information from the system or both receiving and giving informationon the system . Actors only interact with the use case , but does not have control overuse case . Actor illustrated with stick man . Actor can be described asgeneral or specific , which we can use to distinguish relationship.
1.2 Use Case
Use case is a description of the functionality of a system , so that the customer orsystem users know and understand about the usefulness of the system to be built .Note : Use case diagram is a depiction of the system from the user pointThe system ( user ) , thus making the use case is more focused onexisting functionality in the system , not based on the flow or sequence of events .How to determine a Use Case in the system :
a. Behavior patterns of software applications .
b . Job description of an actor .
c . Systems or " objects " which gives something of value to the actor .
d . What is done by the software ( * not how todo it ) .
Making Use Cases :
1 . Use Cases View right-click on the browser .
2 . On the menu select New option : Use Case . A Use Case is placed on the browser .
3 . Click the Use Case , and enter the desired name .
a. Behavior patterns of software applications .
b . Job description of an actor .
c . Systems or " objects " which gives something of value to the actor .
d . What is done by the software ( * not how todo it ) .
Making Use Cases :
1 . Use Cases View right-click on the browser .
2 . On the menu select New option : Use Case . A Use Case is placed on the browser .
3 . Click the Use Case , and enter the desired name .
1.3 Relationship in Use Case
There are some relationships that are in use case diagram :
1 . Association, the connecting link between the elements .
2 . Generalization , also called inheritance ( inheritance ) , an element can bespecialization of the other elements .
3 . Dependency , an element depends in some way to every other element .
4 . Aggregation , Association forms in which an element contains other elements .
1 . Association, the connecting link between the elements .
2 . Generalization , also called inheritance ( inheritance ) , an element can bespecialization of the other elements .
3 . Dependency , an element depends in some way to every other element .
4 . Aggregation , Association forms in which an element contains other elements .
1.4 Use Case Diagram
Is a graphical depiction of some or all of the actors , use cases , and interactionsuch a system is introduced .Creating Main Use Case Diagram
1 . Right click on the Main diagram Use Case View in the browser to open the diagram .
2 . Click and drag the actor in the actor browser into the diagram .
3 . Repeat step 2 to add the necessary actor in the diagram .
4 . Click to select a use case in the browser and drag it into the diagram use case .
5 . Repeat step 4 to add the required use case in the diagram .Note : actor and use case can also be created directly within a use casediagram by using the toolbar .Use Case diagram is useful in three ways :• Describe the existing facilities ( requirements) . New Use Case always produce new facility when the system is analyzed , and the design became more apparent .• Communication with clients . Use notation and symbols in Use Case diagrams make it easier to communicate with developers klienkliennya .• Create a test of general cases . A collection of events for the Use Case can do a decent test cases for these events .
1 . Right click on the Main diagram Use Case View in the browser to open the diagram .
2 . Click and drag the actor in the actor browser into the diagram .
3 . Repeat step 2 to add the necessary actor in the diagram .
4 . Click to select a use case in the browser and drag it into the diagram use case .
5 . Repeat step 4 to add the required use case in the diagram .Note : actor and use case can also be created directly within a use casediagram by using the toolbar .Use Case diagram is useful in three ways :• Describe the existing facilities ( requirements) . New Use Case always produce new facility when the system is analyzed , and the design became more apparent .• Communication with clients . Use notation and symbols in Use Case diagrams make it easier to communicate with developers klienkliennya .• Create a test of general cases . A collection of events for the Use Case can do a decent test cases for these events .
Here is how to draw a use-case diagram :Note :We create a use-case diagram , begins with a first FDD . This is just to help identify the processes in the system .
1 ) Start by registering actor associated with the Use - case , both the sender and receiver .
2 ) The components in a use - case diagram is a Use - Case Name , Description Use - case and participating actors and roles .
3 ) Find demonstrating dependency semantic relations between two Use - case . If the Use - case " A " change can result in Use -case " B " will change as well .There are 2 kinds of dependencies that need to be considered which include and extend.Dependency include :A Use - case be able to include other functionality Use -cases as part of the process in itself . It is generally assumed that the Use - case that will be called whenever include Use -case - clicking executed normally include . A Use - case can be include by more than one other Use - case , so that duplication of functionality can be avoided by pulling out the common functionality .
SOURCE : drw.politekniktelkom.ac.id / ... / MODUL_1_UML.pdf
Langganan:
Komentar (Atom)