No description available.

Faculty of Information Systems School of Economic and Business Sciences 9406128v georgia.sirinidis@fnbcorporate.co.za / Interpersonal Conflict is a neglected topic in Information System Development (ISD). While deemed important, few ISD studies have examined interpersonal conflict, the management of this conflict, or the impact this conflict has on project outcomes. Research in this field has revealed that conflict between different user groups within the systems development team is considered to be a significant threat to the success of a project. Failed systems have been attributed to resistance to system change, political issues that arise as a result of the system change and poor qua lity of teamwork between users and technical staff, analysts, programmers and other IS professionals and cultural differences. Better methods of systems analysis and design are thus needed to ensure appropriate, feasible and acceptable programs and applications and it is therefore with this intention, that this dissertation is submitted: to consider organisational behavioural means, in particular the importance of negotiating within the Systems Development process, to improve systems development. There were multiple objectives to this dissertation. These were: · to investigate whether system development is currently experienced as a process of conflict · to ascertain which roles experience a greater degree of conflict · to ascertain which systems development life cycle (SDLC) and which methodologies experience a greater degree of conflict · to assess whether negotiating skills vary across the different roles within the SDLC, to assess whether negotiating skills vary across SDLC methodologies · to determine whether the interest to improve negotiating skills varies within the SDLC · to evaluate the importance attached to negotiating skills in the SDLC · to assess whether the acceptance of the proposed negotiating framework for systems development varies within the SDLC · to examine what factors play a role in the acceptance of the proposed frameworks and · to assess whether the proposed framework will improve systems delivery. ii The reach of the research was limited to organisations in Southern Africa. These organisations were either large software development houses, or small IT departments within organisations, which specialised in developing either outsourced systems or in- house systems. Selfadministered questionnaires were mailed out to system development teams in South Africa, of varying industries and a total sample of one hundred and fifty five respondents replied. A quantitative approach was adopted to analyse the data. The results of the research show that minimal conflict is currently experienced in the SDLC and respondents across all roles and methodologies feel they possess negotiation skills to handle the conflict. The majority of the sample favourably accepted the proposed framework. Some roles attached more importance to the need for negotiating skills in their line of work, and paid more attention to improving their negotiating skills than others.

This study examines how systems development operations manage the Software Development Life Cycle (SDLC) in a Low-Code Platform (LCP) and how these descriptions relate to today's SDLC standards. To investigate this, a case study for a specific LCP has been made. Semi-structured interviews have been carried out with the aim of investigating theSDLC managed in the investigated LCP. An analysis model based on ISO/IEC/IEEE12207:2017 has been used for a deductive thematic analysis. The analysis shows a great breadth regarding how system development operations can integrate an LCP into their IT infrastructure and work with it. The choice of strategy will control how the system development operation works with the SDLC for IT artifacts that are developed in theplatform. In order for the organization to be able to enjoy the benefits of the LCP, business processes need to be possible to model in the platform. Complex and extensive business rulesaffect the possibilities to model business logic through low-code in the platform. Addressing this through traditional code can increase the complexity of certain elements of the SDLC and the need for expertise, which can significantly increase resource requirements and the time required for the system development process. / Denna studie undersöker hur systemutvecklings-verksamheter hanterar SoftwareDevelopment Life Cycle (SDLC) i en Low-Code Platform (LCP) och hur dessa beskrivningarrelaterar till dagens standarder för SDLC. För att undersöka detta har en fallstudie för enspecifik LCP genomförts. Semistrukturerade intervjuer har utförts i syfte att undersöka hurolika projekt hanterat SDLC i den undersökta LCP:en. En analysmodell baserad påISO/IEC/IEEE 12207:2017 har använts för en deduktiv tematisk analys. Analysen visar på enstor bredd gällande hur systemutvecklings-verksamheter kan integrera en LCP i sinIT-infrastruktur och arbeta med denna. Valet av strategi kommer styra hursystemutvecklings-verksamheten arbetar med SDLC för IT-artefakter som utvecklas iplattformen. För att organisationen ska kunna åtnjuta fördelarna med LCP:en behöveraffärsprocesser vara möjliga att modellera i plattformen. Komplexa och omfattandeaffärsregler påverkar möjligheterna att modellera affärslogik genom low-code i plattformen.Att åtgärda detta genom traditionell kod kan öka komplexiteten i vissa moment i SDLC ochpåverka behovet av kompetens vilket avsevärt kan öka resurskrav och tidsåtgången försystemutvecklingsprocessen.

Thesis is oriented to analysis of existing solutions and making own solutions of SW mo- dules for NI VeriStand. These modules are meant to enable communications with CAN, ARINC429, RS-485, SPI and SDLC buses in scope as defined by Honeywell company. To work on base of existing solutions is highly suitable, and in case of existence of sufficient implementation no additional work is appropriate. Analysis of current state of availa- ble SW resources revealed, that sufficient components for CAN, ARINC429 and RS-485 exist, so I continued to implement only SPI and SDLC. Components are designed as NI VeriStand Custom Devices and have their own FPGA parts.

The number of vulnerable systems with exploitable security defects has increased. This led to an increase in the demand for secure software systems. Software developers lack security experiences to design and build secure software, some even believe security is not their responsibility. Despite the increased need for teaching security and secure programming, security is not well integrated into the undergraduate computing curriculum and is only offered as part of a program or as an elective course. The aim of this project is to outline the importance of incorporating security and secure programming concepts in programming courses starting from the introductory courses. By evaluating the students' security consideration and knowledge regarding software security. As a result, based on the knowledge students lack regarding software security, security and secure programming concepts are identified which need to be integrated into the programming courses.

The purpose of this dissertation is to study the application of Total Quality Management (TQM) in the Information Systems (IS) development processes. The study describes and evaluates TQM concepts and techniques in the IS development processes and interprets sub-organizational elements in the application of TQM in the public sector. This dissertation uses a multiple case study methodology to study the development processes of IS in three public agencies. This study attempts to examine what quality means across these public organizations and to discover the differences between IS development methodologies that do or do not apply TQM concepts and techniques. The late Dr. W. Edwards Deming, regarded as "father" of post war Japanese economic miracle as well as leading advocate of the TQM movement in the United States, developed a systematic approach to solving quality related problems which aims to fulfill customer expectations. His system of management is adopted as the theoretical basis to this dissertation. The "lessons learned" from these case studies, empirically and in literature, reveal multiple experiences of TQM applications to IS development processes in the public sector. / Ph. D.

Companies follow different approaches in the life cycle of software, but usually, activities are divided into different teams, the most important teams are the development team and the operations team. Often the goals of the operations team and the development team are different, which results in an escalating relationship between the two teams, and a conflict occurs between teams due to the blame of responsibility on each other, which in turn leads to long delivery periods and ineffective delivery methods. To solve these problems, the DevOps approach emerged, which is an acronym for the two words development and operations. This approach aims to align both the development team and the operations team and break the barriers between them by working as one team toward a single goal that shares everyone the responsibility. Thus, the speed of the program delivery process increases and the company provides better services to its customers. Since DevOps is a new approach and many companies tend to adopt this approach, this study aims to investigate the benefits of the DevOps approach and the challenges involved in adopting this approach. This study summarized that the adoption of DevOps approach has an impact on the companies in several aspects. The research presents the most important challenges that the DevOps attempts to overcome, DevOps tools that helps to achieve the value of DevOps, and the benefits of the DevOps approach.

DevSecOps emerged to mitigate the challenges of integrating security into DevOps. DevOps have grown tremendously, leading to difficulties in integrating security tools in its development process while maintaining speed and agility. This study aims to investigate the security tools in DevSecOps and how they have been reported in previous literature. The main objective of this study is to provide a knowledge base concerning security tools in DevSecOps that can be used to mitigate challenges regarding the selection and use of security tools in the context of DevSecOps. A systematic literature review was adopted for the research. The study collected a total of  228 studies published between 2015 and 2022; fourteen of these papers were selected to be used for data extraction after conducting a thorough review protocol. This study has identified thirteen security tool categories used or recommended to be used in DevSecOps. These tools have been structured into seven phases of the development process and five security practices. Additionally, this study has identified twelve drawbacks and sixteen recommendations concerning the use of these security tools in DevSecOps.  The security tools categories, recommendations, and drawbacks identified in this study could potentially be used to facilitate the challenges of selecting and using security tools in DevSecOps and similar methodologies that rely on automation and delivering software frequently.

With the globalization era, software companies around the world not only have to face competition in the domestic industry, as well as the subsequent challenge of large international companies. For this reason, domestic software companies must to upgrade their own software quality. Domestic government agencies and non-governmental units together promote Capability Maturity Model Integration (CMMI). Hope to improve their quality of software development process through internationalized professional evaluation. Towards the high-maturity software development process, software development process should be estimated quantitatively in CMMI Level 4. There are frequently used statistical process control (SPC) methods, including control charts, fishbone diagram, pareto charts ... and other related practices. Its goal is to maintain stability of overall software development process, so the output performance can be expected. Primitive SPC applied in manufacturing industry, successfully improving the quality of their products. But some characteristics of software, such as software development is human-intensive and innovative activities. It increases not only variability of control, but also difficulties of implementation. In this study, collate and analyze the operational framework of SPC and CMMI Level 4 through study of literature and case study with the case company-A company's practices. It contains two points, one is organization point of view, the other is methodological point of view. Organizational point of view includes stage of CMMI Level 4 and SPC implemented in the software industry, as well as how to design the organizational structure. Methodological point of view includes the steps to run SPC¡Buseful methods and tools. Methodological point of view also uses control theory to collate relevant control mechanisms. Finally, we illustrate how to integrate SPC into the company's system development life cycle. The framework can provide a reference for domestic software companies of longing for implementing CMMI Level 4 and SPC.

The quality of a product depends on the quality of the underlying process is a well known fact. Software development organizations have been struggling to decrease their cost, increase their ROI, reduce time-to-market, and enhance the quality of their products. This all depends upon the improvement in the processes they are following inside their organizations. A number of software process improvement models exist in market, e.g., CMMI, SPICE and Automotive SPICE. But before an organization can improve its development and management processes, it is very important to know whether it is following the right processes. There exist a number of software development process models, mainly categorized into Traditional and Agile, which provide the step-by-step guidance to develop and manage the software projects.The current thesis presents a study of software process improvement models in automotive industry, their weaknesses and strengths and presents a comparison of how do they relate to each other. This thesis also explores some software development models which are more famous in automotive industry, and the applicability of process improvement models in conjunction with the Agile software development models. A case study was performed at an automotive software supplier organization to investigate the experience of combining Agile practices with organization’s company-tailored software development model that was incorporating Automotive SPICE standards.