Configuration implementation-Summary of practices of an information management project

A project name is suspected of leaking company secrets. Only one Information Management project can be defined here.

The project has the following features:

1. the user's business needs are clear, but the user belongs to the management department and cannot provide specific business requirements (for specific business, refer to the implementation of similar software on the Internet)

2. the user's query, analysis, and statistics requirements are uncertain (determined based on business needs)

3. It is required that the presentation be presented to the supervisor within two weeks, and that the presentation be checked by the superior.

After three years of accumulation, the Information Management System framework can be fully utilized.

Two developers, with one week's development time (basically no overtime at night), concluded that one person made two editing pages. The xml configuration on these four editing interfaces cannot be solved, I had to write a program to control and implement it myself.

1. the system management function is ready-to-use. You only need to adjust the Chinese characters of the field names in XML as needed.

2. The system manages more than 40 functional points in the list, query list, statistics, and analysis graph, all of which are implemented using xml configuration.

3. add, delete, modify, and query of basic data in the system. More than 10 functional points should be configured in XML as much as possible.

4. Detailed information is displayed and printed in the system. For more than 10 functional points, xml configuration is used.

A total of 61 XML files are configured, and 2 HTML templates are printed.

This week, the test and instructions are being written.

Waiting for demonstration by the supervisor and checking by the superior ......

13 additional configurations are added during the wait process to achieve statistical analysis (with analysis graph) and query that can be thought of at the current stage.

Presented to the supervisor on March 13, October 10, basically passed

After three days of preparation of training meeting materials, the project development and testing work is basically completed.

Time period summary:

1. For the first time in September 8, I discussed the requirements with the customer.

2. At ten o'clock A.M. on April 9, September 15, I received a phone call from the manager saying that the customer needed to provide a basic architecture demonstration in the afternoon. I took two hours to ask the artist to help with the presentation, use the existing architecture to complete basic system management functions and demonstrate them.

3. the design, development, and self-test phases of the system are tense from October 23 to October 23 (one day of overtime on October 17)

4. Presentation to the leadership of the competent authority on April 9, September 26

5. From October 11 to October 9, according to the user adjustment, testing, and manual stages (holiday as usual)

6. Presentation to the supervisor on April 9, October 10

7. Preparations for the second round of tests and training materials since January 1, October 10

Welcome to: http: // 121.18.78.216, which is a demonstration platform for ease of query and analysis, workflow, content management, and project management.