Segway Business Pass System Developer Handbook (umlchina.com, reprint)

A developer's Handbook for Business Communication Systems

Sukang (cancan28@163.net)
First, the preface
In order to ensure the development cost optimization of business communication system projects and to facilitate future expansion and reuse, project members must strictly follow the following development manuals. Strive to achieve a default development specification. Second, the design agreement
L The system will use RDS technology to access remote components, and it must remember this limitation that RDS does not support the properties of objects.
L The system must provide a unified and flexible error handling mechanism to unify the management of the component's return information.
L system components try to adhere to the principle of loose coupling, so that components can be reused on the basis of the future to adapt to a variety of changes.
L for the system to be very portable, the design to eliminate the use of stored procedures to implement the dependencies.
L components should be designed to avoid excessive creation of database connection requests.
L Detailed design must be detailed to each component and method and interface.
L Use rational rose as an auxiliary tool for system analysis and design.
L design must be in line with project management and assist requirement managers to provide baseline basis for requirements.
L must get the programmer's feedback and fix the design bug in time.
L Other supplements can be consulted Sukang. Code of Procedure a) VB Programming specification
In the process of software development, the workload of programming is quite large, the same project involved in programming people may have their own programming experience and habits, different styles of program code brings maintenance workload increase, so in order to improve the readability of the code, System stability and maintenance and upgrade costs, The code of the program must strictly follow the unified programming specification.

General:
Should have a good, consistent programming style as possible
The coding should be rigorous, readable, targeted and intuitive.

Comments:
Annotations are essential, whether it is a client-side presentation layer program or a component program. Requirements can account for 20% of the total program, and annotations must be updated in real time when the program changes.
The top of each widget should have a comment
Include: module name
Function description