The Clothes-Processing Industry has its own strong characteristics. Because the clothes are popular and seasonal, many Clothes-Enterprises need to handle hundreds or thousands of stock-units everyday, and need to manage innumerable complicated-data about clothes style, color, size, client's IDs. Besides, selling ways of clothes are complicated, resulting in that the product management and business process of Clothes-Enterprises is very tedious. After analyzing Clothes-Processing Industry, it gives out a Clothes-Processing Logistics Management Model, to solve the problems now existing in Clothes-Processing Industry. The Model completely supports the management commands on product's color and size in Clothes-Processing Industry, binding the buying selling and storing together to the Unit-Management Performance. The Data Center has powerful abilities in information analyzing and decision supporting, ensuring Clothes-Enterprises a quick path to the international competition. MingNi Clothes-Processing Logistics Management System is an application of this model. MingNi Clothes-Enterprise adopts to "Producing Section→Selling Center→Dealers→Monopoly Stores" informational construction management pattern, and combines the Enterprise's Logistics, Information Flow and Money Flow together, regarding the Company Headquarters as Enterprise's Information Center. The Company Headquarters connects Producing Section, Delivery Center, Monopoly Stores and etc., controlling the whole Logistics Procedure. MingNi Clothes-Processing Logistics Management System takes the MingNi Clothes-Enterprise as background. After analyzing its Clothes-Process Procedure, we can conclude the Software Requirement for MingNi Clothes-Processing Logistics Management System. Based on MingNi Clothes-Processing Logistics Management Model mentioned before, we could divide the system into Function Modules, designing the Function Structure of MingNi Clothes-Processing Logistics Management System. MingNi Clothes-Processing Logistics Management System is a Distributed System, adopting the Browser/Server structure. According to the Java Web Layering Theory, the system can be divided into 6 layers, and each layer has its own contribution to the system's function. System adopts improved Struts Framework to delegate Business Logic, and this Framework which is based on MVC Pattern implements the division of Controlling Logic from Presentation Logic, improve the system's maintainability. The system uses Hibernate to encapsulate the access to Data Resource Layer, improving the Persistent Ability of the Business Object. |