企业库存管理系统的设计与实现
企业库存管理系统
摘 要：科学技术不断进步和经济的不断发展，以及全球化信息网络和全球化市场形
成和技术变革的加速，围绕新产品的市场竞争也日趋激烈，企业面临着缩短交货期、提高产品质量、降低成本和改进服务的压力。所有这些都要求企业能对不断变化的市场做出快速反应。作为供应链节点中的一个重要环节，物资管理企业要实现快速地对物资进行收发，必须建立现代化的库存管理系统。用计算机对仓库库存信息进行日常的管理，通过对系统需求分析，从系统设计着手，实现系统各模块，包括输入输出、信息查询、系统维护等功能。库存研究基于信息技术，充分利用管理信息系统、决策支持系统数据库理论与方法，集成物流、资金流、事务流及信息流，对库存管理与控制信息系统的设计进行研究,它对企业减少库存、增加效益、提高竞争力具有重要的意义。但是在系统的动态交互性，及时性，智能性，可靠性和安全性方面还有待提高。
关键词：库存管理、ASP.NET、C#、 SQL Server
企业库存管理系统的设计与实现
The Management System of Stock Based on .NET
Abstract
Nowadays ,with the continuous improvement of technology and development of economy ,as well as the global information network ,the global market forming and the technique changing quickly , the market competition of new products is becoming more and more intensely and enterprise is facing the pressure of shortening the date of delivery ,improving the quality of product ,cutting down the cost and making the service better . All these requests call for fast reaction of enterprise over the very changing market . As a key point of supply chain , material management enterprise should receive and dispatch the goods and materials at a high speed ,and must build a modern stock control management system . According to the system demand analysis and by the design system , we can achieve the function of every module ,such as in-out ,information search system maintenance, etc ,and use computer to supervise daily information of storage. Inventory research is based on information technology ,taking full use of management operating system, DSS theory and methods, logistics, fund flow, transaction flow and information flow, studying inventory management. It plays a very important role on reducing stock ,increase profits, and boosting the competitiveness .However , it has some space to enhance on system trend interactivity ,timeliness, intellectuality, reliability and safety .
Key words: Stock Management 、ASP.NET 、C#、SQL Server
企业库存管理系统的设计与实现
目 录
1.绪 论 ·················································································································································· 1
1.1 课题研究背景及意义 ··············································································································· 1 1.2 本系统使用的方法和语言 ······································································································ 1
1.2.1 统一建模语言UML ········································································································· 1 1.2.2 .NET和C# ····················································································································· 2 1.3系统描述 ··································································································································· 3 1.4 分析方法3 2.需求收集 ·············································································································································· 4
2.1 业务过程分析 ··························································································································· 4 2.2 研究领域分析 ························································································································· 5
2.2.1 初步用例模型开发 ········································································································ 5 2.2.1.1 开发系统业务角色 ···································································································· 6 2.2.2 开发初步类图 ··············································································································· 6 2.3 系统需求研究 ··························································································································· 8
2.3.1 收集系统需求 ··············································································································· 8 2.3.2开发系统功能包图 ········································································································· 9
3．系统分析与设计 ·······························································································································10
3.1 开发系统用例模型 ··················································································································10 3.2 系统数据库设计 ······················································································································ 11
3.2.1 数据库需求分析 ··········································································································· 11 3.2.2 数据库概念结构设计 ··································································································· 11 3.2.3数据库逻辑结构设计 ······································································································13
4.开发系统 ·············································································································································16
4.1 编制代码 ·································································································································16 4.2 系统实现 ·······························································································································16
4.2.1 用户界面 ······················································································································16 4.2.2 登录动作代码 ··············································································································17 4.3 部分系统界面及功能简介 ·····································································································19
4.3.1企业库存管理系统主界面 ····························································································19 4.3.2客户信息管理界面 ········································································································19 4.3.3货品信息管理界面 ········································································································20 4.3.4货品分类管理界面 ········································································································20 4.3.5入库单界面 ···················································································································20 4.3.6入库管理主界面············································································································21 4.3.7入库查询主界面············································································································21 4.4系统特色 ··································································································································21
4.4.1用户密码加密存储 ········································································································21 4.4.2.支持在页面备份数据库 ·······························································································22
5. 部 署 ·············································································································································24 结 束 语 ·················································································································································25 致 谢 ····················································································································· 错误！未定义书签。 参 考 文 献 ···········································································································································25
企业库存管理系统的设计与实现
1.绪 论
1.1 课题研究背景及意义
近几年我国企业信息化呈现持续火爆的势头，有专家预测，我国高新技术产业在企业中占据的位置越来越重要。如何提高自己企业的生产和运营效率，成为企业发展中必须考虑的问题。在现在网络飞速发展的背景下，设计库存管理系统来促进企业生产效率的提高也是一个很好的手段。当前形势下，仅仅靠原始的手工管理或简单的单机管理是不够的，商品部门面对大量的信息，无法有效率地将其中的重要部分提取出来，并做出相应的判断和处理。公司管理者的决策只能依据报表数据，在浪费大量人力、物力的同时无法做到实时监控，难以保证数据的准确性和及时性。因此，先进的管理思想在商业中实现就成为了一个可望而不可及的目标。公司集团非常急需一套既有先进管理思想又适合国内大商业的在线进销存管理信息系统，作为实现目标和提高现有水平的一种重要手段。库存管理系统是一个公司不可缺少的部分,它的执行对于公司的决策者和管理者来说是很有帮助的, 随着科学技术的不断提高,计算机科学日渐成熟,其强大的功能已为人们深刻认识,它已进入人类社会的各个领域并发挥着越来越重要的作用。
1.2 本系统使用的方法和语言
1.2.1 统一建模语言UML
统一建模语言（Unified Modeling Language ,UML）是一种可视化的建模语言，它能让系统构造者用标准的、易于理解的方式建立起能够表达出他们想象力的系统蓝图，并且提供了便于不同人之间有效的共享和交流涉及结果的机制。
UML包括了一些可以相互组合图表的图形元素。由于UML是一种语言，所以UML具有组合这些元素的法规。UML提供了系统设计所需要的多种图，这些图是在用多个视图来展示一个系统，这组视图被称为一个模型（Model）。一个UML模型描述了一个系统需要做什么。同时，UML提供了组织和扩展这些图的方法。
关于标准建模语言UML的内容，首先，UML融合了Booch、OMT和OOSE方法中的基本概念,而且这些基本概念与其他面向对象技术中的基本概念大多相同,因而,UML必然成为这些方法以及其他方法的使用者乐于采用的一种简单一致的建模语言;其次,UML不仅仅是上述方法的简单汇合,而是在这些方法的基础上广泛征求意见,集众家之长,几经修改而完成的,UML扩展了现有方法的应用范围;第三,UML是标准的建模语言,而不是标准的开发过程。尽管UML的应用必然以系统的开发过程为背景,但由于不同的组织和不同的应用领域,需要采取不同的开发过程。
作为一种建模语言,UML的定义包括UML语义和UML表示法两个部分。 (1) UML语义 描述基于UML的精确元模型定义。 (2) UML表示法 定义UML符号的表示法,为开发者或开发工具使用这些图形符号和文本语法为系统建模提供了标准。这些图形符号和文字所表达的是应用级的模型,在语义上它是UML元模型的实例。
1 / 26
企业库存管理系统的设计与实现
标准建模语言UML的重要内容可以由下列五类图(共9种图形)来定义。
第一类是用例图，第二类是静态图(Static diagram),包括类图、对象图和包图。第三类是行为图(Behavior diagram),描述系统的动态模型和组成对象间的交互关系。其中状态图描述类的对象所有可能的状态以及事件发生时状态的转移条件。通常, 状态图是对类图的补充。在实用上并不需要为所有的类画状态图,仅为那些有多个状态其行为受外界环境的影响并且发生改变的类画状态图。而活动图描述满足用例要求所要进行的活动以及活动间的约束关系,有利于识别并行活动。第四类是交互图(Interactive diagram),描述对象间的交互关系。其中顺序图显示对象之间的动态合作关系,它强调对象之间消息发送的顺序,同时显示对象之间的交互;协作图描述对象间的协作关系, 协作图与顺序图相似,显示对象间的动态合作关系。除显示信息交换外,协作图还显示对象以及它们之间的关系。如果强调时间和顺序,则使用顺序图;如果强调上下级关系,则选择协作图，把这两种图合称为交互图。第五类是实现图( Implementation diagram )，包括构件图和配置图。
1.2.2 .NET和C#
.NET 是 Microsoft XML Web services 平台。XML Web services 允许应用程序通过 Internet 进行通讯和共享数据，而不管所采用的是哪种操作系统、设备或编程语言。Microsoft .NET 平台提供创建 XML Web services 并将这些服务集成在一起之所需。对个人用户的好处是无缝的、吸引人的体验。
.NET提供了一种新的运行环境．即.NET框架，它使得程序员能够更容易、迅速地写出优良、健壮的程序代码，并且能够方便地管理、部署和修改代码，所编写的程序和组件都在该环境中执行。它为程序员提供了一些新功能，例如自动内存管理(垃圾收集)．以及更方便地访问所有系统服务。它添加了许多实用功能、例如易于访问因特网和数据库。它还为代码复用提供了一种新的机制一一更易于使用．并且比COM更加有效和灵活。.NET框架更易于部署．因为它不需要进行注册设置。它还为版本的制定提供了标准化、系统级别的支持。程序员可以在任一种与.NET兼容的编程语言中使用上述全部功能
.NET为创建HTML页面提供了一种新的编程模型，称为ASP.NET．尽管智能的单机程序仍在不断涌现，但是在不久的将来，大多数因特网通信都会以通用浏览器作为前端，这就要求服务器能够使用HTML语言来构造页面，以便浏览器识别并显示给用户。ASP.NET是一种运行在因特网信息服务(IIS)下的新环境，它使得程序员能够更容易地编写代码来构造基于HTML语言的web页面，供浏览器查看。 ASP.NET提供了一种新的与语言无关的代码编写方式，并将其与web页面请求相关联。它提供了.NET的Web窗体，它是一种与控件交互的事件驱动编程模型、这使得编写web页面变得就像编写普通的VB窗体一样。ASP.NET包含了良好的会话状态管理和安全功能，它比原来的ASP更加健壮，性能也得以提高。
.NET提供了Windows窗体，它是一种使用.NET框架编写各种客户程序的新方法。 一个使用XML Web服务的专用客户端应用程序必须提供良好的用户界面。高质量的界
2 / 26