US8869096B2ActiveUtilityA1
Requirement management method and apparatus
Est. expiryFeb 14, 2032(~5.5 yrs left)· nominal 20-yr term from priority
Inventors:Yungu He
G06F 8/10G06Q 10/06395
38
PatentIndex Score
0
Cited by
45
References
18
Claims
Abstract
Embodiments of the present invention provide a requirement management method and apparatus. The method mainly includes: dividing all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement; obtaining a direct progress rate of any requirement in the system; obtaining direct progress rates of all lower-layer requirements of the any requirement; and calculating a mean of direct progress rates of all the lower-layer requirements to obtain a verification progress rate of the any requirement, and performing a weighting operation on the direct progress rate and the verification progress rate of the any requirement to obtain a progress rate of the any requirement.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1. A requirement management method executed by a processor, comprising:
dividing all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement;
obtaining a direct progress rate of one of the requirements in the system, wherein the direct progress rate is a progress rate tested by using a test case directly associated with the one requirement;
obtaining a direct progress rate of each requirement of all lower-layer requirements of the one requirement, wherein the direct progress rate of each requirement is a progress rate tested by using a test case directly associated with each requirement;
calculating a mean of direct progress rates of all the lower-layer requirements to obtain a verification progress rate of the one requirement; and
performing a weighting operation on the direct progress rate and the verification progress rate of the one requirement to obtain a progress rate of the one requirement,
wherein the progress rate of the one requirement is calculated according to an equation:
F _ProgressRate= F _DirectProgressRate* X+F _VerificationProgressRate*(1− X ),
wherein F_ProgressRate is the progress rate of the one requirement, F_DirectProgressRate is the direct progress rate, F_VerificationProgressRate is the verification progress rate, and X is a set weight.
2. The requirement management method according to claim 1 , wherein dividing all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement comprises:
dividing all the requirements of the system into 4 layers that include a user problem (PB) layer, a system feature (SF) layer, a system requirement (SR) layer and an allocated requirement (AR) layer,
wherein the PB layer is the highest layer, the SF layer is subordinate to the PB layer, the SR layer is subordinate to the SF layer, and the AR layer is subordinate to the SR layer,
wherein the PB layer is a requirement embodying a special concern of a user service,
wherein the SF layer is a requirement which is of a great value and is provided by the system to solve a user problem,
wherein the SR layer is all functional and non-functional requirements provided by the system externally, and
wherein the AR layer is requirements which are obtained by decomposing system requirements and are allocated to a subsystem or module level.
3. The requirement management method according to claim 1 , wherein after dividing all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement, the method further comprises:
classifying, according to a full life cycle of the system, non-functional attributes of the requirements of every layer into three service classifications that include a product delivery category, a product operation category and a product evolution category,
wherein the product delivery category represents a requirement arising in a process from completion of system development to delivery of the system to a user,
wherein the product operation category represents a requirement arising in an operation and maintenance process after the system is delivered to the user,
wherein the product evolution category represents a requirement arising in error correction, functional upgrading and product evolution processes of the system, and
wherein each requirement of every layer corresponds to one service classification of the three service classifications, and all the requirements of every layer of the system comprise all service classifications of the different service classifications.
4. The requirement management method according to claim 3 , wherein after classifying non-functional attributes of requirements of every layer into three service classifications, the method further comprises checking completeness of every requirement of all the requirements of the system, and if the non-functional attributes of all the requirements of the system do not comprise all service classifications of the three service classifications, sending prompt information to indicate that the requirements of the system fails in the completeness check.
5. A requirement management method executed by a processor, comprising:
dividing all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement;
obtaining a direct progress rate of one of the requirements in the system, wherein the direct progress rate is a progress rate tested by using a test case directly associated with the one requirement;
obtaining a direct progress rate of each requirement of all lower-layer requirements of the one requirement, wherein the direct progress rate of each requirement is a progress rate tested by using a test case directly associated with each requirement;
calculating a mean of direct progress rates of all the lower-layer requirements to obtain a verification progress rate of the one requirement; and
performing a weighting operation on the direct progress rate and the verification progress rate of the one requirement to obtain a progress rate of the one requirement,
wherein calculating a mean of direct progress rates of all the lower-layer requirements to obtain a verification progress rate of the one requirement and performing a weighting operation on the direct progress rate and the verification progress rate of the one requirement to obtain a progress rate of the one requirement comprises:
calculating the verification progress rate F_VerificationProgressRate of the one requirement F according to an equation:
F_VerificationProgressRate
=
∑
i
=
1
n
F
i
_ProgressRate
n
;
and
calculating the progress rate F_ProgressRate of the one requirement F according to an equation:
F _ProgressRate= F _DirectProgressRate* X+F _VerificationProgressRate*(1− X ),
wherein n is the number of all the lower-layer requirements of the one requirement F, F i is an i th requirement of all the lower-layer requirements of the one requirement F, F_DirectProgressRate is the direct progress rate of F tested by using the test case directly associated with F, F i — ProgressRate is a direct progress rate of F i , and X is a set weight and has a value range of 0<=X<=1.
6. The requirement management method according to claim 5 , further comprising:
after a direct progress rate of a lower-layer requirement F 1 of the one requirement F changes, calculating a progress rate F 1 — ProgressRate of F 1 according to an equation:
F 1 — ProgressRate=F 1 — ProgressRateOldValue+( F 1 — DirectProgressRateNewValue− F 1 — DirectProgressRateOldValue)* Y , and
calculating the progress rate F_ProgressRate of the one requirement F according to an equation:
F _ProgressRate= F _ProgressRateOldValue+( F 1 — ProgressRate− F 1 — ProgressRateOldValue)*(1 −X )/ n,
wherein F 1 — ProgressRateOldValue is a progress rate of F 1 before change, F 1 — DirectProgressRateNewValue is a direct progress rate of F 1 after change, F 1 — DirectProgressRateOldValue is a direct progress rate of F 1 before change, Y is a set weight and has a value range of 0<=Y<=1, and F_ProgressRateOldValue is a progress rate of F before the lower-layer requirement F 1 changes; or
when the number of lower-layer requirements of the one requirement F is increased from n to m, calculating a progress rate F_ProgressRate of F after the number of lower-layer requirements changes, according to an equation:
F_ProgressRate
=
(
n
*
F_progressRateOldValue
+
(
m
-
n
)
*
F_DirectProgressRate
*
X
+
(
1
-
X
)
*
∑
i
=
n
+
1
m
F
i
_ProgressRate
)
/
m
,
wherein F_ProgressRateOldValue is a direct progress rate of F before the number of lower-layer requirements changes, F_DirectProgressRate is a direct progress rate of F after the number of lower-layer requirements changes, and F i — ProgressRate is a progress rate of the i th requirement of all the lower-layer requirements of the one requirement F; or
when the number of lower-layer requirements of the requirement F is reduced from n to k, calculating a progress rate F_ProgressRate of F after the number of lower-layer requirements changes, according to an equation:
F_ProgressRate
=
(
-
n
*
F_ProgressRateOldValue
+
(
n
-
k
)
*
F_DirectProgressRate
*
X
+
(
1
-
X
)
*
∑
i
=
k
+
1
n
F
i
_Progress
)
/
(
-
k
)
.
7. The requirement management method according to claim 5 , wherein dividing all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement comprises:
dividing all the requirements of the system into 4 layers that include a user problem (PB) layer, a system feature (SF) layer, a system requirement (SR) layer and an allocated requirement (AR) layer,
wherein the PB layer is the highest layer, the SF layer is subordinate to the PB layer, the SR layer is subordinate to the SF layer, and the AR layer is subordinate to the SR layer,
wherein the PB layer is a requirement embodying a special concern of a user service,
wherein the SF layer is a requirement which is of a great value and is provided by the system to solve a user problem,
wherein the SR layer is all functional and non-functional requirements provided by the system externally, and
wherein the AR layer is requirements which are obtained by decomposing system requirements and are allocated to a subsystem or module level.
8. The requirement management method according to claim 5 , wherein after dividing all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement, the method further comprises:
classifying, according to a full life cycle of the system, non-functional attributes of the requirements of every layer into three service classifications that include a product delivery category, a product operation category and a product evolution category,
wherein the product delivery category represents a requirement arising in a process from completion of system development to delivery of the system to a user,
wherein the product operation category represents a requirement arising in an operation and maintenance process after the system is delivered to the user,
wherein the product evolution category represents a requirement arising in error correction, functional upgrading and product evolution processes of the system, and
wherein each requirement of every layer corresponds to one service classification of the three service classifications, and all the requirements of every layer of the system comprise all service classifications of the different service classifications.
9. The requirement management method according to claim 8 , wherein after classifying non-functional attributes of requirements of every layer into three service classifications, the method further comprises checking completeness of every requirement of all the requirements of the system, and if the non-functional attributes of all the requirements of the system do not comprise all service classifications of the three service classifications, sending prompt information to indicate that the requirements of the system fails in the completeness check.
10. A requirement management apparatus having a processor and further comprising:
a requirement dividing module configured to divide all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement;
a first direct progress rate obtaining module configured to obtain a direct progress rate of one of the requirements in the system, wherein the direct progress rate is a progress rate tested by using a test case directly associated with the one requirement;
a second direct progress rate obtaining module configured to obtain a direct progress rate of each requirement of all lower-layer requirements of the one requirement, wherein the direct progress rate of each requirement is a progress rate tested by using a test case directly associated with each requirement; and
a requirement progress rate obtaining module configured to calculate a mean of direct progress rates of all the lower-layer requirements to obtain a verification progress rate of the one requirement and configured to perform a weighting operation on the direct progress rate and the verification progress rate of the one requirement to obtain a progress rate of the one requirement in the system,
wherein the progress rate of the one requirement is calculated according to an equation:
F _ProgressRate= F _DirectProgressRate* X+F _VerificationProgressRate*(1− X ),
wherein F_ProgressRate is the progress rate of the one requirement, F_DirectProgressRate is the direct progress rate, F_VerificationProgressRate is the verification progress rate, and X is a set weight.
11. The requirement management apparatus according to claim 10 , wherein the requirement dividing module is configured to divide all the requirements of the system into 4 layers that include a user problem (PB) layer, a system feature (SF) layer, a system requirement (SR) layer and an allocated requirement (AR) layer, wherein the PB layer is the highest layer, wherein the SF layer is subordinate to the PB layer, wherein the SR layer is subordinate to the SF layer, wherein the AR layer is subordinate to the SR layer, wherein the PB layer is a requirement embodying a special concern of a user service, wherein the SF layer is a requirement which is of a great value and is provided by the system to solve user problems, wherein the SR layer is all functional and non-functional requirements provided by the system externally, and wherein the AR layer is requirements which are obtained by decomposing system requirements and are allocated to a subsystem or module level.
12. The requirement management apparatus according to claim 10 , further comprising:
a requirement classification module configured to classify, according to a full life cycle of the system, non-functional attributes of requirements of every layer into three service classifications that include a product delivery category, a product operation category and a product evolution category,
wherein the product delivery category represents a requirement arising in a process from completion of system development to delivery of the system to a user,
wherein the product operation category represents a requirement arising in an operation and maintenance process after the system is delivered to the user,
wherein the product evolution category represents a requirement arising in error correction, functional upgrading and product evolution processes of the system, and
wherein each requirement of requirements of every layer corresponds to one service classification of the different service classifications, and all the requirements of every layer of the system comprise all service classifications of the different service classifications.
13. The requirement management apparatus according to claim 12 , further comprising a requirement completeness checking module configured to check completeness of each requirement of all the requirements of the system, and if the non-functional attributes of all the requirements of the system do not comprise all service classifications of service classifications of every layer, send prompt information to indicate that the requirements of the system fail in the completeness check.
14. A requirement management apparatus having a processor and further comprising:
a requirement dividing module configured to divide all requirements of a system into layers from top to bottom according to a service object, a value and granularity of every requirement;
a first direct progress rate obtaining module configured to obtain a direct progress rate of one of the requirements in the system, wherein the direct progress rate is a progress rate tested by using a test case directly associated with the one requirement;
a second direct progress rate obtaining module configured to obtain a direct progress rate of each requirement of all lower-layer requirements of the one requirement, wherein the direct progress rate of each requirement is a progress rate tested by using a test case directly associated with each requirement; and
a requirement progress rate obtaining module configured to calculate a mean of direct progress rates of all the lower-layer requirements to obtain a verification progress rate of the one requirement and configured to perform a weighting operation on the direct progress rate and the verification progress rate of the one requirement to obtain a progress rate of the one requirement in the system,
wherein the requirement progress rate obtaining module is configured to calculate the verification progress rate F_VerificationProgressRate of the one requirement F according to an equation:
F_VerificationProgressRate
=
∑
i
=
1
n
F
i
_ProgressRate
n
;
and
calculate the progress rate F_ProgressRate of the one requirement F according to an equation:
F _ProgressRate= F _DirectProgressRate* X+F _VerificationProgressRate*(1− X ),
wherein n is the number of all the lower-layer requirements of the one requirement F, F i is an i th requirement of all the lower-layer requirements of the one requirement F, F_DirectProgressRate is the direct progress rate of F tested by using the test case directly associated with F, F i — ProgressRate is a direct progress rate of F i , and X is a set weight and has a value range of 0<=X<=1.
15. The requirement management apparatus according to claim 14 , wherein the requirement progress rate obtaining module is further configured to, after a direct progress rate of a lower-layer requirement F 1 of the one requirement F changes, calculate a progress rate F 1 — ProgressRate of F 1 according to an equation:
F 1 — ProgressRate= F 1 — ProgressRateOldValue+( F 1 — DirectProgressRateNewValue− F 1 — DirectProgressRateOldValue)* Y , and
calculate the progress rate F_ProgressRate of the one requirement F according to an equation:
F _ProgressRate= F _ProgressRateOldValue+( F 1 — ProgressRate− F 1 — ProgressRateOldValue)*(1− X )/ n,
wherein F 1 — ProgressRateOldValue is a progress rate of F 1 before change, F 1 — DirectProgressRateNewValue is a direct progress rate of F 1 after change, F 1 — DirectProgressRateOldValue is a direct progress rate of F 1 before change, Y is a set weight and has a value range of 0<=Y<=1, and F_ProgressRateOldValue is a progress rate of F before the lower-layer requirement F 1 changes; or
when the number of lower-layer requirements of the one requirement F is increased from n to m, calculate a progress rate F_ProgressRate of F after the number of lower-layer requirements changes, according to an equation:
F_ProgressRate
=
(
n
*
F_ProgressRateOldValue
+
(
m
-
n
)
*
F_DirectProgressRate
*
X
+
(
1
-
X
)
*
∑
i
=
n
+
1
m
F
i
_Progress
)
/
m
,
wherein F_ProgressRateOldValue is a direct progress rate of F before the number of lower-layer requirements changes, and F_DirectProgressRate is a direct progress rate of F after the number of lower-layer requirements changes; or
when the number of lower-layer requirements of the requirement F is reduced from n to k, calculate a progress rate F_ProgressRate of F after the number of lower-layer requirements changes, according to an equation:
F_ProgressRate
=
(
-
n
*
F_ProgressRateOldValue
+
(
n
-
k
)
*
F_DirectProgressRate
*
X
+
(
1
-
X
)
*
∑
i
=
k
+
1
n
F
i
_Progress
)
/
(
-
k
)
.
16. The requirement management apparatus according to claim 14 , wherein the requirement dividing module is configured to divide all the requirements of the system into 4 layers that include a user problem (PB) layer, a system feature (SF) layer, a system requirement (SR) layer and an allocated requirement (AR) layer, wherein the PB layer is the highest layer, wherein the SF layer is subordinate to the PB layer, wherein the SR layer is subordinate to the SF layer, wherein the AR layer is subordinate to the SR layer, wherein the PB layer is a requirement embodying a special concern of a user service, wherein the SF layer is a requirement which is of a great value and is provided by the system to solve user problems, wherein the SR layer is all functional and non-functional requirements provided by the system externally, and wherein the AR layer is requirements which are obtained by decomposing system requirements and are allocated to a subsystem or module level.
17. The requirement management apparatus according to claim 14 , further comprising:
a requirement classification module configured to classify, according to a full life cycle of the system, non-functional attributes of requirements of every layer into three service classifications that include a product delivery category, a product operation category and a product evolution category,
wherein the product delivery category represents a requirement arising in a process from completion of system development to delivery of the system to a user,
wherein the product operation category represents a requirement arising in an operation and maintenance process after the system is delivered to the user,
wherein the product evolution category represents a requirement arising in error correction, functional upgrading and product evolution processes of the system, and
wherein each requirement of requirements of every layer corresponds to one service classification of the different service classifications, and all the requirements of every layer of the system comprise all service classifications of the different service classifications.
18. The requirement management apparatus according to claim 17 , further comprising a requirement completeness checking module configured to check completeness of each requirement of all the requirements of the system, and if the non-functional attributes of all the requirements of the system do not comprise all service classifications of service classifications of every layer, send prompt information to indicate that the requirements of the system fail in the completeness check.Join the waitlist — get patent alerts
Track US8869096B2 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.