I'm not sure my Use Case diagram is correctly written or it needs more data? I'm creating a web application for a restaurant. You should be able to:
Add reservations
Dashboard for making orders
Dashboard for the kitchen
Dashboard for the bartender
Dashboard to edit menu.
The one who can make a class diagram for me will receive 20$ paypal.
Thanks. :)
What are these dependencies stereotyped return ? That does not exist in the norm
Is the arrow is missing or hidden for the extend ?
yes you can replace the Reservate ---<<return>>---> XX reservation by Reservate <---<<extend>>--- XX reservation but this is not very clear because when you enter a reservation you finally edit it
Seems better to have
enter do not have edit nor delete but the exception cancel
an additional UC "find reservation" having extends to delete or edit or print
You have three direct roles and one indirect
1. Client
2. Accounts
3. waiter
4. chef
Client eats food if there is drink then he drinks drink. He also places order. He also pays for food.
Accountant gets amount of food and beverages served. One for food and other for drink
Waiter receive order for food and beverages
Chef makes food and confirm order
Related
I worked on Dialogflow where I have set the context for my intent but don't know how to set the context in Alexa
user: open demo bot
alexa: welcome! How can I help you?
User: update my name
Alexa: What's your name?
User: Jason
Alexa: your name is updated as Jason, Anything else?
user: John
Alexa: your name is updated as John, Anything else?
it should give an error but it directly updates the name (John).
example 2
user: open demo bot
alexa: welcome! How can I help you? (WelcomeIntent)
user: order food
alexa: We offer item1, item2. What you would like to have? (FoodItemIntent)
user: item2
alexa: you have ordered item2, your order will be served soon. (OrderFoodIntent)
food ordering session completed here
now if user again says any food item like
user: item1
alexa: you have ordered item1, your order will be served soon. (OrderFoodIntent)
it should not directly update the ordered item it should prompt an error message like "I didn't get that, you can ask me to order food or update name"
as the food order session has been completed.
In Alexa, it currently not possible as easily as it is in Dialogflow. But you can play with the server-side, where you can simulate context.
For example, in Alexa's response/request, you will store intent history and values. Based on that you can build context on the server-side. Like when you receive intent that doesn't fit the context, you will send user reprompt to say whatever you need. For that, I recommend some general intents like text_intent which matches the text, or number_intent for numbers and so...
Or if you can put it to a different level when you somehow get what have user asked (not intent), then the sentence will be sent do dialogflow NLU API, and based on the sentence you will get context answer.
In Magento 2.2.2 I have sent shipment mails for more than 10 orders, but for some orders there is no ship option showing on top right, how can I fix the issue?
It happens in case your product does not have any weight.
When I product does not have any weight assigned it becomes a virtual product and virtual products cannot be shipped.
In my case this happened when the shipping method in the orders table did not have the correct shipping method format. It should be
shippingcarriername_shippingmethod
A credit card account (Account) can belong to multiple customers and One customer (Customer) can own multiple credit card accounts. I need to design REST API(s) which can return all accounts owned by a customer. The account number is coming from a manual input by an end user like a service rep into a freeform text box. Following is a constraint though
End consumers/developers know only account number & have no knowledge of customer id (unique identifier of a customer) upfront so to retrieve a list of accounts belonging to a customer -
1.1 find the customer owning the account in question
1.2 then find all the accounts owned by a customer.
I can think of couple of options but feel either they will make interaction chattier or may not be restful.
Only GET scenario has been discussed in below options
Option 1
Ideal way to interact with two separate resources but makes interaction very chatty and will put undue load on the system. Two calls everytime to know all accounts owned by a customer. So 20 Million calls/day in SOAP/RPC will become 40 million calls in REST.
/accounts/{account_nbr}/customers --> returns a list of customers for a specific account
/customers/{customer_id}/accounts --> returns a list of accounts for a customer
Option 2
I don't think this will be restful because query parameter is supposed to be used for identifying a resource in a non-hiearchical data
/customers/accounts?account_nbr = XXXX
Option 3
This option indicates that a list of accounts linked to account_nbr is being returned which is not right because list of accounts are linked to a customer
/accounts/{account_nbr}/linked_accounts
Option 4
Term the relationship between customer and an account as a new type of resource. Its trying to indicate get a list of customer to account relationships and identify specific instance where an account in customer_account_relationships has a value of XXXX.
/customer_account_relationships?account_nbr=XXXX or
Which of the above option, if any, is close to being restful representation? Is there any other way to design this interface?
EDIT
Expected response
{
"customerName" : "Bob",
"customerId" : 1234,
"listOfAccounts": [
{
"accountNbr" : "abcd"
"accountType": "creditcard"
},
{
"accountNbr" : "qrst"
"accountType": "creditcard"
}
]
}
You correctly rejected the first three options. I see two reasonable choices for you. One is to go with option 4:
GET /customer-summaries?account-number=<account-number>
The other is to just make /accounts top-level and do essentially the same thing:
GET /accounts?same-owner-as-account=<account-number>
In the former case, you'd get an instance of your resource above. In the second, you'd just get a list of accounts, each of which presumably has a link to the account owner. It's up to you as to which better suits your use case.
Note that option 4 may return multiple records if there are multiple owners for the same account. That's a common situation for married couples.
This is my first project which I've encountered that I can't get by on NSUserDefaults peppered with some NSCoding protocol. I've been asked to write some POS software.
Essentially, the App needs to store a bunch of products, prices and sales accounts. The user should be able to add items and accounts, and track the balance of accounts over time. The balance of an account should be able to be carried over from one "Session" (time period) to the next.
I'm comfortable with the concepts, but I'd like to be confident that I'm modeling this right. Here's how I've modeled my data. I'd like to know if I've done this properly or if there are any glaring errors/omissions.
I've created an "Account" Entity, which has the following properties:
First Name
Last Name
Account ID
Group
There is a relationship to the transaction entity.
I've created an entity for each Session. Again, a session is just like a fiscal month. The session will have a custom name and an ID.
Session ID
Session Name
There is a relationship to all of the accounts that are applied to that session.
There are of course, products, which have a name and ID. There is also a relationship to the "price" object, so I can change the prices without affecting balances.
Please see this screenshot from Xcode 4 which explains my model in its entirety:
Edit:
Looking at this, it seems that I'm missing some important info, such as dates of transactions etc. That said, am I on the right track?
It has been my experience that point of sale transactions list all the data that is necessary to recreate the receipt in three tables, a header (think date of sale, singular tracking entity), a set of records for all items being sold (linking back to the sale header), and a set of records for all the methods of payment (again linked back to the sale header).
This will give you the opportunity to rebuild the individual transactions in the future. Also, this is a simplistic model, but should suffice for what you're asking. Nominally yo uwould also keep track of applied discounts on a per-line-item basis, and per-invoice discounts, and per-group discounts, and etc.
What's the relationship between sessions and transactions?
You probably don't need to have an entity for price, as it will likely just be a float. I'd recommend adding a price attribute to your product entity instead.
I don't know if transactions will need names or not, I suppose if you want to have notes then they should.
Also transactions should probably have a to-many relationship with products.
Will this be used on a single device or will there be many users? If each user (account) is responsible for its own data then it may make more sense to have transactions/session rather than transactions/user.
I am able to read the barocode but i am confused about how to get the food product value from the barcode value .
Do we need to call a webservice or create a database locally ...
help me out
thanks in advance
Have a look at OpenFoodFacts. It's a database that does just that, with ingredients, calories, etc. It's based on the barcode.
Product bar-codes contain almost no product related information - they are mere unique identifiers. The system used in Europe - EAN13 - consists of a country code, a manufacturer code, a product code, and a check digit. To translate any of this data into usable information you need a database or web-service.
I know this was asked a long time ago but I figured I would give an update for anyone looking now... We use an API called upcFood (www.upcfood.com) They offer a simple API that allows lookup of food products directly from the barcode. upcFood includes nutrition data, Products Data, allergy data, ingredients etc. from a single search.
In case anyone else is looking for this info in 2021, you can get this data directly from the USDA's Food Data Central API, which is public domain. One of their endpoints has a query param, which supports keywords and, as a little tinkering revealed, UPCs! For instance, here's a query for a snack I had laying around:
https://api.nal.usda.gov/fdc/v1/foods/search?query=850126007120&pageSize=10&api_key=DEMO_KEY
API keys can be had with an email address. Hope this is useful to someone!
Free database here:
http://www.upcdatabase.com
and here:
http://www.yoopsie.com/
Otherwise just Google for "upc database" and you'll find people offering to sell you one.
I doubt that the databases will include prices since those are for the individual retailers to set.
I am not sure if you still need the information since it is dated a year..
A french startup has created an application that can find most of the correspondant of ean-code to food product. It provides as well an API for developper to integrate in their application.
You can check it at : http://prixing.fr/api
Since it is based in France, it is in French language .. if it is useful, I hope it can help