A review of PB programming specifications

Author: Xingda Computer technology company (www.study01job.com) Guo Baoli

I. Classification of Programming objects

With PowerBuilder as the foreground development tool, in the process of software development, the programming objects involved are shown in table 1-1.

Table 1-1 Programming Object classification

II. organization of Programming objects

Objects produced using the PowerBuilder development tool can be organized into programming objects in accordance with the design (being written and debugged) and in the state of running (debugging, compiling, testing, and running), focusing on the partitioning of the directory structure and the relative relationship of the specific directory as shown in table 1-2.

Third, team development

A. Obey the team development discipline and schedule.

B. Without the permission of the project leader or the project manager, do not allow unauthorized conduct of any work that may affect the work of other people, such as adding a library, add a database table, etc., if necessary, must submit a written application, explain the reasons and the details of the operation to be changed, by the project management personnel unified operation and coordination.

C. The code must conform to the standard specification, and the project leader or project manager has the right to instruct the developer to modify code that does not conform to the development specification.

D. A directory that is stored in a code set to a file server, where the client is uniformly mapped to a fixed letter, ensuring that the program is available at all times as a complete version rather than a fragmented set of code and is not allowed to be copied to the local hard drive for development.

E. When writing some common parts and code, you must use the check Out feature to ensure that your code is used exclusively and cannot be modified by others, and that the check in feature must be used in a timely manner when the modification is complete to ensure that the code eliminates exclusive state so that others can use the modified code in time.

F. Each individual sets his or her own in the team user id:library->source->connect-> SELECT [PB native]-> set the user ID, fill in the initials of your own name or English name.

4. Version description

A. The software version number is standard A. b, where A and B are numbers from 0 to 99.

B. When a is greater than 1 and B is odd, the current version is defined as "development", and when B is an even number, the current version is a stable, realistically running version, defined as "Stable edition".

C. When the software begins to develop, the version number is 0.1, and as software development progresses, the version number changes with each major function, up to a maximum of 0.99.

D. Upon completion of the initial software development, after the software development team internal testing, the initial ability to complete the software requirements of the business specifications and technical requirements, the software is basically normal operation, at this time, determine the software version number of 1.0 Beta X, which means that the software can be put into the actual application test, where X represents the number of tests.

E. When the 1.0 Beta X version of the software is introduced and tested by the user or trial run, the software version number is determined to be 1.0 RC. This means that the software can be put into actual application operation.

F. When the software 1.0 RC version into the actual application of the operation to achieve a certain time limit, it is considered that the version has been stable, can be completely normal use, at this time, to determine the software version number 1.0, which means that software development completed, can be put into practical application and promotion.

G. When the software is upgraded, if the function changes little, the minor version number changes, if there is a significant change in software functionality, the major version number changes.

The final version number of the software is determined by the project leader or the project manager.