Java------Stand-alone bookstore management system (design ideas and Design Patterns series I) overview

Bookstore Management System

The bookstore management system can be said to be a more classic example of design patterns and design ideas.

This series will be divided into several sections on this transmission management system.

Bookstore management system will be divided into: Users, books, purchase, sales and inventory of five modules, in addition to public packages, toolkits and login packages, there is a framework.

For layered design, it is the presentation layer can call the logical layer, the logical layer calls the data layer, the data layer calls the tool and the public package, the direction cannot be disturbed, must strictly follow this pattern.

This article will be a first introduction to this system.

Project Practice Objectives

1. Basic analysis of Java application
2. Cultivating the basic idea of object-oriented programming
3, Java basic design mode comprehensive application
4. Master the basic design of layering and interface
5. Construct a reasonable Java application package structure
6, comprehensive application of JSE learning knowledge
7. Use the set frame rationally in the application
8. Use the general components of swing in the application
9. Realization mechanism of basic presentation layer
10. Basic operation of IO stream and file
11. Develop good Java programming habits
12, training the ability to debug Java programs, training the ability to change the wrong

Project function requirements

1, can operate the user's registration, modify the basic information, delete and query.
2, can add to the basic information of books, delete, modify and query operation.
3, can fill in the purchase order, a purchase order with a number of specific incoming information, the purchase of books must be in the book management has already had, and the purchase of inventory corresponding to the stock of books.
4, can fill out a sales order, a sales order with a number of specific sales information, sales of books must be in the book management has already had, and the number of sales can not exceed the current inventory quantity, sales of the same time to modify inventory corresponding books inventory volume.
5, you can view the inventory details, you can follow the conditions to find the specific inventory value of the book.
6, the permission to simplify, do a fixed permission control. The user according to the module into different operating rights of the personnel, a special Admin user, you can operate all the functions.

Project Basic Design

★ Architecture Design

Overall framework, module division

Module Division: 5 Modules for users, books, purchase, Sales and inventory

★ System Function Structure Design

Specific functional sub-modules for each function module

Database Design (Use a. txt file instead of a database)

Project Framework Implementation: Sub-modules, tiering, subcontracting, building applications

1. User Management (User.txt)

Field name and order

Description: The type of which is of type int and is used to represent the types of the operation user.

As the admin, you can do all the work
2--as a person who can operate a library module
3--represents the person who can operate the incoming module
4--represents the person who can operate the sales module
5--represents the person who can operate the Inventory module

2. Book Management (Book.txt)

Field name and order

3. Stock Management (InMain.txt)

Field name and order

4, Purchase details management (InDetail.txt)

Field name and order

5. Sales Management (OutMain.txt)

Field name and order

6. Sales Detail Management (OutDetail.txt)

Field name and order

7. Inventory Management (Stock.txt)

Field name and order

Subcontracting of projects

First layer: According to the module sub-

User module, book, Purchase (in), Sales (out), Inventory (store)

Second layer: According to the three-layer mode

Presentation layer (UI), logical layer (business), and Data Layer (DAO)

You typically add a Value object layer (VO)

The third layer: according to the division in the layer to divide

Depending on the circumstances, such as business and DAO also in the form of the Iron Triangle to build the sub-package, and the UI and VO do not need to re-draw the molecular bag.

The hierarchies are as follows:

Java------Stand-alone bookstore management system (design ideas and Design Patterns series I) overview