Software development tool for sharing test and deployment assets

• US 20070240102A1
• Filed: 03/02/2006
• Published: 10/11/2007
• Est. Priority Date: 03/02/2006
• Status: Abandoned Application

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Flores, Romelia, Palmer, Mark, Bello, Stephen
• Application Number:
  US11/366,013
• Publication Number:
  US 20070240102A1
• Time in Patent Office: Days
• US Class Current: 717/104
• CPC Class Codes: G06F 11/3672 Test management
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

A solution for sharing assets associated with componentized software units (software components) having a set of well defined interfaces. Each software component can be associated with a particular level of granularity and can be formed from one or more other lower-level software components. Each software components can be associated with one or more test assets as well as one or more deployment assets. The software components and associated assets can be stored in one or more shared asset repositories. Solutions and/or solution templates can be rapidly developed using automated tools associated with the shared asset repository, as previous design, test, and deployment efforts are able to be strongly leveraged.

Claims

1. A method for sharing reusable software development assets comprising:

componentizing a plurality of software components, each software component having a set of well defined interfaces;

cataloging the plurality of software components within different granularity levels, said granularity levels including a building block level and a system level, wherein at least a portion of the software components of the system level are formed using a plurality of software components of the building block level;

identifying a plurality of test assets, each test asset being associated with at least one of the software components, wherein the test assets include assets for functional testing, user acceptance testing, and performance testing; and

storing said software components and said test assets in a searchable asset repository, wherein the asset repository is accessible by a plurality of test teams, wherein the plurality of teams include teams performing different types of testing, wherein the different types of testing include functional testing, user acceptance testing, and performance testing, whereby functional test teams, user acceptance test teams, and performance test teams are able to access test assets of other teams performing tests upon related software components.

2. The method of claim 1, wherein the test assets include testing scripts, testing drivers, and testing data.

3. The method of claim 1, wherein the test assets include testing objectives, testing scenarios, and testing documentation.

4. The method of claim 1, further comprising:

providing a development interface configured to permit the creation and manipulation of a plurality of labs, wherein each lab permits user to graphically utilize assets of the asset repository for a specific software project.

5. The method of claim 4, wherein the asset repository is one of a plurality of asset repositories, each asset repository automatically sharing data relating to software components and test assets with other asset repositories, wherein different labs are associated with different asset repositories.

6. The method of claim 4, further comprising:

automatically populating a new one of the labs with previously stored software assets and test assets from at least one other lab.

7. The method of claim 4, wherein a plurality of labs utilize a same software component, said method further comprising:

presenting a change notification within other ones of the labs whenever one of the labs changes a stored asset associated with the same software component.

8. The method of claim 1, wherein the software components comprise Web services.

9. The method of claim 1, wherein said steps of claim 1 are performed by at least one machine in accordance with at least one computer program having a plurality of code sections that are executable by the at least one machine.

10. A software development graphical user interface comprising:

a user configurable lab, wherein the lab includes a plurality of graphical objects representing software components, wherein each software component is a componentized software unit having a set of well defined interfaces, and wherein each software component is categorized into one of a plurality of granularity level, said granularity levels including a building block level, a system level, and a solution level, and wherein each software component is associated with a plurality of test assets;

a functional development view of the lab that includes a plurality of graphical objects for functional test assets associated with the software components established for the lab; and

an integration testing view of the lab automatically generated at least in part using previously stored functional test assets and software components specified in the functional development view.

11. A method used for developing software comprising:

storing a plurality of assets within a shared asset repository, said assets comprising software components and test assets associated with the software components;

categorizing said assets by granularity level, wherein the stored software components comprise foundation software components and composite software components, wherein each composite software component comprises a plurality of foundation software components having a granularity level one lower than the composite software component;

identifying criteria for a new software component;

automatically determining at least one stored composite software component having similar criteria as the identified criteria by searching the shared asset repository, wherein the composite software component is categorized at the same level of granularity as the new software component;

utilizing a development interface to construct the new software component from a plurality of foundation software components associated with the at least one composite software components; and

testing the new software component utilizing at least one test asset previously stored within the shared asset repository that is associated with a software component selected from a group consisting of the foundation software components upon which the new software component was constructed and the automatically determined composite software component.

12. The method of claim 11, wherein said assets further comprise deployment assets associated with the software components, said method further comprising:

deploying the new software component utilizing at least one deployment asset previously stored within the shared asset repository that is associated with a software component selected from a group consisting of the foundation software components upon which the new software component was constructed and the automatically determined composite software component.

13. The method of claim 11, wherein said assets further comprise integration assets associated with the determined composite software component used to integrate at least two foundation software components to the composite software component, said method further comprising:

integrating the plurality of software components to the new software component using at least one of the integration assets.

14. The method of claim 11, wherein utilizing step further comprises:

presenting a lab interface for developing the new software component, said lab interface providing an automatically generated template for the new software component comprising the foundation software components, wherein the lab interface permits the template to be customized and thereafter stored for the new software component.

15. The method of claim 11, wherein the granularity levels of the categorizing step comprise at least three sequentially order levels, including an upper level, a middle level, and a lower level, wherein at least one upper level software component is formed from at least one middle level software component that is formed form at least one lower level software component, wherein each of the upper level software component, middle level software component, and lower level software component are software components stored in the asset repository, and wherein each is associated with at least one test asset stored in the asset repository.

16. The method of claim 15, wherein the upper level is a solution level, wherein the middle level is a system level, and wherein the lower level is a building block level.

17. The method of claim 11, said method further comprising:

storing the new software component in the shared asset repository; and

granting other users access to the new software component so that the determining step for at least one of the other users of the method returns the new software component as the automatically determined composite software component.

18. The method of claim 11, wherein the test assets include assets for functional testing, performance testing, and user acceptance testing, which are shared among different testing teams that perform testing against a stored software component associated with the test assets.

19. The method of claim 11, wherein the software components comprise Web services.

20. The method of claim 11, wherein said steps of claim 11 are performed by at least one machine in accordance with at least one computer program having a plurality of code sections that are executable by the at least one machine.