As contemporary organizations experience an increasing pressure to change, organizational agility, i.e. the ability to sense and respond continuously to changes in the environment, is required. Enterprise Architecture (EA) has been proposed as an architectural and organizational approach in order to meet this challenge. In this exploratory study we discuss the usefulness of the approach, building on the contribution of Ross et al. [26]. Our research question is: to what degree can medium sized organizations use EA to build organizational agility?Our empirical evidence is a case study with four medium sized Norwegian organizations. We find that the adoption of EA principles is pragmatic, and that maturity levels are generally low. We do, however, find reasonable support for the assumption that EA is actually increasing organizational agility, in particular the capability to respond to external changes. We identify two paths from EA to organizational agility.

Requests for changes to software systems have a potential damaging effect on software projects and the life span of software. Changes can not be avoided since it seems impossible to produce complete, correct and stable requirements. Late requests for deep, structural software changes are particularly harmful.We present an approach for early detection of evolutionary changes of software requirements, especially deep structural changes that have implications for the software architecture. The approach is based on using business process modelling (BPM) as a tool to increase the level of understanding of the problem domain in early stages. This enables the system stakeholders to identify and prevent certain types of changes earlier in the development process than what is usual with most commonly used development methods.We present a possible taxonomy of changes to help managing the different types of changes that are most important for our purpose.

Purpose The purpose of this paper is to contribute to the ongoing debate on the appropriate organizational design for the process management implementation. Using the lens of institutional theory, the paper discusses how organizations adapt to a required implementation of a process view alongside their organizational structures. Design/methodology/approach The study is designed as a single case study of a Norwegian shipping company. On the one hand, shipping companies are traditionally managed by functions due to the specifics of maritime operations and high safety-related risks of the work. On the other hand, the rising demands of regulatory bodies and customers within the offshore logistics are calling for implementation of a process view within the organizations, which implies management by processes. Findings The study analyses conflicting requirements of the institutional environment influencing organizational structure and how these conflicts are addressed by the company. Besides, it describes the decoupling mechanism the company uses to balance between such requirements and adapt to the changes of the institutional pressures. Originality/value The study introduces a situational-based organizational structure as an alternative for both process and vertical views implementation within the companies operating in the highly demanding institutional environments.

tion, intended for small, hand-held mobile computers is addressed. The structuring of capture, communication and processing of changes, adaption, and control actions is based On the concept of quality Of service (&os). Lightweight solutions are important, due to the restricted resources of small hand-held mobile computersIntegrated resource management for small, handheld mobile computers is addrescied. The apporach is based on the concept of quality of service (&os). The focus is o n provindrng for detectLon and adaption, not on transparency.The large and rapid changes in the services and resources available to mobile computers cannot be made transparent, neither to the user nor to system or application software. On the contrary, detection of changes and adaptation to new service and resource levels is necessary in all software layers in order to maximise the potential of the machine.

No abstract