Microsoft's Software Development Easy Process - Transfer from Tassadar's Blog

xiaoxiao2021-03-06  42

I feel that Tassadar is finalized, reprinting,

[The following is from the lecture record, speaker: Huang Xuebin gtec, recorder: tassadar]

I stage: design phase

Idea -------> Feature List -----------------> Fuction Spec ----------- Implement SPEC

// | Software simulation | _TESTING SPEC

User Survey -> Priority (A:, B:, ...) Description and Function Description

II stage: coding stage

[According to Fuction Spec] (Coding Completed)

CODING ------> Milestone_1 ------> Milestone_2 ------> ....------> CC (GS: BUGS <= 50)

---- Testing ----> -------------> ------------> ------------> ---------> | Testing [According to Fuction Spec]

Daily Builder (successful version of the day, try to use VSS, can roll back)

III stage: test phase

The integration test begins, and the number of bugs will fluctuate with the test, and there are two possibilities:

(1) The number of bugs continues to decline, and reaches ZBB (zero bug rebound points), indicating that the test is over, and the product development is successful.

(2) The number of bugs continues to fluctuate but cannot fall to ZBB, then the product will face internal cancellation.

IV stage: release phase

After testing ZBB, first launch the specific process of the ALPHA internal test version is as follows:

Final version, released to the manufacturer burning

ZBB ---> Alpha ---> Beta1 ---> Beta2 ---> RC ---> RC1, RC2, RC3, ..., RCX ------> RTM (Release to Manufacture)

(Release Candidate) Finding the best RC in RCI

转载请注明原文地址:https://www.9cbs.com/read-47508.html

New Post(0)