In order to strengthen the normative management of the project, ensure the controllability of the project, the interimming rules and regulations are as follows, and the members of each project should be closely matched with the project leader.
Since this system has not been fully practiced, it is necessary to have more valuable advice. If there is any improper, after the study is adjusted or subjected to additional notice, the original working system will still be effective before the modification is not modified.
The group working system will take effect and execute now.
First, week working system
1. Write this week's work plan by the project person in charge, and each project member compiled the corresponding personal work plan according to the distribution plan. At the same time, you must be completed on Month morning. The start time and corresponding time period of the module must be clearly indicated in the plan;
2. Fill in the project member to the last week's work summary, while the reasons, adjustment, or new modules will be used for reasons or supplements, which will facilitate the adjustment of the next week's work plan, and also report the project leader, All of this group of work summary and summarized the work of the project group, unified reporting department manager;
Second, the day work system
1. Ensure that the local code is consistent with the code SAFE code when starting;
2, each project member is estimated to be a day's workload, ensuring that the valid code can be updated to the SourceSafe after get off work, so that the team members can get the latest payable code in time; ensure that the upload is running code, and to ensure Exceptions of exceptions such as exceptions such as serious errors.
l Exceptions: The code that cannot be guaranteed on the same day is in line with the above requirements. According to the situation, it can be adapted to the second day to modify the correct and upload. Special circumstances can be discussed.
3. When modifying the code, try to take only partial code that needs to be modified so that the coordination work between the group members;
Third, the precautions when working
1. Try to minimize the repeatability of work,
Such as: For several similar modules, if technically modifications need to be modified, only single modifications are made, and then fully modified, and thereby avoiding unnecessary workload.
2. When several people modify the same file or after the code is scheduled, other members need to modify or add part of the part code, and must be identified in the modification site (identifier including: new, delete, modification and other three states) ), The identification content includes the reason why the modifier, the modification time, and simultaneously adds the necessary annotations.
Treatment: System submission test or system release.
3. The technical issue of doubt should be in time with relevant personnel when working.
According to the importance of the problem, please exchange:
l does not affect the simple nature of the system
The state of the problem is required to be resolved or problematic. The content must be clearly reflected in the relevant problem feature, and if necessary, give the parties to explain or instance.
Note: The descriptive document is currently temporarily used, and the template document will be unified after being customized.
l Affecting the complex problem of the system or conflicts with the current design, etc.
Direct correction related issues directly, provide related documents or add content to the appropriate document, ensure that the modified document is synchronized.
4. Each project should fill in the project supplement document in time (public descriptive document)
Public description documents include resource utilization, data initialization data, public functions, and component declarations, which are convenient for project member query.
Since there is no unified document template, the project leader is initially developed by the project or provides a template file, and the project member applies. After the company standardizes the documentation, new standards and mechanisms will be unified.
5. After communicating with the user, you must form a document, easy to archive and communication, and the document format is attached. (New)
It is hoped that the members of each project will be implemented in accordance with the provisions, which is inevitable for others.
Standardize the implementation of the project group
2003-03-26
Attached one: unit test report single sample (project member internal communication) module name
Discovery time
Test reason
Steps to find problems
Test suggestion
Addition: Resource definition sample (text format)
// Resource Definition Description
/ *
Both resources: private resources and public resources
1. Private resource format: "IDS _" module name "_" private resources meaning
The module name does not include resource characteristics, such as login system dialog box class cloginsystemdlg or cdlgloginsystem,
Its resource name is "IDS_Loginsystem _" private resource meaning
2. A total resource format: "IDS _" resource type "_" total resources meaning
Such as: database connection fails, its resource type is DATABASE, their resource named IDS_DATABASE_CONNECTERROR
Note:
1, where the first part of the prefix (such as "IDS") must be consistent with the resource naming rules of the system
IDS represents a string resource
ID indicates resource-related string resources
2, the rear resource naming rules: the former type, a subscript after the plurality of types are arranged in order of priority, and to underscore
3, all resources must be capitalized
* /
/ ************************************************* *************************** /
// ------------------------------------------------ ----------------
// Public definition part
// ------------------------------------------------ ----------------
IDS_CONNECTSTRING Database Connection Description Characteristics
/ / -------------------------------------------------------------------------------------------- ----------------
// Distribute
// ------------------------------------------------ ----------------
FORAT format class
IDS_FORMAT_CHIDATE_1 Chinese Date Format:% s Years Midd month% S Day
IDS_FORMAT_CHIDATE_2 Chinese Date Format:% D Yele% D Mid% D Day
// ------------------------------------------------ ----------------
// Classification definition
/ / -------------------------------------------------------------------------------------------- ----------------
Riceoilout grain and oil expenditure interface
Loginsystem system login interface
ARMYSELECT troops selection interface
Attached three: Part of public statement (text format)
// Common function, class closed, interface description
/ *
Common code partial description:
Public definition part
1. All definitions must be stored in Define.h, define the rules as follows: Type meaning subscript, where the type is the feature or meaning of the value or related value group, such as: System default configuration file named System.ini The definition can be:
#define INI_DEFAULTSYSTEM, where the type and the subscript can be available, depending on the situation.
2. Type of set of sets: First define the reference value first, then extend according to the reference, the reference value is: type "_ base", the other type value is: Type "Specific Meaning". Such as: error code definition: #define error_base -1
#define error_type_1 (Error_Base - 1)
#define error_type_2 (Error_Base - 2)
Common function requirements:
1. The code is stored in BaseFunction.h and BaseFunction.cpp
2. Function Definitions must be used flexibility, application-independent.
Public type design requirements:
* /
/ / -------------------------------------------------------------------------------------------- ---------------------
// Function Description Part
/ / -------------------------------------------------------------------------------------------- ---------------------
1. Bool NCTRACE (LPCTSTR LPSZFORMAT, ...);
Description: Used to write log
/ / -------------------------------------------------------------------------------------------- ---------------------
// Classical Description Part
/ / -------------------------------------------------------------------------------------------- ---------------------
CspecialSequence
Description: This class is used for the credential number calculation of the military grain, the string is characterized by 4 years 2 months 6 bit flow
/ / -------------------------------------------------------------------------------------------- ---------------------
// Other instructions
/ / -------------------------------------------------------------------------------------------- ---------------------
Addition: Communication and Conference Documentation
[Incident title]
time:
location:
personnel:
-------------------------------------------------- -------------------------------------------------- ------------------
[specific contents]
[Additional Description] (optional)
Accessories and other descriptions
