Six principles of OA Design

1. Principles of Practicality

Practicality means pragmatism and inaction, and focuses on solving actual problems. It implements excellent and fine-grained core functions, and combines common auxiliary functions to quickly and conveniently deploy and use them, and saves investment, reduce risks. There are a bunch of functions available for Oa. What customers, personnel, finance, assets, knowledge management and so on are all done, but they are very rough and useless.

2. Usability Principle

This requires that the software has a friendly interface, clear structure, reasonable procedures, and clear functions. Menu operations fully meet users' visual processes and usage habits. Easy to understand, easy to learn, easy to use, easy to maintain, easy to upgrade, to achieve a "dumb camera" operation, the implementation, training costs and cycle to a minimum. Ease of use is of vital significance to the smooth implementation and use of software. The lack of ease of use leads to frequent project failures.

3. Principles of Advancement

OA is an advanced tool, so we should adopt advanced technical architecture and design methods to integrate advanced management ideas, with a high level of structure, flexibility, scalability, compatibility, and upgrading, meet the technical development trend and meet user growth needs. It should be noted that you should avoid being misled by the "only technical theory" and "only conceptual theory". Either technology or concept should prevail for you.

4. Stability Principle

After OA is imported into the enterprise, it will produce a lot of dependencies. Therefore, the system should be strictly tested from the underlying database to the functional layer. The database is stable, functions are smooth, and data is not congested or lost, it can run smoothly on different hardware, networks, operating systems, and operating habits for a long time. It is suitable for large-scale users to ensure the normal operation of daily office work.

5. Security Principles

OA systems often store the core information of enterprises and some confidential information of individual users, which requires the system to effectively prevent various external virus attacks and malicious attacks, strict and meticulous access permission management. Internal data has multiple backup methods. If necessary, users are allowed to perform various auxiliary data encryption, password protection, identity authentication, and other control measures.

6. scalability Principle

Most users will add some functional modules or other OA software systems after the OA period, which requires the software to be well extended and provide open and standard interfaces, the system can be flexibly connected to a third-party system without affecting the normal use of the system, so as to interconnect different application systems and build a comprehensive information processing center platform for users.

Based on the six design principles, we found that to reflect the perfect system performance for users, we must take the application as the core and take the three main lines of practicality, ease of use, and ease of use as the starting points, A harmonious unity of technology, application, and development.

Although these six standards are very important, there is no fish in the "water to the Qing Dynasty". There is no perfect OA, And it is enough to do a few of them. In addition, different customers have different requirements and features, and different concerns. As long as you set the focus to "excellent" and set non-focus to "qualified", it is not difficult to find the appropriate OA.