The rapid development of computer and communication technology, especially the development and popularization of Internet technology, providing fast, accurate and reliable information exchange channels inside, enterprises and externally. The information enterprise operation management system has become a must-have support system that enterprises and institutions participate in competition in the global market. It is because of such market demand and technology development status, bringing opportunities for unprecedented development for my country's IT industry, especially software industries. Software companies can seize such a rare opportunity to work, in which software quality assurance plays an important location in their development.
As we all know, India has become the fastest growing country in the world. At present, the annual output value of software has reached billions of dollars, and is still growing at 30% to 50% per year. Comparing the software industry in my country and India, it is not difficult to find that China has huge software market and world-recognized software development resources, in basic research and the technical forward-looking grasp, there is also its own advantage, in the overall socio-economic environment Words are better than India. In addition, China's software developers are relatively low, only about 1/3 of the world market. Although Chinese do not lack the talents developed, today, today, the innate management of the mainly insufficient management, makes us step hard, difficult to get rid of small workshop software development models. The Indian software industry is based on the management model for US software companies from the beginning and follows the management model of its software development.
The management issues cannot be completely solved, and the quality of software is not talking. The author recently learned some detailed information on project management in a software company (hereinafter referred to as Company), which has passed the CMM4-level assessment software (hereinafter referred to as Company), and more deeply experienced the standardization of project management. Close relationship between enterprise software quality assurance. Let's focus on the project management of Indian software from the software company's architecture, software project plan, project management, project manager. Some experience summaries should be conducted on the issue of my country Software Quality Assurance.
1. Software organization structure (1) A Company Structure Figure 1 is a company's organizational map, with a larger different in China with a large number of companies with QA, SSG and human resources sectors.
figure 1
* A company, QUALITY Assure department and R & D department independently, responsible for supervising processes. QA is responsible for the joint working group of leadership and research and development departments to develop the company process.
* SSG (System Support Group) Similar to our IT department, responsible for allocation and management of all companies of computer software and hardware resources. All office environments and development / laboratory environments are responsible for installation and maintenance by SSG. Computer resources belong to SSG. It is proposed to SSG to SSG. After the project is completed, the device needs to return to SSG. Personal and project groups do not have fixed software and hardware resources. The SSG is a parallel department that is developing.
* The Human Resources Department is responsible for the company's human resource management, and maintains the skills of employees. At the beginning of the project, the project group applies for human resources to the SSG to apply for computer hardware and software to the SSG. At the end of the project, you need to release computer resources to SSG, release human resources to the human resource pool, and update employee skills databases. The human resources of the R & D department are allocated by the total leaders of the R & D department and their assistants (similar to the human resources department of all companies in my country).
(2) Project group structure
1) A Company conducts an independent accounting of the project team, and the project specific person in charge is PC (Project Coordinator), responsible for project planning and execution, dividing the project specific members. At the end meeting at each phase (such as the overview of the designed design), the PC should accept the QUALITY COORDINATOR review. In addition to the PC and QC interface, all other external interfaces are completed by the EM (Engineer Manager), and the EM is responsible for dealing with customers, and coordinating the SSG, human resources requires resources, and coordinating with other project groups.
2) Reporting relationship is:
Team MEMBER-> Team Leader-> PC-> EM-> The head of R & D is. 3) Indian engineers are divided into Level 7, half a year of assessment, which has an opportunity to upgrade half a year.
Level 1: Software Engineer, undergraduate and graduate students who have just graduated.
Level 2: Senior Software Engineer.
Level 3: Project LEADER.
Level 4: Project Manager.
Level 5: Senior Project Manager.
Level 3 can be a PC, and the level 4 can be EM. Just starting an average of 2 years, and then the slower afterwards.
Company A stipulates that one person can simultaneously serve as the PC and EM management project of two projects.
A company usually 4 to 5 people, up to 10 people.
The above is A company (also the organization of most standardized software companies in India). It can be seen that the organizational structure of Company A is very clear, and each department is very fine, the task is clear, each step of software production has special sectors, dedicated person responsible, from the most basic developers to the total organizational Manager, layer management, communication channels. In my country, the irregularity of management is often reflected in the company's organizational structure, focusing on the deletions and management of the department. my country's software companies, most of which are small, and more than 100 people with more than 100 developers. In India, software companies regardless of size, "although small, fifty and fly", will never change the reasonable organizational structure due to the size of the company. Therefore, the author believes that domestic software companies must effectively protect the product quality, first, we must work hard in the structure of the architecture, which is like the top floor, just like the foundation, the foundation is not prison, the structure is unreasonable, other Aspect, then work hard is also futile. Some people say that because domestic software companies are small, there is a lack of structural settings, but the author believes that it is precisely because there is no standardized organizational structure, it will make the quality of the software product induction, which seriously affects the development of the company.
2. Project plan
Forewarned is forearmed, without prejudging the waste. The "pre-" here is a plan. For software companies, the importance of the program is self-evident. Let's take a look at how the A company's project plan is developed: In A Company, the scale of the project must be estimated before the project is started (measured by the number of lines); then develop the project plan. The usual time is 2 ~ 3 weeks, and the longest is 5 weeks. The EM is responsible for the development of the project EWP (Engineer Work Paper), which defines the human and computer resources required by the project. The relevant departments agree and report to the total person in charge of the R & D before the project can be started.
The official start time of the project is counted by the Kickoff Meeting of the Project Group, and Closeout Meeting ends.
It is about many people to have heard such a sentence: "Plan can't change the change." This "change" may not have too much impact on certain industries, but for software companies, it will have a serious negative impact on the quality assurance of software products. Why does this "plan to catch change"? For the reason, the author believes that it is mainly because the level of importance is insufficient, the plan is too general, roughly caused too bad executability, plus the impact of some artificial factors, inevitably produces such consequences.
If our software companies can take into account each detail when planning a company, it is not a rush to make a decision, but all relevant departments jointly study, develop, discuss, modify the product plan. Finally form a set of systems, strict, and strong programs. Once the plan is formed, it will be implemented in strict accordance with the plan, and the impact of some people will not only reduce the waste of resources, but also the quality of the product has also been guaranteed. Therefore, it is an important part of the company's effectiveness to ensure the quality of the product is highly attached to the plan.
3. Project Management
When the company has a reasonable organizational structure and has entered the development phase of the product. In this stage, project management has played an important role. The links it involve are quite specific. Here, the details of the Company A on project management are introduced.
(1) Development phase and project cycle
The development phase is more obvious, paying attention to the functions that should be completed at each stage, the work that should be completed in this stage cannot be left next.
(2) process
* A Company pay more attention to the process compared to the process.
* Software development process is very standardized and systematic, and its process is highly executed, and it can be continuously improved during practice. Company A has covered all aspects of project research and development, including the release of the most beginning to the last software (Release), has corresponding process regulations, basically forming a industrialized software development.
* People and processes are two most critical factors that guarantee the success of the project. Project development by good people can maximize the success of the project to maximize the project. A good process can guarantee the things that the poor people don't have to be too bad, but they cannot make sure make a boutique. Software development can be achieved through the process.
(3) plan
1) Plan details, thoughtful.
2) Explicitly define the development phase in the process.
3) Each stage lists the activities of this phase and describes the properties of each activity:
* Enter conditions, input;
* Authentication method;
* End conditions, output.
4) Each phase has the end of the stage to end the meeting. The end of the previous stage can enter the next stage.
5) Every activity in the plan is more specific, and each activity is in units of days (half days). The plan includes time for quality control activities.
(4) REVIEW
According to the Indian company process, REVIEW and test are generally used as two main means to ensure software quality. The importance of the test does not need to be explained, and Review is a very simple and effective way to find the wrong way as soon as possible, it can be said that any payment can be based on REVIEW. At present, a company has a very detailed and comprehensive, highly implemented REVIEW process, and Review Checklist for various deliverables.
In India software companies, there is such a slogan: all things have a plan, and everything will be review.
(5) QA
QC (Quality Manager) as a representative, supervision and guarantee of the project, and the progress of the Project and the template, and collect some problems and solutions found in the project to optimize the process.
(6) Metric data
In CMM, the data is more emphasized, and all the data substantially all of the data during the project will be recorded. Finally, the collected data is submitted to the quality assurance department to analyze and improve the process. Company A project manager and quality manager attaches importance to data collection in the project, including various REVIEW data, test data, and project team members' daily activities. The project manager also maintains a project file. In this project file, it can be said that all outputs, development activities, management activities, etc. in the project development process are included. It can be said that there is this project file, you can fully understand the development process of this project.
(7) Teamwork
Indian companies emphasize team spirit, spirit of cooperation, should be said that their process is essentially demanding mutual coordination and understanding of employees. Relatively speaking, the spirit of cooperation and coordination of Indian employees is much better than our employees. (8) Training
Indian companies emphasize training, generally have a special training sector to coordinate. After new employees enter the company, they will have a company process and other training training to ensure employees' understanding and implementation of the process. For specific projects, project managers will propose all training needs in the project plan when developing a project plan, including technical training and other desired training.
(9) Configuration Management
Before the project is officially carried out, the project manager must formulate a configuration management plan, and specify the configuration administrator to establish a configuration management library, and configure management according to the configuration process. Controlling the changes in the configuration process are also provided, without approved changes requests are absolutely unable.
(10) record
Record in time, sufficient, accurate. These records include: important emails, meeting minutes, audit records, defect reports, test reports.
1) All exchanges of customers and other project groups must be recorded.
2) There is a process of tracking implementation for all activities, such as a status identifier for all REVIEW records and changes requests, identifying its current state, supervising its implementation by tracking its status.
3) There will be a history for all activities, including changes to documents and code.
4) Record is more accurate, more objective.
5) Many records are by quantitative numerical records, emphasizing data speaking (the focus of CMM4 is quantitative management).
The above is some of the major aspects involved in project management, and it is worthwhile to learn from the development of project management planning. In addition, my country's software companies are prone to the following aspects in the process of product development management:
1) Demand indication - demand is unclear, incomplete, too summarized, or not testing, will cause problems.
2) Unrealistic timetable - If you have to do a lot in a short time, there is an error in an error.
3) The test is not sufficient - can only determine the quality of the system according to customer opinions or system crashes.
4) Constantly increasing the function - requires an increase in many new features during the development of the development. This is a common problem.
5) Communication issues - If the developer does not understand the requirements of the customer, or the customer will cause an error.
The emergence of these problems will adversely affect the guarantee of software quality. For the above problems and combined with A company experience in project management, the author puts forward some corresponding solution for reference:
1) Reliable demand - should have a clear, complete, detailed, overall, fully achievable demand that is unanimously contemplated. To help determine the needs, you can use the model (prototypes).
2) Reasonable timetable - for planning, design, testing, changing error, re-test, change, and preparation documents have enough time. The project should not be used to complete the project.
3) Appropriate test - start test as soon as possible; after each change or change, it should be re-test. There is enough time to leave a test and change in the project plan.
4) Unshe to the initial demand - Once the development work begins, it is necessary to prevent modification requirements and new features, and to explain the consequences of this. If you have to change, you must have a corresponding reflection on the timeline. If possible, use a fast model in the design phase to make our customers understand what will be got. This will make them have a high confidence in their demand, reducing future changes.
5) Communication - pre-arrangement and inspection in proper timing; make full use of group communication tools, groupware, network fault tracking tools, change management tools, and the Internet's features. To ensure that the file is available and the latest. Preferred electronic documentation, avoid paper media documentation: long-distance joint operations and collaboration; use models as early as possible to make customers expectations clearly.
4.PC (Project Manager)
The project manager is a key person in the success or failure of the project, which is the main responsibility for the success or failure of the project. Therefore, the relevant content of the project manager will be separately suggested, and the A company will explain the role of PC in the entire product development process, hoping to have an enlightenment to the project manager of domestic software companies. (1) Before A Company, the project manager needs to complete before the process is officially launched:
* Project Plan: This describes the payment, project schedule, training needs, resource requirements, quality assurance planning, and quantitative quality goals of the process and delivery of the entire project.
* Project Configuration Plan: Specify the configuration administrator, describe the project configuration list, configure the management library, version management plan, and more.
* Process Handbook: This project describes the cropping lifecycle model and process taken by this project.
(2) In the process of project development, the project manager needs to know the progress of the project, perform job task refinement, specific planning and arrangement of project member work tasks. The emergency project manager needs to be coordinated in time.
(3) In general, the PC arrangement has such a few features:
A. PC has rich experience in software development, understanding software development universal processes, understands the work required to be completed at all phases, which is the premise of arranging project group members, and the overall quality of PCs in A is very high.
b. Before the project is officially carried out, the PC prepares the project plan document, which contains the project schedule in the project plan, but this timetable is relatively thick, and can only give the starting end date of each stage and each sub-stage. For detailed work arrangements for each stage and each stage, the responsible person can only arrange in the project development project, which is generally performed on this week's detailed work arrangement at weekly projects.
C.PC is often accurate to the work arrangement, sometimes even accurate to hours, to do this, need:
* PC is very understandable. Understanding channels are usually a status report of weekly group members and direct contact with group employees, which also requires members of the project team to report.
* It is very understandable that the work needs to be completed this week or this week. I know what to do now, and you can make a reasonably and more meticientation, because each decomposition work is more meticulous, so the time required for these work is completed relatively accurately.
* PC understands the ability of the project team member, and it can be used as a timing when scheduled. When the arrangement is unfamiliar with the work, the corresponding group members will be assisted.
* PC is more meticulous to the work arrangements for the teamns. Some employees do not have some employees, and some employees do not work, and when this situation or employee is completed in advance, the PC will work accordingly.
D. PC's work arrangements at the project group case are generally limited to this week or even afterwards, three days, generally not too long, the arrangement of long working is easy to lose accuracy and not easy to control. Relatively, a short time work schedule is more accurate and easy to control, and can be adjusted according to the completed work. Of course, this requires PC to grasp the overall progress based on project schedules in the project plan.
e. Project Group general will generally once a week (time is not too long), but if necessary (if the work has completed or other things), you can also hold a project meeting in the middle of the project, general time is short (more than ten minutes) Around, generally no more than half an hour, so as not to waste time), in short, the project meeting will be held when the PC feels it.
f. When an accident or an event of an accident or affecting the project unity, the PC can work and reasonably coordinate and solve the unexarous atmosphere within the project group.
G.PC is good at encouraging the hand, playing the potential of employees, and PC tends to praise the team members who have completed their work.
It can be seen from the above, the ability to PC (including technical and management capabilities) is very high, my country's software companies often pay only attention to PC's technical ability, but in fact, a person who only master technology often can't be a qualified Leaders, the author believes that the first thing to see himself can be more farther than his subordinates, and it is not blindly optimistic. When you encounter setbacks, you will not be able to have a full morale. to sum up
The above experience in combined with Indian software project management has summarized some issues that should pay attention to my country's quality assurance. Some people have filed: such a way to learn to imitate, there is not much hope in the national software industry. But the author believes that in this issue, I may wish to adopt the way "to use theism", for good, facts prove to be successful experience, first "possession", and then "picking" and "innovative". If India's management experience is really understanding and put into practice, I believe that we will actively promote our national software industry.
