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

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

t model as per SKU characteristics is as described in Guidelines For Inventory Model Implementation 23Data flow diagramInventory 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 stagepersonneldepartment responsible for a particular process at any given timeSome mon symbols used are Circles represent processes Cylinders represent information data stores 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 itCHAPTER IIIPHYSICS DESIGN31Entity Relationship DiagramData Dictionary1Cases described Cases nameCases login Subject fieldCases definitionUsers to log on to the system get the corresponding interface and accessRole Inventor controller or managerBusiness trigger eventsUsers ready to use the system for business processing or system managementPreconditionsSystem for the users to establish system has user and assigned corresponding privileges End conditions1success conditionsUser login system and obtain appropriate permissions2failure conditions1 system without the users2 the user name and password mistakeInput overviewUsername password and role Output overviewAnd user rights corresponding interfaceCases noteThe Lord event flowSteps Rolesystem Description Data itemNote Role Start registration procedureSystem Login screen showsTip input user identity and secret wordRole Input user identity and secret word login systemUsername password and roleSystem Verify whether the user is legitimate users secret word is correct Back to user interface the corresponding menuIf not legitimate users or secret words not right turn to A1Branch flows No Lord event flow steps rolesystem Conditions Description Data itemTurned to the Lord event flowSteps Note A14systemNot legitimate users user name and password mistakeUser name and password and role not correspondingFailure to return to login information Login failed information22 Supplier information query cases overview Cases nameSupplier information query Subject fieldSupplier information query casesCases definitionSupplier information queryRole Inventor controllerBusiness trigger eventsFor supplier information queryPreconditionsHas the supplier information records need inquires End conditions1success conditionsTo the suppliers to inquires query information2failure conditionsNot to need inquires the supplier of the query informationInput overviewThe supplier information needed for inquires Output overviewInquires the resultsCases noteThe Lord event flowSteps Rolesystem Description Data itemNote Role Into inquires the interfaceSystem Display inquires the interfaceRole Input the information needed for inquires suppliersSystem Inquires success or failInquires successIf inquires the success turned to A1If inquires the failure turned to A2Branch flows No Lord event flow steps rolesystem Conditions Description Data itemTurned to the Lord event flowSteps Note A14systemComplete supplier information queryReturn to successful informationInquires the supplier of the information2A24systemNo plete supplier information queryReturn to failure informationInquires the failure of information clew23 Supplier information modify cases overview Cases nameSupplier information changes Subject fieldSupplier information changes casesCases definitionSupplier information changesRole Inventor controllerBusiness trigger eventsFor supplier information changePreconditionsA need to modify the supplier information records End conditions1success conditionsTo the suppliers to change query information2failure conditionsNot to need supplier of the change query informationInput overviewThe supplier information needed for modification Output overviewModified resultsCases noteThe Lord event flowSteps Rolesystem Description Data itemNote 9Role Into change the interface10System Display change the interface11Role Input the information needed for change suppliers12System change success or failchange successIf change success turned to A1If change failure turne。