NO4 System porting-project technical data sharing solution

System porting project-Technical data sharing solution

Objective

This article only does the solution analysis, does not do the specific technical point explanation

One: Why the need for technical information sharing

The porting points of the system porting project can be divided into: (1) The porting of the operating system, for example: From window to Linux, from Aix to Window, and (2) to program language, For example, VB6 upgraded to vb.net, migrated from PHP to Java, (3) Background database porting, for example: DB2 migrated to SQL Server, SQL Server ported to Oracle.

General projects are projects that contain multiple migration points and rarely have a single point of migration.

In the process of the project, operating system differences, language differences, database differences, such as personal mastery of knowledge and work experience different, in response to these differences in the method used in different, at a single point is correct, but the comparison of the two may result in inconsistent processing results, resulting in a bug in subsequent operations. There is, when the system transplant, the program across the operating system, cross-language, not everyone's knowledge can cover all the knowledge, all need technology to take the known technical knowledge of technical team members of the project group to share in a timely manner.

In order to have a unified approach to the same type of problem, so that each team member quickly and accurately grasp the corresponding technical knowledge.

Second: the past sharing method.

(1) Documentation method: During the project process, the resulting problems are recorded to the document "Problem list", the migration technology point is recorded in the "Technical list" document, so that the project process has produced a lot of documents.

Limitations: (A) During the course of the project, the team members are very active in documenting and viewing documents, and are rarely or not seen in the late stages of the project. If there is a new problem point or technical point is or have the original corresponding method has a better correspondence is, if only updated the document, no notification to each member, so that the new knowledge will not understand, let alone mastered.

Limitations: (B) lack of standardized and unified management, because each person's perception is different, the same problem may be categorized into different categories, such as: a technical knowledge point, some people recorded in the "Problem list" document, some people recorded in the "Technical point list" document, it is possible to cause a problem will be recorded in multiple documents, First, you don't know the most accurate doubts that are recorded in that file. The second is to increase the cost of document management.

Limitations: (C) If the company does not accompany the project after the completion of the project document archiving, project technical information records of the specialized personnel, after the completion of the project all the technical information is only a document, other similar projects need, from the vast amount of documents to find the desired information is also very difficult. There is a developer writing a document is, if the description is relatively simple, later people are more difficult to understand, which is a lot of waste.

This method is suitable for companies with small size and long project cycles.

(2) Common system platform method: Try Open-source Java platform, which contains a lot of information, such as C#,JAVA,C,VB, the platform is shared with the company, each developer can log on to the problem or technical information information, so that all the information mixed together, it is difficult to distinguish the desired information, After all the trials have been over for a while. The platform I have not tried, just listen to the previous staff said.

Three: Project Technology Library Platform method.

(1) Flat structure Description:

The first is a BS system within the company. is a platform for information recording and presentation, which is based on the project unit and the technology type. The platform results are as shown.

Platform Module Description:

(a) System management: For the management of the platform, such as user management, project management, project completion or the technical point within the project is determined to divide the item into the corresponding technology type.

(b) Project: Access to technical information similar to the project from the type of technology, management of technical knowledge within the project (additional knowledge points, knowledge point responses, knowledge point confirmations, finalization)

(c) Type of technology: primarily to view functions and to present the identified technical data in the category at a glance.

(d) Background data storage: mainly to provide system services and platform data information storage.

(2) Key function Description of core module "project":

First, the platform is to do project technical information sharing, how to make information sharing is his main function and role. To have a simple and clear interface display, followed by a history of information review and new technology issues in time to update.

Interface display: (a) at a glance, take the project technical information as an example. Screen layout: Left and right structure, the structure of the project tree, the proposal is not more than 2 layers, the division to be accurate and clear, on the right is a list of technical records, request a list of keywords and accurate text description, to do at a glance. As shown

Interface display: (b) Technical information, according to the user up and down structure (can refer to the way of the forum), the above users ask questions, follow-up users to answer questions or release their own speech. As shown

This is just a simple page layout display, the following module features combined with the page layout to do a detailed description of the function

(a) Once each member is logged in, the "project" module information at the current project is presented at a glance.

(b) The team members have access to log in and modify entries, log in, modify (major technical changes) after the record will be automatically top-up, and then the other team members log on at the top of the view, indicating that the content needs to be viewed.

(c) Historical accumulation of information acquisition, first good access to all the technical points of the project "refer to previous article: NO3 system upgrade-asset shelf unloading", to obtain all technical points, according to these technical points from the technical type of the total selection of historical technical information.

(d) Historical information can only be viewed, and new solutions should be added if there are scenarios that are inconsistent with historical information.

(e) When an issue or a technical information is finalized, the record can be locked and collated into information that can be used by other projects after logging into the technology type. Easy to use for other projects.

(iv): Platform Outlook:

The platform is already a project unit, according to the previous project experience, the single point of issue only a few items to dozens of between items, not too much, all login is almost at a glance, if new problems or old problems have a new solution, can also be in the latest marked out, do not need to notify each team member, simple and clear.

Using the system platform with the platform administrator can be the company's project experience has a good accumulation. The acquisition of technical knowledge can be done accurately before the start of the project, reduce the duplication of technical investigation, and improve the efficiency.

The above is the project of the Technical information sharing scheme, because of time and personal ability Limited, can only be written here, the basic realization of the shared platform and the main ideas can be basically expressed, there are see please self-improvement. What is the need to send my e-mail or message after the article description.

NO4 System porting-project technical data sharing solution