3. Statement of the problem. Defining the modeling workspace

The shop sells children's and adult clothes and shoes of various brands. Buyer browses the catalog and makes an order. We assume that a potential customer enters the store site, he can click the browse (or download) button of the catalog, then he can put the item he likes in the cart, change the cart and, having decided to buy goods, go from the cart to checkout.

In order to correctly create a system that meets all customer requirements, we must absolutely clearly imagine its main business functions and find out the requirements for the system. To do this, it is necessary to conduct a survey of the company and build its full business model. Since our example is invented, we cannot conduct such a survey and cannot communicate with the customer, we will rely on the verbal description of the system we have invented.

3.1 Description of the system

Each product in the catalog is described by article number, size range, price and photo with a brief description. The buyer can download the catalog of goods. The catalog does not contain sections, has a block structure, consists of a set of products with photos, price in size. The buyer puts the favorite products in the basket, while choosing the size and quantity of the necessary goods of this article. You can change the cart: view, delete the item, change the number of items of one article, return to the catalog. When a customer places an order, he enters his personal data, phone He pays for it by credit card (if the order is not paid, then it is not made). After the order is made, it can be picked up from the warehouse after 1 business day. The order data is received by the store employee, let's call it the sales employee, he checks the availability of goods and sends it to the stockman for a complete set. The storekeeper, having collected the order, makes a mark of readiness. The order is issued from the warehouse by the stockman. The storekeeper issues an order and notes in the system that the order has been issued. The shop does not deliver orders, does not make discounts. For To limit the scope of the task, we do not consider the store's supply system with new goods. This is done by another system, let's call it Warehouse. Information about the goods sold (i.e. orders made) also goes to the Warehouse system. Since it goes through different stages from creation to issuing an order, it will be reasonable to introduce the concept of order status. Store employees can change the status of the order, and the buyer can follow the assembly order. In this case, our system provides another function: to know the status of the order.

3.2 Creating a project

Let's create a new project in StarUML by selecting Rational Approach from the list of suggested approaches. Our model will have four representations: Use Case, Logical, Component and Deployment. In our opinion, this approach to the structure of representations most closely matches the Rational Unified Procces (RUP) methodology, which supports the iterative process of developing information systems. Details on this methodology can be found in [2] and [4]. This manual does not pretend to fully comply with the RUP stages: the purpose of modeling our system is to become familiar with the UML notation and to study methods of work in the CASE-StarUML design and modeling tool. We choose the approach Rational Approach for the convenience of further work. Save the project you created under any name.