7
Views
5
CrossRef citations to date
0
Altmetric
Technical Note

Costing communication standards in information systems using a minimum cut approach

Pages 426-431 | Received 01 May 2002, Accepted 01 Nov 2002, Published online: 21 Dec 2017
 

Abstract

On a very abstract level, an information system consists of a set of system elements which communicate with each other. Communication is an unproductive operation, so the time needed to communicate data should be kept as short as possible and, to put it in monetary terms, the opportunity costs for communication should be kept small. Now, communicating data is more than just transmitting it; it consists in large parts of converting data structures that are used by one system element into data structures that are used by another system element. Such conversion can be avoided, if the system elements, use a common standard of data structures. Since establishing a standard at a system element incurs standardization costs, a decision-maker has to check, if the cost savings gained by standardized communication outweigh the costs for installing the standard. In a recent paper by Buxmann et al1, it is claimed that this so-called standardization problem is an NP-hard optimization problem without giving a formal proof for it. We will demonstrate that this claim is not true, but in fact the standardization problem can be solved in polynomial time by solving a minimum cut problem.

Reprints and Corporate Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

To request a reprint or corporate permissions for this article, please click on the relevant link below:

Academic Permissions

Please note: Selecting permissions does not provide access to the full text of the article, please see our help page How do I view content?

Obtain permissions instantly via Rightslink by clicking on the button below:

If you are unable to obtain permissions via Rightslink, please complete and submit this Permissions form. For more information, please visit our Permissions help page.