System for generating software source code components

• US 4,734,854 A
• Filed: 10/08/1985
• Issued: 03/29/1988
• Est. Priority Date: 10/08/1985
• Status: Expired due to Term

• Current Assignee: NCR Corporation
• Original Assignee: American Telephone & Telegraph Company (AT&T, Inc.), AT&T Information Systems Inc. (AT&T, Inc.)
• Inventors: Afshar, Siroos K.
• Primary Examiner(s): Zache, Raulfe B.
• Application Number:
  US06/785,787
• Time in Patent Office: 903 Days
• Field of Search: 364/200 MS File, 364/300
• US Class Current: 717/107
• CPC Class Codes: G06F 8/36 Software reuse

Abstract

A system has been devised that allows commonly used software components to be designed and developed only once, and reused many times in different applications with different operational contexts and requirements. The system includes a language for the specification of software components in a context-independent generic fashion, a compiler for the specification language and a program for generating concrete software components to work in a specific context.

Claims

1. A system for generating concrete software programs from supplied generic specifications, said system comprising

a compiler for compiling language statements specifying generic software components, each specified generic software component corresponding to one or more user requestable programming services, and each of said programming services being specified by a collection of language statements,

means responsive to said compiler for storing the compiled language statements specifying said generic software components,

means having an input for receiving language statements specifying a particular software application, the language statements specifying said particular software application including at least one indirect statement and at least one request statement, each indirect statement naming any one of said specified generic software components and each request statement naming one user requestable programming service in one named generic software component, said receiving means including

first means responsive to each indirect statement for locating the stored language statements specifying the one generic software component named in that indirect statement,

second means responsive to each request statement for locating the collection of language statements specifying the user requestable programming service named in that request statement in the stored language statements located by said first means, and

means responsive to the collection of language statements located by said second means for creating a concrete version of said particular software application wherein said concrete version is devoid of indirect and request statements.

2. The system set forth in claim 1 wherein each generic software component in a portion of said specified generic software components has at least one assoicated parameter and the indirect and request statements of said particular software application respectively include at least one second indirect statement and at least one second request statement, each second indirect statement names any one generic software component in said portion and specifies a value for each associated parameter and each second request statement names one user requestable service in one named generic software component in said portion, and wherein said receiving means further includes third means responsive to each second indirect statement for correlating the stored language statements located by said first means which specify the generic software component named in that second indirect statement and the value of each associated parameter, and said creating means creating said concrete version of said particular software application also in response to the correlated language statements.

3. The system set forth in claim 2 wherein said particular software application contains a plurality of indirect statements each referencing an identical generic software component in said portion and specifying different values for an identical associated parameter, and

wherein said receiving means includes means for establishing a plurality of different instances of said identical generic software component referenced by said plurality of indirect statements, and means for establishing different names for an identical user requestable service provided by each instance of said identical generic software component.

4. The system of claim 1 wherein said collection of language statements specifying said particular software application may include instructions for inserting indirect statements and request statements referencing an identical or a different generic software component, and wherein said receiving means includes means for monitoring the language statements located by said second means for instructions for inserting indirect and request statements and for reapplying said language statements located by said second means to said input of said receiving means.

5. A system for expanding a collection of language statements under control of a set of instructions written in a transformation language having language statement-to-language statement constructs, said system having means for storing general purpose components, each of said general purpose components corresponding to one or more user requestable transformations, each transformation being specified by a collection of transformation language statements,

means for receiving a collection of user language statements including at least one context specifier statement and at least one request statement, each context specifier statement naming any one of said stored general purpose components and each request statement naming one user requestable transformation in one named general purpose component, said receiving means including

means responsive to each context specifier statement for locating the general purpose component named in that context specifier statement in said stored general purpose components,

means responsive to receipt of each request statement for locating the user requestable transformation named in that request statement in any general purpose component located by said first means, and

means controlled by each located transformation for creating an expanded version of said user-supplied language statements.

6. The system of claim 5 wherein each generic software component in a portion of the stored generic software components has at least associated parameter and said context specifier and request statements respectively include at least one second context specifier statement and at least one second request statement, each second context specifier statement names any one generic software component in said portion and specifies a value for each associated parameter and each second request statement names one transformation in one named generic software component in said portion, and wherein said receiving means further includes means responsive to each second context specifier statement for correlating each stored generic software component named in that second context specifier statement and the value of each associated parameter, and said creating means creating said expanded version of said user-supplied language statements also in response to each correlated generic software component.

7. The system set forth in claim 6 wherein said user-supplied input statements contain a plurality of context specifier statements each referencing an identical generic software component, each such context specifier statement specifying a different set of parameter values, and

wherein said receiving means includes means for establishing a plurality of different instances of each identical generic software component and means for distinguishing between an identical transformation provided by said instances of each identical generic software component.

8. An operating arrangement for use in a computer system in which a program including source code language statements is passed through a conversion process to generate a machine language version of said program, said operating arrangement comprising

a memory;

means for storing general purpose software components in said memory, each of said general purpose components corresponding to one or more user requestable transformations, and each transformation being specified by a collection of language statements such that any one of said general purpose components may control an expansion of user-supplied input language into other language statements,

instantiator means having an input for receiving a source code program, said program including at least one context specifier statement and at least one request statement, each context specifier statement naming a particular one of said general purpose components and each request statement naming a particular transformation in one named general purpose component, said instantiator means including

first means responsive to each context specifier statement for locating in said memory the stored general purpose component named in that context specifier statement,

second means responsive to each request statement for locating the collection of transformation language statements specifying the transformation named in that request statement in one general purpose component located by said first means,

means responsive to the collection of transformation language statements located by said second means for creating a concrete version of said source code program, and

compiler means for converting said concrete version of said source code program into a machine code version of said source code program.

9. The operating arrangement of claim 8 wherein each general purpose component in a portion of the stored general purpose components has at least one associated parameter and the context specifier and request statements received by said instantiator means respectively include at least one second context specifier statement and at least one second request statement, each second context specifier statement names one general purpose component in said portion and specifies a value for each associated parameter and each second request statement names one transformation in one named general purpose component in said portion, and wherein said instantiator means further includes third means responsive to each second context specifier statement for correlating the general purpose component named in that second context specifier statement and located by said first means and the value of each associated parameter, and said creating means also creating said concrete version in response to each correlated general purpose component.

10. A method for generating software programs from supplied generic specifications, said method comprising the steps of

compiling received language statements specifying generic software components, each of said generic software components corresponding to one or more user requestable services for program generation, each said service being specified by a collection of language statements,

storing the compiled language statements of said specified generic software components,

receiving language statements specifying a particular software application, said language statements including at least one indirect statement and at least one request statement, each indirect statement naming any one of said specified generic software cmponents and each request statement naming one user requestable programming service in one named generic software component, said receiving step further including the steps of

locating in response to each indirect statement the stored language statements specifying the generic software component named in that indirect statement,

locating in response to each request statement the collection of language statements specifying the user requestable programming service named in that request statement in the stored language statements that have been priorly located in response to each indirect statement, and

creating in response to the located language statements specifying the user requestable programming service named in each request statement a concrete version of said particular software application wherein said concrete version is devoid of indirect and request statements.

11. The method of claim 10 wherein each generic software component in a portion of said specified generic software components has at least one associated parameter and the indirect and request statements of said particular software application respectively include at least one second indirect statement and second request statement, each second indirect statement names any one generic software component in said portion and specifies a value for each associated parameter and each second request statement names one user requestable service in one named generic software component in said portion, and wherein said receiving step further includes the step of

correlating in response to each second indirect statement the stored language statements which specify the generic software component named in that second indirect statement and the value of each associated parameter;

and wherein

said creating step creates said concrete version of said particular software application also in response to correlated language statements.

12. The method set forth in claim 11 wherein said particular software application contains a plurality of indirect statements, each of said indirect statements referencing an identical generic software component in said portion and specifying a different value for each associated parameter.

13. The method set forth in claim 11 wherein said collection of language statements may include instructions for inserting indirect statements and request statements which reference identical or different generic software components, and wherein said receiving steps includes the step of monitoring said language statements specifying said particular software application of instructions for inserting indirect and request statements and reapplying such instructions through said receiving step.