In the last issue, we introduced in detail to the delivery standards of software outsourcing projects and the problems that need to be paid attention to in enterprise acceptance, but in terms of source code delivery, we also left a problem, and today we will systematically explain a series of problems that need to be paid attention to in source code delivery.
Under normal circumstances, after the end of APP customization, the software outsourcing company needs to deliver a series of achievements such as development source code, design source draft, planning drawing, requirements document, product prototype drawing and so on to the customer. Developing source code is particularly important. Source code, as the name suggests, is the core code that constitutes a software, it is divided into many kinds, if it is a natively developed APP, there are Android system code and IOS system code, some also include web version code, some customers do not understand, it is easy to get mistaken when delivering. So why do software outsourcing companies deliver source code? How can I achieve source delivery? What issues do I need to pay attention to during delivery?
Why do software outsourcing companies deliver source code?
The source code of App development is the core value of the company's products, and the source code is part of the product, so the source code must be delivered. In fact, the product is a service built from a series of source code. In general, the larger the product, the more items will be served, and the more complex and difficult the corresponding source code will be. Coupled with the iterative update of each round of products, the call and assembly between services, and the interplay of source code engineering dependence, it is not only necessary to ensure the quality of source code delivery but also to ensure the efficiency of research and development!
How can I achieve source delivery?
Source delivery is not simply to copy the source code and package it for delivery, but to divide it into different versions, and the version can manage the code efficiently. Therefore, before delivery, software outsourcing companies need to unify the source code path:
1. Branch: Created by the backbone after archiving, the operator develops for the project and is used to implement new function requirements.
2. Trunk: merged by the body test branch, the operator is the quality control test; Used for environment testing, functional testing, pre-release environments, production environment operation.
3.Tag: After the pre-release environment is accepted, the production environment is released and the version is archived, and the operator quality control test is used to record the stable version of the production environment, which is convenient for rolling back the trunk operation.
Secondly, the service version number is mapped through the source code version submission record to ensure the consistency of the source code of different service versions.
1. Determine the baseline Trunk: Engineering Demo – Feature Development – Stable Release
2. Pull branch branch is derived from the stable trunk for the implementation of new features.
3. The merge trunk is merged by the testing branch and is used for functional testing, test environment, pre-release environment, and production environment operation. The merge trunk requires a prerequisite: testing emails. The test email must have the following six elements: version number, branch path, script path, project name, function boundary, and deployment manual.
What issues do I need to pay attention to during the delivery of the source code?
1. The code should only retain the code related to this project, and the invalid code should be removed;
2. The database should only retain the tables, views, stored procedures, functions, triggers, timing jobs, etc. related to the project, and the invalid content should be removed;
3. Pay special attention to the reasonable design of the data table structure, and appropriately redundant to improve performance;
4. The code structure is clear and non-redundant, the comments are complete and effective, and hard coding is avoided;
5. If it does not meet the source code acceptance specifications, the outsourcing team needs to repair it.
These are the issues and details that need to be paid attention to in source code delivery.