End-to-end onboarding management for application bundles

Abstract

End-to-end onboarding management for application bundles is described. A dashboard user interface is presented for displaying information related to at least one application bundle component and presenting a dashboard menu on the dashboard user interface for selecting the at least one application bundle component to create. A selection of the at least one application bundle component to create is received via the dashboard menu. Based on the selection, a creation user interface is displayed including a selectable control component for initiating creation of the at least one application bundle component. In response to receiving a selection of the selectable control component, the at least one application bundle component is created.

Description

[Technical field]

[0001] The present specification relates to a system, method, and non-transitory computer-readable medium for managing end-to-end onboarding for application bundles. [Background technology]

[0002] Newly developed software or applications undergo an onboarding process that includes at least one of quality testing, validation, and certification. Quality testing, validation, and certification of application bundles during the onboarding process improves the process of software adoption. An application bundle is a collection of artifacts used to deploy and manage an application.

[0003] The onboarding process used to deliver and integrate applications is a difficult and time-consuming process involving multiple vendors, multiple services, multiple approval managers, and many steps performed by developers before the application is ready for deployment by users. The steps involved in the onboarding process are currently performed manually. Manual communication occurs between many people, many files are placed and used during the onboarding process, and multiple tickets are issued to ship the application. Coordination between the parties involved in the onboarding process reduces efficiency and consumes more time. Lack of infrastructure understanding and automated deployment causes delays to market. Manual integration, communication, and integration by multiple teams, including cloud, network, security, and infrastructure managers, leads to increased costs. Lack of automated testing and security standardization leads to in-built quality. Summary of the Invention [Means for solving the problem]

[0004] In at least one embodiment, a method for managing end-to-end onboarding for an application bundle includes presenting a dashboard user interface displaying information related to at least one application bundle component and presenting a dashboard menu on the dashboard user interface for selecting the at least one application bundle component to create, receiving a selection of the at least one application bundle component to create via the dashboard menu, and based on the selection, displaying a creation user interface including selectable control components for initiating creation of the at least one application bundle component, and creating the at least one application bundle component in response to receiving the selection of the selectable control component.

[0005] In at least one embodiment, a device for managing application bundle onboarding includes a memory storing computer-readable instructions and a processor coupled to the memory, where the processor is configured to execute the computer-readable instructions to display information related to at least one application bundle component, present a dashboard menu on a dashboard user interface for selecting the at least one application bundle component to create, present a dashboard user interface, receive a selection of the at least one application bundle component to create via the dashboard menu, display a creation user interface including a selectable control component for initiating creation of the at least one application bundle component based on the selection, and create the at least one application bundle component in response to receiving the selection of the selectable control component.

[0006] In at least one embodiment, a non-transitory computer-readable medium having computer-readable instructions stored thereon that, when executed by a processor, cause the processor to perform operations including presenting a dashboard user interface displaying information related to at least one application bundle component and presenting a dashboard menu on the dashboard user interface for selecting at least one application bundle component to create, receiving a selection of the at least one application bundle component to create via the dashboard menu, and based on the selection, displaying a creation user interface including a selectable control component for initiating creation of the at least one application bundle component, and creating the at least one application bundle component in response to receiving the selection of the selectable control component. [Brief description of the drawings]

[0007] Aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings, in which: It should be noted that, in accordance with standard industry practice, various features have not been drawn to scale, and in fact, the dimensions of various features may be expanded or reduced for clarity of illustration.

[0008] [Figure 1] 1 illustrates a system for managing end-to-end onboarding for an application bundle in accordance with at least one embodiment. [Diagram 2] 1 illustrates a service designer GUI in accordance with at least one embodiment. [Diagram 3] 1 illustrates a dashboard user interface in accordance with at least one embodiment. [Figure 4] 1 illustrates a service creation UI in accordance with at least one embodiment. [Diagram 5] 1 illustrates a vendor-created UI in accordance with at least one embodiment. [Figure 6] 1 illustrates a user-created UI in accordance with at least one embodiment. [Figure 7] 1 illustrates an artifact creation UI in accordance with at least one embodiment. [Figure 8] 1 illustrates a Type 1 bundle creation UI in accordance with at least one embodiment. [Figure 9] 1 illustrates a Type 2 bundle creation UI in accordance with at least one embodiment. [Figure 10] 1 illustrates a bundle evaluation approval validation window in accordance with at least one embodiment. [Figure 11] 1 illustrates trigger deployment from an update bundle status UI in accordance with at least one embodiment. [Figure 12] 1 illustrates triggering a QA scan from an update bundle status UI in accordance with at least one embodiment. [Figure 13] 1 illustrates a status check UI in accordance with at least one embodiment. [Figure 14] 1 illustrates a bundle component details capture graphic user interface (GUI) in accordance with at least one embodiment. [Figure 15] 1 is a flowchart of a method for managing end-to-end onboarding for an application bundle according to at least one embodiment. [Figure 16] FIG. 1 illustrates a high-level functional block diagram of a processor-based system according to at least one embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] The embodiments described herein illustrate examples of implementing various features of the subject matter provided. To simplify the present disclosure, examples of components, values, operations, materials, arrangements, and the like are described below. Of course, these are examples and are not intended to be limiting. Other components, values, operations, materials, arrangements, and the like are contemplated. In addition, the present disclosure repeats reference numerals and / or letters in various examples. This repetition is for the purposes of brevity and clarity and does not indicate a relationship and / or configuration between the various embodiments described.

[0010] Additionally, spatially relative terms such as "beneath," "below," "lower," "above," "upper," and the like are used herein for ease of description to describe the relationship of one element or feature to another element(s) or feature(s) as shown in the figures. The spatially relative terms are intended to encompass different orientations of the device during use or operation in addition to the orientation shown in the figures. The device is otherwise oriented (rotated 90 degrees or at other orientations) and the spatially relative descriptors used herein are similarly interpreted accordingly.

[0011] The terms used in the description of the various embodiments herein are for the purpose of describing particular embodiments and are not intended to be limiting. As used in the description of the various described embodiments and the appended claims, the onboarding management device implements at least one graphical user interface (GUI) presented on a display device. The at least one GUI is described with reference to objects or graphic elements including one or more windows, pages, icons, dialogs, tabs, check boxes, edit boxes, text labels, label buttons, radio buttons, sliders, drop-down menus or lists, and text boxes. Those skilled in the art will recognize that the description, number, visual representation, and other characteristics of the GUI elements are presented by way of example and are not intended to be limiting.

[0012] In at least one embodiment, end-to-end onboarding management for an application bundle is provided by presenting a dashboard user interface displaying information related to at least one application bundle component and presenting a dashboard menu on the dashboard user interface for selecting the at least one application bundle component to create, receiving a selection of the at least one application bundle component to create via the dashboard menu, and displaying a creation user interface including selectable control components for initiating creation of the at least one application bundle component based on the selection, and creating the at least one application bundle component in response to receiving the selection of the selectable control component.

[0013] Advantages of the integrated onboarding management device include providing a single point to manage end-to-end onboarding for application bundles. Items and information are collected at a single point, which is then automatically distributed to downstream systems. Automatic email notifications provided to and from administrators are involved in numerous approval decisions. A graphical user interface (GUI) allows users to design and upload application bundles using simple drag-and-drop functionality. The onboarding system provides a coordination process presented via a GUI that allows application developers to design end-to-end application bundles. From the GUI, developers select various parameters and create or upload application bundles to the system. Building of various types of bundles is supported, including type 1 bundles and type 2 bundles. The drag-and-drop functionality allows the end-to-end onboarding process to be managed from a single platform.

[0014] FIG. 1 illustrates a system 100 for managing end-to-end onboarding for an application bundle according to at least one embodiment.

[0015] In FIG. 1, an onboarding management device 110 is provided. The onboarding management device 110 includes a display 112 and presents a graphical user interface (GUI) that allows a user to design and upload an application bundle using simple drag-and-drop functionality. The onboarding management device 110 provides a coordination process presented via a GUI 114 that allows an application developer to design an end-to-end application bundle. From the GUI 114, the developer selects various parameters and creates or uploads the application bundle to the system. The construction of various types of bundles is supported, including type 1 bundles and type 2 bundles. The drag-and-drop functionality allows the end-to-end onboarding process to be managed from the platform. Items and information are collected at a single point by a detail capture user interface (UI) accessible via the GUI 114, and the information is then automatically distributed to the server(s) 120 via the network 130. In at least one embodiment, the server(s) 120 includes one or more servers located at a location. In at least one embodiment, server(s) 120 includes one or more servers distributed across multiple locations. The onboarding management device 110 exchanges automated email notifications with one or more administrators involved in multiple approval decisions during the onboarding lifecycle.

[0016] The GUI 114 presents a dashboard user interface that allows the user to access status information and identification of recent services and bundles. The GUI 114 also allows the user to access a service overview including a list of services and related information. Through the GUI 114, new services and bundles are created by providing details through a detail capture UI that defines the service and bundle, respectively. The detail capture UI allows the user to select various roles, various parameters, configuration files, and scripts. Additionally, the GUI 114 allows the user to create new users, vendors, and artifacts. The GUI 114 allows access to a bundle overview including the bundle's phase and status. The user of the onboarding management device 110 uses the GUI 114 to evaluate the new bundle. In response to a rejection, the developer is provided with changes to be made to the application bundle, where the application bundle moves to a draft stage for making changes before resubmitting the application using the user interface provided through the GUI 114. In response to being approved, the application bundle is registered in a service catalog for deployment. The service catalog can be maintained in the server(s) 120. After deployment, the developer triggers a user-defined QA scan via the onboarding management device 110. After the scan is completed, the GUI 114 allows the user to access a self-certification menu. Once the self-certification is submitted, a release request is created and a release request number is displayed in the GUI 114. An automated process in the onboarding management device 110 fetches the status of the release request. Based on the status of the release request, the user stages the application bundle into the service catalog and the bundle becomes production-ready. An activity log is presented via the GUI 114.

[0017] In at least one embodiment, the onboarding management device 110 is implemented in a standalone system. In at least one embodiment, the onboarding management device 110 is implemented using a distributed computing model that allows two or more distributed or co-located computing devices to coordinate their activities to accomplish end-to-end onboarding management for application bundles. This coordination may occur over a network (e.g., a local area network, a wide area network, and / or the Internet) or some other form of communication coupling. The continuing reduction in costs of computer storage (e.g., random access memory, solid state memory, and hard drives) and always-on networking computing devices (e.g., personal computers (PCs), laptops, tablet devices, and mobile phones) allows new techniques to be adopted to utilize distributed computing systems.

[0018] In particular, cloud-based computing is a term that can refer to a distributed computing architecture in which data and program logic of a cloud-based application is shared between one or more client devices and a server device on a near real-time basis. Portions of this data and program logic may be dynamically distributed as needed to various clients accessing the cloud-based application. For example, the server(s) 120 may store data and program logic that implements the onboarding management device 110 in a cloud-based computing architecture. The details of the architecture may be transparent to users of the client devices. Thus, a PC user accessing a cloud-based application may not be aware that the PC is downloading program logic and / or data from a server device or that the PC is offloading processing or storage functions to the server device.

[0019] FIG. 2 illustrates a service designer GUI 200 according to at least one embodiment.

[0020] In FIG. 2, a user uses a service designer GUI 200 to access a dashboard UI 210, a service creation UI 212, a vendor creation UI 214, a user creation UI 216, an artifact creation / upload UI 218, a bundle creation UI 220, and a bundle deployment and QA scanning UI 222.

[0021] The dashboard UI 210 provides options for creating components of an application bundle, such as services, vendors, users, artifacts, and bundles. The dashboard UI 210 also provides information about the various bundle components to the user. From the dashboard UI 210, the user can begin creating a service by displaying a service creation UI 212. The service creation UI 212 displays information about existing services and has selectable components for adding new services. From the dashboard UI 210, the user can begin creating a vendor by displaying a vendor creation UI 214. The vendor creation UI 214 displays information about existing vendors and has selectable components for adding new vendors. The user creation UI 216 is activated using a menu accessible from the vendor creation UI 214. The user creation UI 216 allows the user to enter data about the user, edit such data, or otherwise configure the user.

[0022] The artifact creation / upload UI 218 is activated from the overview page, which has selectable tabs including artifacts. The artifact creation / upload UI 218 presents selectable components for initiating the creation of an artifact. The bundle creation UI 220 is displayed in response to clicking the bundle tab on the overview page. From the bundle creation UI 220, the user can create a new Type 1 bundle or Type 2 bundle. The bundle deployment and QA scanning UI 222 is presented by selecting a menu item that forms the overview page.

[0023] The dashboard UI 210, service creation UI 212, vendor creation UI 214, user creation UI 216, artifact creation / upload UI 218, bundle creation UI 220, and bundle deployment and QA scanning UI 222 are described in more detail below.

[0024] FIG. 3 illustrates a dashboard user interface 300 according to at least one embodiment.

[0025] 3, a dashboard user interface 300 is accessed by a service designer 302 and provides a pull-down menu 306 to select a bundle component, such as a service, to create. A second pull-down menu 308 allows the user to select a vendor. The dashboard user interface 300 provides information such as total services 310, vendor 312, approved bundles 314, bundles under evaluation 316, and rejected bundles 318.

[0026] Figure 3 illustrates an options menu 320 accessible from the dashboard UI 300. In Figure 3, the options menu 320 includes a services option 322, an accounts option 324, a vendor management option 326, and an organization details option 328. The dashboard user interface 300 also presents a list of recent services 330. The list of recent services includes the service name 332, tags 334, and creation date 336. A kebab icon 338 allows the user to edit the recent services.

[0027] The user can also select Full View 340 to view all recent services 330. A graphical representation of the bundle status is presented, for example using a donut chart 350.

[0028] The dashboard UI 300 also presents recent bundles 360. Under recent bundles 360, the phase 361, status 362, bundle name 363, type 364, bundle version 365, and creation date 366 are presented for the recent bundles.

[0029] FIG. 4 illustrates a service creation UI 400 according to at least one embodiment.

[0030] In Figure 4, a service creation UI 400 is presented upon selection of the services menu from the dashboard UI 300 of Figure 3. The service creation UI 400 shows that the service creation UI 400 is provided by a service designer 402.

[0031] For the service name 410, there are tags 414, creation date 418, and update date 422. Creation date 418 indicates the date the service was created. Update date 422 indicates the date the service was updated. A "+Add New" button 426 is provided to add a new service. When the "+Add New" button 426 is selected, the creation of the service is initiated and a detail capture UI is presented, including a service detail capture page so that the user can enter data and otherwise configure the new service. A kebab icon 430 allows the user to edit the service. A pull-down menu 406 is provided to select components of the application bundle, such as a service.

[0032] FIG. 5 illustrates a vendor-created UI 500 according to at least one embodiment.

[0033] In FIG. 5, a create vendor UI 500 is presented by selecting the manage vendors option 326 in the options menu 320 of FIG. 3. The create vendor UI 500 displays a list of vendors by vendor name 510. For the vendor name 510, a key 512, website 514, type of vendor 516, address 518, city 520, state 522, zip code 524, and country 526 are provided. A kebab icon 530 allows the user to edit a vendor listed in the vendors list. The user selects a "+Add New" button 540 to add a new vendor. When the "+Add New" button 540 is selected, the creation of a vendor is initiated and a capture details UI is presented, including a vendor details capture page so that the user can enter data and otherwise configure the new vendor.

[0034] FIG. 6 illustrates a user-created UI 600 according to at least one embodiment.

[0035] 6, the kebab icon 610 for the vendor name 614 is selected, presenting an options menu 620. From the options menu 620, the user can select a user list option 622. The user list option 622 initiates the display of a details capture UI, including a user details capture page, so that the user can enter data or otherwise configure a new user associated with the vendor name 614.

[0036] FIG. 7 illustrates an artifact creation UI 700 according to at least one embodiment.

[0037] In Figure 7, the Artifacts tab 710 is selected. Artifacts 714, 715, 716 are shown for a Service ID 720 of 123abcdef-abcdef-123456 722 with a Creation Date 724. Service ID 720 of 123abcdef-abcdef-123456 722 has a Creation Identifier 728 indicating it was created by the system 732. The vendor 734 is identified as a vendor name 736.

[0038] Prior to creating an application bundle, artifacts are uploaded using one of three methods: Docker Get involves getting an image from a public Docker and uploading the image to Artifact Factory. Docker Push involves a user uploading a Docker image from the user's local system and pushing that image to JFrog's Artifact Factory in a folder suggested by the service designer. JFrog Get involves getting an image from one location to another JFrog location.

[0039] In FIG. 7, 48 results 740 for artifacts are returned with artifacts 714, 715, 716 shown in artifact window 744. For example, artifact 714 is named golang. The type of artifact 714 is docker 748, and the artifact image was retrieved 750 from public docker at location https: / / public-docker.slb-artifactory-v.stg.local 752. An artifact in artifact window 744 can be selected and listed 754 to view details of the selected artifact. To add a new artifact from the artifact creation UI 800, the user selects the "+" button 756.

[0040] When the "+" button 756 is selected, the creation of the artifact is initiated and a details import UI is presented, including an artifact details import page, so that the user can enter data or otherwise configure the new service. The user can select Overview 711 to present a summary of the information. The user can select the Bundles tab 712 of the artifact creation UI 700 and then click the "+" button 758 to begin creating the bundle.

[0041] Create a Type 1 Bundle FIG. 8 illustrates a Type 1 bundle creation UI 800 according to at least one embodiment.

[0042] The Type 1 bundle creation UI 800 is displayed in response to clicking on the bundle tab 712 of the artifact creation UI 700 shown in FIG. 7 and then clicking on the “+” button 758. In FIG. 8, the Type 1 bundle creation UI 800 is for adding a Type 1 bundle. A Type 1 bundle is a bundle that is specific to a particular enterprise. A Type 2 bundle adheres to an industry standard for publishing an application. The Type 1 bundle creation UI 800 displays stages of data entry including a basic details entry 810, a resource entry 811, an observability data entry 812, a configuration data entry 813, a networking data entry 814, a security data entry 815, a bare metal entry 816, and a preview stage 817.

[0043] In FIG. 8, basic details 810 are entered for a Type 1 bundle 820. Data entry for resources 811, observability 812, configuration 813, networking 814, security 815, and bare metal 816 are described below with reference to Type 1 bundle import 1418 in FIG. 14. For basic details 810, an image is uploaded to the area associated with the bundle icon 814. The bundle name window 823 is used to enter an appropriate name for the bundle. The type window 824 indicates whether the bundle is an application bundle, a network service bundle, or a network slice. The deployment window 826 has a drop-down menu for selecting Type 1 or Type 2. In FIG. 8, Type 1 828 is selected.

[0044] The version window 830 shows the version of the Type 1 bundle. The producer window 834 has a drop down menu. Here, RCP 836 is shown as selected. The API version 838 is shown as 1.0 at 840. The description window 842 contains a brief description of the bundle. The tags window 846 allows entry of tags for performing lookups and searches.

[0045] The technology window 850 is a drop down menu that allows the selection of the appropriate technology. Here, LTE 852 is selected. The domain window 854 shows Bss 856 for the domain. The NE type window 858 shows ACTBROKER_DB 860 that identifies the type of NE provisioning. The category window 862 shows Independent 864. Independent 864 is selected in response to not having a dependency on other bundles. Network service dependent (not shown here) is selected in response to creating a network service bundle. The configuration management database (CMDB) software version window 866 shows the version of the CMDB software that manages the bundle. The bundle access options window 870 shows whether the accessibility of the bundle is public or private. The image path window 874 shows the path of the image. The "SD path" 876 is selected to be obtained from JFrog, and "Custom path" (not shown here) is selected to provide a path for the artifactory.

[0046] The bundle details window 880 includes options for Create New 882 and Upload 884. Here, Create New 882 is selected. A drag and drop area 886 is provided for uploading a Type 2 bundle. A bundle name window 887 is provided for entering a bundle name, e.g., bundle name 123 888. A version window 889 is provided for entering a file version, e.g., 1.0.0.0 890. A tag window 891 is provided for entering a tag 892.

[0047] After the details of the Create Type 1 Bundle UI 800 are entered, the user clicks Next 894. After clicking Next 894, a Import Details UI 1400, as shown below with respect to FIG. 4, is presented, which includes an Import Type 1 Bundle page 1418 so that the user can enter further data to otherwise configure the Type 2 bundle.

[0048] Create a Type 2 bundle FIG. 9 illustrates a Type 2 bundle creation UI 900 according to at least one embodiment.

[0049] In Figure 9, the Type 2 bundle creation UI 900 is displayed in response to clicking on the Bundles tab 712 in the artifact creation UI 700 shown in Figure 7 and then clicking on the "+" button 758. Type 2 bundles conform to industry standards for publishing applications. The Type 2 bundle creation UI 900 displays stages for data entry including basic details 910, resources 911, observability 912, configuration 913, networking 914, security 915, bare metal 916, and a preview stage 917.

[0050] In Figure 9, basic details 910 are entered for a Type 2 bundle 920. Data entry for resources 911, observability 912, configuration 913, networking 914, security 915, bare metal 916 are discussed below with reference to Type 2 bundle ingestion 1420 in Figure 14. For basic details 910, an image is uploaded into the area associated with the bundle icon 821.

[0051] In Figure 9, basic details 910 for creating a Type 2 bundle are entered. In the bundle icon area 921, an image is uploaded, e.g., serviceimage.jpg. The bundle name window 922 is used to enter an appropriate name for the bundle. The type window 923 has a drop down menu for selecting the bundle type, e.g., application 924. The deployment window 925 has a drop down menu for selecting a Type 2 bundle 926. The deployment window 925 has a drop down menu for selecting Type 1 or Type 2. In Figure 9, Type 1 926 is selected.

[0052] The version window 927 shows the version of the bundle. The producer window 930 has a drop down menu. Here, RCP 932 is selected. The API version window 934 shows "1.0" 936. The description window 938 contains a brief description of the bundle. The tags window 942 allows entry of tags for performing lookups and searches.

[0053] The technology window 946 is a drop down menu that allows for the selection of the appropriate technology. Here, T5G 948 is selected indicating that the bundle is associated with 5G technology. The domain window 950 shows Bss 952 for the domain. The NE type window 954 shows ACI_MONITORING_VM 956 indicating Application Centric Infrastructure (ACI) monitoring of virtual machines. The category window 958 shows Independent 960, which is selected in response to not being dependent on any other bundles. The CMDB software version window 962 shows the version of the CMDB software. The bundle access options window 966 indicates whether the accessibility of the bundle is public or private. Here, public 968 is selected.

[0054] The bundle details window 970 includes options for Create New 972 and Upload 974. Here, Upload 974 is selected. A drag and drop area 976 is provided for uploading a type 2 bundle, e.g., abc-def1_cluster1.tor.gz 978. After the details of the type 2 bundle are entered, Next 980 is selected.

[0055] After the details of the Type 2 bundle creation UI 900 are entered, the user clicks Next 980. After clicking Next 980, a details import UI 1400, as shown below with respect to FIG. 4, is presented, which includes a Type 2 bundle import page 1420, so that the user can enter further data to otherwise configure the Type 2 bundle.

[0056] FIG. 10 illustrates a bundle evaluation approval verification window 1000 in accordance with at least one embodiment.

[0057] In Figure 10, the user has evaluated the bundle information and selected the Approve button 1002 on the Bundle Evaluation UI 1004. A Bundle Evaluation Approval Verification window 1000 is displayed, providing the user with the option to select Yes 1010 or No 1012. The user selects Yes 1010 to verify approval of the details on the Bundle Evaluation UI 1004. After selecting Yes 1010 and the bundle is approved, the bundle proceeds to Sandbox or Stage Testing depending on its configuration and begins testing SBX.

[0058] FIG. 11 illustrates trigger deployment from an updated bundle status UI 1100 in accordance with at least one embodiment.

[0059] 11, the Bundles tab 1102 is selected and a list of bundles is shown for a service ID 1103 of 1104 at 123abcdef-abcdef-123456 with a creation date 1105. The service ID 1103 of 1104 at 123abcdef-abcdef-123456 has a creation identifier 1106 of system 1107. The vendor 1108 is identified as the vendor name 1109.

[0060] For the bundle with bundle name 1110 of 1120 in bundle name 123, the phase 1112 of the bundle is shown as "In Test SBX" 1132. The status 1114 shows "Action Required" 1134.

[0061] The bundle name 1120 of r1sontest1142 has a type 1116 of 1136 which is type 1, and a bundle version 1118 of 1138 which is 1.0.0.0. The creation date 1130 is 7:14:07 PM 1140 on February 1, 2022. The bundle with bundle name 1110 of r1sontest1142 has a type 1116 of 1144 which is a type 2 bundle.

[0062] Approving the bundle details results in a request for a prototype service catalog registration. After the prototype service catalog registration is complete, selecting the kebab icon 1150 displays a menu 1160 from which to select a deployment trigger option 1162 to deploy the bundle.

[0063] FIG. 12 illustrates triggering a QA scan from an updated bundle status UI 1200 in accordance with at least one embodiment.

[0064] 12, the Bundles tab 1202 is selected and a list of bundles is shown for a service ID 1203 of 1204 at 123abcdef-abcdef-123456 with a creation date 1205. The service ID 1203 of 1204 at 123abcdef-abcdef-123456 has a creation identifier 1206 of system 1207. The vendor 1208 is identified as the vendor name 1209.

[0065] For the bundle with bundle name 1210 of 1220 in bundle name 123, the phase 1212 of the bundle is shown as "In Test SBX" 1232. The status 1214 shows "Action Required" 1234.

[0066] The bundle name 123 1220 has a type 1116 of 1236 which is type 1, and a bundle version 1218 of 1238 which is 1.0.0.0. The creation date 1230 is 7:14:07 PM 1240 on February 1, 2022. The bundle with bundle name 1210 of r1sontest1242 has a type 1216 of 1244 which is a type 2 bundle.

[0067] Approving the bundle details results in a request for a prototype service catalog registration. After the prototype service catalog registration is complete, selecting the kebab icon 1250 displays a menu 1260 where a QA trigger option 1262 can be selected to initiate a post-production scan on the bundle.

[0068] FIG. 13 illustrates a status check UI 1300 according to at least one embodiment.

[0069] 13, the status check UI 1300 shows that selecting the sonar scan results tab 1310 shows sonar scan results for a bundle with a service ID 1303 of 1304 at 123abcdef-abcdef-123456 with a creation date 1305. The service ID 1303 of 1304 at 123abcdef-abcdef-123456 has a creation identifier 1306 of system 1307. The vendor 1308 is identified as the vendor name 1309.

[0070] The status check UI 1300 shows a quality gate (pass) window 1314. In the quality gate window 1314, a reliability window 1318 is shown with "0" bugs 1320 identified. A first security window 1322 shows "0" vulnerabilities 1324. A second security window 1326 shows a security rating 1328 of "A". A security assessment window 1330 shows "0" security hotspots 1332. Once the information from the sonar scan results has been evaluated, approval 1334 is selected.

[0071] FIG. 14 illustrates a bundle component details capture graphic user interface (GUI) 1400 according to at least one embodiment.

[0072] 2, a user uses the service designer GUI 200 to access a dashboard UI 210, a service creation UI 212, a vendor creation UI 214, a user creation UI 216, an artifact creation / upload UI 218, a bundle creation UI 220, and a bundle deployment and QA scanning UI 222. The dashboard UI 210 provides options for creating bundle components such as services, vendors, users, artifacts, and bundles.

[0073] From the dashboard UI 210, a user can begin creating a service by displaying a create service UI 212, which adds a new service using selectable components. From the dashboard UI 210, a user can begin creating a vendor by displaying a create vendor UI 214, which adds a new vendor using selectable components. A create user UI 216 is activated using a menu accessible from the create vendor UI 214.

[0074] The artifact creation / upload UI 218 is activated from an overview page with selectable tabs containing artifacts that use selectable components to initiate the creation of an artifact. The bundle creation UI 220 is displayed in response to clicking on the bundles tab on the overview page. From the bundle creation UI 220, the user can create a new Type 1 bundle or Type 2 bundle.

[0075] Once creation of a bundle component is initiated from a creation UI, such as a service creation UI 212, a vendor creation UI 214, a user creation UI 216, an artifact creation / upload UI 218, and a bundle creation UI, and initial details are provided in the creation UI, a details capture UI 1400 is displayed allowing the user to provide further details for creating the bundle component.

[0076] The import details UI 1400 presents at least one of a import service page 1410, an import vendor page 1412, an import user page 1414, an import artifact page 1416, an import type 1 bundle page 1418, and an import type 2 bundle page 1420. Those skilled in the art will recognize that in at least one embodiment, the import service page 1410, the import vendor page 1412, the import user page 1414, the import artifact page 1416, the import type 1 bundle page 1418, and the import type 2 bundle page 1420 include multiple pages that receive details for configuring and creating associated bundle components.

[0077] For example, the service capture page 1410 includes one or more pages having a service data entry window 1430 configured to accept details for creating a service. In at least one embodiment, the service data entry window 1430 is configured to upload an icon associated with the service being added. Any suitable image file can be uploaded using various image formats such as PNG, JPG, etc. The service data entry window 1430 is configured to allow the user to enter a service name, add tags that are useful for performing service name searches and allow faster searches, enter a brief description of the service, e.g., communication app, payment app, etc., and enter email addresses, names, and vendors associated with approvers, release managers, members, and owners of the service. Approvers, release managers, members, and owners information for the service can be entered, including role, provider name, email address, and name. A service name and description can also be entered. Once the service details are entered, the user can create the service, where the service ID, creation date, and creation entry are displayed. From the service data entry window 1412, the user can have an overview displayed based on the details entered.

[0078] The vendor capture page 1412 includes one or more pages having a vendor data entry window 1432 configured to accept details for creating a vendor. In at least one embodiment, the vendor data entry window 1432 is configured to receive the vendor's occupation, a key associated with the vendor, a website associated with the vendor, and the vendor's address, city, state, country, and zip code. The type of vendor, e.g., partner, can be entered via the vendor data entry window 1432. A user can preview the information entered using the vendor data entry window 1432. A user can list users, edit information about a vendor, and delete a vendor.

[0079] The user capture page 1414 includes one or more pages with a user data entry window 1434 configured to accept details for creating a user. In at least one embodiment, the user data entry window 1434 is configured to receive information associated with the user's status, name, email ID, contact, organization, and role. The user's roles are bundle owner, bundle release administrator, service designer admin, and service designer default. The user data entry window 1434 allows the user to drag and drop an image of the user for display or upload an image file. The user can enter a Keycloak ID to provide user authentication without the user logging in and authenticating with the application.

[0080] The artifact import page 1416 includes one or more pages having an artifact user data entry window 1436 configured to accept details for creating a user. In at least one embodiment, the artifact user data entry window 1436 is configured to allow a user to enter an artifact type, for example, a Docker image, a name for the artifact, a tag for the image available in public Docker, and an identifier for the artifact, for example, as a pull type artifact where the image can be retrieved from the public Docker and uploaded, or as a push type artifact where the image can be uploaded from a local system and pushed to the artifact in a folder suggested by the system to manage end-to-end onboarding for the application bundle.

[0081] The artifact user data entry window 1436 is also configured to allow the user to enter the source type, e.g., Docker Hub, the location of the artifact, identification of whether the artifact is auto-enabled, and if private, a username and password. Via the artifact user data entry window 1436, the user can view the artifact's status, version, type (push type or pull type), the name of the image source, the type of artifact (Docker), and whether authentication is used.

[0082] The Type 1 bundle ingest page 1418 includes one or more pages having a Type 1 bundle data entry window 1438 configured to accept details for creating a user. In at least one embodiment, the Type 1 bundle data entry window 1438 accepts data entries including resources 811, observability 812, configuration 813, networking 814, security 815, bare metal 816, and preview stage 817 data entries as described above with respect to FIG. 8. One skilled in the art will recognize that the description of data entries for the Type 1 bundle data entry window 1438 is provided as an example and is not intended to limit the embodiments described herein. The Type 1 bundle data entry window 1438 can be used for entry of additional data, different types of data, or less data than described herein.

[0083] The Type 1 bundle data entry window 1438 is configured to receive advanced details under the resource data entry 811, including receiving application details, receiving a profile, an indication of whether snapshots are enabled, whether the bundle is cloned and if so, the method for cloning the bundle, receiving application hooks via scripts, and receiving affinity rules including the affinity rule name, type (e.g., infrastructure), and target. The Type 1 bundle data entry window 1438 presents options for entry of data related to components, resources, lifecycles, and pre-configured bundles.

[0084] The Type 1 bundle data entry window 1438 is configured to receive new role details including the role name, role description, and additional role information including advanced options, security context, labels, annotations, environment variables, affinity rules, IP pools, host aliases, and tolerances.

[0085] The Type 1 bundle data entry window 1438 is also configured to receive information about resources including image selection, computer information, storage information, service information, and volume information. Computer information includes memory configuration, number of cores used, and CPU type. Storage details include storage type, type of storage (e.g., solid state drive), path to storage, and size of allocated storage.

[0086] The Type 1 bundle data entry window 1438 receives details of the services associated with the Type 1 bundle, including type (e.g., node port), scope (e.g., pod), port area, and protocol (e.g., TCP). Volume details include volume name, mount path, subpath, and volume type. The user can enter a yaml file.

[0087] The Type 1 bundle data entry window 1438 is configured under the observability data entry 812 to receive metrics and logging details. Metric details include a name associated with the metric, a match label, a role name, a metric alert, a description of the metric, a type associated with the metric, an expected range, and a data format representation. Logging details include a logging label, a role identifier associated with the role, a name for the logging label, a value associated with the role, and a definition of the type of log output.

[0088] The Type 1 bundle data entry window 1438 is configured to receive configuration data under the Configuration Data Entry 813. The user can select to add a configuration or a Configuration Management Database (CMDB). The Type 1 bundle data entry window 1438 is configured under the Networking Data Entry 814 to receive data associated with the API Gateway and Networking tabs. When the API Gateway tab is selected, data for a new API Gateway is entered. The API Gateway data includes name, version, and brokering policy. The brokering policy data includes request ID policy in / policy out data, security scheme and security policy, visibility configuration, API environment, endpoint URL, swagger file upload option, certificate upload selection, type of configuration, tenant name, and environment.

[0089] The Type 1 bundle data entry window 1438 is configured to present a GRC producer tab under security data entry 815 for security data entry including an indication of whether the GRC producer is a corporate affiliate, application and / or organization, application name, application ID, application owner email, country, applicable industry, application data, privacy data, application data backup information, and application data security information. The Type 1 bundle data entry window 1438 is configured under bare metal data entry 816 for user input to add roles and permissions for managing access to the bundle, such as keycloak integration of the bundle, and to add performance and fault management policies.

[0090] In the preview state, the Type 1 bundle data entry window 1438 presents an option to view the details entered.

[0091] The Type 1 bundle data entry window 1438 is configured to present a preview 817 that presents the service ID, tag, creation date, creation information, and vendor of the application bundle. The preview 817 provided in the Type 1 bundle data entry window 1438 also presents metrics details and logging details.

[0092] The Type 1 bundle data entry window 1438 presents an option to view the bundle status including pre-deployment scan phase and status. The display of bundle status provided by the Type 1 bundle data entry window 1438 includes a kebab icon for evaluation selection, Type 1 bundle, and Type 2 bundle. Selection of the evaluation option presents a bundle evaluation page including an Evaluation Bundle tab, a Comments tab, an X-Ray Scan Results tab, and a Sonar Scan Results tab. The X-Ray and Sonar scans are downloaded by selecting the X-Ray Scan Results tab and the Sonar Scan Results tab. Once the details in the Bundle Data Entry window 1438 are determined to be acceptable, the Type 1 bundle data entry window 1438 presents an Approve button for the user to select to approve the bundle.

[0093] Once the bundle is approved in the Type 1 bundle data entry window 1438, self-QA certification data can be entered, including project name, description, tags, start date, end date, environment type, priority, version associated with the bundle release, release type, services affected by the bundle, services affected by the change, certification summary, arb status, arb number, and uploaded reports.

[0094] Activities tab to view and select log details and also generate release request. After release request is created, "Pre-deployment" job is triggered to get release request status approved by technical manager and "Deployable" job to check if bundle is ready to be deployed to staging environment and registered in service catalog, then bundle is deployed and post-deployment scan is run on deployed application. "Post-deployable" job runs to check accepted / rejected release request status and "Artifact Transfer Cron" runs to check where release request is accepted and bundle file is moved to production artifact factory for deployment on production. Type 1 bundle data entry window 1438 also presents date and time related logs in chronological order (newest first to oldest shown on top).

[0095] The Type 2 bundle ingest page 1420 includes one or more pages having a Type 2 bundle data entry window 1440 configured to accept details for creating a user. In at least one embodiment, the Type 2 bundle data entry window 1440 accepts data entries including resources 911, observability 912, configuration 913, networking 914, security 915, bare metal 916, and preview stage 917 data entries as described above with respect to FIG. 9. One skilled in the art will recognize that the description of data entries for the Type 2 bundle data entry window 1440 is provided as an example and is not intended to limit the embodiments described herein. The Type 2 bundle data entry window 1440 can be used for entry of additional data, different types of data, or less data than described herein.

[0096] The Type 2 bundle data entry window 1440 is configured to display, beneath the resource data entry 911, a sandbox area for entering memory size, number of CPUs, storage size, and tags.

[0097] The Type 2 bundle data entry window 1440 is configured under Observability 912 to receive metrics and logging data. Metrics data includes the name of the metric and the match label. Logging data includes the name associated with the logging data, the match label, and the value associated with the log.

[0098] A Type 2 bundle data entry window 1440 is configured under Configuration 913 for the user to add a configuration or a configuration management database (CMDB). Under Networking 914, the Type 2 bundle data entry window 1440 presents an API Gateway tab and a Networking tab. When the API Gateway tab is selected, data for a new API Gateway is entered. API Gateway data includes name, version, and brokering policy. Brokering policy data includes request ID policy in / policy out data, security scheme and security policy, visibility configuration, API environment, endpoint URL, swagger file upload option, certificate upload selection, type of configuration, tenant name, and environment.

[0099] The Type 2 bundle data entry window 1440 is configured to present a GRC producer tab under security 915 for entry of security data including an indication of whether the GRC producer is a corporate affiliate, application and / or organization, application name, application ID, application owner email, country, applicable industry, application data, privacy data, application data backup information, and application data security information. The Type 1 bundle data entry window 1438 is configured under bare metal data entry 816 for entry of a user to add roles and permissions for managing access to the bundle, such as keycloak integration of the bundle, and to add performance and fault management policies.

[0100] In the preview 917, the Type 2 bundle data entry window 1440 presents an option to view the bundle status including the phase and status of the pre-deployment scan. The display of the bundle status provided by the Type 2 bundle data entry window 1440 includes a kebab icon for evaluation selection, Type 1 bundle, and Type 2 bundle. Selection of the evaluation option presents a bundle evaluation page including an Evaluation Bundle tab, a Comments tab, an X-Ray Scan Results tab, and a Sonar Scan Results tab. The X-Ray and Sonar scans are downloaded by selecting the X-Ray Scan Results tab and the Sonar Scan Results tab. If the details in the bundle evaluation page 5900 are determined to be acceptable, the Type 2 bundle data entry window 1440 presents an Approve button for the user to select to approve the bundle.

[0101] Once the bundle is approved in the Type 2 bundle data entry window 1440, self-QA certification data can be entered, including project name, description, tags, start date, end date, environment type, priority, version associated with the bundle release, release type, services affected by the bundle, services affected by the change, certification summary, arb status, arb number, and uploaded reports.

[0102] FIG. 15 is a flowchart 1500 of a method for managing end-to-end onboarding for an application bundle according to at least one embodiment.

[0103] In FIG. 15, the method begins S1510 where a dashboard user interface is presented that displays information related to at least one application bundle component and presents a dashboard menu on the dashboard user interface for selecting at least one application bundle component to create (S1514). Referring to FIG. 2, the dashboard UI 210 provides options for creating application bundle components such as services, vendors, users, artifacts, bundles, etc. The dashboard UI 210 also provides information to the user regarding the various bundle components. From the dashboard UI 210, the user can initiate the creation of a service by displaying the service creation UI 212.

[0104] Selection of components of at least one application bundle to be created is received via a dashboard menu (S1518). Referring to Figure 3, a dashboard user interface 300 is accessed by a service designer 302 and provides a pull-down menu 306 for selecting bundle components to be created.

[0105] Based on the selection, a creation user interface is displayed including selectable control components for initiating creation of at least one application bundle component (S1522). With reference to FIG. 2, from the dashboard UI 210, the user can initiate the creation of a service by displaying the service creation UI 212. The service creation UI 212 displays information about existing services and has selectable components for adding new services. From the dashboard UI 210, the user can initiate the creation of a vendor by displaying the vendor creation UI 214. The vendor creation UI 214 displays information about existing vendors and has selectable components for adding new vendors.

[0106] In response to receiving a selection of the selectable control component, a bundle component details capture user interface is presented (S1526). Referring to Figure 14, once creation of a bundle component is initiated from a creation UI, such as a service creation UI 212, a vendor creation UI 214, a user creation UI 216, an artifact creation / upload UI 218, and a bundle creation UI, and initial details are provided to the creation UI, a details capture UI 1400 is displayed to enable the user to provide other details for creating the bundle component.

[0107] A bundle component evaluation interface is presented (S1530) that provides details related to the created bundle components. Referring to FIG. 1, the GUI 114 allows access to an overview of the bundle, including the bundle's phase and status. A user of the onboarding management device 110 uses the GUI 114 to evaluate the new bundle.

[0108] Input is received from the bundle component evaluation interface to trigger deployment of the created bundle components (S1534). Approval of the bundle details results in a request for a prototype service catalog registration. Referring to Figure 11, after the prototype service catalog registration is completed, selection of the kebab icon 1150 displays a menu 1160 from which a deployment trigger option 1162 for deploying the bundle is selected.

[0109] Input is received from the bundle component evaluation interface to trigger a quality assurance (QA) post-deployment scan on the created bundle components (S1538). Referring to Figure 12, approval of the bundle details results in a request for a prototype service catalog registration. After the prototype service catalog registration is complete, selection of the kebab icon 1250 displays a menu 1260 where a QA trigger option 1262 can be selected to initiate a post-production scan on the bundle.

[0110] A status assessment interface is presented to check the status of the created bundle components based on a post-QA deployment scan of the created bundle components (S1542). Referring to FIG. 13, the status check UI 1300 shows that the sonar scan results tab 1310 has been selected to show the sonar scan results of the bundle.

[0111] An approval input page is presented to approve or reject the created bundle components (S1546). Referring to Figure 10, a bundle evaluation approval verification window 1000 is displayed providing the user with the option to select Yes 1010 or No 1012. The user selects Yes 1010 to verify approval of the details in the bundle evaluation UI 1004. After selecting Yes 1010 and the bundle is approved, the bundle proceeds to sandbox or stage testing depending on its configuration and begins testing SBX.

[0112] The process then ends (S1550).

[0113] At least one embodiment for managing end-to-end onboarding for an application bundle includes presenting a dashboard user interface displaying information related to at least one application bundle component, presenting a dashboard menu on the dashboard user interface for selecting the at least one application bundle component to create, receiving a selection of the at least one application bundle component to create via the dashboard menu, and based on the selection, displaying a creation user interface including selectable control components for initiating creation of the at least one application bundle component, and creating the at least one application bundle component in response to receiving the selection of the selectable control component.

[0114] FIG. 16 is a high-level functional block diagram of a processor-based system 1600 according to at least one embodiment.

[0115] In at least one embodiment, the processing circuit 1600 provides end-to-end application onboarding. The processing circuit 1600 implements an application bundle onboarding management device using the processor 1602. The processing circuit 1600 also includes a non-transitory computer-readable storage medium 1604 used to implement the application bundle onboarding management device. The storage medium 1604 is encoded with, among other things, instructions 1606, i.e., computer program code that stores the instructions 1606, i.e., that the processor 1602 executes, causing the processor 1602 to perform operations to manage end-to-end onboarding for application bundles. Execution of the instructions 1606 by the processor 1602 represents (at least in part) an application bundle onboarding management application that implements at least a portion of the methods (hereinafter, the described processes and / or methods) described herein according to one or more embodiments.

[0116] The processor 1602 is electrically coupled to a computer readable storage medium 1604 via a bus 1608. The processor 1602 is electrically coupled to an input / output (I / O) interface 1610 by the bus 1608. A network interface 1612 is also electrically coupled to the processor 1602 via the bus 1608. The network interface 1612 connects to a network 1614 such that the processor 1602 and the computer readable storage medium 1604 connect to external elements via the network 1614. The processor 1602 is configured to execute the instructions 1606 encoded on the computer readable storage medium 1604, enabling the processing circuit 1600 to execute at least a portion of a process and / or method. In one or more embodiments, the processor 1602 is a central processing unit (CPU), a multiprocessor, a distributed processing system, an application specific integrated circuit (ASIC), and / or other suitable processing unit.

[0117] The processing circuit 1600 includes an I / O interface 1610. The I / O interface 1610 couples to external circuitry. In one or more embodiments, the I / O interface 1610 includes a keyboard, a keypad, a mouse, a trackball, a trackpad, a touch screen, and / or cursor direction keys for communicating information and commands to the processor 1602.

[0118] The processing circuit 1600 also includes a network interface 1612 coupled to the processor 1602. The network interface 1612 enables the processing circuit 1600 to communicate with a network 1614 to which one or more other computer systems are connected. The network interface 1612 includes a wireless network interface, such as Bluetooth, Wi-Fi, Worldwide Interoperability for Microwave Access (WiMAX), General Packet Radio Service (GPRS), or Wideband Code Division Multiple Access (WCDMA), or a wired network interface, such as Ethernet, Universal Serial Bus (USB), or Institute of Electrical and Electronics Engineers (IEEE) 864.

[0119] The processing circuit 1600 is configured to receive information via an I / O interface 1610. The information received via the I / O interface 1610 includes one or more of instructions, data, design rules, libraries of cells, and / or other parameters for processing by the processor 1602. The information is transferred to the processor 1602 via a bus 1608. The processing circuit 1600 is configured to receive information from a non-transitory computer readable medium 1604, etc. The processor uses user interface data 1622 from the non-transitory computer readable medium 1604 to display a user interface 1632 on a display device 1630.

[0120] In one or more embodiments, one or more non-transitory computer-readable storage media 1604 are described herein that store instructions (compressed or uncompressed) that may be used to program a computer, processor, or other electronic device to perform a process or method. The one or more non-transitory computer-readable storage media 1604 include one or more of an electronic storage medium, a magnetic storage medium, an optical storage medium, a quantum storage medium, and the like. For example, the computer-readable storage medium may include, but is not limited to, a hard drive, a floppy diskette, an optical disk, a read-only memory (ROM), a random access memory (RAM), an erasable programmable ROM (EPROM), an electrically erasable programmable ROM (EEPROM), a flash memory, a magnetic or optical card, a solid-state memory device, or other type of physical medium suitable for storing electronic instructions. In one or more embodiments that use an optical disk, the one or more non-transitory computer-readable storage media 1604 include a compact disk read-only memory (CD-ROM), a compact disk read / write (CD-R / W), and / or a digital video disk (DVD).

[0121] In one or more embodiments, the storage medium 1604 stores instructions 1606 configured to cause the processing circuit 1600 to execute at least a portion of a process and / or method for end-to-end application onboarding. In one or more embodiments, the storage medium 1604 also stores information, such as algorithms, that facilitate execution of at least a portion of a process and / or method for managing end-to-end onboarding for application bundles. Thus, in at least one embodiment, the processor circuit 1600 executes a method for managing end-to-end onboarding for application bundles. The process includes presenting a dashboard user interface that displays information related to at least one application bundle component, presenting a dashboard menu on the dashboard user interface for selecting at least one application bundle component to create, receiving a selection of the at least one application bundle component to create via the dashboard menu, and displaying a creation user interface including a selectable control component for initiating creation of the at least one application bundle component based on the selection, and creating the at least one application bundle component in response to receiving the selection of the selectable control component.

[0122] Separate instances of these programs may run or be distributed on any number of separate computer systems. Thus, although certain steps are described as being performed by a particular device, software program, process, or entity, this is not necessarily the case. Various alternative implementations will be appreciated by those skilled in the art. Moreover, those skilled in the art will readily appreciate that the techniques described above can be utilized in a variety of devices, environments, and contexts. Although embodiments have been described in language specific to structural features or methodological acts, the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as exemplary forms of implementing the claims.

Claims

1. 1. A method for managing end-to-end onboarding for an application bundle, comprising: presenting a dashboard user interface that displays information related to at least one application bundle component, and presenting a dashboard menu on the dashboard user interface for selecting the at least one application bundle component to be created; receiving, via the dashboard menu, a selection of components of the at least one application bundle to be created; displaying a creation user interface including graphical control elements for initiating creation of the at least one application bundle component based on the selection; and creating the at least one application bundle component in response to receiving activation of the graphical control element.

2. Creating the at least one application bundle component includes presenting a bundle component detail import user interface, and presenting the bundle component detail import user interface includes: at least one service detail capture page for receiving details for creating a service; at least one vendor detail capture page for receiving details for creating a vendor; at least one user details capture page for receiving details for creating a user; at least one artefact detail capture page that receives details for creating an artefact; or and presenting at least one bundle detail capture page that receives details for creating a bundle.

3. The method of claim 2 , wherein presenting the at least one bundle detail capture page further comprises presenting a bundle rating interface that provides details related to the bundle.

4. 4. The method of claim 3, wherein presenting the bundle evaluation interface further comprises: presenting a bundle deployment menu for deploying the bundle; and receiving an input via the bundle deployment menu that triggers deployment of the bundle.

5. 4. The method of claim 3, wherein presenting the bundle evaluation interface further comprises presenting a quality assurance (QA) menu that triggers a QA post-deployment scan on the bundle, and receiving an input via the QA menu that triggers running the QA post-deployment scan on the bundle.

6. The method of claim 5 , further comprising: in response to receiving the input and triggering the execution of the QA post-deployment scan on the bundle, presenting a bundle status evaluation interface that checks the status of the bundle based on the execution of the QA post-deployment scan on the bundle.

7. The method of claim 3 , wherein presenting the bundle evaluation interface further comprises presenting an approval input page and receiving input on the approval input page to approve or reject the bundle.

8. A device for managing end-to-end onboarding of an application bundle, comprising: A memory storing computer readable instructions; a processor coupled to the memory, wherein the processor executes the computer readable instructions to: presenting a dashboard user interface that displays information related to at least one application bundle component and presents a dashboard menu on the dashboard user interface for selecting the at least one application bundle component to be created; receiving, via the dashboard menu, a selection of components of the at least one application bundle to be created; displaying a creation user interface including graphical control elements for initiating creation of a component of the at least one application bundle based on the selection; A device configured to create components of the at least one application bundle in response to receiving activation of the graphical control element.

9. The processor is further configured to create the at least one application bundle component by presenting a bundle component detail capture user interface, where the bundle component detail user interface comprises: at least one service detail capture page for receiving details for creating a service; at least one vendor detail capture page for receiving details for creating a vendor; at least one user details capture page for receiving details for creating a user; at least one artefact detail capture page that receives details for creating an artefact; or and at least one bundle detail capture page that receives details for creating a bundle.

10. The device of claim 9 , wherein the at least one bundle detail capture page includes a bundle rating interface that provides details related to the bundle.

11. The device of claim 10 , wherein the bundle evaluation interface further comprises a bundle unfolding menu for unfolding the bundle, and wherein the processor receives an input triggering unfolding of the bundle via the bundle unfolding menu.

12. 11. The device of claim 10, wherein the bundle evaluation interface further includes a quality assurance (QA) menu for triggering a QA post-deployment scan on the bundle, and wherein the processor receives an input via the QA menu to trigger execution of the QA post-deployment scan on the bundle.

13. The device of claim 12 , wherein in response to receiving an input triggering the execution of the QA post-deployment scan on the bundle, the processor presents a bundle status evaluation interface that checks a status of the bundle based on the execution of the QA post-deployment scan on the bundle.

14. The device of claim 10 , wherein the bundle evaluation interface further comprises an approval input page, and wherein the processor receives input on the approval input page to approve or reject the bundle.

15. A non-transitory computer readable medium having computer readable instructions stored thereon that, when executed by a processor, cause the processor to: presenting a dashboard user interface that displays information related to at least one application bundle component, and presenting a dashboard menu on the dashboard user interface for selecting the at least one application bundle component to be created; receiving, via the dashboard menu, a selection of components of the at least one application bundle to be created; displaying a creation user interface including graphical control elements for initiating creation of the at least one application bundle component based on the selection; and in response to receiving activation of the graphical control element, creating a component of the at least one application bundle.

16. Creating the at least one application bundle component includes presenting a bundle component detail capture user interface, and presenting the bundle component detail user interface includes: at least one service detail capture page for receiving details for creating a service; at least one vendor detail capture page for receiving details for creating a vendor; at least one user details capture page for receiving details for creating a user; at least one artefact detail capture page for receiving details for creating an artefact; or and at least one bundle detail capture page that receives details for creating a bundle.

17. 20. The non-transitory computer-readable medium of claim 16, wherein presenting the at least one bundle detail capture page further comprises presenting a bundle rating interface that provides details related to the bundle.

18. 20. The non-transitory computer-readable medium of claim 17, wherein presenting the bundle evaluation interface further comprises presenting a bundle deployment menu for deploying the bundle, and receiving an input via the bundle deployment menu that triggers deployment of the bundle.

19. 20. The non-transitory computer-readable medium of claim 17, wherein presenting the bundle evaluation interface further comprises: presenting a quality assurance (QA) menu that triggers a QA post-deployment scan on the bundle; and receiving an input via the QA menu for triggering execution of the QA post-deployment scan on the bundle; and wherein in response to receiving the input for triggering execution of the QA post-deployment scan on the bundle, presenting a bundle status evaluation interface that checks a status of the bundle based on execution of the QA post-deployment scan on the bundle.

20. 20. The non-transitory computer-readable medium of claim 17, wherein presenting the bundle evaluation interface further comprises presenting an approval input page and receiving input on the approval input page to approve or reject the bundle.

Images