1. Overview
An analysis model for the mail order company. Review the solution to the Early Elaboration Assignment.
You will continue based upon the scenario discussed below.
1. Update your model, presenting a set of UML class relationship diagrams describing your discovered and updated classes.
-The focus of your diagrams should be on generalization and aggregation relationships. If a class does not participate in one of these kinds of relationships, it is acceptable for you to show it as a single class object in its own diagram, although you should show dependencies and labelled associations if they make your model clearer.
-Each class must be shown (in at least one diagram) with its complete set of attributes and functions as known to your model so far. All attributes and functions must be defensible from the information provided.
2. For the provided scenario, prepare a UML sequence diagram demonstrating that your model is capable of representing the actions of that use case.
-You may use reference frames to factor out long repeated sequences of actions.
Compile these deliverables into a single PDF file.
1.2 General Overview
Note: as in any real-world design, not all of the details in the problem statement will necessarily be relevant to the higher levels of this design. Furthermore, ambiguous and inconsistent language are par for the course.
2. Submitting the Assignment
UML class diagrams and UML sequence diagrams may be prepared using any of the tools listed on the course Library page or with other drawing tools that you may have available. You, not your drawing tool, are responsible for the readability and accuracy of your diagrams.
3. Scenario
Customer Order Processing
1: The mail-order facility (MOF) receives an order from customer Jones. The order is for three items.
2: After checking on warehouse stock levels, the MOF determines that the Norfolk warehouse can supply the first two items, and the Memphis warehouse can supply the third.
3: The order is divided accordingly and the packing slips for the two parts of the order are sent to the warehouses.
4: Each warehouse receives the packing slip, assembles the order, and ships it to the customer address listed on the slip.
5: The MOF prints a single invoice, which is mailed to the customer.
Alternative: Out of Stock
2: After checking on warehouse stock levels, the MOF determines that one of the three items is out of stock at all warehouses, but that the Norfolk warehouse can supply the other two items.
3: A packing slip for those two items is sent to the Norfolk warehouse, which assembles the partial order and ships it to the customer address listed on the slip.
4: A back-order slip is created for Jone's request for the remaining out-of-stock item and kept on file at the MOF.
5: The MOF prints an invoice, including notification of the back-ordered item and mails it to the customer.
4. Notes
As in any real-world design, not all of the details in the problem statement will necessarily be relevant to the higher levels of this design. Ambiguous and inconsistent language are par for the course.
What objects should appear in the diagram? Only objects that participate actively (sending or receiving messages). Objects that are simply passed as parameters may be listed as such in a particular message call, but need not have their own time line.
Pay attention to which steps are direct consequences of earlier steps. That gives you a clue as to which messages are part of the function body of an earlier call.
Remember that a message is a function call. If the scenario indicates that information is being passed, that information may be passed as a parameter to a message or as the return values from a message, but might not itself constitute a message.
If a scenario gives a specific name to an object, use that name in your sequence diagram. E.g., in the first scenario, use jones: Customer rather than the anonymous object :Customer.
Do not forget that you can use reference frames to factor out long repeated sequences of actions.
Attachment:- early laboration.rar