Hybris: difference between promotion and voucher - sap-commerce-cloud

I am working on POC on promotions and vouchers. I was going through hybris documentations at most all kind of discounts are covered in promotion Engine.
I also noticed we have coupon promotion too. Having said this, in which case we will chose over vouchers?
It would be great if you can explain me with a example.
Promotion: https://help.hybris.com/1811/hcd/6badeeed32a546689404b9897f8d54ee.html
Voucher:
https://help.hybris.com/1811/hcd/8c7fc4e886691014b2ace5fe565624a1.html

Broadly speaking,
Promotions are implicit. The customer has no control over it. If the order qualifies for a promotion then it would definitely be applied.
Vouchers are explicitly applied. The customer is given a voucher number. If and only if the customer enters the voucher number during the checkout process, the voucher will be applied.

Related

Correct usage of includes and extends in use case diagram

I am creating a use case diagram for a barber shop system. I am not sure if the Add Product Inventory use case should include the Purchase Product use case.
The actors which will interact with the barber shop system are:
Customers
System users (ie. Barber)
System Administrator (ie. Manager)
All users will need to be able to login in, customers will need to register if they are a first time user.
The customer will interact with the system to make a booking or purchase a product i.e gel, shampoo, wax. A booking can extend to cancelling the appointment, it is unlikely for the customer to be able to reschedule the appointment but rather cancel the appointment and book again at a different time.
The system user, the barbers, need to be able to view the timetable of appointments, view customer contact details and login to the system.
The system admin, who is likely a manager and head barber, should also be able to view the timetable of appointments, view customer contact details and add a product inventory to the store. The product inventory will also include setting product specification, the colour or size of product, and setting the price.
I am not sure if the Add Product Inventory use case should include the Purchase Product use case.
This is not the case, else that means each time a product is added in the inventory it is also purchased during that add. Note also the actors are not the same for these two use cases, but having the include that means the purchase is also done by the admin.
There is no extend too.
The fact a product was added in the inventory before to be purchased is a precondition you put in the description of the UC Purchase.
There are other problems in your diagram :
all your extends are drawn in the wrong direction, except may be between Login and Register depending on what you wanted to say
it is common to put the secondary actors on the right, so Customer seems to be a secondary actor but this is not the case.
Admin and Barber cannot Login (but they can logout), to have one of these roles a real person needed to successfully login before and that is done with an actor Guest or something like that.
in the same way a Customer cannot Register (nor Login)
But in fact Login and Register (and logout) are very common and simple features and probably do not have enough plus value to be use cases.
A Customer can cancel an appointment only during its creation, this is not what you want.
you need to allow Customer to activate Cancel Appointment in an other way (directly or as an extension of the probable View Own Appointments, see after)
for me while an appointment is under construction it does not exist and then the Customer cannot cancel the appointment, but the customer can abort the construction. So for me there is no extend between these use cases. Of course in the description of Make Appointment you can say an abort is possible, but I think this is the case in all the UC.
Very probably a Customer can view his/her appointments so an UC (let say View Own appointments) must be added. Note this is not like the UC View Appointmenst a Barber can activate, so these UCs must not have the same name. To have Cancel Appointment as an extend of this new UC seems a good way and in that case Cancel Appointment cannot be directly activated by Customer.
Some UCs an Admin can activate are missing, to modify the price of a product, to remove a product, to modify a barber details, to remove a barber, ...
I'm not familiar with the business rules in your scenario, so this is a little bit of guess-work and a few assumptions which you can verify.
I assume the 'Add Product Inventory' Use Case is about adding products to an inventory of all products. For our purposes to answer your question, I don't think it matters whether this Use Case relates to adding one product, multiple products, managing products (e.g. editing or removing them), whether the inventory already exists or not, or if the Inventory is a separate thing to the Products on it, but answers to those questions are not 100% clear from your model and you may consider clarifying those points.
I also assume that a Product needs to be on the Inventory in order that it can be Purchased. If that is the case, then I think what you are asking is about this very point -- how do I represent the fact that the Product needs to be Added to the Inventory before it can be Purchased? If that is what you're asking, then you can represent that using a simple 'dependency' relationship which would run from the Purchase Product Use Case to the Add Product Inventory Use Case as per below. This states that the Product Purchase is somehow dependent on Add Product, but does not go further in explaining that relationship. Alternatively, you could use a preceedes relationship running instead from the Add to the Purchase. I don't think extend is the correct relationship -- the steps of Add Product don't need to be factored in every time you Purchase Product, the dependency is on the objective of Add Product having first been achieved, not the steps.

Which type of relationship should I use?

I'm currently attending a class on UML diagrams where there are lab exercise which we need to complete.
In lab exercise, there are various data class in regards to the topic Supermarket. One of the data class is called Receipt which include attributes like id, payment datetime, purchased items and total price. There is also another data class called Payment which include a payment type attribute, Payment data class is "linked" to Receipt data class, however I'm not sure which relationship to use.
The full question paragraph is as follow:
Shopper arrives at checkout counter.
The total price is calculated and the shopper is given an receipt which includes a list of purchased items.
Payment is recorded when it occurs, either now (cash) or later (card payment).
Assuming that you make a class diagram:
The "link" is a simple association, since nothing in the wording suggests composition or aggregation.
"Payment is recorded when it occurs, either now or later" means that it is possible at some moment in time that there is no payment (yet) for a payment.
"either now (cash) or later (card payment)" strongly suggests that a receipt is paid with a single payment (multiple partial payments are not excluded by the wording, but it seems improbable).
so the multiplicity is 0..1 payments for a receipt.
Nothing is said about the multiplicity of receipts for a payment. We can imagine that there is a minimum of 1, since nobody would make a payment for nothing. But it cannot be excluded that a payment with a credit card is made for paying several unpaid receipts at once. I would therefore prudently let it unspecified in the diagram. In the real world, this is something that you would verify with your customer. In your exercise, depending of the practice you've witnessed from the professor, you may want to put a 1.
So here the simplified diagram (I haven't shown properties and operations for the sake of simplicity, nor the items which you dodn't mention as a problem):

UML: Use Case Diagram

I need to create USE Case for the following component.
Manage Consultant
Use cases--add consultant, update consultant, add speciality, update speciality Consultants and specialities are either active or inactive.
Speciality is a stand alone class
Speciality is also part of Consultant class
2nd Component
Confirm appointment--consultant views appointments and confirms times. Firm appointment is saved and customer gets email confirming time.
Confirm Invoice--consultant views invoices and, if an invoice has been paid, marks as paid.
Am I right?
From my understanding USE Case does not show the detailed list steps with in the USE Case. So mark paid you don't don't ned to be shown.
For your first diagram: do not use generalization with UCs. Each UC represents a unique single added value for the actor. If there were such a thing as a generalized added value that would never be unique. Remember: there's just a unique selling point, never a general one. Just remove the Manage-UCs and connect the "real ones" directly.
Your 2nd diagram looks fine to me.

Any mistakes or improvements to my use case diagram

Here's the question:
CarHere is a national car rental company that provides low cost car rental extensively in the British Isles. Their cars are available through their rental offices located at all main airports and some central city locations. They currently have a poorly performing computerised system that is to be replaced. A team has now been commissioned to start the development work.
When a potential customer requests a rental from CarHere company the booking clerk takes the rental requirements that include the pick-up and drop-off times and places, the class of vehicle and any special needs. A booking will be made once the details are agreed. All bookings are provisional until confirmed by the customer before the given confirmation date
.
For each booking, the booking clerk will record the details of the customer and any other drivers they nominate: title, first name, surname, telephone, address, licence number and class of car to be rented and any special features. Once the customer pays the full amount the clerk will record the payment details: payment date, payment method and amount. The clerk then updates the bookings as “confirmed” and issues a rental document to be signed by the customer. Payments can be made by credit/debit card or in cash. Confirmed bookings may be cancelled no later than three days prior to pick-up; the payment is reimbursed, less a charge of 10%.
Every morning a list of provisional bookings that are overdue and a list of all cancellations for confirmed bookings are produced. Provisional bookings are then cancelled and customer is reimbursed.
Here's my diagram:
Is there anything I can do to improve the diagram?
First, you want to understand that included use cases are required and extensions are optional. "Add payment record" doesn't look optional, and neither do the extensions to "Get rental requirements." So, if you're not clear on this, you'll want to revise your extends and includes accordingly.
Next, don't try to fully explain the behavior of a use case in terms of other use cases it includes. If your included use cases are really part of the base use case, then leave them out. There are other ways of documenting the behavior as I will explain.
Next, if you have different ways of accepting payment, you might want to have each as a separate use case that inherits the "Pay" use case.
Finally, to fully explain the behavior of a use case, use an activity diagram, one per use case. You can go into whatever detail you want there. You may also want to google "use case narrative" to see ways that you can verbally document the behavior of a use case; this narrative is what an activity diagram would depict. If you have a particularly complex path through a use case, look up "use case scenario" and how to document one with a sequence diagram.

UML assignment question

Sorry, I know this is a very lame question to ask and not of any use to anyone else. I have an assignment in UML due tomorrow and I don't even know the basics (all-nighter ahead!). I'm not looking for a walkthrough, I simply want your opinion on something. The assignment is as follows (you only need to skim over it!):
=============
Gourmet Surprise (GS) is a small catering firm with five employees. During a typical weekend, GS caters fifteen events with twenty to fifty people each. The business has grown rapidly over the past year and the owner wants to install a new computer system for managing the ordering and buying process. GS has a set of ten standard menus. When potential customers call, the receptionist describes the menus to them. If the customer decides to book an event (dinner, lunch, picnic, finger food etc.), the receptionist records the customer information (e.g., name, address, phone number, etc.) and the information about the event (e.g., place, date, time, which one of the standard menus, total price) on a contract. The customer is then faxed a copy of the contract and must sign and return it along with a deposit (often a credit card or by check) before the event is officially booked. The remaining money is collected when the catering is delivered. Sometimes, the customer wants something special (e.g., birthday cake). In this case, the receptionist takes the information and gives it to the owner who determines the cost; the receptionist then calls the customer back with the price information. Sometimes the customer accepts the price, other times, the customer requests some changes that have to go back to the owner for a new cost estimate. Each week, the owner looks through the events scheduled for that weekend and orders the supplies (e.g., plates) and food (e.g., bread, chicken) needed to make them. The owner would like to use the system for marketing as well. It should be able to track how customers learned about GS, and identify repeat customers, so that GS can mail special offers to them. The owner also wants to track the events on which GS sent a contract, but the customer never signed the contract and actually booked a GS.
Exercise:
Create an activity diagram and a use case model (complete with a set of detail use case descriptions) for the above system. Produce an initial domain model (class diagram) based on these descriptions.
Elaborate the use cases into sequence diagrams, and include any state diagrams necessary. Finally use the information from these dynamic models to expand the domain model into a full application model.
=============
In your opinion, do you think this question is asking me to come up with a package for an online ordering system to replace the system described above, or to create UML diagrams that facilitate the existing telephone-based system?
Create an activity diagram and a use case model (complete with a set of detail use case descriptions) for the above system.
I think it's right there in the text: they want you to document the system described.
Best of luck!

Resources