【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 personnel 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 discrepancies due to 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.
These four modules are typical flow transformation modules. They all have process definition, registration (or drafting), processing, drafting, review, signing, countersigning, planning, signing, electronic signature, assigning, rejecting, checking, and submitting. Filing, printing, destroying, archiving, querying, process tracking, viewing comments, relocation and other operational processes.
Taking document receipt management as an example, it mainly registers and processes official documents, including internal documents and external documents. In the process of registering and receiving documents, a variety of methods are provided, such as document introduction, electronic document transfer, scanning and direct input, and the registered documents are sent to the leader for instructions or reading (the process of instructions can be completely defined according to the needs of users, or You can use the official document approval process that the system administrator has defined), and archive the document after processing. Managers can supervise, urge, and relocate the entire process of receiving documents, and can also track the document process at any time and view the comments and instructions of all their leaders.
In response to these situations, when conducting test analysis and design, firstly according to the test data mentioned above based on the existing company system for analysis and design, and then distinguish whether each leader is part-time. It is usually recommended to prepare two sets of data as follows:
· Leaders do not work part-time
The situation where the leader does not work part-time is relatively simple, that is, each leader is only responsible for one instruction.
In the process of executing the test, it is also necessary to pay attention to the parallel and serial conditions of the instructions.
· Part-time leaders
The situation where the leader is part-time, that is, each leader may be responsible for multiple instructions in different processes, is a difficulty in the testing of the flow transformation module, which requires special attention.
As in the above case, the parallel and serial conditions of the instructions should also be considered. In the process of test execution, whether the combination method can be fully covered is closely related to the tester's experience, familiarity with the module requirements and design, whether the test data preparation is sufficient, and whether the tester is thoughtful and comprehensive.
· Personal affairs
Personal affairs usually include: to-do work, schedule, personal data, personal business card, personal notepad, outgoing statement and other modules. Some OA systems also include personal mail and instant message modules.
With its independence, personal affairs can complete personal daily office work, such as reviewing various official documents reported by various departments, reviewing various documents exchanged by colleagues, replying or sending emails, drafting various reports, and checking personal activity schedules, Going out and other arrangements, the system can automatically remind to-do items.
Taking personal business cards as an example, users can register business cards, manage, query and print them, and at the same time, they can share some business cards for others to use according to their needs. Everyone can only see their own business card set and shared business card set. Through all business cards collected by individuals and the business card collection of the entire unit, the owner of the business card to be contacted can be quickly found, and they can be conveniently notified to participate in the meeting or send mail etc.
Special consideration is required in conducting test analysis, design and execution:
· Whether a warning is given for inputting duplicate business cards when creating or modifying business cards;
Whether the private business card maintained by the individual can be seen or used by others when creating a new or modified business card ;
· Whether it affects the business cards of other users when an individual deletes a private business card;
Whether the shared business card can be properly viewed and used by others;
· After the unit's business card set is modified, whether the personal business card set is correctly affected;
When contacting the owner of the business card who needs to be contacted, whether it can be contacted correctly, and whether the contact content is displayed correctly;
· Comprehensive information
Comprehensive information usually includes: suggestion management, electronic forum, online survey, electronic greeting card, information collection and other modules.
Taking information collection as an example, information collection can collect information needed for office from all available information sources through various channels, collect various relevant information from various media and record it as original information, and edit it into a file after screening and sorting. Information publications on various topics. At the same time, information publications also support the transfer of the red head to the official document module of the administrative office. Information publications and all their original information content can be easily searched and retrieved. And statistics on the use and reading of information, the number of times.
Important considerations when conducting test analysis, design, and execution:
Whether the content and format of the original information can be properly and intactly preserved when collecting information from information sources ;
· Whether the sorted information can properly preserve the content and format of the original information;
· Whether the sorted information can be correctly transferred to the official document process;
· Basic service
Basic services include: personnel registration, department setting, data maintenance and other modules.
Take data maintenance as an example: the system provides a number of data maintenance services for system administrators. Some commonly used data can be set, including user login name/user password combination, user login name/user password length, subject words, common comments, automatic numbering, storage size, storage time and document format, as well as administrative office The flow of each flow module to be used is predefined.
Special consideration should be given when conducting test analysis, design and execution:
Whether the combination of user login name and user password is set correctly;
Whether the user login name/user password length setting is correct and valid;
Whether the storage size setting is correct and valid; whether the system can correctly prompt the storage size beyond the set;
· Whether the various circulation modules in the predefined administrative office can be correctly applied;
· Summary
Some businesses of the OA system are similar to other knowledge management systems, but due to its distinctive features, it has become a self-contained system.
The test analysis introduced in this paper is mainly closely related to the OA's unique business processing method, and how to focus on the test analysis when a tester is involved in an OA project.
Similar to the methods of interface testing, boundary testing, illegal verification, field restriction, etc., which are required for other B/S-structured systems, they all need to be analyzed one by one before the actual testing process, and will not be repeated here.