scholarly journals Adapting Agile DevOps for Strategic Information Systems Development: The Future of IS Development Methodologies

2019 ◽  
Author(s):  
FRANCIS KAGAI
Keyword(s):  
Information Systems ◽  
Systems Development ◽  
Adverse Impact ◽  
Information Systems Development ◽  
Strategic Information ◽  
Technological Environment ◽  
Strategic Information Systems ◽  
The Future ◽  
Is Development ◽  
Definition Of

Despite continued evolution of information systems methodologies for more than three decades, the rates of software rejection and failure are still high. This paper investigates the technological environment as a major cause of such disruptions. Additionally, the paper evaluates Agile and DevOps as the remedial methodologies for managing the adverse impact of technological disruptions. The main findings affirm both Agile and DevOps as methodologies that emanated from improvements or re-engineering of earlier methodologies. Further findings discern most methodologies; including agile and DevOps; as not strategically focused but appraise DevOps as the most progressive methodology towards this respect. Rather than re-invent the wheel and come up with a new methodology, a framework that aligns DevOps for use in strategic information systems development is proposed. Besides, a more realistic definition of operations is postulated to bolster the alignment.

scholarly journals Adapting Agile DevOps for Strategic Information Systems Development: The Future of IS Development Methodologies

2019 ◽  
Author(s):  
FRANCIS KAGAI
Keyword(s):  
Information Systems ◽  
Systems Development ◽  
Adverse Impact ◽  
Information Systems Development ◽  
Strategic Information ◽  
Technological Environment ◽  
Strategic Information Systems ◽  
The Future ◽  
Is Development ◽  
Definition Of

Despite continued evolution of information systems methodologies for more than three decades, the rates of software rejection and failure are still high. This paper investigates the technological environment as a major cause of such disruptions. Additionally, the paper evaluates Agile and DevOps as the remedial methodologies for managing the adverse impact of technological disruptions. The main findings affirm both Agile and DevOps as methodologies that emanated from improvements or re-engineering of earlier methodologies. Further findings discern most methodologies; including agile and DevOps; as not strategically focused but appraise DevOps as the most progressive methodology towards this respect. Rather than re-invent the wheel and come up with a new methodology, a framework that aligns DevOps for use in strategic information systems development is proposed. Besides, a more realistic definition of operations is postulated to bolster the alignment.

scholarly journals ISMS-Final TechRxiv.pdf

2019 ◽  
Author(s):  
FRANCIS KAGAI
Keyword(s):  
Information Systems ◽  
Systems Development ◽  
Adverse Impact ◽  
Information Systems Development ◽  
Strategic Information ◽  
Technological Environment ◽  
Strategic Information Systems ◽  
Definition Of

Despite continued evolution of information systems methodologies for more than three decades, the rates of software rejection and failure are still high. This paper investigates the technological environment as a major cause of such disruptions. Additionally, the paper evaluates Agile and DevOps as the remedial methodologies for managing the adverse impact of technological disruptions. The main findings affirm both Agile and DevOps as methodologies that emanated from improvements or re-engineering of earlier methodologies. Further findings discern most methodologies; including agile and DevOps; as not strategically focused but appraise DevOps as the most progressive methodology towards this respect. Rather than re-invent the wheel and come up with a new methodology, a framework that aligns DevOps for use in strategic information systems development is proposed. Besides, a more realistic definition of operations is postulated to bolster the alignment.

scholarly journals Selecting a methodology for business information systems development: Decision model and tool support

2012 ◽  
Vol 9 (1) ◽  
pp. 135-164 ◽  
Author(s):  
Damjan Vavpotic ◽  
Olegas Vasilecas
Keyword(s):  
Information Systems ◽  
Decision Model ◽  
Systems Development ◽  
Development Project ◽  
Information Systems Development ◽  
Tool Support ◽  
Positive Contribution ◽  
Project Organization ◽  
Business Information ◽  
Is Development

The paper presents a decision model and a tool that helps to find an information systems development methodology (ISDM) for a computer-based business information system (IS) that is suitable to a certain IS development project or an organization dealing with IS development. The intention of the model is not only to suggest a certain ISDM, but also to propose the properties an ISDM should have to suite the project or the organization. It is designed in a way that facilitates experimentation with different project, organization and ISDM properties. Based on the model we created a tool that has been applied on several cases in which we validated the correctness of its recommendations and established that it can have a significant positive contribution in the process of ISDM selection and in the process of improvement of existing ISDM.

Security Over the Information Systems Development Cycle

2011 ◽  
pp. 113-154
Author(s):  
C. Blanco ◽  
D. Rosado ◽  
C. Gutiérrez ◽  
A. Rodríguez ◽  
D. Mellado ◽  
...  
Keyword(s):  
Information Systems ◽  
Software Engineering ◽  
Systems Development ◽  
Information Systems Development ◽  
Security Engineering ◽  
Secure Systems ◽  
Development Stages ◽  
Access Control Policies ◽  
Main Components ◽  
Definition Of

Information security is currently considered to be a crucial aspect of systems development. However it has traditionally been considered during the final stages of development, once the main components of the system have been developed and therefore provides solutions which are inappropriate for security integration. Software engineering has traditionally been separated from security engineering, and security issues have not usually been included in software engineering processes, activities, techniques, models, and so on. Furthermore, security engineering has not been aligned with information systems, and has focused rather on the definition of protocols, cryptographic algorithms, access control policies, etc. However, the scientific community is beginning to realize the importance of aligning software engineering and security engineering in order to develop more secure systems. Security in software engineering is a branch of research in which many contributions dealing with security integration from the early development stages have recently appeared. This chapter discusses some of the most interesting contributions in this area, and also provides a summary of our contributions through the development of various research lines dealing with different strategies to integrate security into information systems development as early in the development stages as is possible.

Outlining organisational failure in information systems development

2003 ◽  
Vol 12 (4) ◽  
pp. 319-327 ◽  
Author(s):  
Markos Goulielmos
Keyword(s):  
Information Systems ◽  
Development Process ◽  
Systems Development ◽  
Organisational Learning ◽  
Information Systems Development ◽  
Diagnostic Model ◽  
Learning From Failure ◽  
Research Findings ◽  
Is Development

Defines the concept of “organisational failure” in information systems (IS) development, and proposes a diagnostic model drawn from research done into IS consultancy firms that develop systems using a variety of methodologies. The research involved a qualitative study aimed at the nature of the development process and the role of organisational issues in this process. The model’s elements and relationships were determined by the research findings. Presents two cases of failure that show how IS failure is rooted in organisational pathology and examine existing failure concepts. The concept and model proposed can be used by practitioners and management before and during a project for diagnosing organisational failure before it interferes with IS development and afterwards for extracting deeper rooted organisational learning from failure.

Ontology-Driven Method Engineering for Information Systems Development

2011 ◽  
pp. 174-217 ◽  
Author(s):  
Roland Holten ◽  
Alexander Dreiling ◽  
Jörg Becker
Keyword(s):  
Information Systems ◽  
Systems Development ◽  
Engineering Method ◽  
Information Systems Development ◽  
Development Projects ◽  
Common Language ◽  
Method Engineering ◽  
Changing Environments ◽  
Communication Processes ◽  
Is Development

Information systems development has to deal with evolving technologies and changing environments. Therefore, the engineering of methods as the problem of creating suitable instruments for new situations is critical to information systems development. The failure of IS development projects shows that method engineering is an open field. The question is if and how research on ontology can contribute to overcome the current situation. We show, based on linguistic and philosophical findings, how ontology can be used as linchpin in method engineering. We found that the language critique approach of Kamlah and Lorenzen (1984) provides the means to create ontologies by linguistic actions and that ontologies are always related to language communities sharing the knowledge of using a common language in communication processes. We present an ontology-driven engineering method for information systems development. Our method helps to create required language constructs to handle new situations. The ontology-driven engineering method is demonstrated using an elaborate example case.

Ethics Authenticity and Emancipation in Information Systems Development

2011 ◽  
pp. 249-254 ◽  
Author(s):  
Stephen K. Probert
Keyword(s):  
Information Systems ◽  
Developed Countries ◽  
Systems Development ◽  
Information Systems Development ◽  
Practical Action ◽  
Ethical Codes ◽  
The World ◽  
Is Professionals ◽  
Is Development ◽  
Development Methods

This chapter describes research in progress on the philosophical concept of authenticity – used as a framing device for providing an interpretation of aspects of both ethical and practical action on the part of information systems (IS) professionals. Ethical codes and prescriptive IS development methods for IS professionals can be found in most developed countries in the world. Here it is argued that ethical codes and IS methods may be of limited value in IS work. One key problem here is that IS analysts and designers have to intervene in organisations (and thereby intervene in the lives of the members of those organisations). It is argued that an important issue for IS research is whether they choose to do so in (what will be characterised as) an authentic manner, rather than doing so in sincere adherence with either a code of professional ethics or with a series of methodological precepts.

Sign in / Sign up

Export Citation Format

Share Document