Acquiring the project source files, technical exchanges and guidance Contact Q: 1225467431
One. System specification
1.1 description of the problem and significance
Dining a la carte traditional way is purely manual operation, recorded by a customer of the dish the waiter, prone to the following questions in specific work: handwritten documents scribbled causing the wrong dish, pantry sub-single serious mistake, food to eat and audit procedures more cumbersome. Handle special taste omissions and deviations, guests dishes forgotten phenomenon more frequent reminders, calculate billing error-prone and inconvenient personnel management. For this reason, online ordering patterns emerged. It not only can effectively improve the efficiency of the catering industry, but also standardized service system, improve the overall service quality and management level, and to provide a solid technical foundation for the large-scale operation.
We live in an era of information technology, online ordering can be said that the industry is bound ordering, the customer through online ordering, the ordering information to the server, then the merchant, to order the data acquired from the server through operation, after the deal, customers can get through to refresh your browser.
1.2 development environment, tools and related technologies
1.2.1MIS (Management Information System) platform
Modern enterprise MIS system platform model should be the main consideration C / S mode and B / S mode. B / S mode currently applies only to information dissemination, for online transaction processing applications are still substantial difficulties, and C / S model has accumulated a large number of applications and information. C / S (Client / Server) structure, i.e., the well-known client and server structure. It is a software system architecture, which allows you to take advantage of both ends of the hardware environment, the rational allocation of tasks to the Client side and Server side to achieve reduced communication overhead system. Most application software systems are Client / Server in the form of two-tier structure, the current system is a software application to a distributed Web applications development Web and Client / Server applications can perform the same business process, different application modules shared logic component; therefore, internal and external users can access the new and existing applications can be extended by new applications of existing application logic. This is currently the direction of development of the system.
1.2.2 Development Tools
Development tools are mainly of four parts: 64 J2EE version of Eclipse, Tomcat v7.0, Mysql database management system, google web browser.
1.3 Functional Requirements
Order management system needs to have the following functions:
( 1) Log Function: This feature includes login and logout users
( 2) registration function: This function includes new user registration information
( 3) ordering those features include: access to information and to order those who edit, obtaining food product information, order generation
( 4) business function: includes business information acquisition and editing, food product information management, order management
two. system design
2.1 overall design
Specific system function block diagram in FIG. 2-1:
Figure 2-1
2.2 detailed functional design
( 1) User login module
Ordering system using a first module, the interface comprising predominantly two text boxes, respectively, for a user name and password. Registered users can log in directly, the login process username and password does not meet the requirements, or username and password do not match, you will need to re-enter, or normal access to the main interface. No new registered users will need to go to user registration interface.
( 2) User registration module
New users (including those with a merchant to order) by their own information fill in a text box, by registering detected, users have to re-register the same name, the same name as the user can not successfully registered. You can go to the login screen after successful registration.
( 3) s meal interface module
Ordering those successful login can visit the shop list screen, select a shop, see a list of foods to change the shop, by selecting the type and amount of food, after selection, fill in delivery time, place, notes. To generate orders, waiting for the merchant to confirm.
( 4) User interface module
Login successful business can go to his shop interface to view and edit their own food list to see their own order management shop.
( 5) individual central module
Users can log on successfully manage and update their information
( 6) Logout module
I want to log out to end users through its own logout session.
2.3 User Interface Design
By ordering the login screen shown in Figure 2-2
Figure 2-2
Store List interface shown in Figure 2-3
Figure 2-3
Food list interface shown in Figure 2-4
Figure 2-4
FIG personal Center Interface 2-5
Figure 2-5
2.4 Design of data with the data table
This database has a total of four tables:
Users who are divided into meal table with the business table,
( 1) s meal table (buyuser) including user name (bId), password (password), nickname (bname), phone number (cellphone), gender (sex);
( 2) the merchant table (selluser) including user name (sId), password (password), nickname (sname), phone number (cellphone), store name (storename), store address (storeaddress), picture (simage), gender ( sex);
( 3) food table (food) including food number (fId), food name (fname), food prices (price), food pictures (fimage), merchant name (sId);
( 4) Orders table (ordered) including order number (oId), ordering username (bId), merchant user name (sId), food list (fIds), the number of list (numbers), delivery time (sendtime), send meal address (sendaddress), notes (markup), state (state);
Detailed table is as follows:
( 1) s meal table (buyuser) Table 2-1
S meal table ( buyuser) Table 2-1
( 2) Business table (selluser) Table 2-2
Merchant table ( selluser) Table 2-2
( 3) Food table (food) as shown in Table 2-3
Food table ( Food) Table 2-3
( 4) Orders table (ordered) Table 2-4
Orders table ( ordered) Table 2-4
three. System test
It is divided into two parts: those who test meal, business test
3.1 ordering those tests
( 1) run the program, to enter the login screen, as shown in FIG 3-1
Figure 3-1
( 2) the new user registration shown in FIG 3-2
Figure 3-2
( 3) successful login the main interface as shown in FIG 3-3
Figure 3-3
( 4) post-click interface shown in Figure 3-4 food shop
Figure 3-4
( 5) After choosing the type and quantity of food to enter the order confirmation screen shown in Figure 3-5
Figure 3-5
( 6) into the center of FIG personal 3-6
Figure 3-6
( After 7) Click to view order details in Figure 3-7:
Figure 3-7
( 8) Click logout back to the login screen shown in Figure 3-8
Figure 3-8
3.2 Test Merchant
( 1) login screen shown in Figure 3-9
Figure 3-9
( 2) Register interface shown in Figure 3-10
Figure 3-10
( 3) after a successful login interface shown in Figure 3-11 Home
Figure 3-11
( 4) into the center of the individual shown in Figure 3-12
Figure 3-12
( 5) Click to view order details and operation of the order shown in Figure 3-13:
Figure 3-13
( 6) After the successful operation state to receive 3-14 in FIG.
Figure 3-14
( 7) Click logout back to the login screen shown in Figure 3-15
Figure 3-15
four. Experimental experience
4.1 Design features
The design of the interface is simple, practical function, easy to operate, can achieve the basic functions ordering system.
4.2 Design inadequate
This design also does not implement features such as real-time order update time, positioning ordering persons. There is the appearance of the interface, due to the lack of knowledge of art terms, so do not come are not particularly beautiful.
4.3 Harvesting and experience
Through this project development, I use have a dynamic web platform development project javaee some knowledge, but also to review the database of knowledge, a better understanding of mysql, the course of the experiment, the error is constantly through continuous debugging debug , a section of the code test investigation, and ultimately eliminate the error, completed the project.