Software System Maintenance Plan

Software System Maintenance Plan

Author:Liang Qifeng

Time: 2007-7-13

1Collection of maintenance items...1

1.1System Faults...1

1.2New requirements...1

2Research and maintenance feasibility...1

3Analysis, Design, and maintenance Solutions...1

4System Maintenance...1

4.1Participants...1

4.2Assignment...1

5System update and re-release...2

1 Collection of maintenance items 1.1 System Faults

The system is in use, but several errors are often found during use. You need to collect, sort, and classify these errors, in this process, relevant individuals and departments should be provided with timely support.

1.2 New requirements

With the discovery of the company's business, the organization and business model of the company may change. To adapt to new business processes and settlement methods, the existing system should be upgraded or re-developed. At this time, it is necessary to communicate with relevant departments, understand the requirements in a timely and accurate manner, and classify the requirements into documents.

2 Research and maintenance feasibility

Call relevant departments and personnel to authenticate technical implementation of the maintenance items and confirm whether the maintenance items can be implemented. When possible, we also need to consider whether there are enough people at hand to invest in development and whether we have enough time to complete the system upgrade and revision.

3 Analysis, Design, and maintenance Solutions

When you have a sufficient understanding of the problem and confirm that there are sufficient resources to be completed on time, you need to turn the requirement into a technical document for development, such as the system maintenance summary, system maintenance function list, new database list, and system maintenance detailed manual; then, detailed development plans are listed based on existing personnel. Finally, all documents are handed over to the business department for confirmation. After they have no opinions, they can enter the system maintenance work.

4 System Maintenance 4.1 Participants

For a large project, we recommend that you have a project supervisor,DBA, Developers, artists, and testers.

4.2 Assignment

The project leader shall grasp the progress of the entire project and be responsible for assigning, tracking, reviewing, and providing necessary support for development tasks.

DBAEnsures database stability and assists developers in Data Mining and writing.SQLStatements, stored procedures, and so on.

Mainly written by developersCode, For testing, with the supervisor, artist,DBACommunication to ensure developmentDelay.

The artist is responsible for page design and beautification to ensure page style consistency.

Testers should perform full tests before the system goes online to ensure system security, stability, and efficiency.

5 System update and re-release

after the system is developed, the project owner re-releases the system after repeated and thorough tests, however, we should try to ensure the integrity of the original data to ensure that the switching between the old and new systems also affects the use of business departments. Therefore, we recommend that you run the New and Old systems in parallel before turning off the old system after the new system is stable.