Showing posts with label Case study. Show all posts
Showing posts with label Case study. Show all posts

Thursday, January 30, 2020

Draw the system sequence diagram for process sale scenario.

https://stg-tud.github.io/eise/WS11-EiSE-11-System_Sequence_Diagrams.pdf



Draw the system sequence diagram for process sale scenario.

CASE STUDY: Retail Store Management System

Construct a design element for Point of sale terminal management system that can be used for buying and selling of goods in the retail shop.

When the customer arrives at the post check point with the items to purchase. The cashier records each item, price and adds the item information to the running sales transaction. The description and price of the current item are displayed. On completion of the item entry the cashier informs the sales total and tax to the customer. The customer chooses payment type (cash, cheque, credit or debit).After the payment is made the system generates a receipt and automatically updates the inventory. The cashier handovers the receipt to the customer.


USE Case Diagram:-


Use Case Diagram for Point Of Sale Terminal




Activity Diagram :-Sale Transaction




Class Diagram: 





State Chart Diagram



Sequence Diagram:-


Collaboration Diagram:- 


Deployment Diagram:-




Component Diagram:-

Draw the state transition diagram of Telephone Line System with proper explanation.

http://www.programsformca.com/2012/03/state-diagram-for-telephone-line.html



Draw the interaction diagram for” Renew of book use case in library system.”


Library Management System

https://www.startertutorials.com/uml/uml-diagrams-library-management-system.html



Library Management System
Read the following documents/reports to understand the problem statement, requirements and other necessary things related to the Library Management Application: Doc1, Doc2, Doc3, Doc4, Doc5, Doc6

Use case diagram

library management system use case diagram

Class diagram

library management system class diagram

Sequence diagram

library management system sequence diagram

Collaboration diagram

library management system collaboration diagram

Statechart diagram

library management system state chart diagram

Activity diagram

library management system activity diagram

Component diagram

library management system component diagram

Deployment diagram

library management system deployment diagram

Draw Class diagram for, customer order from a retail catalog. The central class is the Order. Associated with it is the Customer making the purchase and the payment. A payment is one of three kinds: Cash, Check, or Credit. The order contains Order Details (line items), each with its associated Item.

https://circle.visual-paradigm.com/class-diagram-example-sales-order-system/

Wednesday, January 15, 2020

Activity diagrams may be used for different purposes during system development process. List such purposes.



A soft drink vending machine accepts coins for a variety of products. When the amount of money deposited into the machine is equal to or greater than the price of any of its available products, the respective product selection buttons will be enabled for the user to make the selection .After the user has made a valid selection, the machine wil dispense the soft drink, together with the change (if applicable). Draw the Activity Diagram for this vending machine. State clearly about assumptions and limitations you have considered during your design. 







Algorithm Name: Vending Machine

Assumptions:
  • only dispense change in coins (5, 10, 25 cents)
  • different items could have different costs
  • users can press a button for requested item type, or to return all input money
  • there is a message window, can call "print(string)" and it will display.in LED
  • there is a "dispense(item type)" function
  • assume that machine will reject all coins except US nickel, dime, or quarter
  • it is our responsibility to update Bal and coins[C], but the machine will keep track of available[X] for us

Representation:
  • there is a counter called "Bal" that keeps track of total of coins input so far
  • cans could have different costs: cost[X]
  • available[X] is a boolean variable that indicates whether there is ³1 of X left
  • the internal reservoir of  coins is represented by coins[C] where C is 5, 10, or 25 and returns an ordinal number for how many coins of that type there are inside

Strengths
  • if machine is completely out of requested choice (or all cans), user can ask for their money back
  • algorithm is guaranteed never to give back more than the balance
  • if the user just asks for their money, back we can guarantee to always make change (at  least by using the coins they input, but not necessarily)

Limitations:
  • it is possible that this algorithm might by unable to make change, for example, in the case where a user puts in $1.00 (4 quarters), buys an item that costs $0.90, and we have no dimes or nickels to start with



Pseudocode:

if user inputs a legal coin C (e.g. 5, 10, or 25):
  coins[C] = coins[C]+1
  Bal = Bal+C
if user presses the 'return change' button:
  make_change(Bal)
  Bal = 0
if user presses button for can of type X:
  if available[X]=False:
    print("unavailable, make another choice")
  else if Bal<cost(X):
    print("insufficient funds, put in more money")
  else:
    dispense(X) // machine will update available[X]
    make_change( Bal-cost(X))
    Bal = 0

subroutine make_change(Bal):
 while Bal>0:
  if Bal>25 and coins[25]>0:
    dispense quarter
    coins[25] = coins[25]-1
    Bal = Bal-25
  else if Bal>10 and coins[10]>0:
    dispense dime
    coins[10] = coins[10]-1
    Bal = Bal-10
  else if Bal>5 and coins[5]>0:
    dispense nickel
    coins[5] = coins[5]-1
    Bal = Bal-5