System and method for system integration test (SIT) planning

• US 8,352,237 B2
• Filed: 09/11/2009
• Issued: 01/08/2013
• Est. Priority Date: 09/11/2009
• Status: Expired due to Fees

• Current Assignee: Broadcom Semiconductors Israel Limited (Broadcom, Inc.)
• Original Assignee: International Business Machines Corporation
• Inventors: Bassin, Kathryn A., Kagan, Steven, Li, Shao C., Li, Zhong J., Liu, He H., Skrabanek, Susan E., Tan, Hua F., Zhu, Jun
• Primary Examiner(s): ALHIJA, SAIF A
• Application Number:
  US12/558,375
• Publication Number:
  US 20110066420A1
• Time in Patent Office: 1,215 Days
• Field of Search: 703/22
• US Class Current: 703/22
• CPC Class Codes: A61B 5/7275 Determining trends in physiological measurement data; Predicting development of a medical condition based on physiological measurements, e.g. determining a risk factor
• CPC Class Codes: G06F 11/3676 for coverage analysis
• CPC Class Codes: G16H 50/30 for calculating health indices; for individual health risk assessment

Abstract

A method is implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions. The programming instructions are operable to receive a system architecture model of a system and receive trigger coverage rules. Additionally, the programming instructions are operable to determine system integration test (SIT) coverage for each connection and interface of the system architecture model and select a set of use cases execution scenarios to satisfy the SIT coverage.

Claims

1. A method implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions operable to:

receive a system architecture model of a system using a processor, wherein the receiving the system architecture model comprises;

determining whether the system architecture model exists;

importing the system architecture model when determined to exist;

when the system architecture model is determined to not exist;

identifying and capturing a components model of the system architecture model;

identifying and capturing a connections model of the system architecture model; and

refining the connections model into interface models;

annotating the system architecture model; and

mapping from the system architecture model to one or more use case models;

receive trigger coverage rules;

determine system integration test (SIT) coverage for each connection and interface of the system architecture model; and

select a set of use cases execution scenarios to satisfy the SIT coverage.

2. The method of claim 1, wherein the components model comprises at least one of a system, a sub system and a module of the system architecture model.

3. The method of claim 1, wherein the connection model comprises at least one of a connection and an interface between components of the system architecture model.

4. The method of claim 1, wherein the one or more use case models represent business functions of the system.

9. The method of claim 1, wherein the selecting the set of use case execution scenarios to satisfy the SIT coverage comprises selecting a minimum set of use case execution scenarios to satisfy the SIT coverage.

10. The method of claim 9, wherein selecting the minimum set of use case execution scenarios to satisfy the SIT coverage, comprises:

determining a minimum set of use case execution scenarios; and

generating an SIT plan from the minimum set of use case execution scenarios.

12. The method of claim 1, wherein a service provider at least one of creates, maintains, deploys and supports the computer infrastructure.

13. The method of claim 1, wherein steps are provided by a service provider on a subscription, advertising, and/or fee basis.

5. A method implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions operable to:

receive a system architecture model of a system using a processor;

receive trigger coverage rules;

determine system integration test (SIT) coverage for each connection and interface of the system architecture model; and

select a set of use cases execution scenarios to satisfy the SIT coverage,

wherein the receiving the trigger coverage rules comprises;

receiving projected occurrence frequencies for each of a plurality of SIT triggers for each connection and interface of the system architecture model; and

determining one or more rules for adjusting the projected occurrence frequencies based on one or more risk levels.

6. The method of claim 5, wherein:

the one or more risk levels is one of high risk, medium risk, and low risk, wherein the medium risk ranges between the high risk and the low risk, and the determining one or more rules for adjusting the one or more of the projected occurrence frequencies comprises;

increasing a projected occurrence frequency for a connection having a high risk; and

decreasing a projected occurrence frequency for a connection having a low risk.

7. The method of claim 5, wherein the plurality of SIT triggers comprise at least one of coverage, variation, sequencing and interaction.

8. The method of claim 5, wherein the determining the system integration test (SIT) coverage for each connection and interface of the system architecture model comprises:

determining a risk level of one or more connections of the system architecture model; and

adjusting the projected occurrence frequencies for each of a plurality of SIT triggers for each connection and interface of the system architecture model based on the risk level of the one or more connections.

11. A method implemented in a computer infrastructure having computer executable code tangibly embodied on a computer readable storage medium having programming instructions operable to:

receive a system architecture model of a system using a processor;

receive trigger coverage rules;

determine system integration test (SIT) coverage for each connection and interface of the system architecture model; and

select a set of use cases execution scenarios to satisfy the SIT coverage,

wherein the selecting the set of use case execution scenarios to satisfy the SIT coverage comprises selecting a minimum set of use case execution scenarios to satisfy the SIT coverage;

wherein determining the minimum set of use case execution scenarios comprises;

setting the minimum set of use case execution scenarios to a null set;

detecting a use case scenario from a plurality of use case scenarios which covers a highest number of uncovered SIT trigger requirements;

adding the use case scenario to an intermediate set of use case execution scenarios;

determining whether the intermediate set of use case execution scenarios satisfies the SIT coverage; and

wherein;

when the intermediate set of use case execution scenarios satisfies the SIT coverage, setting the intermediate set of use case execution scenarios as the minimum set of use case execution scenarios; and

when the intermediate set of use case execution scenarios does not satisfy the SIT coverage, reverting to the detecting.

14. A system implemented in hardware, comprising:

a system architecture model acquisition (SAMA) tool, implemented in a processor, operable to receive a system architecture model of a system, wherein the receiving the system architecture model comprises;

determining whether the system architecture model exists;

importing the system architecture model when determined to exist;

when the system architecture model is determined to not exist;

identifying and capturing a components model of the system architecture model;

identifying and capturing a connections model of the system architecture model; and

refining the connections;

model into interface;

models;

annotating the system architecture model; and

mapping from the system architecture model to one or more use case models;

a trigger coverage rule (TCR) tool operable to receive trigger coverage rules;

a system integration test (SIT) coverage determination tool operable to determine SIT trigger coverage for each connection and interface of the system architecture model; and

a use case scenario selection (UCSS) tool operable to select a set of use cases execution scenarios to satisfy the SIT trigger coverage.

15. The system of claim 14, wherein:

the components model comprises at least one of a system, a sub system and a module of the system architecture model;

the connection model comprises at least one of a connection and an interface between components of the system architecture model; and

the one or more use case models represent business functions of the system.

20. The system of claim 14, wherein the selecting the set of use case execution scenarios to satisfy the SIT coverage comprises selecting a minimum set of use case execution scenarios to satisfy the SIT coverage, comprising:

determining a minimum set of use case execution scenarios; and

generating an SIT plan from the minimum set of use case execution scenarios.

16. A system implemented in hardware, comprising:

a system architecture model acquisition (SAMA) tool, implemented in a processor, operable to receive a system architecture model of a system;

a trigger coverage rule (TCR) tool operable to receive trigger coverage rules;

a system integration test (SIT) coverage determination tool operable to determine SIT trigger coverage for each connection and interface of the system architecture model; and

a use case scenario selection (UCSS) tool operable to select a set of use cases execution scenarios to satisfy the SIT trigger coverage, wherein the receiving the trigger coverage rules comprises;

receiving projected occurrence frequencies for each of a plurality of SIT triggers for each connection and interface of the system architecture model; and

determining one or more rules for adjusting the projected occurrence frequencies based on one or more risk levels.

17. The system of claim 16, wherein:

the one or more risk levels is one of high risk, medium risk and low risk, wherein the medium risk ranges between the high risk and the low risk, and the determining one or more rules for adjusting the one or more of the projected occurrence frequencies comprises;

increasing a projected occurrence frequency for a connection having a high risk; and

decreasing a projected occurrence frequency for a connection having a low risk.

18. The system of claim 16, wherein the plurality of SIT triggers comprise at least one of coverage, variation, sequencing and interaction.

19. A system implemented in hardware, comprising:

a system architecture model acquisition (SAMA) tool, implemented in a processor, operable to receive a system architecture model of a system;

a trigger coverage rule (TCR) tool operable to receive trigger coverage rules;

a system integration test (SIT) coverage determination tool operable to determine SIT trigger coverage for each connection and interface of the system architecture model; and

a use case scenario selection (UCSS) tool operable to select a set of use cases execution scenarios to satisfy the SIT trigger coverage, wherein, wherein the determining the system integration test (SIT) coverage for each connection and interface of the system architecture model comprises;

determining a risk level of one or more connections of the system architecture model; and

adjusting the projected occurrence frequencies for each of a plurality of SIT triggers for each connection and interface of the system architecture model based on the risk level of the one or more connections.

21. A computer program product comprising a computer readable storage medium having readable program code embodied in the storage medium, the computer program product includes at least one component operable to:

receive a system architecture model of a system, using a processor wherein the system architecture model comprises;

a components model comprising at least one of a system, a sub system and a module of the system architecture model;

a connection model comprising at least one of a connection and an interface between components of the system architecture model; and

one or more use case models represent business functions of the system;

receive trigger coverage rules;

determine system integration test (SIT) coverage for each connection and interface of the system architecture model; and

select a minimum set of use cases execution scenarios to satisfy the SIT coverage wherein;

the receiving the trigger coverage rules comprises;

receiving projected occurrence frequencies for each of a plurality of SIT triggers for each connection and interface of the system architecture model; and

determining one or more rules for adjusting the projected occurrence frequencies based on one or more risk levels, wherein;

the one or more risk levels is one of high risk, medium risk and low risk wherein the medium risk ranges between the high risk and the low risk; and

the determining one or more rules for adjusting the one or more of the projected occurrence frequencies comprises;

increasing a projected occurrence frequency for a correction having a high risk; and

decreasing a projected occurrence frequency for a connection having a low risk; and

the determining the system integration test (SIT) coverage for each connection and interface of the system architecture model comprises;

determining a risk level of one or more connections of the system architecture model; and

adjusting the projected occurrence frequencies for each of a plurality of SIT triggers for each connection and interface of the system architecture model based on the risk level of the one or more connections.