Abstract
Information system change is concerned with deliberate modifications to an organization's technical and organizational subsystems that deal with information. Changes result in adjustments being made to the configuration of information systems that could have an impact on the operations of those systems. This paper examines the problem of interference between old configuration activities, new configuration activities and reconfiguration activities that occur due to overlapping modes. The paper proposes a novel form of depicting and solving the problem based on a flow-based conceptualization in which a configuration can be viewed as a system of flow systems organized architecturally, described by their internal flows, and connected by external flows and triggering. This method of diagramming is applied to a complex case study involving the reconfiguration of an office workflow for order processing described in BPMN. The diagrams resulting from this method and the BPMN diagrams are then examined side by side. Accordingly, the conclusion is that a new high-level representation seems more systematic as a foundation for building a conceptual schema of business processes.
Highlights
The ancient Greek philosopher Heraclitus is quoted as saying, “Everything changes and nothing stands still.” The phenomenon of change applies to organizations and their information systems
This paper has applied an alternative representation of workflows to the problem of dynamic reconfiguration in the context of business processes
A new solution to the problem is not introduced; rather, the paper proposes a novel form of depicting the problem and its solution
Summary
The ancient Greek philosopher Heraclitus is quoted as saying, “Everything changes and nothing stands still.” The phenomenon of change applies to organizations and their information systems. The phenomenon of change applies to organizations and their information systems. An organization must make frequent changes to its IS in order to update hardware and software components, fix software flaws and other errors, address security threats, and adapt to changing business objectives. These constant changes result in adjustments being made to the configuration of IS; they could have an impact on systems’ operations. Software configuration management is concerned with assembling software applications systems from component parts with a focus more on change management [5]. The configuration specification determines aspects that may vary when the system is reconfigured
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
