Abstract: A watermarking method for smart contract according to an embodiment of the present disclosure comprises compiling a source code of a smart contract to create a contract creation bytecode and a runtime bytecode; generating a control flow graph including a plurality of byte regions based on the runtime bytecode; setting opcode groups by grouping consecutive opcodes in an opcode list in the plurality of byte regions of the generated control flow graph so that a sum of gas costs for the consecutive opcodes is greater than or equal to a preset gas cost value; extracting a watermarkable byte region based on the set opcode groups; determining watermarking bytes, in which a watermark is to be embed in the watermarkable byte region, to embed the watermark and storing location information of the determined watermarking bytes; hashing fingerprint information including information on the watermark and the location information of the watermarking bytes to create a fingerprint; and embedding the created fingerprint in the

Abstract: Methods, systems and apparatus for providing a variety of end product build plans based on multiple business scenarios for exhausting excess inventory. Raw financial data and variable scaling factors are input into a scenario engine component along with a business objective that contains logic. The scaling factor may be embedded within the logic of the business objective, or it may be selected by a user to indicate the user's preferences. The scenario engine then applies the financial data and variable scaling factor inputs to the business objective logic to generate modified financial data. The logic of the business objective may also be manipulated to provide modified logic. The modified financial data, and optionally the modified logic, are then input into an optimizer component for determining multiple portfolios for end products that, if built, would consume excess inventory.

Abstract: Methods, systems and apparatus for providing a variety of end product build plans based on multiple business scenarios for exhausting excess inventory. Raw financial data and variable scaling factors are input into a scenario engine component along with a business objective that contains logic. The scaling factor may be embedded within the logic of the business objective, or it may be selected by a user to indicate the user's preferences. The scenario engine then applies the financial data and variable scaling factor inputs to the business objective logic to generate modified financial data. The logic of the business objective may also be manipulated to provide modified logic. The modified financial data, and optionally the modified logic, are then input into an optimizer component for determining multiple portfolios for end products that, if built, would consume excess inventory.

Abstract: Methods, systems and apparatus for providing a variety of end product build plans based on multiple business scenarios for exhausting excess inventory. Raw financial data and variable scaling-factors are input into a scenario engine component along with a business objective that contains logic. The scaling factor may be embedded within the logic of the business objective, or it may be selected by a user to indicate the user's preferences. The scenario engine then applies the financial data and variable scaling factor inputs to the business objective logic to generate modified financial data. The logic of the business objective may also be manipulated to provide modified logic. The modified financial data, and optionally the modified logic, are then input into an optimizer component for determining multiple portfolios for end products that, if built, would consume excess inventory.

Abstract: A solution for managing a business engagement between a provider and a client is provided. The business engagement includes one or more business solutions for which a client risk preference level is obtained. One of a plurality of engagement types is also obtained for the business solution(s) based on a business goal for the business solution(s). A pricing model for each business solution is then selected based on the engagement type and the client risk preference level. Further, the pricing model can be selected based on additional factors, such as a provider risk preference level, a business value for the business solution, and/or the like. The pricing model can comprise a risk/gain sharing pricing model having a fixed price and/or variable price pricing structure. Performance data for the business solution can be obtained and used as feedback for future business engagements and/or to implement the risk/gain sharing pricing model.

Abstract: A method, system, and program product for managing one or more business solutions is provided. One or more candidate business solutions, each of which has a corresponding set of resource requirements and a corresponding business value that is based on a risk and an expected return are used to generate a set of proposed business solutions that maximizes a total value while remaining within a set of resource constraints. In this manner, business decisions regarding particular business solutions to implement can be made with an understanding as to relative risk and/or a total value that will be provided to a business entity.

Abstract: Methods, systems and apparatus for providing a variety of end product build plans based on multiple business scenarios for exhausting excess inventory. Raw financial data and variable scaling-factors are input into a scenario engine component along with a business objective that contains logic. The scaling factor may be embedded within the logic of the business objective, or it may be selected by a user to indicate the user's preferences. The scenario engine then applies the financial data and variable scaling factor inputs to the business objective logic to generate modified financial data. The logic of the business objective may also be manipulated to provide modified logic. The modified financial data, and optionally the modified logic, are then input into an optimizer component for determining multiple portfolios for end products that, if built, would consume excess inventory.

Abstract: A value model that can be used to value an enterprise function is provided. The value model includes one or more levels of enterprise function nodes that are related to each other and/or a bottom level of driver metric nodes, such as driver metric nodes in a value driver graph. The modification to one or more enterprise function nodes can be received and a value impact of the modification can be determined based on the modification and the relationships in the value model. In this manner, the value model provides an effective manner for determining a value impact on a particular value measurement that a specific enterprise function, such as an information technology solution/service, provides/is expected to provide.

Abstract: A method (and structure) for developing a distribution function for the probability of winning a bid by a seller for a product or service, using the seller's own historical data for winning bids and lost bids, includes normalizing the data for winning bids and the data for lost bids and merging the normalized data into a single set of data.

Abstract: A method (and structure) for developing a distribution function for the probability of winning a bid by a seller for a product or service, using the seller's own historical data for winning bids and lost bids, includes normalizing the data for winning bids and the data for lost bids and merging the normalized data into a single set of data.