Abstract: The invention relates to a method for managing risk of an enterprise. The method steps include generating, using risk survey responses, risk panels for first level risk survey items; presenting the risk panels for each of the first level risk survey items; receiving a selection of a first risk panel of the risk panels for a first level risk survey item; presenting, based on the selection, a second risk panel of the risk panels for second level risk survey items; receiving, using the second risk panel, additional risk survey responses for one of the second level risk survey items; updating, based on the additional risk survey responses and using a computer processor, the risk panels for the first level risk survey item to generate revised risk panels; and presenting the revised risk panels for the first level risk survey items.

Abstract: The invention relates to a method for managing risk of an enterprise. The method steps include generating, using risk survey responses, risk panels for first level risk survey items; presenting the risk panels for each of the first level risk survey items; receiving a selection of a first risk panel of the risk panels for a first level risk survey item; presenting, based on the selection, a second risk panel of the risk panels for second level risk survey items; receiving, using the second risk panel, additional risk survey responses for one of the second level risk survey items; updating, based on the additional risk survey responses and using a computer processor, the risk panels for the first level risk survey item to generate revised risk panels; and presenting the revised risk panels for the first level risk survey items.

Abstract: Various aspects described herein are directed to a system that develops and manages releases of software applications. The system includes a server-side branch management module to automatically create one or more branches for deployment of a software application release, a deployment repository to store one or more box sets for a plurality of artifacts for the software release, and a code repository to store the plurality of artifacts. The system may further include a release management module configured to manage continuing releases of the software application, a continuous deployment dashboard module configured to receive the plurality of box sets from the deployment repository, and one or more development modules configured to create or modify at least some artifacts of the plurality of artifacts. The plurality of artifacts are automatically tagged with respective packaging types for automatic generation of the plurality of box sets.