Abstract: A mobile app is analyzed to determine each UI configuration in a set of UI configurations that is reachable in a possible use of the mobile app. A set of elements used in the mobile app relative to a selected UI configuration from the set of UI configurations is detected. A function performed by a selected element relative to the selected UI configuration is analyzed. The function is matched with a function identified in a hierarchy of elements, the hierarchy being applicable to a plurality of mobile apps. A category of the function identified in the hierarchy is assigned to the selected element. Using the hierarchy, a type of development skill used in developing the selected element is determined. In a blueprint of the mobile app, the category, the type of the development skill, and a numerosity of occurrences of the selected element in the mobile app are output.

Abstract: An example operation may include one or more of receiving, by a mobile service provider, a mobile number portability request from a mobile device connected to a current mobile service provider; fetching mobile device porting data from a blockchain ledger accessible by the mobile service provider and by the current mobile service provider; verifying fetched mobile device porting data; in response to a successful verification, sending a request to the blockchain ledger to update current mobile service provider data; and receiving a notification from the blockchain indicating that a connection between the current mobile service provider and the mobile device is disconnected; porting a mobile device number; and updating the mobile device porting data in the blockchain ledger.

Abstract: An example operation may include one or more of receiving, by a mobile service provider, a mobile number portability request from a mobile device connected to a current mobile service provider; fetching mobile device porting data from a blockchain ledger accessible by the mobile service provider and by the current mobile service provider; verifying fetched mobile device porting data; in response to a successful verification, sending a request to the blockchain ledger to update current mobile service provider data; and receiving a notification from the blockchain indicating that a connection between the current mobile service provider and the mobile device is disconnected; porting a mobile device number; and updating the mobile device porting data in the blockchain ledger.

Abstract: An example operation may include one or more of receiving, by a mobile service provider, a mobile number portability request from a mobile device connected to a current mobile service provider; fetching mobile device porting data from a blockchain ledger accessible by the mobile service provider and by the current mobile service provider; verifying fetched mobile device porting data; in response to a successful verification, sending a request to the blockchain ledger to update current mobile service provider data; and receiving a notification from the blockchain indicating that a connection between the current mobile service provider and the mobile device is disconnected; porting a mobile device number; and updating the mobile device porting data in the blockchain ledger.

Abstract: An example operation may include one or more of receiving, by a mobile service provider, a mobile number portability request from a mobile device connected to a current mobile service provider; fetching mobile device porting data from a blockchain ledger accessible by the mobile service provider and by the current mobile service provider; verifying fetched mobile device porting data; in response to a successful verification, sending a request to the blockchain ledger to update current mobile service provider data; and receiving a notification from the blockchain indicating that a connection between the current mobile service provider and the mobile device is disconnected; porting a mobile device number; and updating the mobile device porting data in the blockchain ledger.

Abstract: A mobile app is analyzed to determine each UI configuration in a set of UI configurations that is reachable in a possible use of the mobile app. A set of elements used in the mobile app relative to a selected UI configuration from the set of UI configurations is detected. A function performed by a selected element relative to the selected UI configuration is analyzed. The function is matched with a function identified in a hierarchy of elements, the hierarchy being applicable to a plurality of mobile apps. A category of the function identified in the hierarchy is assigned to the selected element. Using the hierarchy, a type of development skill used in developing the selected element is determined. In a blueprint of the mobile app, the category, the type of the development skill, and a numerosity of occurrences of the selected element in the mobile app are output.

Abstract: An analysis of a mobile app is performed to determine each UI configuration in a set of UI configurations that is reachable in a possible use of the mobile app. A set of elements is detected that is used in the mobile app relative to a selected UI configuration from the set. A function performed by a selected element relative to the selected UI configuration is analyzed and matched with a function identified in a hierarchy of elements. The hierarchy is applicable to several mobile apps. A category of the function identified in the hierarchy is assigned to the selected element. The category and a numerosity of occurrences of the selected element in the mobile app are output in a blueprint of the mobile app.

Abstract: Example embodiments of the present invention provide a method, an apparatus, and a computer program product for authenticating a request from a first domain to access a resource in a second domain according to credentials in the first domain. The method includes receiving, from the first domain, an assertion in the second domain and generating, according to the assertion, a token configured to be redeemed by a client in the first domain to access the resource in the second domain. The token then may be provided to the first domain.

Abstract: A mobile app is analyzed to determine each UI configuration in a set of UI configurations that is reachable in a possible use of the mobile app. A set of elements used in the mobile app relative to a selected UI configuration from the set of UI configurations is detected. A function performed by a selected element relative to the selected UI configuration is analyzed. The function is matched with a function identified in a hierarchy of elements, the hierarchy being applicable to a plurality of mobile apps. A category of the function identified in the hierarchy is assigned to the selected element. Using the hierarchy, a type of development skill used in developing the selected element is determined. In a blueprint of the mobile app, the category, the type of the development skill, and a numerosity of occurrences of the selected element in the mobile app are output.

Abstract: An example operation may include one or more of receiving, by a mobile service provider, a mobile number portability request from a mobile device connected to a current mobile service provider; fetching mobile device porting data from a blockchain ledger accessible by the mobile service provider and by the current mobile service provider; verifying fetched mobile device porting data; in response to a successful verification, sending a request to the blockchain ledger to update current mobile service provider data; and receiving a notification from the blockchain indicating that a connection between the current mobile service provider and the mobile device is disconnected; porting a mobile device number; and updating the mobile device porting data in the blockchain ledger.

Abstract: An example operation may include one or more of receiving, by a mobile service provider, a mobile number portability request from a mobile device connected to a current mobile service provider; fetching mobile device porting data from a blockchain ledger accessible by the mobile service provider and by the current mobile service provider; verifying fetched mobile device porting data; in response to a successful verification, sending a request to the blockchain ledger to update current mobile service provider data; and receiving a notification from the blockchain indicating that a connection between the current mobile service provider and the mobile device is disconnected; porting a mobile device number; and updating the mobile device porting data in the blockchain ledger.

Abstract: An approach is provided for managing a deployment of a software package. First and second quality assurance (QA) seals are determined to match exactly one QA seal and no QA seal, respectively, in a plurality of QA seals. First details about hardware, middleware, and applications required in a first environment, which are included in the first QA seal, are determined to match second details of the first environment. Based on the first QA seal matching exactly one QA seal and the first details matching the second details, the software package is determined to be compatible with the first environment and a notification is generated authorizing the deployment of the software package to the first environment. Based on the second QA seal not matching any of the plurality of QA seals, a notification is generated indicating that the deployment of the software package to a second environment is not authorized.

Abstract: A mobile app is analyzed to determine each UI configuration in a set of UI configurations that is reachable in a possible use of the mobile app. A set of elements used in the mobile app relative to a selected UI configuration from the set of UI configurations is detected. A function performed by a selected element relative to the selected UI configuration is analyzed. The function is matched with a function identified in a hierarchy of elements, the hierarchy being applicable to a plurality of mobile apps. A category of the function identified in the hierarchy is assigned to the selected element. Using the hierarchy, a type of development skill used in developing the selected element is determined. In a blueprint of the mobile app, the category, the type of the development skill, and a numerosity of occurrences of the selected element in the mobile app are output.

Abstract: An analysis of a mobile app is performed to determine each UI configuration in a set of UI configurations that is reachable in a possible use of the mobile app. A set of elements is detected that is used in the mobile app relative to a selected UI configuration from the set. A function performed by a selected element relative to the selected UI configuration is analyzed and matched with a function identified in a hierarchy of elements. The hierarchy is applicable to several mobile apps. A category of the function identified in the hierarchy is assigned to the selected element. The category and a numerosity of occurrences of the selected element in the mobile app are output in a blueprint of the mobile app.

Abstract: An approach is provided for securely authenticating an identity of a user participating in an electronic transaction. A request for a biometric identifier/security question is converted to a first Quick Response (QR) code. Based on user attributes and a request from the user's mobile device to a computer to initiate the transaction, the first QR code is disassembled into first and second portions. The first portion, but not the second portion, is sent to the mobile device. Responsive to the mobile device receiving and converting the biometric identifier/answer to the security question to a second QR code, and disassembling the second QR code into first and second portions, the second QR code is reassembled. The transaction is authorized based on whether the biometric identifier/answer matches a data repository record.

Abstract: A metrics based design method and system is disclosed. The method includes receiving by a computer processor, an informational model comprising data objects, attributes, and relationships associated with a service. The data objects comprise sub-objects. The computer processor receives business affinity (BA) band data associated with the data objects, threshold levels associated with the business affinity (BA) band data, business affinity (BA) levels associated with the business affinity (BA) band data, and service interface operation parameters. The computer processor computes a business affinity (BA) for the informational model based on the business affinity (BA) band data, the threshold levels, the business affinity (BA) levels, and the service interface operation parameters. The computer processor computes a data variation percentage and a reusability count.

Abstract: An approach is provided for securely authenticating an identity of a user participating in an electronic transaction. A request for a biometric identifier/security question is converted to a first Quick Response (QR) code. Based on user attributes and a request from the user's mobile device to a computer to initiate the transaction, the first QR code is disassembled into first and second portions. The first portion, but not the second portion, is sent to the mobile device. Responsive to the mobile device receiving and converting the biometric identifier/answer to the security question to a second QR code, and disassembling the second QR code into first and second portions, the second QR code is reassembled. The transaction is authorized based on whether the biometric identifier/answer matches a data repository record.

Abstract: An approach is provided for securely authenticating an identity of a user participating in an electronic transaction. A request for a biometric identifier/security question is converted to a first Quick Response (QR) code. Based on user attributes and a request from the user's mobile device to a computer to initiate the transaction, the first QR code is disassembled into first and second portions. The first portion, but not the second portion, is sent to the mobile device. Responsive to the mobile device reassembling the first QR code, receiving and converting the biometric identifier/answer to the security question to a second QR code, disassembling the second QR code into first and second portions, and transmitting the first portion of the second QR code to the computer, the second QR code is reassembled. The transaction is authorized based on whether the biometric identifier/answer matches a data repository record.

Abstract: A method of securing authentication of a user's identity is disclosed. The method comprises the steps of: an authentication program of an entity receiving initiation of a transaction from a user; the authentication program searching for associated information of the user; the authentication program choosing an authentication query requiring input from the user based on the associated information; the authentication program generating a visual code representing the authentication query; the authentication program splitting the visual code into pieces; and the authentication program sending each piece of visual code to the user via a separate communication channel. A method of securing authentication of a user's identity with an entity is also disclosed.

Abstract: An approach is provided for securely authenticating an identity of a user participating in an electronic transaction. A request for a biometric identifier/security question is converted to a first Quick Response (QR) code. Based on user attributes and a request from the user's mobile device to a computer to initiate the transaction, the first QR code is disassembled into first and second portions. The first portion, but not the second portion, is sent to the mobile device. Responsive to the mobile device reassembling the first QR code, receiving and converting the biometric identifier/answer to the security question to a second QR code, disassembling the second QR code into first and second portions, and transmitting the first portion of the second QR code to the computer, the second QR code is reassembled. The transaction is authorized based on whether the biometric identifier/answer matches a data repository record.