System and method for iterative generating and testing of application code
A method begins by generating application system state transitions from inputted requirements and parameters. For a current implementation of generating application code, the method continues by entering a loop. The loop begins by generating a current intermediate result based on a previous implementation and in accordance with current application code development factors. The loop continues by generating at least one test case based on the one or more of the application system state transitions. The loop continues by testing the current intermediate result in accordance with the at least one test case. When the testing is unfavorable, the loop continues by modifying one or more of: the one or more of the plurality of application system state transitions, the one or more of the parameters, and the one or more implementation tools. The loop then continues by repeating the loop using the modified current application code development factors.
1. A method for execution b one or more computing entities, the method comprises:
iteratively generating application code utilizing one or more implementation tools and by:
generating, automatically by the one or more computing entities, a plurality of requirements artifacts based on a component use case input requirement artifact, a scenario input requirement artifact, and a correctness criteria input requirement artifact;
generating, automatically by the one or more computing entities for an architecture level design phase, a plurality of architecture level artifacts based on at least some of the plurality of requirements artifacts and the component use case input requirement artifact;
generating, automatically by the one or more computing entities for a high-level design (HLD) phase, a plurality of HLD artifacts based on at least some of the plurality of architecture level artifacts, at least a second some of the plurality of requirement artifacts, non-functional input requirements, and protocol document input requirements;
generating, automatically by the one or more computing entities for a low-level design (LLD) phase, a plurality of LLD artifacts based on at least a second some of the plurality of architecture level artifacts, at least some of the plurality of HLD artifacts, behavior definition input requirement artifacts, and platform document input requirement artifacts; and
generating, automatically by the one or more computing entities for an application code level development phase, a plurality of code artifacts based on at least some of the plurality of LLD artifacts, at least a second some of the plurality of HLD artifacts, and at least a third some of: the plurality of requirement artifacts, the behavior definition input requirement artifacts, and the platform document input requirement artifacts, wherein at least one of the plurality of code artifacts includes the application code.
2. The method of claim 1 , wherein the plurality of architecture level artifacts comprises:
one or more structure models; and
one or more test models.
3. The method of claim 1 , wherein the plurality of HLD artifacts comprises:
one or more architecture models;
one or more structure models;
one or more state models;
one or more sanity test models; or
one or more protocol specification models.
4. The method of claim 1 , wherein the plurality of LLD artifacts comprises:
one or more structure models;
one or more state models;
one or more behavior models;
one or more platform models; or
one or more protocol test models.
5. The method of claim 1 , wherein the plurality of code artifacts further comprises:
one or more user code models;
one or more user application code;
one or more model code;
one or more platform code;
one or more protocol code; or
one or more platform test models.
6. A computing device comprising:
memory;
an input/output module operable to output application code;
a processing module operably coupled to the memory and the input/output module, wherein the processing module is operable to implement production of application code in an iterative manner using one or more implementation tools and to:
generate a plurality of requirements artifacts based on a component use case input requirement artifact, a scenario input requirement artifact, and a correctness criteria input requirement artifact;
generate, for an architecture level design phase, a plurality of architecture level artifacts based on at least some of the plurality of requirements artifacts and the component use case input requirement artifact;
generate, for a high-level design (HLD) phase, a plurality of LLD artifacts based on at least some of the plurality of architecture level artifacts, at least a second some of the plurality of requirement artifacts, non-functional input requirements, and protocol document input requirements;
generate, for a low-level design (LLD) phase, a plurality of LLD artifacts based on at least a second some of the plurality of architecture level artifacts, at least some of the plurality of HLD artifacts, behavior definition input requirement artifacts, and platform document input requirement artifacts; and
generate, for an application code level development phase, a plurality of code artifacts based on at least some of the plurality of LLD artifacts, at least a second some of the plurality of HLD artifacts, and at least a third some of the plurality of requirement artifacts, the behavior definition input requirement artifacts, and the platform document input requirement artifacts wherein at least one of the plurality of code artifacts includes the application code.
7. The computing device of claim 6 , wherein the plurality of architecture level artifacts comprises:
one or more structure models; and
one or more test models.
8. The computing device of claim 6 , wherein the plurality of HLD artifacts comprises:
one or more architecture models;
one or more structure models;
one or more state models;
one or more sanity test models; and
one or more protocol specification models.
9. The computing device of claim 6 , wherein the plurality of LLD artifacts comprises:
one or more structure models;
one or more state models;
one or more behavior models;
cine or more platform models; and
one or more protocol test models.
10. The computing device of claim 6 , wherein the plurality of code artifacts further comprises:
one or more user code models;
one or more user application code;
one or more model code;
one or more platform code;
one or more protocol code; and
one or more platform test models.
11. A computing device comprising:
memory;
an input/output module operable to output application code; and
a processing module operably coupled to the memory and the input/output module, wherein the processing module is operable to:
implement production of the application code in an iterative manner using one or more implementation tools;
during an architecture level design phase, automatically produce architecture artifacts based on application requirements, parameters, and architecture phase feedback;
during a high-level design (HLD) phase, automatically produce HLD artifacts based on the architecture artifacts, the application requirements, the parameters, and HLD phase feedback;
during a low-level design (LLD) phase, automatically produce LLD artifacts based on the architecture artifacts, the HLD artifacts, the application requirements, the parameters, and LLD phase feedback;
during a code development phase, automatically produce code artifacts based on the HLD artifacts, the LLD artifacts, the application requirements, the parameters, and a code development phase feedback, wherein at least one code artifact of the code artifacts includes the application code; and
generate a final application code based on the architecture level design, HLD, LLD, and code development phases.
12. The computing device of claim 11 , wherein the architecture level design phase provides one or more of: model tests or structure models.
13. The computing device of claim 11 further comprises a testing unit generating the architecture phase feedback by testing the results corresponding to a development of the architecture artifacts using architecture level test cases.
14. The computing device of claim 11 , wherein the HLD artifacts include one or more of: structure models or state models.
15. The computing device of claim 11 further comprises a testing unit generating the HLD feedback by testing the results corresponding to a development of the HLD artifacts using HLD level test cases.
16. The computing device of claim 11 , wherein the LLD artifacts include one or more of: structure models, state models, behavior models, or protocol tests.
17. The computing device of claim 11 further comprises a testing unit generating the LLD feedback by testing the results corresponding to a development of the LLD artifacts using LLD level test cases.
18. The computing device of claim 11 , wherein the code artifacts include one or more of: user codes, application codes, or integration tests.
19. The computing device of claim 11 further comprises a testing unit generating the code development phase feedback by testing the code artifacts using code level test cases.
20. The computing device of claim 11 , wherein a group of the architecture, HLD, LLD and code artifacts include any of: nonfunctional requirements, component use cases, scenarios, correctness criteria, behavior definitions, platform documents, data definitions, formalized requirements, verified requirements, application system state transitions (ASST), composite structure diagrams, state machine diagrams (SM), architecture model(s), protocol specification(s), design tests, sanity tests, detailed composite structure diagrams state machine diagrams, data structure definitions (DD), platform model(s), protocol tests, user code, model code, platform code, protocol code or integration tests.