A customer calls a sales parson in a company to order a product. The sales person fills out an order form and gives it to a warehouse clerk to package the orders and arrange their shipping to the customer via truck or train according to customer’s wish. The system needs to support adding new orders, modifying existing orders, packaging orders, checking current inventory levels, and restocking the inventory. When a new order is added, the system would need to notify the accounting system so that an invoice could be generated. You are required to perform the following tasks using a proper UML tool: 1. Create a use case diagram for this problem. 2. Describe the core use cases (scenarios) textually. . 3. Create a complete class diagram (including attributes, operations, relationships (association, dependency, aggregation, inheritance), multiplicities, etc. 4. Select one main use case (scenario) and create a sequence diagram that describes it. 5. Select another use case (scenario) and create an activity diagram that models the scenario. 6. Create an architectural model (using package/component diagram) showing the architectural layers of the system. 7. Create a deployment diagram to map the software components/layers to physical nodes (computers) 8. Create a mapping between the class diagram (created in step 3) and the corresponding ER-Model (database model).
A customer calls a sales parson in a company to order a product. The sales person fills out an order form and
gives it to a warehouse clerk to package the orders and arrange their shipping to the customer via truck or train
according to customer’s wish.
The system needs to support adding new orders, modifying existing orders, packaging orders, checking current
inventory levels, and restocking the inventory.
When a new order is added, the system would need to notify the accounting system so that an invoice could be
generated.
You are required to perform the following tasks using a proper UML tool:
1. Create a use case diagram for this problem.
2. Describe the core use cases (scenarios) textually. .
3. Create a complete class diagram (including attributes, operations, relationships (association,
dependency, aggregation, inheritance), multiplicities, etc.
4. Select one main use case (scenario) and create a sequence diagram that describes it.
5. Select another use case (scenario) and create an activity diagram that models the scenario.
6. Create an architectural model (using package/component diagram) showing the architectural layers of
the system.
7. Create a deployment diagram to map the software components/layers to physical nodes (computers)
8. Create a mapping between the class diagram (created in step 3) and the corresponding ER-Model
(
Step by step
Solved in 3 steps
