032 Business Acceptance Module requirements analysis and database design-BOS

First, business acceptance module requirements analysis

The whole BOS project is divided into basic settings, pick-up, transit, routing, reports and so on.
Acceptance link, is the beginning of the logistics company's business, as the front end of the service, the customer through the telephone, network and other means of commissioned, business, through communication with customers, access to customer service requirements and specific information, the service instructions to enter our service system.

The customer through the telephone way carries on the logistics entrust, the logistics company's customer service personnel needs to enter the entrust information into the BOS system, this input information is called the business notice.
When the customer service personnel will enter the business notice information into the system, the system will automatically match the customer's address to a pick-up, and for this pick-up staff to generate a task, this task is called work orders.
Pick-up after receiving the task, will go to the customer address to pick up the goods, the dispatch will allow customers to fill out a paper list (sender information, recipient information, etc.), to send the goods back to the logistics company outlets, need to put the paper on the list of information into the BOS system, the input information called work orders.

Second, the Business Acceptance module database design

/*==============================================================*/
/* DBMS Name:mysql 5.0 */
/* Created ON:2017/8/19 13:27:42 */
/*==============================================================*/

drop table if exists Qp_noticebill;

drop table if exists Qp_workbill;

drop table if exists qp_workordermanage;

/*==============================================================*/
/* Table:qp_noticebill */
/*==============================================================*/
CREATE TABLE Qp_noticebill
(
ID varchar (+) NOT NULL,
staff_id varchar (32),
customer_id varchar (32),
Customer_name varchar (20),
Delegater varchar (20),
Telephone varchar (20),
Pickaddress varchar (200),
arrivecity varchar (20),
Product varchar (20),
Pickdate date,
Num INT,
Weight Double,
Volume varchar (20),
Remark varchar (255),
OrderType varchar (20),
user_id varchar (32),
Primary KEY (ID)
);

/*==============================================================*/
/* Table:qp_workbill */
/*========== ====================================================*/
CREATE TABLE Qp_workbill
(
ID varchar (+) NOT NULL,
noticebill_id varchar (+),
type varchar (a),
Pickstate varchar (),
Buildtime timestamp,
Attachbilltimes int,
Remark varchar (255),
staff_id varchar (+),
Primary key (ID)
);

/*==============================================================*/
/* Table:qp_workordermanage */
/*==============================================================*/
CREATE TABLE Qp_workordermanage
(
ID varchar (+) NOT NULL,
arrivecity varchar (20),
Product varchar (20),
Num INT,
Weight Double,
FLOADREQR varchar (255),
Prodtimelimit varchar (40),
Prodtype varchar (40),
SenderName varchar (20),
Senderphone varchar (20),
SENDERADDR varchar (200),
Receivername varchar (20),
Receiverphone varchar (20),
RECEIVERADDR varchar (200),
Feeitemnum int,
Actlweit Double,
Vol varchar (20),
Managercheck varchar (1),
UpdateTime date,
Primary KEY (ID)
);

ALTER TABLE Qp_noticebill add constraint fk_reference_2 foreign key (USER_ID)
References T_user (ID) on the delete restrict on update restrict;

ALTER TABLE Qp_noticebill add constraint fk_reference_3 foreign key (staff_id)
References Bc_staff (ID) on the delete restrict on update restrict;

ALTER TABLE Qp_workbill add constraint fk_reference_4 foreign key (staff_id)
References Bc_staff (ID) on the delete restrict on update restrict;

ALTER TABLE Qp_workbill add constraint FK_WORKBILL_NOTICEBILL_FK foreign key (noticebill_id)
References Qp_noticebill (ID) on the delete restrict on update restrict;

Iii. implementing hibernate reverse Engineering building entities

032 Business Acceptance Module requirements analysis and database design-BOS