Izdelava UMLdiagramov v MS Visio peterbaloh'net

1
Izdelava UML-diagramov v MS Visiopeter_at_baloh.ne
t
2
Kaj bomo poceli?Requirements development

• Za izbrani proces Posnetek stanja in novo stanje
• Diagram primerov uporabe (Use Case)
• Sekvencni diagrami (Sequence Diagram)
• Diagrami razredov (Class Diagrams)
• Diagrami aktivnosti (Activity Diagrams)

3
Kaj bomo poceli?Requirements development

• Za izbrani proces Posnetek stanja in novo stanje
• Diagram primerov uporabe (Use Case)
• Sekvencni diagrami (Sequence Diagram)
• Diagrami razredov (Class Diagrams)
• Diagrami aktivnosti (Activity Diagrams)

4
Requirements developmentUse Case Diagram
Primerov uporabe
Kako akter uporablja razlicne dele inf sistema

• Opis problema
• Diagram Primerov uporabe
• Identificiranje akterjev
• Primeri uporabe (opis vsakega
  posameznega sklopa aktivnosti)
• Diagram primerov uporabe (slika vseh
  primerov uporabe)

5
Requirements developmentUse Case (Primer
uporabe) - akterji
Kakna je interakcija IS in uporabnika v
doloceni situaciji

• Akterji
• Who will put the information into the system?
• Who will use this information?
• Who will be interested in this particular task?
• Who will this task benefit?
• Where is the system going to be used and who will
  be the people located there?
• Who will edit and delete this information?

6
Requirements developmentUse Case (Primer
uporabe) - akterji
Kakna je interakcija IS in uporabnika v
doloceni situaciji

• When interviewing a user, here are some of the
  key questions you want answered
• What roles does the user play and what does the
  user do in each of these roles?
• Does the user play more than one role in the
  system?
• Does the user create, edit, delete, or save any
  information in the system?
• What type of information does the user require to
  perform their task?
• What are possible things that the user can do
  that are incorrect tasks?

7
Requirements developmentUse Case (Primer
uporabe) - opis
Kakna je interakcija IS in uporabnika v
doloceni situaciji

• The Actor Creates an Order
• The actor receives the phone call from a customer
• The actor is asked by the customer to place an
  order
• The actor retrieves the name and address from the
  customer
• The actor enters the name in the system
• The actor checks whether the customer's personal
  information is correct
• If the information is correct, the actor requests
  the order information
• The actor retrieves the product names and
  quantities from the customer
• The actor selects a product category
• The actor selects the products
• The actor types a quantity for each product
• The actor selects a shipper
• The actor confirms with the customer that all the
  information is correct
• The actor completes the Order Details
• The actor saves the order to the database

8
Requirements developmentUse Case (1) Primer
uporabe
Kakna je interakcija IS in uporabnika v
doloceni situaciji

• Create new customer
• Overview
• The main purpose of this use case is to create a
  new customer
• Primary Actor
• Sales Representative
• Secondary Actor
• None
• Starting point
• This use case starts when the actor requests to
  create a new customer.
• Ending Point
• The actor's request to create a customer is
  eithercompleted or canceled.

9
Requirements developmentUse Case (2) Primer
uporabe
Kakna je interakcija IS in uporabnika v
doloceni situaciji

• Measurable Result
• A customer is added to the system.
• Flow of Events
• The actor is prompted to enter information that
  defines the customer (name, address, contact,
  etc.) The actor can choose to save the
  information or to cancel the operation. If the
  actor decides to save the information the new
  customer is created in the system, and the list
  of customers that was presented earlier is
  updated.
• Alternative Flow of Events
• The actor attempts to add a customer that already
  exists. The system will notify the user and
  cancel the operation. The actor enters an
  improper value for one of the fields. The system
  will not allow the update until a proper value
  for the field is entered.
• Use Case Extensions
• None

10
Requirements developmentUse Case (2) Diagram
primerov uporabe
Kako akter uporablja razlicne dele inf sistema

• Primer uporabe
• Akter
• Povezave

11
Requirements developmentUse Case (3) Diagram
primerov uporabe
Kaj se dogaja v nekem (ne informacijskem)
sistemu
12
Requirements developmentUse Case (3) Diagram
primerov uporabe
Kako akter uporablja razlicne dele inf sistema
13
Kaj bomo poceli?Requirements development

• Za izbrani proces Posnetek stanja in novo stanje
• Diagram primerov uporabe (Use Case)
• Sekvencni diagrami (Sequence Diagram)
• Diagrami razredov (Class Diagrams)
• Diagrami aktivnosti (Activity Diagrams)

14
Requirements developmentSequence Diagram
Sekvencni diagram
Interakcija med akterji in komponentami
sistema Predstavlja vse mone dogodke primera
uporabe

• Akter
• Objekti (entitete)
• Obvestila (tokovi podatkov)
• Za vsak Primer uporabe naredimo en sekvencni
  diagram.

15
Kaj bomo poceli?Requirements development

• Za izbrani proces Posnetek stanja in novo stanje
• Diagram primerov uporabe (Use Case)
• Sekvencni diagrami (Sequence Diagram)
• Diagrami razredov (Class Diagrams)
• Diagrami aktivnosti (Activity Diagrams)

16
Requirements developmentClass Diagram
Podroben graficni prikaz staticne slike sistema.

• Prikazuje strukturo sistema
• Razrede
• Odnose med razredi

17
Kaj bomo poceli?Requirements development

• Za izbrani proces Posnetek stanja in novo stanje
• Diagram primerov uporabe (Use Case)
• Sekvencni diagrami (Sequence Diagram)
• Diagrami razredov (Class Diagrams)
• Diagrami aktivnosti (Activity Diagrams)

18
Requirements developmentActivity Diagram
Za modeliranje poslovnega procesa in poslovne
logike.

• Ekvivalent diagramom poteka (flow-chart),
  diagramom tokov podatkov (DFD).
• Modeliramo vsak primer uporabe (use case) ali
  poslovno pravilo (business rule).

19
Requirements developmentActivity Diagram

• The initial state
• An action state a type of state that represents
  a completed activity.
• A transition from an action state occurs when the
  action is completed. A relationship between two
  states.
• To indicate concurrent activities that must be
  completed before the next activity can occur, use
  a join transition.
• Guard a condition that specifies when an event
  can take place.
• To indicate activities that can occur in
  parallel, use a fork transition.
• The final state represents the completion of
  activity in the situation.