[the path of system analyst] Chapter V software engineering (software process improvement)

【 The path of System Analyst 】 The fifth chapter Duplicate disk software engineering （ Software process improvement ）

Preface Analysis of real test sites over the years

1） Test point analysis

Software process improvement is a knowledge point in software engineering , This knowledge point is not the key point from the frequency of investigation , After all, the main work of system analysts is still carried out around requirements . Although the paper also appeared once , But I don't think it's likely to happen again . Students who have spare power can prepare for this part , If you don't have any spare strength, you'd better give up this chapter , After all, I don't think it's a big problem .

2） Important knowledge points

01） Software quality assurance includes
02） The main steps of software process improvement
03） The concept of software technology review

The first part Comprehensive knowledge over the years

2007 Next, the real problem of comprehensive knowledge over the years （1 branch ）

【2007 The second part is the true question 19 topic ： yellow 】
19. About SQA Description of the activity , What's not right is （26）.
(26)
A. Review various software engineering activities , To verify whether it conforms to the defined software process
B. Responsible for the software process description of the development project
C. Audit assigned software work products , To verify compliance with the corresponding parts of the defined software process
D. Record all non-conforming parts , And report to senior management

answer ： The answer is B.B and C Choose one from two .
Software quality assurance （SQA） It is an activity applied to the whole software process ,SQA The responsibility of the team is to assist the software engineering team to obtain high-quality final products .
SQA contain ：
（1） A quality management method .
（2） Effective software engineering technology （ Methods and tools ）.
（3） A formal technical review used throughout the software process .
（4） A multi-level testing strategy .
（5） Control of software documents and their modifications .
（6） Ensure that the software complies with software development standards .
（7） Measurement and reporting mechanisms .
Software quality is not SQA Full responsibility , Many participants in software development have the responsibility to ensure software quality , Including software engineers 、 project manager 、 Customer 、 Sales people and SQA Members of .SQA The group acts as the customer's representative within the company , Software must be viewed from the customer's point of view .SQA The responsibility of the team is to assist the software engineering team to obtain high-quality final products , To this end, a set of plans for quality assurance have been developed 、 supervise 、 Record 、 Analysis and reporting SQA Activities , These activities consist of an independent SQA Group execution （ Or push ）.
Software engineers adopt reliable technical methods and measures 、 Conduct a formal technical review 、 Perform well planned software testing to consider quality issues , This is not SQA The job of .

2008 Comprehensive knowledge over the years （1 branch ）

【2008 The first part of the year is the truth problem 21 topic ： green 】
22. Formal technical review （FTR） It is a software quality assurance activity carried out by software engineers , The following activities do not belong to FTR What's important is （25）.
(25)
A. Discover functionality in any representation of software 、 A logical or implementation error
B. Clearly state the functional and performance requirements of the software , Define documented development standards
C. Verify that the reviewed software does meet the requirements
D. Ensure that the representation of the software complies with predefined standards

answer ： The answer is B. Send questions .

1. Options B It is actually part of the definition of software quality , It doesn't belong to FTR Scope of responsibility .

The third part Real topic of thesis writing over the years

2013 Comprehensive knowledge over the years （75 branch ）

Question 2 On the software process improvement of software enterprises
Software process is a group of activities that people use to develop and maintain software and related products 、 Methods and practices , It's the most complex of software companies 、 The most important business processes . Software process improvement （Software Process Improvement,SPI） Help software enterprises plan 、 Implement software process improvement , To serve the business of the enterprise , It must be guided by the development strategy of the enterprise . Software process improvement finds problems in software process through software development practice , And find a way to solve the problem in practice , Continuously promote the continuous improvement of software process , Improve the quality of a product or service , Improve the efficiency of software development . Software companies want to be efficient 、 Developing software with high quality and low cost , It has to focus on software process improvement , Carry out software engineering and quality management in an all-round way .
Please surround “ On the software process improvement of software enterprises ” The thesis , This paper discusses from the following three aspects .
1. Briefly describe the software process improvement projects you participated in and the main work you did .
2. The main steps of software process improvement and the work content of each step are discussed in detail .
3. Combined with the software process improvement projects you are involved in , This paper expounds in detail which aspects of the software process the software enterprise mainly implements the software process improvement , And the implementation effect is explained in detail

The main steps of software process improvement and the work content of each step are as follows ：
Find out the target gap
In this step , The current status needs to be analyzed , And specify the state to be achieved （ Target state ）, Then analyze the gap . If an agency decides to adopt CMMI For reference , Based on its key process areas KPA, Develop a target state that meets the characteristics of your organization and products .
Select the scope of improvement
After identifying all the gaps , What needs to be done is to determine the scope of improvement , The definition of scope is not clear enough , Can't do quantifiable 、 Degree of verifiability . Most of the time, there are some qualitative requirements 、 Not quantitative , for example “ Friendly interface , High operability , Improve user satisfaction ” etc. . Such vague requirements are the root cause of subsequent project wrangling . A clear definition of the scope of the project , Experienced project managers and system analysts will play a crucial role . The scope can be improved from the following aspects .
1） Determine the responsibility of the plan
2） State the main objectives and issues
3） Associate problem groups to corresponding goals
4） Identify goals and issues that are clear and compelling enough
5） Set goal priorities
6） Export metrics for goals
Make improvement plan
Choosing the scope and planning for a process improvement activity is a difficult task , There will be many obstacles . If you want to adopt the whole process improvement framework , Tasks can become daunting ;
It's important to make a plan , Whether the plan is reasonable 、 workload 、 Whether the difficulty is moderate , Will directly affect the success or failure of our process improvement .
The improvement plan can be formulated from the following key aspects ：
1） Set up a process improvement team , Assign special personnel to take charge of the whole process improvement
2） According to the background and business analysis , Project analysis , Internal factors , Evaluate the existing software process according to the product characteristics
3） Give detailed suggestions for software process improvement according to the evaluation
4） Translate suggestions for software process improvement into actions , The whole operation is carried out by the improvement team SPEG Responsible for monitoring and tracking .
5） Implement software process improvement , And closely monitor the improvement process . If there is a problem, solve it immediately
6） Evaluate the process improvement implemented
7） Institutionalize successfully implemented software processes
Implement improvement plan
When the plan is made , We need to put it into practice . To implement the plan , Feel a little overwhelmed . Including building and deploying solutions , Firm your mind and overcome resistance . In the process of implementing improvement, the following aspects can be considered ：
1） Prioritize expected and necessary work
2） Continue to emphasize goals and issues
3） Coordinate the behavior of managers and practitioners
Check the progress of improvement
After implementing the improvement plan , What needs to be done is to check the progress of the improvement plan , Tracking progress allows you to know the progress of improvement activities , Provide visibility into improvement activities to detect problems early , And give data to make future plans more effective . Corrective actions include a series of Midway changes , Its basis comes from “ Target planning and Implementation ” The results and lessons of this stage .
Corrective actions include ： Revise the action plan to achieve the unmet goals , Revise the planning method used in the planning stage , Change the way in which new skills are developed and deployed in the implementation phase , Rearrange the content of improvement activities according to the new priority , Or revise the metrics used to monitor progress . The progress can be checked from the following aspects ：
① Whether to make progress towards the goal ;
② Whether progress has been made on the improvement plan ;
③ Whether progress has been made towards improving the framework ;
④ What lessons have been learned so far .
Checking progress is a very important activity , Provide feedback to the organization during the implementation of process improvement activities . Metrics based on business objectives are the basic information that helps to review progress and guide improvement activities .
Summarize the experience of this round of improvement
When a round of improvement is completed , Make the next round of improvement , It's a process of continuous improvement