摘 要
近年来，随着我国经济的迅速发展，国内企业的发展也越来越快，企业内部管理面临的问题也随之越来越多。需要有更好的管理理念，更好的管理方式融入到企业当中。
目前，ERP已不在是什么新鲜事物，已在国内外很多大型企业中普遍应用。而对于国内中小型流通行业企业（不包含生产环节）中，大多都是采用Office文档来记录事务，尚未使用ERP，导致工作效率相对缓慢，出现信息输入错误的概率很高，管理不方便等问题。从这些企业内部管理文件的发现，其管理思想已达到实施ERP的管理思想，但上ERP的成本太高，让企业无法实施。
关键词 ERP；.NET框架；B/S模式；业务
Abstract
Along with our country economy rapid development, the domestic enterprise''s development also more and more was in recent years quick, the enterprise internal management faced the question more and more were also many along with it.Needs to have the better management idea, the better management way integrates to the enterprise.
At present, ERP already in is not any new things, has applied generally in the domestic and foreign very many major industries. Butregarding the domestic middle and small scale circulation profession enterprise (does not contain produces link), mostly all is uses the Office documents to record business, not yet uses ERP, causes the working efficiency to be relatively slow, appears the information input wrong probability to be very high, manages and so on the questions not not conveniently.From these enterprise internal management document discovery, its management thought had achieved implements ERP the management thought, but on the ERP cost too is high, lets the enterprise be unable to implement.
Key words ERP The. NET frame B/S mode Service
目 录
摘 要 1
Abstract 2
第1章 绪论 7
1.1 课题背景 7
1.1.1 ERP系统产生背景 7
1.1.2 ERP系统现况 7
1.2 目的和意义 7
1.2.1 实施ERP系统的目的 7
1.2.2 实施ERP系统的意义 8
1.3 系统设计思想 8
1.3.1 现有市场上ERP产品的分析 8
1.3.2 流通业ERP系统设计思想 9
1.3.3 流通业ERP系统的创新 9
第2章 可行性分析 12
2.1 流通业中小型企业业务流程分析 12
2.1.1 流通业中小型企业业务流程分析简要概述 12
2.1.2 业务流程图 13
2.2 系统开发可行性分析 15
2.2.1 经济可行性分析 15
2.2.2 技术可行性分析 16
2.2.3 运行可行性分析 16
2.2.4 法律可行性分析 16
2.3 本章小结 16
第3章 需求分析 18
3.1 系统的基本需求描述与需求分析 18
3.1.1 系统的基本需求描述 18
3.1.2 系统的需求分析 18
3.1.3 数据流图 18
3.1.4 数据字典 24
3.2 本章小结 35
第4章 总体设计 36
4.1 系统模块总体设计 36
4.1.1 系统功能概述 36
4.1.2 系统功能模块图 37
4.2 数据库设计 39
4.2.1 数据分析 39
4.2.2 数据库的详细设计 40
4.3 本章小结 49
第5章 详细设计 50
5.1 系统开发环境 50
5.1.1 B/S结构的数据库访问模式 50
5.1.2 .NET简介 51
5.1.3 相关数据库简介 51
5.2 系统整体框架设计 52
5.2.1 系统编码架构层次设计 52
5.2.2 系统界面风格设计 54
5.3 系统主界面设计 54
5.4 销售管理模块 55
5.4.1 定单默认值设置 55
5.4.2 录入新定单 57
5.4.3 销售机会查看 59
5.5 客户管理模块 60
5.5.1 价格策略管理 60
5.5.2 客户组别管理 61
5.5.3 创建新客户 62
5.6 库存管理模块 63
5.6.1 库存信息管理 63
5.6.2 销售出库作业 65
5.7 账款管理模块 66
5.7.1 流动资金余额管理 66
5.7.2 流动资金期间转换作业 68
5.7.3 资金转换作业 68
5.7.4 收款作业 69
5.7.5 应收款项管理 70
5.7.6 流动资金统计 71
5.8 财务总账模块 72
5.8.1 会计科目查看 72
5.8.2 自动分录设置 73
5.8.3 新建批次 75
5.8.4 未过账批次查看 76
5.8.5 日记账统计 77
5.9 用户管理模块 78
5.9.1 添加新用户 78
5.10 公司主文件管理模块 79
5.10.1 期间设置 79
5.11 本章小结 80
第6章 系统测试与性能分析 81
6.1 系统测试 81
6.1.1 系统测试的目的 81
6.1.2 测试的基本概念 82
6.1.3 测试步骤 83
6.2 本系统测试 83
6.2.1 创建新客户测试 83
6.2.2 其他模块测试 84
6.3 本章小结 84
第7章 系统主要功能使用说明 85
7.1 系统运行环境 85
7.2 系统登陆步骤 85
7.3 流通业ERP系统主要使用说明 86
7.3.1 期间设置 86
7.3.2 业务设置 87
7.3.3 创建客户 88
7.3.4 销售作业 89
7.3.5 采购作业 90
7.3.6 流动资金管理 92
7.3.7 款项转换作业 92
7.3.8 收款付款作业及款项分配作业 93
7.3.9 流动资金期间转换 94
7.3.10 会计分录录入作业 95
7.3.11 用户管理 96
结论 98
致谢 99
参考文献 100
附录1 101
附录2 104
第1章
系统的可行性研究的目的就是用最小的代价在尽可能短的时间内确定问题是否能够解决。在进行可行性研究时需要了解和分析现有的系统，并以概括的形式表达对现有的系统的认识。考虑各中小企业的运作情况，结合实际，在进行可行性研究时需要了解和分析现有的流程，并对现有的系统流程给出一定的认识。本章将对系统的流程及系统的可行性进行介绍分析。
2.1 流通业中小型企业业务流程分析
2.1.1 流通业中小型企业业务流程分析简要概述
根据对中小流通业（不包括生产环节）的企业的市场调研发现，一般业务作业流程包括进销存作业、财务作业、员工信息管理等作业的管理，在现有的企业环境中，目前作业管理文档的管理方式大部分都是采用EXCEL文档来记录处理的事务，如图2-1所示。这种管理方式会产生很多的文件，并且管理不方便，检索速度缓慢，也不方便给出统计分析信息。考虑各中小企业的运作情况，结合实际，在进行可行性研究时需要了解和分析现有的流程，并对现有的系统流程给出一定的认识。
图2-1 客户采购记录Excel文档
2.1.2 业务流程图
根据流通业中小型企业的业务流程的具体情况进行分析得到，流通业中小型企业的业务流程大致可分为以下几大作业：销售作业、库存作业、采购作业、账务作业、总账作业。在各个作业之间进行交互管理。流通业中小型企业业务流程描述如下
1. 销售作业：在产生销售作业时，需要销售人员录入销售定单，销售人员将定单录入完毕后，将销售定单提交到库存部门，由库存部门管理人员根据销售定单的商品明细分配库存商品，库存管理人员分配完毕库存商品后需要将销售定单提交到运输部门，运输管理人员在将分配的商品进行装载运输，销售作业完成。销售作业完成以后，需要销售更新处理，销售更新阶段会产生应收款项提交到财务部门，在将销售产生的会计分录提交到财务部门，有财务人员来管理销售作业产生的账务及会计分录。在销售更新时，还需要对保存到数据中的定单进行统计分析产生销售机会信息，供销售人员参考。
2. 采购作业：在需要采购时，需要采购人员录入采购单，采购人员将采购单录入完毕后，需要将采购单提交到库存部门，之后等待采购入库。当采购的商品到达仓库时，需要入库根据采购单进行核准入库。入库完毕以后，需要采购更新处理，采购更新阶段会产生应付款项提交到财务部门，在将采购产生的会计分录提交到财务部门，有财务人员来管理采购作业产生的账务及会计分录。
3. 库存作业：库存作业中主要作业是在销售作业中的出库作业及采购作业中的入库作业。并对库存商品及仓库进行管理等。
4. 账务作业：账务作业中除了要管理销售作业、采购作业中产生的应收账款、应付账款以外，还需要对流动资金的收入、支出作业进行管理，此外，还需要对银行的资金信息进行管理。账务主要产生自销售更新和采购更新，也可手工录入一笔账务，在产生账务时需要收入、支出的款项来冲销账务。
5. 总账作业：总账作业中的分录主要来自销售更新、采购更新、账务更新等作业，也可以自己手工录入一笔会计分录。当录入完一笔会计分录后将分录存储到数据库中，在后续作业中在对分录进行统计处理，统计报表包括：分类明细账统计报表、总账统计报表、日记账统计报表、流动资金统计报表等。
第6章 系统测试与性能分析
设计阶段从抽象的概念出发，逐步设计出具体的软件系统，直到用一种适当的程序设计语言写出可执行的程序代码。但是，在测试阶段测试人员努力设计出一系列测试方案，目的却是为了”破坏”已经建造好的软件系统—竭力证明程序中有错误不能按照预定要求正确工作。
6.1 系统测试
经过需求分析、设计和编码等阶段的开发后，得到了源程序，开始进入到软件测试阶段。然而，在测试之前的各阶段中都可能在软件产品中遗留下许多错误和缺陷，如果不及时找出这些错误和缺陷，并将其改正，这个软件产品就不能正常使用，甚至会导致巨大的损失。目前，程序的正确性证明尚未得到根本的解决，因此软件测试仍是发现软件中错误和缺陷的主要手段。
测试是一项很艰苦的工作，其工作量约占软件开发总工作量的40%以上，特别对一些关系到人的生命安全的软件。
6.1.1 系统测试的目的
系统测试的目的是为了发现问题之后来解决问题。其目标是为了发现程序中的错误而执行程序的过程，软件测试中涉及的第一个问题是为了确认和验证软件、设计、实现过程中的逻辑正确性以及发现软件产品中存在的问题，并通过测试不断提高和完善软件产品的质量。软件测试中涉及的第二个问题是排错，也称为调试。排错的目的是诊断程序错误的性质及产生的原因并加以改正。软件测试涉及的第三个问题是软件可靠性的评测。可靠性是软件高效、正确运行的保证。
正确认识测试的目标十分重要的，测试目标决定了测试方案的设计。在测试阶段积累的测试结果，可以用更形式化的方法进行统计分析。系统可靠性模型使用这些错误率数据，可以估计将来出现错误的情况并进一步对系统可靠性进行预测。
如果为了表明程序是正确的而进行测试，就会设计一些不易发现错误的测试方案；相反，如果测试是为了发现程序中的错误，就会力求设计出最能暴露错误的测试方案。
从流通业ERP系统的实际情况及本系统的特性考虑，软件测试的目标要求是不同的用户能够通过Internet登陆并进行各种操作；能够正常的访问远程数据库，并保证数据传输的安全性和正确性；后台管理程序能够进行核对、添加、删除等操作。
6.1.2 测试的基本概念
1. 测试的目的
软件测试的目的是尽可能多地发现软件产品（主要是指程序）中的错误和缺陷。
明确测试的目的是一件非常重要的事，因为在现实世界中对测试工作存在着许多模糊或者错误的看法，这些看法严重影响着测试工作的顺利进行。
有人认为测试是为了证明程序是正确的，也就是说程序不再有错误，事实证明这是不现实的。因为要通过测试来发现程序中的所有错误就要穷举所有可能的输入数据，检查它们是否产生正确的结果。例如，一个需要3个16位字长的整型输入数据的程序，输入数据的所有组合情况大约有3×1014种，若每组数据的测试时间为1ms，那么即使一年365天，每天24小时地测试，也大约需要1万年的时间。
2. 测试用例
要进行测试，除了要有测试数据（或称输入数据）外，还应同时给出该组测试数据应该得到怎样的输出结果，我们称它为预期结果。在测试时将实际的输出结果与预期结果比较，若不同则表示发现了错误。因此测试用例是由测试数据和预期结果构成的。
为了发现程序中的错误，应竭力设计能暴露错误的测试。一个好的测试用例是极有可能发现迄今为止尚未发现的错误的测试用例。一次成功的测试是发现了至今为止尚未发现的错误的测试。
3. 白盒测试和黑盒测试
测试的关键是测试用例的设计，其方法可分成两类，白盒测试和黑盒测试。
白盒测试是把程序看成装在一只透明的白盒子里，测试者完全了解程序的结构和处理过程。它根据程序的内部逻辑来设计测试用例，检查程序中的逻辑通路是否都按预定的要求正确地工作。
黑盒测试是把程序看成一只黑盒子，测试者完全不了解（或不考虑）程序的结构和处理过程。它根据规格说明书规定的功能来设计测试用例，检查程序的功能是否符合规格说明的要求。
6.1.3 测试步骤
软件测试的主要步骤有单元测试、集成测试和确认测试。
1. 单元测试(Unit Testing)
单元测试也称模块测试。通常单元测试可放在编码阶段，程序员在编写好一个模块后，总会对自己编写的模块进行测试，检查它是否实现了详细设计说明书中规定的模块功能和算法。单元测试主要发现编码和详细设计中产生的错误，通常采用白盒测试。
2. 集成测试（Integration Testing）
集成测试也称组装测试，它是对由各模块组装而成的程序进行测试，主要检查模块间的接口和通信。集成测试主要发现设计阶段产生的错误，通常采用黑盒测试。
3. 确认测试(Validation Testing)
确认测试的任务是检查软件的功能、性能及其他特征与用户的需求一致，它是以需求规格说明书（即需求规约）作为依据的测试。确认测试通常采用黑盒测试。
Abstract
In recent years, as China''s rapid economic development, the development of domestic enterprises are increasingly fast, internal management problems also will be more and more. The need for better management concept, better management methods into the portfolio.
Currently, ERP is no longer what is new, at home and abroad have been widely used in many large enterprises. As for the circulation of the domestic small and medium sized industries and enterprises (excluding production chain), the majority are based on Office documents to record the transaction, yet the use of ERP, leading to relatively slow productivity, there is high probability of error information input, management issues such as inconvenience . From these documents the discovery of internal management of enterprises, their management thinking has reached the implementation of ERP in management thinking, but at the cost of ERP is too high, so that businesses can not be implemented.
Keywords ERP;. NET Framework; B / S mode; Business
Abstract
Along with our country economy rapid development, the domestic enterprise''s development also more and more was in recent years quick, the enterprise internal management faced the question more and more were also many along with it.Needs to have the better management idea, the better management way integrates to the enterprise.
At present, ERP already in is not any new things, has applied generally in the domestic and foreign very many major industries. Butregarding the domestic middle and small scale circulation profession enterprise (does not contain produces link), mostly all is uses the Office documents to record business, not yet uses ERP, causes the working efficiency to be relatively slow, appears the information input wrong probability to be very high, manages and so on the questions not not conveniently.From these enterprise internal management document discovery, its management thought had achieved implements ERP the management thought, but on the ERP cost too is high, lets the enterprise be unable to implement.
Key words ERP The. NET frame B / S mode Service
Directory
Summary 1
Abstract 2
Chapter 1 Introduction 7
1.1 Background 7 topics
1.1.1 ERP system to produce the background 7
1.1.2 ERP system, the status of seven
1.2 The purpose and significance of 7
1.2.1 Implementation of ERP system is intended to seven
1.2.2 the implementation of ERP system, the meaning of 8
1.3 System Design Idea 8
ERP products available in the market 1.3.1 Analysis of 8
1.3.2 Circulation ERP system design ideas 9
1.3.3 Circulation ERP systems of innovation 9
Chapter 2 Feasibility Analysis 12
2.1 Circulation of small and medium enterprise business process analysis 12
2.1.1 Circulation of small and medium enterprise business process analysis a brief overview of 12
2.1.2 The business process diagrams 13
2.2 System Development Feasibility Analysis 15
2.2.1 Economic Feasibility Analysis 15
2.2.2 Technical Feasibility Analysis 16
Running 2.2.3 Feasibility Analysis 16
2.2.4 Legal Feasibility Analysis 16
2.3 Chapter Summary 16
Chapter 3 Requirements Analysis 18
3.1 The basic needs of the system description and requirements analysis 18
3.1.1 System description of the basic needs of 18
3.1.2 System Requirements Analysis 18
3.1.3 data flow diagram 18
3.1.4 Data Dictionary 24
3.2 Chapter Summary 35
Chapter 4 Design 36
4.1 System Module Design 36
4.1.1 The system features an overview of 36
4.1.2 system function block diagram 37
4.2 Database Design 39
4.2.1 Data Analysis 39
4.2.2 The detailed design of the database 40
4.3 Chapter Summary 49
Chapter 5 Detailed Design 50
5.1 system development environment 50
5.1.1 B / S structure of the database access mode 50
5.1.2. NET Introduction 51
5.1.3 Introduction 51 relational database
5.2 Design of the overall framework of the system 52
5.2.1 System-Level Design 52 encoding architecture
5.2.2 System Interface style 54
5.3 System Master Interface Design 54
5.4 Sales Management Module 55
5.4.1 orders default settings 55
5.4.2 Input of new orders 57
5.4.3 sales opportunities View 59
5.5 Customer Management Module 60
5.5.1 Price Policy Management 60
5.5.2 Client Group Management 61
5.5.3 Creating new customers 62
5.6 Inventory Management Module 63
5.6.1 Inventory Information Management 63
5.6.2 sold database operations 65
5.7 Receivable Management Module 66
5.7.1 Liquidity balance management 66
5.7.2 Liquidity during the conversion operation 68
5.7.3 money conversion operation 68
5.7.4 Collection operations 69
5.7.5 Receivables Management 70
5.7.6 Liquidity and Statistics 71
5.8 Financial Ledger Module 72
5.8.1 Accounting subjects view 72
5.8.2 Automatic record setting 73
5.8.3 New batches of 75
5.8.4 is not posting batches Show 76
5.8.5 journal Statistics 77
5.9 User Management Module 78
5.9.1 Add a new user 78
5.10''s master file management module 79
5.10.1 During the set 79
5.11 Chapter Summary 80
Chapter 6 System Test and Performance Analysis 81
6.1 System Test 81
6.1.1 The purpose of system testing 81
6.1.2 Testing the basic concept of 82
6.1.3 Test step 83
6.2 System Test 83
6.2.1 Create a new Customer Test 83
6.2.2 Other Module Test 84
6.3 Chapter Summary 84
Chapter 7 main functions of the system instructions 85
7.1 system operating environment 85
7.2 system, landing steps to 85
7.3 Circulation ERP system is mainly instructions 86
7.3.1 During the set 86
7.3.2 Business Set 87
7.3.3 Creating Customer 88
7.3.4 Sales Job 89
7.3.5 Procurement Job 90
7.3.6 Liquidity Management 92
7.3.7 money conversion operation 92
7.3.8 Collection of payment operations and the amount of homework, 93
7.3.9 Liquidity During the conversion 94
7.3.10 accounting entries input operations 95
7.3.11 User Management 96
Conclusion 98
Thanks 99
References 100
Appendix 1 101
Appendix 2 104
Chapter 1
The purpose of a feasibility study is to use the smallest cost in the shortest possible time to determine whether the problem be solved. Feasibility studies need to understand and analyze existing systems, and in summary form to express their understanding of existing systems. Taking into account the operation of small and medium enterprises, combined with practical, conduct feasibility studies need to understand and analyze existing processes, and the existing system processes are given a certain understanding. This chapter will be the system processes and systems analysis of the feasibility of introduction.
2.1 Circulation of small and medium enterprise business process analysis
2.1.1 Circulation of small and medium enterprise business process analysis brief overview of the
Based on the medium and small circulation (not including production processes) and corporate market research found that general business workflow, including Invoicing operations, financial operations, employee information management, operations management, in the existing enterprise environment, the current job management the document management methods are mostly used to record the EXCEL documents transacted, as shown in Figure 2-1. This management approach will produce a lot of files, and manage inconvenient, slow retrieval, or to facilitate statistical analysis of the information given. Taking into account the operation of small and medium enterprises, combined with practical, conduct feasibility studies need to understand and analyze existing processes, and the existing system processes are given a certain understanding.
Figure 2-1 customer purchase records Excel document
2.1.2 business process diagrams
According to circulation of small and medium enterprises business process analysis of the specific situation to be, circulation of small and medium enterprises business processes can be divided into the following major operations: sales operations, inventory jobs, purchasing jobs, accounts jobs, general ledger operations. Interaction between the various operations management. Circulation of small and medium enterprise business processes described as follows
1. Sales jobs: sales operations in the production, the need for sales staff input sales orders, sales staff will complete order entry, will be submitted to the inventory department sales orders from the inventory sales orders according to departmental management details the allocation of stock commodity goods, inventory allocation of management staff after the completion of stock commodity sales orders need to be submitted to the transport sector, transportation management and staff will be assigned to load the transport of goods, sales job is completed. Sales job is completed, need to update the address marketing, sales receivables update phase will have to submit to the financial sector, the sales generated accounting entries submitted to the finance department, with financial staff to manage sales operations and accounting sub-accounts created recorded. In the sales update, also need to save the data in order to conduct statistical analysis of information generated sales opportunities for the sales officers.
2. Procurement practices: The need to purchase, you need to input purchase orders procurement staff, procurement staff will purchase a single entry has been completed, the need to purchase orders submitted to the inventory department, after waiting for procurement of storage. When the procurement of goods arrived in the warehouse, need to be approved storage warehouse under the purchase order. Storage after they have finished, need to purchase update processing, procurement update phase will have to cope with the amount submitted to the finance department, resulting in the purchase accounting entries submitted to the finance department, with finance staff to manage the procurement operations generated accounts and accounting entries .
3. Inventory operation: inventory operations principal operations are in the sales operations of a library operations and procurement practices in the warehousing operation. As well as stock commodity and warehouse management.
4. Accounts operations: Accounts operations in addition to managing sales operations, procurement practices arising from accounts receivable, accounts payable, is also the need for liquidity, income, expenditure management operations, in addition to the need for banks The financial information management. Accounts arising from sales of major updates and purchasing updates can also be manually input a sum accounts, accounts required in the production of income and expenditure of the funds to write-off accounts.
5. Ledger operations: general ledger sub-operations were recorded mainly from sales of updates, procurement update, updating the accounts work, you can also manually input their own amount of accounting entries. When the input end an entry accounting entries will be stored in a database, in the follow-up operations recorded in the statistics of sub-processing, statistical reports, including: classification and a breakdown of statistical reports, general ledger, statistical reports, journal statistical reports, cash-flow statistics Statements.
Chapter 6 System Test and Performance Analysis
The design stage, from an abstract concept, step by step to design a specific software system, until in a proper programming language to write executable program code. However, in the testing phase testers efforts to design a series of test programs, the objective is to "damage" has been the construction of a good software system - trying to prove wrong the program does not work correctly in accordance with pre-determined requirements.
6.1 System Testing
Through requirements analysis, design and coding phases of the development, got the source code, start to get into the software testing stage. However, in various stages of testing before the software products may be left behind many errors and shortcomings, if not in time to identify these errors and shortcomings, and its correction, the software product will not work properly, and even lead to a huge loss. At present, the program has not yet been fundamentally proven the correctness of the solution, so software testing is still the software errors and deficiencies found in the principal means.
Test is a very hard work, their workload or about software development for more than 40% of the total workload, in particular, some related to human life and safety software.
6.1.1 The purpose of system testing
System testing is designed to identify problems of the later problems. The goal is to discover an error in the program implementation procedures of the process, software testing involved in the first issue is to confirm and validate the software, design, and implementation process of the logical correctness and the discovery of problems in software products, and through Test continuously improve and perfect the quality of software products. Software testing involved in the second issue is the troubleshooting, also known as debugging. The purpose of troubleshooting is to diagnose the nature of procedural errors and their causes and to be corrected. Software Testing The third issue is related to software reliability evaluation. The software reliability is efficient and correct operation guarantee.
A correct understanding of the objectives of the test, the test objectives determine the test program design. Accumulation in the test phase the test results, you can use a more formal approach to statistical analysis. System reliability model uses the error rate data, estimate the future errors and further to predict the reliability of the system.
If the program is to show the right to conduct tests, they will design some difficult to find errors of the testing program; On the contrary, if the test is to discover errors in the program will strive to design the most exposed to the wrong test program.
ERP from the circulation system of the actual situation and take into account the characteristics of this system, the software testing objectives and requirements of different users can login through the Internet and conduct a variety of operations; to the normal access to remote databases and to ensure data transmission security and the right sex; management procedures to carry out background check, add, or delete operation.
6.1.2 Testing the basic concepts of
1. Testing purposes
The purpose of software testing is to discover as much as possible software products (mainly refers to the program) errors and shortcomings.
Explicit purpose of testing is a very important matter, because in the real world, there are many pairs of tests vague or erroneous point of view, these views seriously affect the test carried out smoothly.
Some people think that test is to prove that program is correct, that program is no longer an error is proved to be unrealistic. Because the program to pass the test to find all the errors must exhaustive of all possible input data to check whether they produce the correct results. For example, a need for three 16-bit integer input data word length of the program, all the combinations of input data there are about 3 × 1014 species, if the test time for each data 1ms, then even if 365 days a year, every day 24 hours to test, it takes about a years time.
2. Test
To test this, we must have test data (or input data), we must also test data and gives the group what should be the output of results, we call it the expected results. In the test of actual output compared with the expected results, if the difference indicates an error was found. Therefore, test cases from the test data and expected results of composition.
In order to find program errors, every effort should be designed to expose the wrong test. A good test case is very likely to find that to date have not yet discovered the wrong test case. A successful test is found so far been found errors in testing.
3. White-box testing and black-box testing
Testing is the key test case design, its methods can be divided into two categories, white-box testing and black box testing.
White-box testing is to program as packed in a transparent white box, test procedures were fully aware of the structure and process. It is based on the program''s internal logic to design test cases, check whether the program logic of access requirements are scheduled to work properly.
Black box testing is to program as a black box, testers did not understand (or consider) program structure and process. It is based on functional requirements specification to design test cases, check whether the program''s functionality specification requirements.
6.1.3 Test step
The main steps in software testing are unit testing, integration testing and validation testing.
1. Unit Testing (Unit Testing)
Unit testing, also known as module. Unit testing is usually available on the encoding phase, a good programmer in the preparation of a module will always be prepared for their test module to check whether it implements the provisions of the detailed design specifications of the module functions and algorithms. Unit testing code and detailed design of the major findings arising from errors, usually white-box testing.
2. Integrated Test (Integration Testing)
Integration testing, also known as final assembly and testing, it is a module assembled by the testing procedures, the main check the interface between the module and communications. Integration tests are mainly found in the design phase produces the error, usually black-box testing.
3. Validation Testing (Validation Testing)
Validation testing task is to check the software functionality, performance and other characteristics consistent with the needs of users, it is based on requirements specification (ie, Requirements Specification) as a basis for testing. Validation testing usually black-box testing.
