Method for mapping the structure of a complex software product

• US 8,650,539 B2
• Filed: 12/04/2007
• Issued: 02/11/2014
• Est. Priority Date: 12/21/2006
• Status: Expired due to Fees

• Current Assignee: Siemens Healthcare GMBH (Siemens AG)
• Original Assignee: Siemens AG
• Inventors: Gbel, Michael
• Primary Examiner(s): Wong, Don
• Assistant Examiner(s): KRETZMER, ERIKA A
• Application Number:
  US11/987,739
• Publication Number:
  US 20080155494A1
• Time in Patent Office: 2,261 Days
• Field of Search: None
• US Class Current: 717/120
• CPC Class Codes: G06F 8/10 Requirements analysis; Specification techniques
• CPC Class Codes: G06F 8/70 Software maintenance or management

Abstract

To allow simplified illustration of the complex technical relationships for a complex software product, provision is made for the structure of the complex software product to be mapped, in at least one embodiment, using an at least three-dimensional system matrix. In this context, the latter is generated by the variables functionality, program components and version level. The complex software product of at least one embodiment is formed by a plurality of functionalities, each functionality being formed by the interaction of a plurality of executable program components associated with it and the program components having one of a plurality of possible version levels. In at least one embodiment, the system matrix is used to check, verify and possibly extend a customer configuration for the software product. At the same time, the matrix is also used to extend the complex software product on the software provider side.

Claims

1. A method for mapping a structure of a complex software product, comprising:

implementing a plurality of functionalities in the complex software product, each functionality being formed by interaction of a plurality of executable program components associated with each functionality, the program components including one of a plurality of version levels;

generating an at least three-dimensional system matrix, the system matrix having at least three axes representing at least a functionality variable, a program component variable, and a version level variable, at least one item of information from a further variable being stored for each of the plurality of program components in the version level variable, the further variable including each of, frequency of error in the program component from a particular version level, reference to a specification for the program component from a particular version level, the specification specifying requirements for the plurality of program components to meet, reference to test schedules for the development of new program components from a particular version level, and reference to documentation for the program component from a particular version level;

mapping an association between the program components at their respective version level and the functionalities in the system matrix;

using the system matrix to ascertain an existing customer configuration for the complex software product, the customer configuration being the complex software product usable by a customer; and

transmitting the system matrix of the existing customer configuration to an external evaluation unit, where the transmitted system matrix is used to construct a test customer configuration identical to the existing customer configuration.

2. The method as claimed in claim 1, further comprising at least one of:

reproducing processes using the test customer configuration, and

analyzing errors using the test customer configuration.

3. The method as claimed in claim 1, further comprising:

implementing a new functionality in the complex software product, the system matrix being used to ascertain what additional program components are required at what version level.

4. The method as claimed in claim 3, wherein the new functionality is provided by a software product manufacturer and implemented in the existing customer configuration, execution of the new functionality requiring defined program components, and wherein the additionally required program components are ascertained by using the system matrix to ascertain which of the defined program components are already implemented in the software product.

5. The method as claimed in claim 3, wherein the new functionality is implemented as part of further development of the complex software product.

6. The method as claimed in claim 1, wherein the at least one item of information in the system matrix corresponds to a value in a field associated with the respective component at the respective version level.

8. The method as claimed in claim 1, further comprising:

evaluating the further variable for all program components associated with a particular functionality.

9. The method as claimed in claim 1, further comprising:

evaluating the further variable over all functionalities for a respective one of the program components in the respective version.

11. The. method as claimed in claim 1, further comprising:

additionally using a routine to automatically evaluate the system matrix.

12. A non-transitory computer readable medium including program segments for, when executed on a computer device, causing the computer device to implement the method of claim 1.

15. The method of claim 1, further comprising:

at least one of checking, verifying, and extending an existing customer configuration for the software product using the system matrix.

16. The method of claim 1, further comprising:

extending the complex software product on the software provider side using the system matrix.

7. A method for mapping a structure of a complex software product, comprising:

implementing a plurality of functionalities in the complex software product, each functionality being formed by interaction of a plurality of executable program components associated with each functionality, the program components including one of a plurality of version levels;

generating an at least three-dimensional system matrix, the system matrix having at least three axes representing at least a functionality variable, a program component variable, and a version level variable;

the system matrix storing at least one item of information from a further variable for the individual program components in the respective version, the at least one item of information in the system matrix being indicated as a value in a field associated with the respective component at the respective version level, the system matrix having a plurality of additional items of information in the respective field of the system matrix are indicated as n-tuples, the n-tuples being a series of digits, the digits being arranged at discrete positions and the digits associated to the respective additional items of information, the digits of the n-tuple indicating, a frequency of error in the program component from a particular version level, a specification for the program component from a particular version level, the specification specifying requirements for each of the plurality of program components to meet, a test schedule for the development of new program components from a particular version level, and a documentation associated with a respective program component for a particular version level; and

mapping an association between the program components at their respective version level and the functionalities in the system matrix.

10. The method as claimed in claim 7, further comprising:

creating overall documentation from the one or more references to documentation for different program components in the respective version.

13. A non-transitory computer readable medium including program segments for, when executed on a computer device, causing the computer device to implement the method of claim 7.

14. A non-transitory computer readable medium including program segments for, when executed on a computer device, causing the computer device to implement the method of claim 10.