Supporting a work packet request with a specifically tailored IDE

• US 8,782,598 B2
• Filed: 09/12/2012
• Issued: 07/15/2014
• Est. Priority Date: 07/31/2008
• Status: Expired due to Fees

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Chaar, Jarir K., Huchel, Joseph P., Jobson, Thomas A.
• Primary Examiner(s): Nguyen, Phillip H
• Application Number:
  US13/611,902
• Publication Number:
  US 20130014081A1
• Time in Patent Office: 671 Days
• Field of Search: 717/106, 717/109, 717/107, 717/108
• US Class Current: 717/109
• CPC Class Codes: G06F 8/00 Arrangements for software engineering testing or debugging G06F11/36; administrative, planning or organisation aspects of software project management G06Q10/06
• CPC Class Codes: G06F 8/20 Software design

Abstract

A computer-implemented method, system, and/or computer program product supports a user who is servicing a work packet request within a software factory. A tooling environment that is necessary to service a work packet request in a software factory is established. The software factory includes an assembly line that executes work packets to create the deliverable software, and a published set of services that describes what assembly services for assembling the work packets are offered by the assembly line. A full work packet-aware Integrated Development Environment (IDE) that is specific for a work packet identified by the work packet request is created. The full work packet-aware IDE and an associated Graphical User Interface (GUI) are transmitted to a user who has been assigned to service the work packet request, thus allowing resources depicted in the GUI to be interactively supplied to that user.

Claims

1. A processor-implemented method of supporting a user who is servicing a work packet request within a software factory, the processor-implemented method comprising:

establishing a needed tooling environment that is necessary to service a work packet request in a software factory, wherein the software factory comprises;

an assembly line and job shop that receive and execute work packets to create a deliverable software, wherein the work packets include governance procedures, standards, reused assets, work packet instructions, integration strategy, schedules, exit criteria and artifact checklist templates for Input/Output routines, and

a published set of services that are published to a design center, and wherein the published set of services describes what assembly services for assembling the work packets are offered by the assembly line and job shop;

creating, by a processor, a full work packet-aware Integrated Development Environment (IDE) that is specific for a work packet that is identified by the work packet request, wherein the full work packet-aware IDE provides specifically tailored access to all resources that are needed to service the work packet request;

transmitting the full work packet-aware IDE and an associated Graphical User Interface (GUI) to a user who has been assigned to service the work packet request; and

interactively supplying the user with resources depicted in the GUI.

2. The processor-implemented method of claim 1, wherein the full work packet-aware IDE includes a pre-populated window of Instant Messaging (IM) users, wherein the IM users are on a same team as the user for launching a project that utilizes the work packet.

3. The processor-implemented method of claim 1, wherein the full work packet-aware IDE includes a hardware resource window, wherein the hardware resource window is pre-populated with access to hardware resources that are required to service the work packet request, and wherein requisite hardware resources depicted in the hardware resource window are automatically brought on line with the full work packet-aware IDE in response to the user selecting one or more of the requisite hardware resources.

4. The processor-implemented method of claim 1, wherein the full work packet-aware IDE includes a Lightweight Directory Access Protocol window, and wherein the processor-implemented method further comprises:

in response to the user clicking an icon that represents a particular listed software resource in an LDAP tree, automatically retrieving the particular listed software resource that is represented by the icon that the user has clicked.

5. The processor-implemented method of claim 1, wherein operations within the software factory further comprise:

collecting a plurality of software artifacts that have been archived during an assembly of previous work packets;

collecting a plurality of metrics that have been utilized during the assembly of previous work packets;

defining a template for a new work packet, wherein the template for the new work packet is created by a packet definition process that defines attributes that are needed in the new work packet;

under a control of the packet definition process, selecting requisite software artifacts from the plurality of software artifacts;

under the control of the packet definition process, selecting requisite metrics from the plurality of metrics; and

sending the template, requisite software artifacts and requisite metrics to a packet assembly process, wherein the packet assembly process assembles, under the control of the template and the requisite metrics, the requisite software artifacts to create the new work packet.

6. The processor-implemented method of claim 1, wherein the software factory further comprises:

a software factory governance section that evaluates a project proposal for acceptance by the software factory.

7. The processor-implemented method of claim 1, wherein the software factory further comprises:

a published set of requirements for the assembly line and job shop, wherein the published set of requirements for the assembly line and job shop are published to the design center, and wherein the published set of requirements describes what execution environment must be used by work packets that are provided by the design center for assembly in the assembly line and job shop.

8. The processor-implemented method of claim 1, wherein the assembly line and job shop include software that automatically recognizes a project type for a project proposal, and wherein the assembly line and job shop assemble the work packets into the deliverable software in accordance with the project type that is recognized by the assembly line and job shop.

9. The processor-implemented method of claim 1, wherein the assembly line and job shop conduct an integration test, a system test, a system integration test and a performance test of the deliverable software, wherein the integration test tests the deliverable software for compatibility with the client'"'"'s system, the system test checks the client'"'"'s system to ensure that the client'"'"'s system is operating properly, the system integration test tests for bugs that may arise when the deliverable software is integrated into the client'"'"'s system, and the performance test tests the deliverable software for defects as it is executing in the client'"'"'s system.

10. A system comprising:

a processor;

a data bus coupled to the processor;

a memory coupled to the data bus; and

a tangible computer-usable medium on which is stored computer program code, the computer program code comprising instructions executable by the processor and configured for supporting a user who is servicing a work packet request within a software factory by performing the steps of;

establishing a needed tooling environment that is necessary to service a work packet request in a software factory, wherein the software factory comprises;

an assembly line and job shop that receive and execute work packets to create a deliverable software, wherein the work packets include governance procedures, standards, reused assets, work packet instructions, integration strategy, schedules, exit criteria and artifact checklist templates for Input/Output routines, and

a published set of services that are published to a design center, and wherein the published set of services describes what assembly services for assembling the work packets are offered by the assembly line and job shop;

creating a full work packet-aware Integrated Development Environment (IDE) that is specific for a work packet that is identified by the work packet request, wherein the full work packet-aware IDE provides specifically tailored access to all resources that are needed to service the work packet request;

transmitting the full work packet-aware IDE and an associated Graphical User Interface (GUI) to a user who has been assigned to service the work packet request; and

interactively supplying the user with resources depicted in the GUI.

11. The system of claim 10, wherein the full work packet-aware IDE includes a pre-populated window of Instant Messaging (IM) users, wherein the IM users are on a same team as the user for launching a project that utilizes the work packet.

12. The system of claim 10, wherein the full work packet-aware IDE includes a hardware resource window, wherein the hardware resource window is pre-populated with hardware resources that are required to service the work packet request, and wherein requisite hardware resources depicted in the hardware resource window are automatically brought on line with the full work packet-aware IDE in response to the user selecting one or more of the requisite hardware resources.

13. The system of claim 10, wherein the full work packet-aware IDE includes a Lightweight Directory Access Protocol window, and wherein the computer program code further comprises instructions executable by the processor and configured for:

in response to the user clicking an icon that represents a particular listed software resource in an LDAP tree, automatically retrieving the particular listed software resource that is represented by the icon that the user has clicked.

14. The system of claim 10, wherein the software factory further comprises:

a published set of requirements for the assembly line and job shop, wherein the published set of requirements for the assembly line and job shop are published to the design center, and wherein the published set of requirements describes what execution environment must be used by work packets that are provided by the design center for assembly in the assembly line and job shop.

15. A computer program product for supporting a user who is servicing a work packet request within a software factory, the computer program product comprising a non-transitory computer readable storage medium having program code embodied therewith, the program code readable and executable by a processor to perform a method comprising:

establishing a needed tooling environment that is necessary to service a work packet request in a software factory, wherein the software factory comprises;

an assembly line and job shop that receive and execute work packets to create a deliverable software, wherein the work packets include governance procedures, standards, reused assets, work packet instructions, integration strategy, schedules, exit criteria and artifact checklist templates for Input/Output routines, and

a published set of services that are published to a design center, and wherein the published set of services describes what assembly services for assembling the work packets are offered by the assembly line and job shop;

creating a full work packet-aware Integrated Development Environment (IDE) that is specific for a work packet that is identified by the work packet request, wherein the full work packet-aware IDE provides specifically tailored access to all resources that are needed to service the work packet request;

transmitting the full work packet-aware IDE and an associated Graphical User Interface (GUI) to a user who has been assigned to service the work packet request; and

interactively supplying the user with resources depicted in the GUI.

16. The computer program product of claim 15, wherein the full work packet-aware IDE includes a pre-populated window of Instant Messaging (IM) users, wherein the IM users are on a same team as the user for launching a project that utilizes the work packet.

17. The computer program product of claim 15, wherein the full work packet-aware IDE includes a hardware resource window, and wherein the computer program product further comprises program code that is readable and executable by the processor for:

pre-populating the hardware resource window with hardware resources that are required to service the work packet request, and automatically bringing on line requisite hardware resources depicted in the hardware resource window with the full work packet-aware IDE in response to the user selecting one or more of the requisite hardware resources.

18. The computer program product of claim 15, wherein the full work packet-aware IDE includes a Lightweight Directory Access Protocol window, and wherein the computer program product further comprises program code that is readable and executable by the processor for:

in response to the user clicking an icon that represents a particular listed software resource in an LDAP tree, automatically retrieving the particular listed software resource that is represented by the icon that the user has clicked.

19. The computer program product of claim 15, wherein the software factory further comprises:

a published set of requirements for the assembly line and job shop, wherein the published set of requirements for the assembly line and job shop are published to the design center, and wherein the published set of requirements describes what execution environment must be used by work packets that are provided by the design center for assembly in the assembly line and job shop.

20. The computer program product of claim 15, wherein the computer executable instructions are capable of being provided by a service provider to a customer on an on-demand basis.