Evolutionary software development to support organizational and business process change: a case study account

Kawalek, Peter; Leonard, Jenny

doi:10.1080/026839696345243

Cited by 12 publications

(5 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…It was proven in previous studies by Pava (1983), Trist (1981) and Dzazali et al (2009) albeit in a different knowledge domain. A social‐technical perspective has also been used to describe the organization as a composite of a social system and a technical system (Kawalek and Leonard, 1996; Cherns, 1976).…”

Section: Literature Reviewmentioning

confidence: 99%

Assessment of information security maturity

Dzazali¹,

Zolait

2012

J of Systems and Info Tech

View full text Add to dashboard Cite

PurposeThe purpose of this paper is to examine the basis factors involved in the information security management systems of Malaysian public service (MPS) organizations. Therefore, it proposes an empirical analysis which was conducted to identify the antecedents of the information security maturity (ISM) of an organization; and to clarify the relationship between ISM and the social and technical factors identified.Design/methodology/approachThis study uses quantitative approach, convenience sampling and the required data collected from 970 key players' managers in information security, in a total of 722 government agencies, through a self‐administrated survey. Research adopted the Wallace et al. process to develop and validate the study's instrument.FindingsThe paper provides empirical insights and reveals a number of underlying dimensions of social factors and one technical factor. The risk management was found to be the formal coping mechanism adopted in the MPS organizations and is the leading factor towards ISM. The social factors have the most influence on MPS organizations' ISM. Findings demonstrate that two independent variables, risk management and individual perception, discriminate between those organizations that have high and low ISM.Research limitations/implicationsThe research results may lack generalization; therefore, researchers are encouraged to test the proposed propositions further in a different context.Practical implicationsThe paper includes implications for the development of a powerful instrument in explaining the ISM. Moreover, it helps internal stakeholders of an organization to formulate a more appropriate policy or give a more effective focus on issues that are really relevant to MPS information security management.Originality/valueThis paper fulfils the identified need to explore determinants of information security maturity.

show abstract

Section: Literature Reviewmentioning

confidence: 99%

Assessment of information security maturity

Dzazali¹,

Zolait

2012

J of Systems and Info Tech

View full text Add to dashboard Cite

show abstract

“…The latter are an integral part of any organization, as users learning to use the ES results in evolving requirements (Wagner and Newell, 2007). Furthermore, organizational actors adjust their work routines, which leads to organizational transformation over time and accordingly evolving ES requirements (Kawalek and Leonard, 1996;Orlikowski, 1996). Additionally, resistance to the use of implemented software may arise (Griffiths and Light, 2009).…”

mentioning

confidence: 99%

How do Requirements Evolve over Time? A Case Study Investigating the Role of Context and Experiences in the Evolution of Enterprise Software Requirements

Schneider

Wollersheim

Krcmar

et al. 2018

Journal of Information Technology

View full text Add to dashboard Cite

In recent years, organizations have increasingly sourced cloud-based enterprise software (ES). Although comprehensively capturing organizations' requirements considerably affects the success of an ES sourcing project, little is known about how requirements evolve beyond the implementation. We conduct a longitudinal, exploratory single-case study of the life cycle of cloud-based ES in a medium-sized organization. Over 5 years, we trace the evolution of requirements throughout the ES life cycle, beginning with the initial adoption decision and ending with considerations to retire the ES. We develop a process theory that explains how requirements evolve beyond ES implementation and throughout its life cycle. We isolate nine mechanisms that explain how contextual factors and experiences are intertwined and shape the evolution of requirements. We then develop seven propositions that explain how sourcing cloud-based ES alters the mechanisms that shape the evolution of requirements. Our findings emphasize that the evolution of requirements for cloud-based ES follows similar mechanisms to that of the requirements for on-premises ES but changes how particular mechanisms manifest. Sourcing cloud-based ES changes the influence of business divisions in acquisition and configuration activities, the role of upgrade and customization procedures, and the influence of the ES' ecosystem.

show abstract

“…Today's working environments call for flexible work practices and dynamic Enterprise Resource Planning (ERP 4 ) systems in support of these practices because these systems are adaptable to environmental changes (Germonprez et al, 2007;Kawalek and Leonard, 1996;von Hippel, 2005). Developing systems that are flexible and ''easy-to-adapt'' by end users has been the focus of End-User Development (EUD), end-user programming, end-user computing, and (end-user) tailoring.…”

Section: The Need For Tailoring Business Processesmentioning

confidence: 99%

Supporting business process experts in tailoring business processes

Dorner

Yetim

Pipek

et al. 2011

Interacting with Computers

View full text Add to dashboard Cite

Supporting end users to adapt business processes is rather uncommon in the context of large Enterprise Resource Planning systems. We present our new business process modeling environment, called SiSO, that enables business process experts to model and adapt business processes. SiSO enhances the descriptions of services that are provided by Service-Oriented Architectures. These enhanced descriptions focus on organizational-specific information, which makes it easier for business process experts to understand the capabilities of services in their organizational context. The information includes descriptions of services' functions, ratings, and keywords. SiSO's graphical user interface employs the box-and-wire UI design technique to enable business process experts to model business processes in the context of Enterprise Resource Planning systems. SiSO was qualitatively evaluated with six employees of three different companies and found useful in two application fields: (a) the visualization and automation of business processes and (b) the creation of calculations using data from different systems and sources. We think that enabling business process experts to create individual business processes is an important challenge for the design of future Enterprise Resource Planning systems

show abstract

Evolutionary software development to support organizational and business process change: a case study account

Cited by 12 publications

References 10 publications

Assessment of information security maturity

Assessment of information security maturity

How do Requirements Evolve over Time? A Case Study Investigating the Role of Context and Experiences in the Evolution of Enterprise Software Requirements

Supporting business process experts in tailoring business processes

Contact Info

Product

Resources

About