You have an XQuery automation plugin that performs several interactions with OSM, including searching for orders, getting detailed order information based on search results, and deciding whether to suspend those orders or not. What interface would you suggest to be used by this plugin in order to perform these interactions?
You implement a dependency between two functions in a product specification. What is the default configuration you expect in this dependency?
You have a cartridge that defines three stages of decomposition. The first stage contains order components that represent functions, the second stage contains order components that represent target systems, and the third stage contains order components that represent granularities. You want to define decomposition rules that always apply the same granularity to a function, independent of the target system that this function is communicating to. How would you design these decomposition rules such that it is easy to maintain them in the future evolutions of your system topology?
Which two pieces of information must be retrieved from the order items of an incoming order to create a follow-on order dependency?
You are working with an architecture that involves multiple billing systems. Each billing system returns its own set of external fulfillment states that you want to map to a smaller set of mapped fulfillment states defined in your cartridge. Identify two ways to implement this.
One of your clients requirements involves enrichment of an order received from a CRM system with a customer geographic region that can be retrieved by using a web service interface. Considering that the order cannot be created without this information, which development approach would you propose to meet this requirement?
