Application architecture generation

A method for application architecture generation comprising:

• ascertaining, by an input receiver that is executed by at least one hardware processor, for a project, an input that includes project information, component information, and target information;
• parsing, by a command line input analyzer that is executed by the at least one hardware processor, the project information to determine whether the project is an existing project or a new project;
• generating, by a configuration manager that is executed by the at least one hardware processor, a component list from the component information;
• ascertaining, by an architecture modeler that is executed by the at least one hardware processor, components from the component list based on installation paths identified in a configuration file associated with the project;
• mapping, by a mapper that is executed by the at least one hardware processor, each of the ascertained components to a corresponding target determined from the target information and based on target type and to a template representing a structure for an application with respect to source code, by attaching, based on the installation paths, a file associated with each ascertained component of the ascertained components to the corresponding target;
• analyzing, by a dependency manager that is executed by the at least one hardware processor, a dependency for each of the ascertained components relative to at least one other component of the ascertained components;
• and
• generating, by an integrated output generator that is executed by the at least one hardware processor, based on the mapping and the analyzed dependency, an integrated output that includes an architecture for the application associated with the project.

A non-transitory computer readable medium having stored thereon machine readable instructions, the machine readable instructions, when executed by at least one hardware processor, cause the at least one hardware processor to:

• ascertain, for a project, an input that includes project information, component information, and target information;
• parse the project information to determine whether the project is an existing project or a new project;
• generate a component list from the component information;
• receive, at a workbench integrator that operates with a cartridge service, an indication of components that are to be ascertained from the component list;
• ascertain, based on the received indication of the components from the component list and from a workbench repository, the components from the component list based on installation paths identified in a configuration file associated with the project;
• map each of the ascertained components to a corresponding target determined from the target information and to a template representing a structure for an application with respect to source code, by attaching, based on the installation paths, a file associated with each ascertained component of the ascertained components to the corresponding target;
• analyze a dependency for each of the ascertained components relative to at least one other component of the ascertained components;
• and
• generate, based on the mapping and the analyzed dependency, an integrated output that includes an architecture for the application associated with the project.