目 录
摘 要 ································································································· I Abstract ·································································································II 第1章 概 述 ···················································································· 1 1.1 课题来源 ······························································································ 1 1.2 课题目的及意义 ···················································································· 1 1.3 国内外发展状况 ···················································································· 2 第2章 方案论证 ···················································································· 3 2.1 开发方案选择 ······················································································· 3 2.2 开发技术简介 ······················································································· 3 2.3 可行性分析 ·························································································· 4 第3章 需求分析 ···················································································· 6 3.1 系统目标设计 ······················································································· 6 3.2 开发设计思想 ······················································································· 6 3.3 系统功能需求分析 ················································································· 6 3.3.1 现场要求 ························································································· 6 3.3.2 数据流图 ························································································· 7 3.4 系统性能要求 ······················································································· 8 3.4.1 用户接口 ························································································· 8 3.4.2 数据库特性 ······················································································ 9 3.4.3 可扩展性 ························································································· 9 3.4.4 稳定性与健壮性 ··············································································· 9 第4章 过程论述 ··················································································· 10 4.1 总体结构图 ························································································ 10 4.2 数据库设计 ························································································ 11 4.3 输入输出设计 ····················································································· 16 4.3.1 输出设计 ······················································································· 16 4.3.2 输入设计 ······················································································· 17 4.4 安全性设计 ························································································ 18 4.4.1 数据安全性 ···················································································· 18 4.4.2 登陆用户的安全性 ··········································································· 18 4.4.3 操作的安全性 ················································································· 18 4.4.4 系统安全性的其他考虑 ···································································· 18 4.5 数据库管理 ························································································ 18
IV
4.6 系统详细设计 ····················································································· 19 4.6.1 数据库连接模块 ·············································································· 19 4.6.2 登录模块设计 ················································································· 20 4.6.3 入、出、退库模块设计 ···································································· 21 4.6.4 结算模块设计 ················································································· 23 4.6.5 支付欠款模块设计 ·········································································· 25 4.6.6 系统管理模块设计 ·········································································· 26 4.6.7 报表模块设计 ················································································· 27 4.6.8 商品分类模块设计 ·········································································· 28 第5章 软件测试与结果分析 ··································································· 30 5.1 软件测试的技术 ·················································································· 30 5.2 黑盒测试 ···························································································· 31 5.2.1 黑盒测试 ······················································································· 31 5.2.2 功能测试 ······················································································· 31 5.3 白盒测试 ···························································································· 34 5.4 系统测试 ···························································································· 36 5.5 测试结论 ···························································································· 36 结 论 ······························································································· 37 致 谢 ······························································································· 38 参考文献 ······························································································· 39 附 录 ······························································································· 41
V
第1章 概 述
1.1 课题来源
随着社会经济的迅速发展和科学技术的全面进步，计算机与通信技术为基础的信息系统正处于蓬勃发展的时期。与此同时，为了管理大量的货品，货品仓库也大量的出现，仓库的管理问题也就提上了日程。随着物资的大量增加，其管理难度也越来越大，如何优化仓库的日常管理也就成为了一个大众化的课题。
在计算机飞速发展的今天，将计算机这一信息处理应用于仓库的日常管理已是势必所然，而且这也将为仓库管理带来前所未有的改变，它可以带来意想不到的效益，同时也会为企业的飞速发展提供无限潜力。采用计算机管理信息系统已成为仓库管理科学化和现代化的重要标志，它给企业管理来了明显的经济效益和社会效益。主要体现在：极大提高了仓库工作人员的工作效率，大大减少了以往入出存流程繁琐，杂乱，周期长的弊端。基于仓库管理的全面自动化，可以减少入库管理、出库管理及库存管理中的漏洞，可以节约不少管理开支，增加企业收入。仓库的管理的操作自动化和信息的电子化，全面提高了仓库的管理水平。
随着我国改革开放的不断深入，经济飞速的发展，企业要想生存、发展，要想在激烈的市场竞争中立于不败之地，没有现代化的管理[19]是万万不行的，仓库管理的全面自动化、信息化则是其中极其重要的部分。为了加快仓库管理自动化的步伐，提高仓库的管理业务处理效率，建立仓库管理系统已变得十分心要。入库、出库还是现在企业货品仓库管理的常规基本模式，虽然，最近又出现了很多新的管理模式，如：基于零库存思想的沃尔玛特管理方式，但这些新的思想在中国大部分企业的管理中还是难以实现的。所以如何设计好仓库管理系统，尽可能地减少仓库管理的重复性和低效性就成为当前最为重要的问题。货品仓库管理的核心是入库和出库之间的联系，如何处理好二者之间的关系是系统最为关键的部分。通过对仓库管理日常工作的详细调查，搜集了大量的资料，从系统结构的组织，功能的实现，技术的要求以及可行性等多方面进行考虑，认为本课题是一个适应现今货品仓库管理需求的计算机信息管理系统，具有一定的实际开发价值和使用价值。
1.2 课题目的及意义
仓库管理是与我们日常生活息息相关的问题。大到公司、超市的仓库管理，小到图书馆的藏书管理，都可以认为是各种各样的仓库管理需求。随着我国改革开放的不断深入，经济飞速的发展，企业要想生存、发展，要想在激烈的市场竞争中立于不败之地，没有现代化的管理是万万不行的，仓库管理的全面自动化、信息化则是其中极其重要的部分。为了加快仓库管理自动化的步伐，提高仓库的管理业务处理效率，建立仓库管理系统，尽可能地减少仓库管理的重复性和低效性，已变得十分必要。
1
1.3 国内外发展状况
国外状况:据统计，目前，美国在财务会计上占有90%的工作由计算机完成；计划管理是80—90%；在计算机应用发展较快的国家中，计算机应用于信息管理的占80%；用于科技计算的占8%，用于生产过程控制的占12%；由此可以看出，信息管理是计算机应用的主要领域。
国内状况:由于种种原因，我国的信息资源建设水平远远落后于信息基础设施的建设的水平。长期以来，我国信息资源的开发管理未能与信息资源的增长同步进行。我国有丰富的原始信息资源，但在此基础上再生的二次信息系统和数据库产业的规模和市场占有率、使用率相当低，大量的有价值的信息未能进一步加工成商品使其增值。我国的计算机应用要比西方国家落后十几年，因此，信息资源的开发和利用已被确立为国民经济信息的核心内容，信息数字化，传输的网络化是缩小发展中国家与发达国家差距的捷径，世界信息化浪潮正以不可阻挡之势席卷全球时，我国要迎头赶上，就必须利用现有的信息基础设施，重点开发和推广应用于各类科技经济等数据库和网络资源服务系统，以便取得巨大的社会效益和经济效益。
现代企业的物流系统日趋复杂，高效的物流系统要求有效地对企业的库存进行管理。目前的仓库管理系统一般技术比较落后、性能较差且很不完备，人工干涉多，操作使用不方便，有的还故障率高而不实用。现阶段仓库管理的特点是信息处理量特别大，所管理的物资设备种类繁多，而且入库单、出库单、需求单等单据的发生量特别大，关联信息多，查询和统计的方式各不相同。因此在管理上实现起来有一定的困难。在管理的过程中经常出现信息的重复传递等问题。仓储管理部门越来越需要一套低成本、高性能、方便使用、功能完善的综合仓库管理信息系统。而现在计算机技术、网络技术、的成熟与发展，为仓储管理自动化提供了强有力的技术支持。课题以某仓库应用背景，通过研究当前仓库系统的管理现状、存在问题以及现实需求，设计一个针对仓库管理工作的管理信息系统。该系统能够提供较为完备的功能，可以全面管理仓库中储存的商品和货物，缩短了库存信息流转时间，使企业的物料管理层次分明，井然有序，为采购、销售和生产提供依据，对于提高企业的经营效率、加快仓库管理的自动化具有重要的意义。
仓库管理系统是一个企业单位不可缺少的部分,所以仓库管理系统应该能够为管理者提供充足的信息和快捷的查询手段。但一直以来人们使用传统人工的方式管理文件档案，这种管理方式存在着很多缺点,如:效率低、保密性差,另外时间一长,将产生大量的文件和数据,这对于查找、更新和维护都带来了不少的困难。
随着科学技术的不断提高,计算机科学日渐成熟,其强大的功能已为人们深刻认识,它已进入人类社会的各个领域并发挥着越来越重要的作用。而利用计算机对仓库系统进行管理,有着手工管理所无法比拟的优点.比如:检索迅速、查找方便、可靠性高、存储量大、保密性好、寿命长、成本低等。这些优点能够极大地提高仓库管理的效率,也是企业的科学化、正规化管理,与世界接轨的重要条件。
2
第2章 方案论证
2.1 开发方案选择
B/S结构，即Browser/Server(浏览器/服务器)结构，在这种结构下，用户界面完全通过WWW浏览器实现，一部分事务逻辑在前端实现，但是主要事务逻辑在服务器端实现，形成所谓3-tier结构。B/S结构，主要是利用了不断成熟的WWW浏览器技术，结合浏览器的多种Script语言(VBScript、JavaScript等)和ActiveX技术，用通用浏览器就实现了原来需要复杂专用软件才能实现的强大功能，并节约了开发成本，是一种全新的软件系统构造技术。B/S结构采用星形拓扑结构建立企业内部通信网络或利用Internet虚拟专网（VPN）。
Internet为数据库应用系统提供了新的机会，就是构建一种以Web技术为中心的应用。即采用B/S结构，客户机上只要安装一个浏览器（Brower），最多再安装很小的支持库；中间层采用Web服务器，它接受客户端的请求，将其转换为Sql语句，通过ODBC或其他手段传给数据库服务器，并将数据库服务器返回的结果用HTML文件格式传回给客户机。客户机实际上就是一个将标准语言转化为界面的解释器，应用程序安装在Web服务器上，其运行也是在这单进行的。
图2-1 浏览器/服务器结构
浏览器 操作系统服务器 SQL server数据库 2.2 开发技术简介
ASP[2]：近年来随着Internet技术的飞速发展及用户需求的不断升级，Web页面技术也不断的推陈出新，使得Web站点的功能越来越强大，能够提供的服务种类越来越繁多。从HTML、Client Script到CGI,从JAVA的诞生到ActiveX,Web页面设计人员不断受到冲击，微软公司在总结了以往技术，重新思考Web页面设计的真正需要后，推出了Active Server Pages (ASP)，一种用以取代CGI(Common Gateway Interface，通用网关接口)的技术。
简单讲，ASP是位于服务器端的脚本运行环境，ASP内含于IIS之中 , 通过ASP
3
基于web技术的仓库管理系统设计与实现毕业论文设计
