Stand alone version of bookstore management system of Java design module series (1)

Bookstore management system:

Project exercise objectives: 1. Basic analysis of Java application 2. Cultivate the basic idea of object-oriented programming 3. Comprehensive application of java basic design pattern 4. Master the basic design of layering and interface 5. Build a reasonable Java application package structure 6. Comprehensively apply the knowledge learned by JSE 7. Make rational use of collection framework in application 8 Comprehensively use the common components of swing in the application 9, the implementation mechanism of the basic presentation layer 10, the basic operation of IO streams and files 11, cultivate good java programming habits 12, cultivate the ability to debug Java programs and correct errors

Project functional requirements: 1. Be able to register operation users, modify basic information, delete and query. 2. It can add, delete, modify and query the basic information of books. 3. Can fill in the purchase order, a purchase order with multiple specific purchase information, and the purchased books must be existing in the library management; Modify the inventory quantity of books corresponding to inventory while purchasing. 4. Be able to fill in sales orders. A sales order contains multiple specific sales information. The books sold must be existing in the library management, and the sales quantity cannot exceed the current inventory quantity; Modify the inventory quantity of books corresponding to inventory while selling. 5. You can view the inventory details and find the inventory value of specific books according to conditions. 6. Simplify the permission and make fixed permission control. Divide users into personnel with different operation permissions according to modules, and set up an admin user to operate all functions.

Basic design of the project: ★ overall framework of architecture design, module division: five modules: user, book, purchase, sales and inventory

★ system functional structure design the specific functional sub modules of each functional module

★ implementation of database design project framework: sub module, layering, subcontracting and construction of application program

1. User management (user. Txt)

Note: the type is int type, which is used to represent the type of operation user. 1 -- denoted as admin, which can perform all operations. 2 -- denoted as the person who can operate the book module. 3 -- denoted as the person who can operate the purchase module. 4 -- denoted as the person who can operate the sales module. 5 -- denoted as the person who can operate the inventory module

2. Library management (book. Txt)

3. Purchase management (inmain. Txt)

4. Purchase details management (indetail. Txt)

5. Sales management (outmain. Txt)

6. Sales details management (outdetail. Txt)

7. Inventory management (stock. Txt)

Project subcontracting

Layer 1: divided into user module, book, in, out and store according to modules

Layer 2: it is divided into presentation layer (UI), logic layer (business) and data layer (DAO) according to the three-tier model, and a value object layer (VO) is usually added

The third layer: it is divided according to the division within the layer, depending on the specific situation. For example, business and Dao also need to use the form of iron triangle to build sub packages, while UI and VO do not need to be divided into molecular packages).

Project layering idea:

Not perfect, please continue to pay attention to this series (II)