Generating a software complex using superordinate design input

• US 10,248,386 B2
• Filed: 06/27/2017
• Issued: 04/02/2019
• Est. Priority Date: 08/06/2015
• Status: Active Grant

• Current Assignee: Symphore, LLC
• Original Assignee: Symphore, LLC
• Inventors: Woodward, Christopher
• Primary Examiner(s): Khatri, Anil
• Application Number:
  US15/634,651
• Publication Number:
  US 20170293473A1
• Time in Patent Office: 644 Days
• Field of Search: 717104-108
• CPC Class Codes: G06F 8/20 Software design
• CPC Class Codes: G06F 8/35 model driven
• CPC Class Codes: G06F 8/70 Software maintenance or management
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for generating software complexes. In one aspect, a method includes defining a software complex that is to include a group of software members that share information inherent to the software complex and act on that information. The defining includes receiving selections of design aspects as superordinate design inputs for the software complex and storing the superordinate design inputs in a source data store. The superordinate design inputs are compiled in the source data store using a software complex architectural language compiler. An in-memory model of the software complex is generated as an output of the compilation. Software member emitters are selected. For each selected software member emitter, a software member of the defined type of the selected software member emitter is generated.

Claims

1. A computer-implemented method, comprising:

receiving data specifying selections of design aspects as superordinate design inputs for a software complex that will include a group of software members including at least one executable, the design aspects including a software as a service design aspect that specifies that the software complex will include one or more software as a service features;

generating an in-memory model of the software complex including identifying and configuring, based on the superordinate design inputs, a set of software implements that each specify an implementation of one or more software features of the software complex in one or more types of software members of the software complex, the set of software implements including one or more software implements for implementing the one or more software as a service features;

selecting, based on the superordinate design inputs and the in-memory model, a plurality of software member emitters, each software member emitter being arranged to emit a software member of a defined type, wherein each type is different from each other type; and

for each selected software member emitter, generating a software member of the defined type of the selected software member emitter, wherein at least one of the selected software member emitters generates a software member that implements at least one of the one or more software as a service features.

2. The method of claim 1, wherein receiving data specifying selections of design aspects comprises:

providing a user interface that enables a user to select and define design aspects for the software complex; and

receiving, at the user interface, selections and definitions of the design aspects.

3. The method of claim 1, wherein the software member that implements at least one of the one or more software as a service features comprises a software as a service database.

4. The method of claim 1, further comprising:

receiving updated data specifying one or more updated design aspects for the software complex subsequent to generating the software members;

generating an updated in-memory model based on the one or more updated design aspects; and

generating, based on the updated in-memory model, software members for a second software complex different from the software complex.

5. The method of claim 4, wherein the updated in-memory model is generated based on the updated design aspects and at least one design aspect specified by the received data that was not updated.

6. The method of claim 4, wherein the one or more updated design aspects include a platform for the second software complex that is different from each platform of the software complex.

7. The method of claim 6, wherein the platform for the second software complex is associated with one or more software members that are included in the second software complex but that are not included in the software complex.

8. A system, comprising:

a data processing apparatus; and

a memory storage apparatus in data communication with the data processing apparatus, the memory storage apparatus storing instructions executable by the data processing apparatus and that upon such execution cause the data processing apparatus to perform operations comprising;

receiving data specifying selections of design aspects as superordinate design inputs for a software complex that will include a group of software members including at least one executable, the design aspects including a software as a service design aspect that specifies that the software complex will include one or more software as a service features;

generating an in-memory model of the software complex including identifying and configuring, based on the superordinate design inputs, a set of software implements that each specify an implementation of one or more software features of the software complex in one or more types of software members of the software complex, the set of software implements including one or more software implements for implementing the one or more software as a service features;

selecting, based on the superordinate design inputs and the in-memory model, a plurality of software member emitters, each software member emitter being arranged to emit a software member of a defined type, wherein each type is different from each other type; and

for each selected software member emitter, generating a software member of the defined type of the selected software member emitter, wherein at least one of the selected software member emitters generates a software member that implements at least one of the one or more software as a service features.

9. The system of claim 8, wherein receiving data specifying selections of design aspects comprises:

providing a user interface that enables a user to select and define design aspects for the software complex; and

receiving, at the user interface, selections and definitions of the design aspects.

10. The system of claim 8, wherein the software member that implements at least one of the one or more software as a service features comprises a software as a service database.

11. The system of claim 8, wherein the operations comprise:

receiving updated data specifying one or more updated design aspects for the software complex subsequent to generating the software members;

generating an updated in-memory model based on the one or more updated design aspects; and

generating, based on the updated in-memory model, software members for a second software complex different from the software complex.

12. The system of claim 11, wherein the updated in-memory model is generated based on the updated design aspects and at least one design aspect specified by the received data that was not updated.

13. The system of claim 11, wherein the one or more updated design aspects include a platform for the second software complex that is different from each platform of the software complex.

14. The system of claim 13, wherein the platform for the second software complex is associated with one or more software members that are included in the second software complex but that are not included in the software complex.

15. A non-transitory computer storage medium encoded with a computer program, the program comprising instructions that when executed by a data processing apparatus cause the data processing apparatus to perform operations comprising:

receiving data specifying selections of design aspects as superordinate design inputs for a software complex that will include a group of software members including at least one executable, the design aspects including a software as a service design aspect that specifies that the software complex will include one or more software as a service features;

generating an in-memory model of the software complex including identifying and configuring, based on the superordinate design inputs, a set of software implements that each specify an implementation of one or more software features of the software complex in one or more types of software members of the software complex, the set of software implements including one or more software implements for implementing the one or more software as a service features;

selecting, based on the superordinate design inputs and the in-memory model, a plurality of software member emitters, each software member emitter being arranged to emit a software member of a defined type, wherein each type is different from each other type; and

for each selected software member emitter, generating a software member of the defined type of the selected software member emitter, wherein at least one of the selected software member emitters generates a software member that implements at least one of the one or more software as a service features.

16. The non-transitory computer storage medium of claim 15, wherein receiving data specifying selections of design aspects comprises:

providing a user interface that enables a user to select and define design aspects for the software complex; and

receiving, at the user interface, selections and definitions of the design aspects.

17. The non-transitory computer storage medium of claim 15, wherein the software member that implements at least one of the one or more software as a service features comprises a software as a service database.

18. The non-transitory computer storage medium of claim 15, wherein the operations comprise:

receiving updated data specifying one or more updated design aspects for the software complex subsequent to generating the software members;

generating an updated in-memory model based on the one or more updated design aspects; and

generating, based on the updated in-memory model, software members for a second software complex different from the software complex.

19. The non-transitory computer storage medium of claim 18, wherein the updated in-memory model is generated based on the updated design aspects and at least one design aspect specified by the received data that was not updated.

20. The non-transitory computer storage medium of claim 19, wherein:

the one or more updated design aspects include a platform for the second software complex that is different from each platform of the software complex; and

the platform for the second software complex is associated with one or more software members that are included in the second software complex but that are not included in the software complex.