Abstract: A method of managing software design specifications with functional rule versioning may include storing references to a plurality of software components in a database system, and storing references to a plurality of functional rules in the database system. In some embodiments, the functional rules may define behaviors that may be assigned to the plurality of software components. The method may also include receiving a selection of one or more software components from the plurality of software components. The one or more software components may define a software product. The method may additionally include receiving assignments of the plurality of functional rules to the one or more software components, and providing an interface for navigating through the one or more software components and editing the assignments.

Abstract: A system is provided that manages consigned inventory procurement. The system generates an agreement including consignment terms and purchasing terms. The system further generates a consignment order for consigned inventory items, where the consignment order references the agreement. The system further generates a receipt in response to receiving the consigned inventory items, where the receipt references the consignment order. The system further generates a consumption advice in response to a consumption of a consigned inventory item, where the consumption advice references the agreement and the receipt. The system further sends the consumption advice to a supplier. The system further generates an invoice for the consigned inventory item in response to receiving a supplier invoice from the supplier, where the invoice references the consumption advice. The system further generates a payment for the consigned inventory item in response to a receipt of the invoice, where the payment references the invoice.

Abstract: A method of managing software design specifications with functional rule versioning may include storing references to a plurality of software components in a database system, and storing references to a plurality of functional rules in the database system. In some embodiments, the functional rules may define behaviors that may be assigned to the plurality of software components. The method may also include receiving a selection of one or more software components from the plurality of software components. The one or more software components may define a software product. The method may additionally include receiving assignments of the plurality of functional rules to the one or more software components, and providing an interface for navigating through the one or more software components and editing the assignments.

Abstract: A rules engine uses a set of sequenced rules in determining which rule to apply when assigning buyers in a procurement organization to requisitions submitted to the procurement organization. The rules are user-configurable to provide flexible reconfiguration of how the rules engine determines buyer assignments. Attributes of the requisitions may be utilized to determine the appropriate buyers by comparing the attributes with the rules. Sequencing of the rules allows for prioritization of the rules in instances where multiple rules may be applicable to a received requisition. Updates to a rule set can be tested on sample requisitions to allow users to see the results of the updates.