What are the things that need to be considered when designing and developing a complete user system?

Step 1: Demand research and analysis 1 The relevant system analyst has a preliminary understanding of the requirements from the user, and then lists the large functional modules of the system to be developed in word, what are the small functional modules of each large functional module, and when some requirements are more clearly related to the interface, a small number of interfaces can be preliminarily defined in this step. 2. The system analyst has an in-depth understanding and analysis of the requirements, and uses word or related tools to make a document of the functional requirements of the document system according to his own experience and needs.

This document will clearly use the general functional modules of the system, what are the small functional modules of the large functional modules, and also list the relevant interfaces and interface functions. 3 The system analyst reconfirms the requirements to the user. Step 2:

Outline Design First of all, developers need to conduct a schematic design of the software system, that is, system design. The outline design needs to consider the design of the software system, including the basic processing flow of the system, the organizational structure of the system, the division of modules, the allocation of functions, the design of interfaces, the design of operation, the design of data structure and the design of error processing, etc., so as to provide the basis for the detailed design of the software. Step 3:

Detailed Design On the basis of the outline design, the developer needs to carry out the detailed design of the software system. In the detailed design, the main algorithms, data structures, class hierarchies and invocation relationships involved in the implementation of specific modules are described, and the design considerations of each program (each module or subprogram) at each level of the software system need to be explained for coding and testing. It should be ensured that the requirements of the software are fully distributed to the software as a whole.

The detailed design should be detailed enough to be able to be coded according to the detailed design report. Step 4: Coding In the software coding stage, the developer starts to write specific programs according to the design requirements for data structure, algorithm analysis and module implementation in the "Software System Detailed Design Report", and realizes the functions of each module respectively, so as to realize the requirements for the function, performance, interface, interface and other aspects of the target system.

Step 5: Test Test the written system. It is handed over to the user to use, and the user confirms each function one by one after using it.

Step 6: Preparation for software delivery After the software test proves that the software meets the requirements, the software developer shall submit to the user the target installer, the data dictionary of the database, the "User Installation Manual", the "User Guide", the demand report, the design report, the test report and other products agreed in the contract between the two parties. The User Installation Manual should introduce in detail the requirements of the installed software for the operating environment, the definition and content of the installed software, the specific installation steps on the client, server and middleware, and the system configuration after installation.

The User Guide should include the use process, operation steps, corresponding business introduction, special tips and precautions of each function of the software, and should also give examples when necessary. Step 7: Acceptance User acceptance.

Alone in a foreign land as a stranger, every festival is full of relatives.

The following main issues should be considered in the design of the system:

When designing a system, it is necessary to consider the object system to be designed and the environment around the object system, the former is called the internal system, the latter is called the external system, there is a mutual support and mutual constraint relationship between them, and the combination of the internal system and the external system is called the overall system.

Therefore, in the system design, it is necessary to adopt the thinking principle of combining internal design and external design, and comprehensively consider the function, input, output, environment, program, human factor, and material medium of the overall system to design the overall optimal system.

The system design must adopt the thinking principle of combining internal design and external design, and comprehensively consider the function, input, output, environment, program, human factor, and material medium of the overall system to design the overall optimal system.

System design principles.

1. The principle of stage development.

2. The principle of ease of use.

It is convenient for Internet customers to browse and operate, minimize the burden of background management personnel, and achieve automatic processing of part of the business.

3. The principle of business integrity.

It can make timely and correct responses to special situations in business progress to ensure the integrity of business data.

4. The principle of business standardization.

At the same time of system design, it also formulates a relatively perfect specification for the future business process, which has strong practical operability.

5. Scalability principle.

The system design should take into account the needs of the future development of the business, and the design should be as concise as possible, and the coupling degree between each functional module should be small, so as to facilitate the expansion of the system. If you have a legacy database system, you need to consider compatibility.

This is too much, depending on what system design you do, the following is a reference.

1. Considerations for the runtime structure of the program:

1) Conformity of requirements: correctness and completeness; functional requirements, non-functional requirements;

2) overall performance (memory management, database organization and content, non-database information, task parallelism, network multi-person operations, key algorithms, impact on performance of interfaces with networks, hardware, and other systems);

3) Operational manageability: it is convenient for the operation of the control system, monitoring the system status, and error handling; simplicity of communication between modules; Not the same as maintainability;

4) Compatibility with other system interfaces;

5) Compatibility and performance with network and hardware interfaces;

6) System security;

7) System reliability;

8) Adjustability of business processes;

9) Adjustability of business information.

10) Ease of use.

11) Consistency of architecture style.

Note: Runtime load balancing can be considered from the aspects of system performance and system reliability.

2. Considerations of the organizational structure of the source **:

1) Development manageability: it is convenient for the division of labor (module independence, load balancing of development work, schedule optimization, prevention of the impact of personnel turnover on development), conducive to configuration management, rationality and moderate complexity of size;

2) Maintainability: different from operational manageability;

3) Scalability: upgrade, expansion and expansion performance of the system solution;

4) Portability: different clients, application servers, database management systems;

5) Compliance with requirements (organizational considerations of the source).

Conformity of requirements: correctness, completeness; Functional requirements, non-functional requirements, overall performance.

System security.

Reliability interfaces with other systems.

Scalability.

Based on our experience in software development, we would like to introduce it to you.

First, the small details that can easily lead to failure:

1. I don't know what I want, and I want to do it, and I want to do it, but I think it's very simple to make a software, so it's vague when describing the requirements3. Lack of patience, I don't understand and never think about how complicated what I want to do4. I don't know the specific functions of what I want to do, and I have to guess by the developer.

Second, the details to be paid attention to in the customized development of software outsourcing.

1. All fees must be clear before signing the contract.

2. Determine which terminals (Android or iOS) the software needs

3. When designing UI, avoid ambiguity, and be sure to determine the interface of each UI 4. The progress of software development, how many days will it take to deliver the beta version, how many days to deliver the official version, etc.

Software development is generally divided into five phases:

1.Problem definition and planning.

This stage is a joint discussion between software development and requirements, mainly to determine the development goals and feasibility of the software.

2.Requirements analysis.

In the case of determining the feasibility of software development, a detailed requirements analysis is carried out on the individual functions that need to be implemented in the software. The requirements analysis phase is a very important stage, and if this stage is done well, it will lay a good foundation for the development of the entire software project. "The only constant is the change itself", and the software requirements are constantly changing and deepening during the development process of the software, so we must customize the requirements change plan to cope with this change to protect the overall project as it happens.

3.Software design.

In this stage, the entire software system should be designed according to the results of the requirements analysis, such as system framework design, database design, etc. Software design is generally divided into general design and detailed design. Also the software design will lay a good foundation for software program writing.

4.Program coding.

This stage is the transformation of the results of the software design into a program that can be run on a computer**. In the program coding, it is necessary to develop a system.

1. Write specifications that meet the standards. In order to ensure the readability and easy maintenance of the program. Improve the operational efficiency of the program.

5.Software testing.

After the software design is completed, it is necessary to conduct rigorous testing, and find and correct the problems in the software throughout the software design process. The whole test stage is divided into three stages: unit test, assembly test, and system test. The test methods mainly include white-box testing and black-box testing.

According to the actual analysis of the actual situation, the development of a set of OA system needs to consider what kind of function is developed, the complexity of the function, the number of functional modules, the difficulty of development, the workload, and the labor cost. Depending on the situation, it will range from tens of thousands to hundreds of thousands, or even more.

For the enterprise as a whole, the OA system can meet the needs of back-end integrated management and front-end personalization; Realize business scenarios and office automation; Meet the needs of daily collaborative office and grasp the company's business trends in real time; Its rich mobile application scenario experience and convenient applet experience can realize paperless office in different places, save time and achieve efficient office, which is a good OA system.

In detail, a good OA office system function module is mainly composed of the following parts:

1. Personal office function module.

Personal office mainly plays the role of auxiliary work in the OA system.

The main functions that can realize the personal office functions of the OA system are: application process, approval process, view message notification, add schedule management, writing, view address book function, modify personal settings and other functions.

2. Public information management function module.

The OA system has multiple modules for management, each module is managed by a different department system, which can realize attendance information statistics, detailed process records for the use of public assets, and detailed and clear records for the statistics and archiving of enterprise contracts. It can simplify office processes and save paper.

3. OA system workflow.

OA system workflow, simply put, is to realize the OA system process in which a group of people completes all the work carried out by a certain business in multiple steps and transfers (interacts) the work. Almost all business processes are workflows, especially the processing of official document approval and circulation. OA system process, that is, each work in the form of a process, initiated by the initiator (such as the draughtsman) of the process, after the newspaper department and other departments of the processing (such as signing, countersigning), and finally reach the end of the process (such as issuing documents, archiving and storage).

The specific process and system functions include: document management, document circulation, and document receipt management.

To sum up, an OA system can meet the needs of enterprises for daily office, mainly to achieve paperless office, with main functions: process approval, attendance, notice announcement, voting management, administrative management, personnel management, asset management, project management, customer management, etc. is a good OA system, which effectively integrates the internal and external branches (subsidiaries) of the enterprise and various departments and institutions and other organizations and groups, and jointly provides great functional support for the realization of automated office and collaborative and convenient office of the enterprise.

The system development process is divided into: requirement analysis - outline design - detailed design - coding - system testing - system delivery - user acceptance - maintenance.

Requirement analysis: The relevant system analyst has a preliminary understanding of the user's requirements.

The outline design needs to consider the design of the software system, including the basic processing flow of the system, the organizational structure of the system, the division of modules, the allocation of functions, the design of interfaces, the design of operation, the design of data structure and the design of error processing, etc., so as to provide the basis for the detailed design of the software.

Detailed Design On the basis of the outline design, the developer needs to carry out the detailed design of the software system.

Coding: According to the design requirements of data structure, algorithm analysis and module implementation, the developer starts to write specific programs to realize the functions of each module, so as to realize the requirements for the function, performance, interface, interface and other aspects of the target system.

Product design is an important part of the development system, which requires systematic cooperation with UI, R&D, testing and other personnel. Ultimately, ensure that the developed system is in line with the needs of the business operation.

1. OA custom process.

OA custom process refers to the user can customize the operation of the process, the process is circulated according to the user's needs, for example, there is a work task in the enterprise now, after the manager approves it, it will hand over these tasks to the subordinate employees to complete, and in this company, there are many people who can complete this work task, then the workflow of this task is to flow to whom the manager has to customize the operation, this process is also called OA custom process operation.

2. OA immobilization process.

The OA fixed process is generally used in the tasks to be carried out every day, for example, the enterprise has its own product production base, at this time, the production line operation in the base needs to use the OA fixed process, because the production base has to produce products every day, and each process is fixed, so these processes can be fixed.

3. Combination of OA fixation and custom process.

If you stumble upon a process that needs to be optimized in the fixed process, then you can combine the fixed process with the custom process to change a small part of the process in the fixed process.