采购管理信息系统设计

共享知识分享快乐越努力·越幸运目录目录·····································································································I1前言································································································11.1作业背景·····················································································11.2选题说明·····················································································11.2.1基本思路·················································································21.2.2作业目标·················································································21.3工作业绩······················································································21.3.1个人主要工作··············································································21.3.2主要收获····················································································21.3.3自我评定····················································································31.3.4小组成员任务分工情况··································································32系统规划··························································································42.1可行性分析···················································································42.1.1可行性研究方法············································································42.1.2可行性综合分析············································································43系统分析··························································································53.1详细调查分析················································································53.1.1业务流程图·················································································53.2系统的逻辑模型·············································································53.2.1数据流程图·················································································53.2.2数据字典····················································································64系统设计··························································································84.2总体设计·······················································································84.2.1功能结构图设计············································································84.2.2E-R····························································································94.3详细设计·······················································································94.3.1输入输出设计············································································94.3.2代码设计···················································································104.3.3数据库设计················································································105系统实施·························································································12共享知识分享快乐越努力·越幸运结束语································································································28参考文献·····························································································29共享知识分享快乐越努力·越幸运1前言1.1作业背景本文根据《管理信息系统开发实践》课程要求而做。课程作业要求如下：管理信息系统开发作为独立的教学环节，是学习完《管理信息系统》课程并进行完专业实习后进行的一次全面的综合练习。其目的在于加深对管理信息系统基础理论和基本知识的理解，掌握使用信息系统分析、设计的基本方法，提高解决实际管理问题、开发信息系统的实践能力。具体内容是：用信息系统开发工具（例如PowerBuilder、Delphi、Vb、Vfp等）开发一个实用的中小型采购管理信息系统。具体要求如下：1、根据课程实践时间选择适当规模大小的设计课题。针对信息系统课程实践的具体特点，体现项目管理的思想，由指导教师对学生进行分组（每组4-6人），一组一题，分工合作，共同完成。2、根据合理的进度安排，按照系统开发的流程及方法，踏实地开展课程实践活动。3、课程实践过程中，根据选题的具体需求，在开发各环节中撰写相关的技术文档，最后要求提交详细的课程实践报告。4、开发出可以运行的管理信息系统，通过上机检查。1.2选题说明进入21世纪，随着技术进步和客户需求多样化，企业经营的市场环境发生了很大的变化,从过去的供应商主导的、静态的、简单的市场环境变成客户为主导的、动态的、复杂的市场环境。企业之间由单纯产品质量、性能方面的竞争转向企业所在的供应链之间的竞争。在企业经营管理中,采购是最重要的一个环节。它对于企业降低经营成本、确保产品质量、缩短生产周期具有非常重要的意义。采购管理为降低采购成本，提高采购效益提供了广阔的空间，但也同时为采购管理带来了新的机遇和挑战。目前,我国大多数企业仍然没有建立健全的供应链管理体系,物资的采购还存在机构设置分散,资源浪费严重,信息传递滞后等问题。共享知识分享快乐越努力·越幸运1.2.1基本思路本文从全通公司提高采购管理的需求入手,给出了适合本企业的采购供应管理系统整体设计方案。在系统业务流程改造和功能模块的设计中体现出先进的采购管理思想,并对采购业务管理的具体内容进行了分析与设计。1.2.2作业目标该系统将有效的整合企业内外部的资源,加强企业与供应商之间的紧密合作,增强企业采购业务的透明度,规范标准业务流程,提高采购的效率和质量,提升企业的核心竞争力。通过对采购管理系统设计与开发，使采购部门的工作效率大大提升，实现采购管理工作的信息化，网络化等，从而降低采购的总体成本，增加企业的利润，并能更好的完成企业最终目标。1.3工作业绩1.3.1个人主要工作我在团队中的主要工作是进行系统实施，系统实施的主要内容包括物理系统的实施、程序设计与调试、人员培训、数据准备与录入、系统转换与评价等。系统实施阶段既是成功地实现新系统，又是取得用户对系统信任的关键。1.3.2主要收获通过对全通公司的采购管理系统进行设计，使我不仅了解到系统实施部分的内容，也使我更深的掌握了管理信息系统的开发方法以及重要性。开发一个管理信息系统好像建一栋大楼，系统分析、系统设计是根据用户的要求画出各种蓝图，系统实施是调集各类人员、设备、材料，在现场根据图纸按实施方案的要求把“大楼”建起来。通过对这个系统的开发设计，使我这学期所学的管理信息系统得到了运用，实现了从理论到实践的升华，一个完善的管理信息系统可以促使公司向信息化方向发展，将管理工作统一化、规范化、现代化，使公司处于一个信息灵敏、管理科学、决策准确的良性循环中，为公司带来跟高的效益。最后，我还明白了集体协作的重要性。我们组的各个成员通过合理分工、互帮共享知识分享快乐越努力·越幸运互助才完成了这个系统的开发设计，所以。通过这次团队合作，不仅学到先进的专业知识，更加深了团队合作的意识。1.3.3自我评定□优□良□中□及格□不及格1.3.4小组成员任务分工情况本组为本次课程设计第四组，组长为：，小组所有成员分工如下：共享知识分享快乐越努力·越幸运2系统规划2.1可行性分析2.1.1可行性研究方法通过调查分析采购供应管理信息系统所具备的能力及实现的方法。确定总体结构，利用数据库所具有的能力，以最简洁最容易的方法，使其成为一个初级的系统软件。2.1.2可行性综合分析（1）可行性：系统现阶段的发展过程中，利用现有人力和物力是完全具备的能力开发出来的，作为阶段性产品，日后的发展空间大，实现方法逐步简单容易。对于该系统的技术要求，现行的软件开发条件，环境，完全可以实现。SQLServer2000完全可以提供该系统的操作要求和数据库需求。所以采购供应管理信息系统在技术上是完全可行的。（2）技术可行性：该系统的开发要求是界面简单，易于操作。（3）经济可行性：该系统做为课程设计开发，经济可行性在此不做讨论。（4）管理可行性：此次采购系统的开发得到了大商集团采购部门经理的大力支持，期待