Abstract: A component selector may select a first software component stored in a software component library in conjunction with a first annotation, the first annotation being linked to a second annotation of a second software component via a link. An evaluation engine may evaluate a property expressed by the first annotation relative to a requirement expressed by the second annotation, and thereby verify compliance of the first software component and the second software component for inclusion within a software application being developed. A component update monitor may re-verify the compliance, based on an update to at least one of the first software component and the second software component.

Abstract: A progression collector may collect, in conjunction with displayed learning context provided by a learning management system (LMS), first learner progression data of a first learner, and second learner progression data of a second learner. A team aggregator may aggregate the first learner progression data and the second learner progression data into team progression data, and may provide the team progression data to the LMS as virtual learner progression data. A rendering engine may receive progression results processed by the LMS for each of the first learner progression data, the second learner progression data, and the virtual learner progression data representing team progression results.

Abstract: A multi-domain decision manager facilitates software development of a software application across knowledge domains, based on relationships between a first knowledge domain and a second knowledge domain. The multi-domain decision manager includes an assessment engine configured to construct a first assessment as an instantiation of a first knowledge base model of the first knowledge domain, and a second assessment as an instantiation of a second knowledge base model of the second knowledge domain. A relationship engine may be configured to characterize relationships between the first assessment and the second assessment, wherein the relationships characterize a likelihood that inclusion of a first selectable assessment option of the first assessment is associated with inclusion of a second selectable assessment option of the second assessment.

Abstract: A component selector may select a first software component stored in a software component library in conjunction with a first annotation, the first annotation being linked to a second annotation of a second software component via a link. An evaluation engine may evaluate a property expressed by the first annotation relative to a requirement expressed by the second annotation, and thereby verify compliance of the first software component and the second software component for inclusion within a software application being developed. A component update monitor may re-verify the compliance, based on an update to at least one of the first software component and the second software component.

Abstract: A multi-domain decision manager facilitates software development of a software application across knowledge domains, based on relationships between a first knowledge domain and a second knowledge domain. The multi-domain decision manager includes an assessment engine configured to construct a first assessment as an instantiation of a first knowledge base model of the first knowledge domain, and a second assessment as an instantiation of a second knowledge base model of the second knowledge domain. A relationship engine may be configured to characterize relationships between the first assessment and the second assessment, wherein the relationships characterize a likelihood that inclusion of a first selectable assessment option of the first assessment is associated with inclusion of a second selectable assessment option of the second assessment.

Abstract: A progression collector may collect, in conjunction with displayed learning context provided by a learning management system (LMS), first learner progression data of a first learner, and second learner progression data of a second learner. A team aggregator may aggregate the first learner progression data and the second learner progression data into team progression data, and may provide the team progression data to the LMS as virtual learner progression data. A rendering engine may receive progression results processed by the LMS for each of the first learner progression data, the second learner progression data, and the virtual learner progression data representing team progression results.

Abstract: Techniques for managing a display of a system architecture include displaying a first visual representation of the system architecture that includes respective virtual representations of at least two components of the system architecture at a first level of detail; displaying a first virtual representation of a semantically relevant connector that extends between the two components of the system architecture at the first level of detail; receiving a request from a user to display a second visual representation of the system architecture; and generating a second visual representation of the system architecture for display, that includes respective virtual representations of the at least two components of the system architecture at a second level of detail different than the first level of detail, and a second virtual representation of the semantically relevant connector that extends between the at least two components of the system architecture at the second level of detail.

Abstract: Implementations of methods of the present disclosure include providing a process model based on the process, the process model comprising a plurality of tasks, receiving user input at a computing device, the user input specifying one or more security requirements, the user input relating each of the one or more security requirements to at least one task of the plurality of tasks, generating, using the computing device, a formal model of the process based on the process model and the one or more security requirements, the formal model being based on a specification meta-language, processing the formal model using a model checker that is executed on the computing device to determine whether violation of at least one of the one or more security requirements occurs in the process, generating an analysis result based on the processing, and displaying the analysis result on a display.

Abstract: Various embodiments of systems and methods for risk management of business processes are described herein. A system integrating process monitoring and automated risk management through a risk-annotated business process model is described. Such a risk would be computed for each of the possible path of execution of the business process. The source of such a data can be derived from other systems or be entered manually. A risk prediction rule is executed when a given event has happen. Depending on the current execution state of a business process instance, the risk is calculated from the probability and the impact. If the risk is over a certain threshold, some actions can be taken (e.g., stopping processes, initiate mitigation processes or notifying the business process owner).

Abstract: A system and method for security-aware data flow analysis are described. In various embodiments, a system analyses relationships between users, roles, tasks, and data objects, and permissions set thereon and grants access to users to specific data objects or data fields. In various embodiments, a method for creating an authorization matrix for data used in business processes is described. The method includes analyzing organizational policies associated with functional requirements and granting access to data to users if organizational policies are complied with.