Abstract: A system obtains content access attributes associated with content presented at a user interface at a particular physical location. The content access attributes indicate intended accessibility of the content presented at the user interface at the particular physical location. The system obtains entity authorization attributes determined for an entity detected by sensors configured to obtain sensor data associated with entities positioned at the particular physical location. The entity authorization attributes are determined based upon the sensor data obtained by the sensors. Based upon the content access attributes and the entity authorization attributes, the system determines an interface security action for implementation at the user interface at the particular physical location.

Abstract: A computer system for just-in-time authentication displays a user interface comprising a first portion and a second portion. The first portion of the user interface is associated with a first permission attribute, and the second portion of the user interface is associated with a second permission attribute. The first permission attribute is associated with a first user and the second permission attribute is associated with a second user. The computer system receives, from one or more proximity sensors, a proximity of the second user relative to the user interface. The computer system also receives, from an identity-verification sensor, a verification of an identification of the second user. Further, the computer system activates the second portion of the user interface for interaction from the second user.

Abstract: Embodiments are directed to providing interfaces for software updating and code building. In one embodiment, a software code building interface is provided which includes a manufacturing and production process analyzer configured to divide the manufacturing and production process into multiple physical, discrete steps. The software code building interface includes other modules that identify dependencies between the discrete steps, generate reusable, global software code elements having data structures that are implemented to dynamically create interactive interfaces that present and allow interaction with the discrete steps, and access the generated global software code elements and the identified dependencies to generate interactive manufacturing and production process interfaces. These interfaces allow users to provide information relating to the discrete steps, ensuring that the manufacturing and production process is performed in an intended manner.

Abstract: A production system is configurable to obtain a set of computer-executable instructions that are operable to cause the production system to perform a set of workflow steps. The production system is also configurable to obtain implementation data associated with the set of workflow steps and identify a set of synthetic execution indicators associated with the set of workflow steps. The production system is configurable to (1) generate a validation test based on the implementation data, the set of synthetic execution indicators, and the set of workflow steps, and (2) perform the validation test by synthetically executing the one or more workflow steps on the production system using inputs generated from the implementation data, recording synthetic execution output in a synthetic execution data repository, and refraining from recording the synthetic execution output as production transaction output on a production transaction data repository.

Abstract: Embodiments are directed to providing interfaces for software updating and code building. In one embodiment, a software code building interface is provided which includes a manufacturing and production process analyzer configured to divide the manufacturing and production process into multiple physical, discrete steps. The software code building interface includes other modules that identify dependencies between the discrete steps, generate reusable, global software code elements having data structures that are implemented to dynamically create interactive interfaces that present and allow interaction with the discrete steps, and access the generated global software code elements and the identified dependencies to generate interactive manufacturing and production process interfaces. These interfaces allow users to provide information relating to the discrete steps, ensuring that the manufacturing and production process is performed in an intended manner.

Abstract: Embodiments are directed to providing interfaces for software updating and code building. In one embodiment, a software code building interface is provided which includes a manufacturing and production process analyzer configured to divide the manufacturing and production process into multiple physical, discrete steps. The software code building interface includes other modules that identify dependencies between the discrete steps, generate reusable, global software code elements having data structures that are implemented to dynamically create interactive interfaces that present and allow interaction with the discrete steps, and access the generated global software code elements and the identified dependencies to generate interactive manufacturing and production process interfaces. These interfaces allow users to provide information relating to the discrete steps, ensuring that the manufacturing and production process is performed in an intended manner.

Abstract: Embodiments are directed to performing risk-based software validation and to applying change control when upgrading a software application. In one scenario, a computer system calculates a risk score for features in a software application. This risk score indicates a relative level of risk for installing and using the software application. The computer system performs internal usage testing to determine how the software application is recommended for use, and conducts use tests to determine how a specified client uses the features of the software application as compared to the determined recommended use. Then, based on the calculated risk and the determined use of the features, the computer system provides a recommendation for the specified client indicating which portions of the software application are to undergo client-specific validation. In another scenario, a computer system applies change control when upgrading a software application from a first version to a second version.

Abstract: A computer system for just-in-time authentication displays a user interface comprising a first portion and a second portion. The first portion of the user interface is associated with a first permission attribute, and the second portion of the user interface is associated with a second permission attribute. The first permission attribute is associated with a first user and the second permission attribute is associated with a second user. The computer system receives, from one or more proximity sensors, a proximity of the second user relative to the user interface. The computer system also receives, from an identity-verification sensor, a verification of an identification of the second user. Further, the computer system activates the second portion of the user interface for interaction from the second user.

Abstract: Embodiments are directed to performing risk-based software validation and to applying change control when upgrading a software application. In one scenario, a computer system calculates a risk score for features in a software application. This risk score indicates a relative level of risk for installing and using the software application. The computer system performs internal usage testing to determine how the software application is recommended for use, and conducts use tests to determine how a specified client uses the features of the software application as compared to the determined recommended use. Then, based on the calculated risk and the determined use of the features, the computer system provides a recommendation for the specified client indicating which portions of the software application are to undergo client-specific validation. In another scenario, a computer system applies change control when upgrading a software application from a first version to a second version.

Abstract: Embodiments are directed to performing risk-based software validation and to applying change control when upgrading a software application. In one scenario, a computer system calculates a risk score for features in a software application. This risk score indicates a relative level of risk for installing and using the software application. The computer system performs internal usage testing to determine how the software application is recommended for use, and conducts use tests to determine how a specified client uses the features of the software application as compared to the determined recommended use. Then, based on the calculated risk and the determined use of the features, the computer system provides a recommendation for the specified client indicating which portions of the software application are to undergo client-specific validation. In another scenario, a computer system applies change control when upgrading a software application from a first version to a second version.

Abstract: Embodiments are directed to performing risk-based software validation and to applying change control when upgrading a software application. In one scenario, a computer system calculates a risk score for features in a software application. This risk score indicates a relative level of risk for installing and using the software application. The computer system performs internal usage testing to determine how the software application is recommended for use, and conducts use tests to determine how a specified client uses the features of the software application as compared to the determined recommended use. Then, based on the calculated risk and the determined use of the features, the computer system provides a recommendation for the specified client indicating which portions of the software application are to undergo client-specific validation. In another scenario, a computer system applies change control when upgrading a software application from a first version to a second version.

Abstract: Embodiments are directed to performing risk-based software validation and to applying change control when upgrading a software application. In one scenario, a computer system calculates a risk score for features in a software application. This risk score indicates a relative level of risk for installing and using the software application. The computer system performs internal usage testing to determine how the software application is recommended for use, and conducts use tests to determine how a specified client uses the features of the software application as compared to the determined recommended use. Then, based on the calculated risk and the determined use of the features, the computer system provides a recommendation for the specified client indicating which portions of the software application are to undergo client-specific validation. In another scenario, a computer system applies change control when upgrading a software application from a first version to a second version.

Abstract: Embodiments are directed to performing risk-based software validation and to applying change control when upgrading a software application. In one scenario, a computer system calculates a risk score for features in a software application. This risk score indicates a relative level of risk for installing and using the software application. The computer system performs internal usage testing to determine how the software application is recommended for use, and conducts use tests to determine how a specified client uses the features of the software application as compared to the determined recommended use. Then, based on the calculated risk and the determined use of the features, the computer system provides a recommendation for the specified client indicating which portions of the software application are to undergo client-specific validation. In another scenario, a computer system applies change control when upgrading a software application from a first version to a second version.

Abstract: Embodiments are directed to methods and systems for iteratively collecting and transforming data. In one scenario, a computer system instantiates a software application that tracks the progress of a manufacturing process. The software application receives inputs from a first set of workers associated with the manufacturing process. The inputs are related to a given iteration of a process phase and are provided in a manner that is expected by the first set of workers. The computer system also receives a request to present the iteratively collected data received in the inputs in a second different manner, and generates a representation of the data which includes a report on the specified iteration of the manufacturing process phase. The computer system presents the report to a second, different set of workers, which allows the workers to consume the report in a manner expected by the second set of workers.

Abstract: Embodiments are directed to providing interfaces for software updating and code building. In one embodiment, a software code building interface is provided which includes a manufacturing and production process analyzer configured to divide the manufacturing and production process into multiple physical, discrete steps. The software code building interface includes other modules that identify dependencies between the discrete steps, generate reusable, global software code elements having data structures that are implemented to dynamically create interactive interfaces that present and allow interaction with the discrete steps, and access the generated global software code elements and the identified dependencies to generate interactive manufacturing and production process interfaces. These interfaces allow users to provide information relating to the discrete steps, ensuring that the manufacturing and production process is performed in an intended manner.

Abstract: A method for automatically creating a modem interface on a computer device for use with a wireless device. The method of the present invention creates a modem interface without requiring the user to execute a standard operating system's manual modem installation procedure. The modem interface can then be used as a standard interface to a wireless device. This allows existing software to be used in conjunction with the wireless device connected to the modem interface.