Customer configuration updating
Response success and error codes Each response comes with an HTTP status code that indicates success or failure and additional debugging information. This call requires an ETag for concurrency detection.
This method is developed by researchers of the Utrecht University.This article is about the delivery phase of the CCU method.Delivery concerns the process which starts at the moment a product is finished until the actual shipping of the product to the customer.A software vendor develops and releases a software product and afterwards it has to be transported to the customer. This process is highly complex because the vendor often has to deal with a product which has multiple versions, variable features, dependency on external products, and different kinds of distribution options.The CCU method helps the software vendor in structuring this process.In figure 2, the process-data diagram of the delivery phase within CCU is depicted. On the left side you can see the meta-process model and on the right side the meta-data model.
The two models are linked to each other by the relationships visualized as dotted lines.
So in this case a package just has to contain 1 software package.
On the left side of the picture the process-data model is depicted.
Each of these items will have a status—Learn More, Train, or Configure—which will determine what actions a user admin can take.
When a user admin clicks on an item with a Configure status, they are brought to the Configure Tab.
The meta-data model (right side) shows the concepts involved in the process and how the concepts are related to each other.