Individual software cheating

To ensure security, you can obtain cheating information from the Internet through any terminal in case of an emergency. It is a good practice to write my summary into a blog and publish it to the Internet:

Body:

1. The product plan should describe the products to be developed, including (product scale, working time and progress) estimation.

2. The job ID log is a (Product Plan) document.

3. The task of the software engineer is to deliver high-quality software products at the scheduled time and schedule ).

4. Checkpoint: (a point that can be objectively identified in a task, also known as a milestone ).

5. What is included in a complex product plan?
A: it includes three aspects: product scale, working time and progress estimation, division of responsibilities, staffing plan, product or process specifications, and test or quality assurance terms.

6,CodeHow is the peer review conducted during review, and what is the best code review policy?
A: peer review allows several engineers to review each otherProgram. The best code review strategy is: First Review personal code, then compile, and then conduct peer review before testing.

7. What is the defect density? If a 16-line program has 14 defects, what is the defect density?
A: The number of defects (defects/kloc) in each thousand lines of code is called the defect density. The defect density of this program is: 1000*14/96 = 145.83 defects/kloc.

8. Some Notes for filling out the table:
1. Program Scale (LOC): Before development: Estimated number of lines changed by login, maximum and minimum scale value. After development, add the actual number of new development and updated code lines.
Note: In the accumulated row, the actual new development and updates are added with the previous accumulation.

2. defect density (defects/kloc): Before development: Find the cumulative defect density value of the last program. Use this value as the planned defect density value for the current project.
After development: calculate the actual defect density value and the cumulative value so far. Actual value = 1000 * Total number of actual defects/number of actually newly developed and modified code lines.

9. Data type conversion can be divided into display and implicit conversion. Subclass conversion is called (implicit (reference) conversion)

The base classes of all feature types in 10, C # are: attribute

11. Best execution steps for peer review, test, code review and compilation: Code Review-> compilation-> peer review-> test.

12. Benefits of phase defect elimination = 100 * (number of defects excluded in this phase)/(number of defects in the product upon entry of this phase ).

13. Defining the defect exclusion benefit is the percentage of defects found before the first compilation and test.

14. Process benefit = 100 * (number of defects excluded before compilation)/(number of defects introduced before compilation)

14. Program questions:
Class myclass
{
Static void main ()
{
Chello Hello = new csuperhello ();
Hello. Fun (); // Hello world in csuperhello!
Hello. function (); // call in chello. Function
}
}

Class chello
{
Public Virtual void fun ()
{
Console. writeline ("Hello world in Chello! ");
}
Public void function ()
{
Console. writeline ("call in chello. function ");
}
}

class csuperhello: chello
{< br> Public override void fun ()
{< br> console. writeline ("Hello world in csuperhello! ");
}< br> New Public void function ()
{< br> console. writeline (" call in csuperhello. function! ");
}< BR >}

15. Program question:
public class count
{< br> static int count;
int number;
Public count ()
{< br> count + = 1;
Number = count;
}< br> Public void show ()
{< br> console. writeline ("Object = {0}, Count = {1}", number, count );
}< BR >}

class class1
{< br> static void main (string [] ARGs)
{< br> count a = new count ();
. show (); // o = 1, C = 1
Count B = new count ();
. show (); // o = 1, C = 2
B. show (); // o = 2, c = 2
Count C = new count ();
. show (); // o = 1, C = 3
B. show (); // o = 2, c = 3
C. show (); // o = 3, C = 3
}< BR >}

16. The three elements of quality cost (cqq) are: error cost, inter-cost and prevention cost.
The cost of negligence includes all costs for fixing defects in the product. Quality control costs include evaluating the product quality to determine whether there are any defects in the product, but do not include the time spent on fixing the defects.
The preventive cost is the cost incurred by the modification process to avoid introducing defects.
Quality Cost Calculation: The quality control cost is the percentage of the total review time to the total development time. The gross cost is the total compilation and testing time as a percentage of the total development time.

17. What is the quality control negligence ratio? When its value is smaller than 1 or greater than 2, what problems can be explained?
A: The ratio of quality control cost to negligence cost. A/FR. A/FR is used to measure the relative value of the time spent on finding defects before the first compilation.
When a/FR <1, many errors are often found during program testing. When the number is greater than 2, each thousand lines of code has few defects.

18. Draw and explain the PSP process.

The improvement process is as follows:
1. define quality objectives
2. Measure Product Quality
3. Understand the process
4. Adjust the process
5. Application adjusted Process
6. Measurement Results
7. Comparison of results and objectives-> 4

19. What tables are available in the PSP process? What are the effects of these tables on the improvement of individual software capabilities?
PSP Project Plan Summary Table, event record log, job number log, project notepad, code review checklist, and code writing specifications. Role.