Experiences in Software Quality Management System

1 Dai Ming Theory: PDCA:
P: Plan D: Execute C: Check A: Correct

2. formula for calculating the number of concurrent users of the system:

C = NL/T
N: Number of users logging on to the system. L: The period from login to logout, that is, the time when the user is online
T: The length of time, that is, the length of time when the system is online.

3 peer review: it is a SG (special goal) verified by the server in cmme. During peer review,
People with multiple points can participate, such as software.CodeInspection review,
Not only is it responsible for the software coders, but it can also be better for software designers.

4. During peer review, you must collect as much data as possible. Peer-reviewed ROI

Time spent by each person in this review ut = preparation time for this review + meeting time + tracking time after defect discovery
Everyone spends PC (RMB) = ua1 + ua2 + ua3 in this review
Total cost rc = Cost of Defect 1 D1 + cost of defect 2 D2 + cost of defect 3 d3
ROI = total rework cost RC/total attendance cost PC

5. The departments or teams for software quality assurance should be independent development teams under the leadership of senior managers of the company.
6 baseline is a group of work products that have been officially reviewed and should be supervised and controlled by the CCB change control board.
7. Establish an organization-level risk database for reference. The risk table contains the following items;
Risk source, risk classification, cause, possibility, severity level, prevention measures, response measures, and response owner

Risk value = Risk possibility * risk severity

8. Goals for project planning:
Business objectives, quality objectives, process improvement goals, training objectives, and measurement objectives
9 project workload = Function Point/person-day

Lifecycle project 1 Project 2 project 3 ....
Project Initiation 2% 3% 4%
Demand development 5% 3% 2%
.......
As the project workload is calculated, you can:

Life cycle distribution rate workload
Project Initiation: 2% project workload x 2%
Demand development: 5% project workload x 5%

10 software requirement engineering includes requirement development (demand research, demand analysis, requirement normalization) and requirement management;
During demand research, you should understand the user's business objectives and industry background, clarify the specific workflow of each user, and the user's usage habits and non-functional requirements for each function.
11 A good method in demand research: 5w1h, that is, why, what, who, when, where, and how

12 decision-making methods can be analyzed using decision trees or weighted scores, for example:
criterion 1 xxxxxx weight Scheme 1 Score Scheme 2 score
........................ ...........