A tool for IT process construction
Introduction
IT processes deliver to the enterprise the required information by using IT resources [1]. Control objectives for information and related technology (COBIT) [1] has identified 34 IT processes that are generally used (e.g. manage service desk and incidents, manage problems, manage quality – please refer to [1] for the complete list). Business processes in organisations (as well as IT processes) are defined by the following interrelated factors: organisational structure, culture, technology, and people [2], which together constitute a complex sociological and technological system. Practice shows that it is impossible to define universal IT processes suitable for any organisation. ITIL, the world-wide de facto standard in IT service management, states that every activity should not be cast in stone, since methods and requirements differ from organisation to organisation [3]. Therefore, IT processes should be constructed that provide acceptable service in a particular organisation and at the same time make optimal use of available resources.
When designing IT processes, several standards, guidelines, and best practices may be consulted depending on the environment (e.g. COBIT, ITIL, ISO/IEC 20,000). Although these documents describe IT processes from different points of view, none of them explicitly defines which IT process elements are suitable for the organisations according to their socio-technical characteristics. In addition, the tacit knowledge plays an important role in this activity. Many important decisions about the structure of an IT process are made according to the process consultant’s subjective opinion. This field lacks a scientifically based systematic tool for IT process construction. Hence, the goal of our research is to develop a tool for IT process construction and test it in real organisations.
The tool presented in this paper is called IT Process Engineering (ITPE). ITPE is a systematic, scientifically-based tool that constructs organisation-specific IT processes according to the organisation’s socio-technical characteristics. ITPE uses Holistic IT processes (HITP) as a starting point (in Fig. 1 an excerpt of HITP is presented in the upper left corner – marked with Label A), i.e. IT processes that include IT process elements (e.g. subprocesses, activities, applications, roles, and artifacts) identified in literature or previously implemented in organisations. We typically create HITPs by examination of different standards and best practices (e.g. ITIL, COBIT). Based on the analysis of the technical and social characteristics of a particular organisation, ITPE than tailors HITPs into organisation-specific IT processes. The conditions that define which HITP elements to consider according to the organisation’s socio-technical characteristics are important components of HITPs (marked with black diamond in HITP – Fig. 1, Label A). The results of ITPE are presented as: (1) an activity diagram in which each activity suggests an IT process element to implement or improve (Fig. 1, Label B); (2) likelihood of unsuccessful implementation of the suggested IT process elements (Fig. 1, Labels C1 and C2); and (3) suggested scenarios for reducing it (Fig. 1, Labels D1 and D2). In order to apply ITPE in an organisation for a particular IT process, two activities must be performed: (1) identification of organisation’s socio-technical characteristics, which is done by interviews and questionnaires, and (2) generation of ITPE results by the use of our tool. The results of ITPE serve as a guideline for improving the IT process under consideration (Fig. 1).
The paper is organised as follows. In Section 2, related work is presented. Section 3 introduces the background and theoretical foundations of our research. The core of the paper consists of Section 4, where the details of ITPE are introduced, and Section 5, where the validity of ITPE is tested in three real organisations for two selected IT processes. Concluding remarks are presented in Section 6.
Section snippets
Related work
In order to develop the ITPE an extensive literature review of the fields referring to the design/improvement of business processes was performed. These fields can roughly be divided into two groups: group one dealing with the design/improvement of an arbitrary business process, and group two dealing with the design/improvement of a software development process.
O’Neil and Sohal [4] state that many authors refer to design/improvement of an arbitrary business process with variations on terms:
Background and theoretical foundations
ITPE is based on PCA. In order to understand ITPE, the PCA and the COBIT’s maturity model are briefly introduced (Subsections 3.1 Process configuration approach (PCA), 3.2 COBIT’s maturity model).
IT process engineering (ITPE)
In the same way different ME approaches construct tailored software development methods by considering different characteristics (i.e. project, organisation, SW development team characteristics), ITPE creates organisation-specific IT processes according to the organisation’s socio-technical characteristics. In order to understand the details of ITPE a running example is presented in Fig. 1.
ITPE is based on PCA, presented in Subsection 3.1. Thus, established ME principles are used for IT process
Case studies
In order to test ITPE in real organisations we employed case studies combined with direct observation and interviews [42].
Conclusion and further work
ITPE introduces scientific rigour to the field of IT process construction and provides a valid reference for IT process consultants, IT managers, and IT process owners. The ITPE results provide useful information for IT process improvement to the organisation.
A successful application of ME principles in the field of IT process construction is another important result relevant to the field of ME. It demonstrates that established ME principles can also be applied in research fields other than
Acknowledgement
This research has been supported by the Slovene Research Agency ARRS within the research program P2-0359.
References (43)
- et al.
Business process reengineering: a review of recent literature
Technovation
(1999) - et al.
A simulation-based decision support system for business process planning
Fuzzy Sets and Systems
(2002) - et al.
A modelling technique for re-engineering business processes controlled by ISO 9001
Computers in Industry
(2002) - et al.
Business process engineering with partial models
Computers in Industry
(1995) - et al.
Managing re-engineering with the CIMOSA architectural framework
Computers in Industry
(1995) Method engineering: engineering of information systems development methods and tools
Information and Software Technology
(1996)- et al.
Method configuration: adapting to situational characteristics while creating reusable assets
Information and Software Technology
(2004) - et al.
Practice-driven approach for creating project-specific software development methods
Information and Software Technology
(2007) - et al.
A configurable reference modelling language
Information Systems
(2007) - et al.
Software quality and IS project performance improvements from software development process maturity and IS implementation strategies
Journal of Systems and Software
(2007)
Organizational innovation adoption – a multi-level framework of determinants and opportunities for future research
Journal of Business Research
IT and organizational change: where does BPR fit In?
ARIS – Business Process Modeling
Process construction and customization
Journal of Universal Computer Science
Software development method tailoring at Motorola
Communications of the ACM
Process Tailoring and the Software Capability Maturity Model
A comprehensive view of process engineering
Cited by (9)
Knowledge management in requirement elicitation: Situational methods view
2018, Computer Standards and InterfacesCitation Excerpt :The question is how one can handle the method requirements process [14]. Method requirements are often formulated based on interviews with project members [22,23]. In this respect, one of the major constraints is the fact that these requirements are often vague, poorly understood, and difficult to express - which is true for requirements in general - and also they affect the methods that are used within system development projects [11].
Implementing information security best practices on software lifecycle processes: The ISO/IEC 15504 Security Extension
2015, Computers and SecurityCitation Excerpt :In order to guide software organizations involved in process improvement programmes according to ISO/IEC 15504 in the implementation of the ISO/IEC 27000 standard, even obtaining a certification against ISO/IEC 27001 (ISO/IEC 2013a), it is necessary to adequately select and efficiently implement the appropriate security controls between all the controls provided by the ISO/IEC 27002 standard (ISO/IEC 2013b). During the last years, several initiatives relating quality and security best practices have emerged (Boynton, 2007; Da Veiga and Eloff, 2010; Knapp et al., 2009; Lepmets et al., 2012; Xiao-yan et al., 2011; Zvanut and Bajec, 2010). Barafort et al. (2006) developed a process reference model and a process implementation model which provide a framework for assessing and increasing process capability and organisational maturity in the field information security.
MC Sandbox: Devising a tool for method-user-centered method configuration
1970, Information and Software TechnologyCitation Excerpt :According to Henderson-Sellers and Ralyté [13] this is still a major challenge when working with situational methods: how to handle the method requirements process? Method requirements are often formulated based on interviews with project members [14,15]. The method engineer later uses these requirements to define a situational method, which is introduced to the project team.
Towards a method engineering approach for business process reengineering
2016, IET SoftwareOutsourcing as an Economic Development Tool in Transition Economies: Scattered Global Software Development
2015, Information Technology for DevelopmentMIN-ITs: A framework for integration of IT management standards in mature environments
2014, International Journal of Software Engineering and Knowledge Engineering
- 1
Tel.: +386 14768 814; fax: +386 14768 705.