1, Html (Css framework such as CSS, JavaScript and JQuery is better, and beginners don't need it) 2, Php language, access is written in PHP, this is a must 3, database knowledge and database foundation are enough, access uses MySQL 4, server configuration, mainly installing access OA, and defining the directory. Flexible use of 5, access OA management, this is very simple, it is easy to master these basically, there is no problem in the secondary development of access, and then the understanding of the table structure in the database needs to be accumulated slowly.
Not many, but you need to accumulate practice to reach the level of free development, for reference only. The workflow part is not real development. When you are a novice, it takes some time to understand. Count one.
2. What problems should be paid attention to when developing 2. OA system?
4. Consider the price, learn more, compare more, and try to choose the most cost-effective one.
Third, the trial stage 1, in which all employees, including leaders, really participate in the use and regard the trial as an online trial; 2, functional departments targeted trial, detailed and in-depth use of functions, timely find problems; 4. Commissioning online stage 1, when enterprises reach an agreement on specific issues, and then communicate with OA implementers; 2. For the problems that can be solved, remind the other implementer to realize them within the planned time; 3. For the problems that can't be solved, ask the implementers to give relevant reasons, so as to compare and find information and find other solutions; V. Training phase 1. System administrator training. It is suggested that software providers conduct one-on-one special training; 2. For the training of ordinary users, it is suggested to carry out targeted training according to functional departments; 3. It is best to explain the training and solve the problems in operation alternately. 6. In the daily operation and maintenance stage, the system administrator should solve the user's problems in time, and contact the developer's implementer in time if they cannot be solved. System administrators should gradually improve their ability to solve problems in the cycle of constantly appearing problems to ensure the implementation effect of OA system.
For the implementation of OA system, there are still many problems that need to be paid attention to in practical application. The person in charge of the project must fully understand the actual management situation of the enterprise, fully study the OA products, and carry out them in a planned, step-by-step and strict manner to ensure the successful implementation of the OA system. There are many manufacturers of OA products in China, including Zhiyuan software, access software with simple management, Jinhe, Jinjin, Pan Wei and so on, which are good at platformization of mobile and business applications.
Zhiyuan Software (OA) has ranked first in the market share for nine consecutive years. It is a member company of UFIDA, and its products are good. Can move OA office, can use mobile phone, Ipad to handle official documents, for approval. Zhiyuan's solutions for various industries can be found on their websites, and they are still complete.
3. Seek the development process of oa office system
Here I will talk about the development process of developing OA office system with rapid development platform, without code configuration.
This rapid development tool can solve the problem that enterprises can develop a management system that really conforms to the company's reality without knowing programming but knowing business. Moreover, this development platform can adjust the functional modules at any time when the company's business or management changes in the future, and can also add other modules as needed.
The first step: requirement analysis: I called all their business-related departments to hold several meetings, sorted out and unified the functional requirements of each department, and wrote a functional requirements specification, listing in detail the actual problems to be solved and the goals to be achieved by the software. They demand that software can solve their practical problems and bring real value.
For example, directly bring them more orders, help them find and retain customers, save labor costs, prevent unnecessary waste in business, and finally realize the growth of the company's profits. In my opinion, if a software can't bring substantial economic value, it is better not to use it if it is only used to decorate the company's facade and improve work efficiency.
This is also the reason why they don't like some finished software and choose custom development. The situation of each company is different, and finished software vendors often can't know the pain points of each customer, so the products they make are not really suitable for customers.
Only by their own targeted development can we really solve the problem. Only customers know what their company needs most, how to acquire and retain customers, how to design business processes and so on.
The most suitable software is to develop some practical functions. Through this project, I realize that the process of writing software requirements specification is very important, which determines whether the future development process will take a detour, whether it will waste time and money because of developing unnecessary functions, and whether there will be conflicts between program function modules.
A lot of energy has been spent on the preparation of the demand statement, and there is a feeling that sharpening the knife does not mistake the woodcutter. Finally, after all employees unanimously passed this demand statement, we decided to proceed to the next step.
Step 2: Develop a proposal. A development proposal is to transform the functional requirement specification into a specific action plan that can be developed. I have compiled according to the development rules of the development platform, optimized the functional modules in the software requirement specification, analyzed the data structure, data relationship and operation logic of each module, combed the business processes among each module, and finally planned the interface styles of each module according to the actual situation of the personnel in each business department. My development plan is also very detailed, but it feels easier than the functional requirements specification. After all, the general direction is already there.
In the development plan, I plan and name all the tables and fields in the data structure, including their data types and lengths, make tables, and explain the data sources and editing methods of each field. I forgot to explain before. Although I don't know how to program, I still know a little about the database because of my previous experience in managing software operations. However, I have enough knowledge of the database when developing with Tianzong rapid development platform. If you need more complicated SQL statements in the future, please search online.
The development plan is very important for the later system development. The following development process is actually the process of configuring the development plan content on the rapid development platform. Step 3: Make and test the development plan, and the next development will be very easy. In fact, it is the process of configuring the content of the development plan to the development platform, which is why I found such a development platform to develop this system.
Developing software with configuration development platform is quite simple and fast, and the general module can be done in three steps. The first step is to set module information, the second step is to set form properties, and the third step is to set each field in the table. Maybe you still don't believe me when I say this, okay.
Above! Tianzong rapid development platform can be divided into development background and application prospect. As the name implies, the development background is for developers, and the application foreground is where the developed system is used.
Ok, let's enter the development background, as shown below: Click module design, and you can start configuring the module. Choosing the module type is the key to this step, that is, what kind of module you want to develop. There are many function templates built into the development platform. What you need to do is to analyze which template the module you want to develop belongs to, and you can realize your module interface and function by choosing a template.
There are many kinds of modules, including all aspects of commonly used management software, as well as special module function templates and operation manuals, which you will know when developing. After defining a module, you can define a table in the module. A module may have multiple tables, define them one by one and establish the relationship between them.
As shown below: In the process of form definition, you need to set the form editing interface style and some data rules. After the form is set, it is time to set the fields of each table.
As shown below: Through three-step configuration, a functional module is basically completed. Isn't it simple and quick! Is the whole development process completed by configuration?
Of course, the above are some of the most basic configurations. For modules with complex functional requirements, more detailed configuration may be required. Because the configuration development platform omits code writing, the development speed is greatly improved. Because the interfaces are automatically generated by the middleware of the development platform according to the configured business parameters, there is no need to write a set of codes for each interface, so the error rate is greatly reduced, and the performance and stability of the software are naturally guaranteed.
Step 4: Write the operation manual. After the system is developed, there is still a finishing work that cannot be saved, that is, writing an operation manual. Fortunately, I like to write some blogs when I have nothing to do, and I am not afraid to write.
The operation manual is for users to learn and operate. In the operation manual, I listed the operation process of the system and its precautions in detail. Afterwards, I learned that the operation manual is also one of the important factors for the formal use of this system, because the operation manual I wrote is vivid and clear, and my colleagues who operate this system will soon understand and get started. My experience is that the earlier the operation manual is written, the better. It is best to write it out at the same time of development, and some key contents in the development process should be recorded immediately for future reminder.
4.OA system development process
At least 0.27 yuan/day, you can open Baidu library members and view all the contents in the library >
Original publisher: ulei3 10
System development In order to ensure that the software system is completed on time and with good quality, the design and development of the system strictly abide by the specifications of software engineering and CMM2 software process management, and the waterfall model is adopted for project development, and the workflow shown in the following figure is formulated. Every stage has a review. Every review is a test of the work at this stage, and only through the review can we enter the next stage. Through strict evaluation, the progress and quality of system development can be effectively guaranteed. The process of system development is shown in the figure, which describes the sequence of each stage in the development process in detail. Figure 6-9 System Development Flow (1) Development Plan According to the user's requirements for system functions and business management needs, the technical scheme and development plan of this system are determined on the basis of fully analyzing the current technologies and platforms for the development and design of provincial information management systems, which provides a basic outline scheme for the construction and implementation of the system and ensures that the functions of the system meet the needs of applications. At the initial stage of system implementation, it is necessary to have a basic understanding and analysis of system functions, formulate a perfect system design scheme, analyze and design various software and hardware platforms for system application, provide reasonable platform selection scheme and technical scheme for system implementation, do a good job in technical research of system development and implementation, and determine the feasibility of system development. (2) System survey and demand analysis survey and user demand analysis are the keys to successful system design. This process is that the customer describes to the system designer the work to be completed by the system; In addition, the customer's business process should be described to the system designer. System designers should understand the customer's ideas, and how much they know basically determines the success of the system, because understanding the customer's ideas can analyze the customer's ideas; Reasonable in practical conditions or technology; What functions can't be realized by the computer; Which functions should be implemented flexibly. From the customer's point of view.