[管理学]库存管理系统毕业论文英文版

[管理学]库存管理系统毕业论文英文版内容摘要：

er DFD to detail the bination in another page. Logical flow chart explains the inventory control process as carried out to manage the StockOnhand and StockOnOrder. Various decision blocks are used to check the process at various stages such as Order Receiving, Quality Adjustments and so on. For each SKU, appropriate model is used for managing the stock levels. Method for finding correct model as per SKU characteristics is as described in 39。 Guidelines For Inventory Model Implementation39。 10 11 Data flow diagram Inventory Model data flow diagram is shown above. The data flow diagram is based upon the Yourdon technique. This technique was proposed by Ed Yourdon and is a very simple but effective way to depict the information flow in systems. This basically helps us to precisely understand the flow of information in a system and point out the exact stage/personnel/department responsible for a particular process at any given time. Some mon symbols used are: Circles represent processes Cylinders represent information data stores 12 Rectangles show a resource Rhombus is used to show a gate process Arrows show the direction of data flow. As shown in the above diagram, the process is initiated when the customer places an order. Here the data would consist of details like number of items, delivery dates, shipment details etc. Then the inventory is checked where again data is fed from a data store. This data store (1) keeps a record of the historical data. The data store (2) also has input from data store (3) which keeps the warehouse records like inventory levels, location etc. The inventory is checked for availability, which is a gate process. If there is availability, then the item is retrieved and the shipment is scheduled. The customer receives the item and provides feedback, which again goes into data store (4). If enough inventory is not available then Reorder placement is done. A lot of factors are to be considered for the reorder placement. Looking at the bottom of the diagram, it can be seen how the model is determined. Input from data store (5) goes into the SKU classification process. The key factors that are considered are volume flow rate, size etc. This SKU classification influences the type of model that is to be used for that SKU. The demand patterns are also considered and are fed into data store (6), which also determines the model to be selected. After the model is determined, the EOQ and reorder points are set. Various factors like leadtime and back order costs are considered and then the reorder placement is done. This DFD shows the exact information flow in the system, which can help recognize the individual processes and the data transfer associated with it. 13 CHAPTER III PHYSICS DESIGN Entity Relationship Diagram 14 Data Dictionary described Cases name Cases login Subject field Cases definition Users to log on to the system, get the corresponding interface and access. Role Inventor controller or manager. Business trigger events Users ready to use the system for business processing or system management. Preconditions System for the users to establish system has user, and assigned corresponding privileges. End conditions conditions User login system and obtain appropriate permissions conditions 1) system without the users. 2) the user name and password mistake Input overview Username, password, and role Output overview And user rights corresponding interface Cases note 15 The Lord event flow Steps Role/system Description Data item Note 1. Role Start registration procedure 2. System Login screen shows。 Tip input user identity and secret word 3. Role Input user identity and secret word, login system Username, password, and role 4. System Verify whether the user is legitimate users, secret word is correct。 Back to user interface, the corresponding menu If not legitimate users, or secret words, not right turn to A1. Branch flows No. Lord event flow steps role/system Conditions Description Data item Turned to the Lord event flow Steps Note A1 4 system Not legitimate users, user name and password mistake, User name and password and role not corresponding Failure to return to login information Login failed information 2 2. Supplier information query cases overview Cases name Supplier information query Subject field Supplier information query cases Cases definition Supplier information query Role Inventor controller Business trigger events For supplier information query Preconditions Has the supplier information records need inquires End conditions conditions To the suppliers to inquires query information 16 conditions Not to need inquires the supplier of the query information Input overview The supplier information needed for inquires Output overview Inquires the results Cases note The Lord event flow Steps Role/system Description Data item Note 5. Role Into inquires the interface 6. System Display inquires the interface 7. Role Input the information needed for inquires suppliers 8. System Inquires success or fail Inquires success If inquires the success turned to A1 If inquires the failure turned to A2 Branch flows No. Lord event flow steps role/system Conditions。