【Abstract】 At present, OA system software occupies a certain proportion in software projects. This paper mainly aims at the requirements of OA system software, and gives the corresponding basic ideas of software testing and analysis.
【Keywords】 Office automation system, software requirements
· Introduction to Office Automation System
Office automation is Office Automation, referred to as OA.
At present, the popular office automation system mostly adopts multi-layer architecture, and its application service structure is located on the middle layer. The client accesses the system through the commonly used IE browser interface, which has the characteristics of unified interface, simple access, easy upgrade and expansion.
As far as the above characteristics are concerned, the test of the office automation system can be organized using the test strategy of the B/S structure.
Next, we will analyze how to organize the test analysis for the office automation system from several stages of the software engineering process - requirements, design, and coding.
· Organize test analysis according to the characteristics of OA requirements and design
The office automation system is good at handling the needs and design of administrative office applications such as announcements, official documents and other circulation types, as well as the needs and design of relatively independent personal related materials, business cards, notes and other personal affairs.
The authority management of office automation system software is another feature that is different from other application software. The system needs to provide users with the function of setting different permissions and access permissions. The administrator can adjust the access permissions of each functional module to set some functions that general users can use and some functions are not allowed; and create and log out for employees. Accounts and access rights. Improve the security of the information of the enterprise system and prevent unauthorized persons from entering the system illegally.
· Administrative office needs and design for flow transformation
The administrative office needs and design of the flow transformation usually include: drafting, reviewing, signing, counter-signing, planning, signing, electronic signature, assigning, returning, reference, filing, printing, destruction and other business processing functions. The functions of complex user rights and access permissions are also involved in the business process processing of the administrative office.
In view of this situation, it is best to use the existing company system to analyze and design the test requirements. There are two advantages to doing this:
· Easy to communicate.
The roles and people in a ready-made company system are much easier to understand and communicate than each tester constructing his own virtual user rights and access permissions.
When a defect is discovered during test execution, the described defect makes it easier for developers and testers to communicate.
· Test data is easy to prepare and less prone to discrepancies.
Since the objects used by the OA system are all employees of the entire company or employees of a certain department, if we use the existing company system, we only need to prepare a unified set of test data to meet the requirements of all test objects.
When the testers communicate, they will not cause unnecessary differences due to the different constructed data, and artificially increase the barriers of communication within the test group.
· Designed for independent personal affairs needs and designs
Independent personal affairs usually include: maintaining and viewing personal and public event schedules, and automatically reminding all personal to-do items, allowing users to query various information. However, personal affairs usually only allow users to maintain and view personal affairs, and do not allow other users to maintain and view. In some current OA systems, even superusers including administrators cannot maintain and view private personal transactions.
In view of the above special circumstances, when analyzing and designing test requirements, we must first consider uniformly marking different users with special marks. Next, when preparing the test data, it should be avoided that different users have the same personal information and related materials, so as to avoid the testers falling into a state of confusion during the test execution process, and even the testers themselves do not know which one is used. user's information.
· Organize test analysis for the functional characteristics of OA coding
Common OA system functional modules mainly include four parts: administrative office, personal affairs, comprehensive information, and basic services.
· Administrative office
Administrative office usually includes modules such as document receipt management, document management, file management and meeting management. Some OA systems also include reception management and office resource management modules.
这四个模块是典型的流转型模块，它们都有流程定义、登记（或拟稿）、办理、拟稿、审核、签收、会签、拟办、签批、电子签名、交办、退稿、备查、提交归档、打印、销毁、归档、查询、流程跟踪、查看意见、重定位等操作过程。
以收文管理为例，主要对公文进行登记和处理，包括内部公文和外部公文。在登记收文过程中提供了多种种方式，比如文件引入、电子公文调入、扫描和直接输入，并将登记后的收文送领导批示或阅读（批示的流程完全可以根据用户的需要自己定义，也可以使用系统管理员已经定义好的公文批示流程），处理结束后将文件进行归档。管理人员可以对收文处理全过程进行监督、催办、重定位，也可以随时进行文件流程跟踪及查看其所有领导的批示意见、批示时间。
针对这些情况，在进行测试分析和设计时，首先按照上面提到的根据现成的公司体制进行分析和设计的测试数据，然后将各个领导是否兼职的情况区分开来。通常建议准备这样两套数据：
·领导不兼职
领导不兼职的情况，相对较简单，即每个领导只负责一个批示。
在执行测试过程中，还需要重点注意批示的并行和串行的情况。
· 领导兼职
领导兼职的情况，即每个领导可能负责不同过程中多个批示，是流转型模块测试的一个难点，需要特别注意。
跟上面的情况一样，同时也要考虑批示的并行和串行的情况。在测试执行过程中，其组合方式是否能够全面覆盖，与测试人员的经验、对模块的需求和设计熟悉程度、测试数据准备是否充分以及测试人员是否考虑周到全面等因素息息相关。
·个人事务
个人事务通常包括：待办工作、日程安排、个人资料、个人名片、个人记事本、外出声明等模块。有的 OA 系统还包括个人邮件、及时消息模块。
个人事务以其独立性，完成个人日常的办公工作，例如批阅各部门上报的各种公文，评阅同事交流的各种文件内容，回复或发送电子邮件，起草各类报告，查看个人的活动日程、外出等安排，系统能自动提醒待办事项。
以个人名片为例，用户可将名片登记并进行管理查询和打印，同时可根据需要将部分名片共享，供他人使用。每个人只能看到自己的名片集及共享的名片集，通过所有由个人收集的名片以及整个单位的名片总集，可很快找出所需要联系的名片主人，并方便地通知他们参加会议或发送邮件等等。
在进行测试分析、设计和执行中需要特别考虑：
· 新建或修改的名片时对于输入重复的名片是否给予提示警告；
· 新建或修改的名片时个人维护的私有名片是否能被其他人看到或使用；
· 个人删除私有名片时是否影响到其他用户的名片；
· 共享的名片是否可以被其他人正确查看和使用；
· 单位的名片集修改后，是否正确影响个人的单位名片集；
· 给需要联系的名片主人联系时，是否可以正确联系上，其联系内容是否显示正确；
·综合信息
综合信息通常包括：建议管理、电子论坛、网上调查、电子贺卡、信息采集等模块。
以信息采集为例，信息采集可以通过各种渠道，从所有可利用的信息源收集办公需要的信息，从各种媒体采集各种相关信息后作为原始信息记录在案，经过筛选整理后编辑成各种主题的信息刊物。同时信息刊物也支持套红头转入行政办公的公文模块中。可以方便地查询、检索信息刊物及其所有原始信息内容。并对信息采用和阅读情况、次数进行统计。
在进行测试分析、设计和执行时要重点考虑：
· 从信息来源收集信息时，是否能正确完好的保存其原始信息的内容和格式；
· 整理后的信息是否能正确完好的保存其原始信息的内容和格式；
· 整理后的信息是否能正确转入公文流程中；
· 基础服务
基础服务包括：人员注册、部门设置、数据维护等模块。
以数据维护为例：系统为系统的管理员提供了多项数据维护的服务。可以对一些常用的数据进行设置，包括用户登录名 / 用户密码组合方式、用户登录名 / 用户密码长度、主题词、常用意见、自动编号、存储大小、存储时间和公文格式，也可以对行政办公中所要使用的各个流转模块的流程进行预定义。
在进行测试分析、设计和执行时要特别考虑：
· 用户登录名 / 用户密码组合方式设置是否正确；
· 用户登录名 / 用户密码长度设置是否正确、有效；
· 存储大小设置是否正确、有效；对于超出设定的存储大小系统是否能正确提示；
· 预定义的行政办公中各个流转模块是否能被正确应用；
· 小结
OA 系统的某些业务与其他知识管理系统相类似，但由于其鲜明的特点，目前已经自成体系。
本文介绍的测试分析主要与 OA 特有的业务处理方法紧密联系，作为测试人员介入 OA 项目时如何有重点的进行测试分析。
与其他 B/S 结构的系统所要进行的界面测试、边界测试、非法校验、字段限制等方法一样，在实际执行测试过程之前都需要一一进行分析，在此就不赘述了。