The development of e-government systems in South Africa has raised major concerns when coming to the systems development methodology used. Through the literature review conducted and the data collected, the study has indicated that there is lack of uniformity, isolated cost, models for choosing project teams and the overall control of the whole process of e-government systems development. As a result, this research investigates the use of systems development methodologies in the development of e-government systems. The study followed the qualitative research method; interviews were conducted in four case studies involved in the development of e-government systems. The collected data were then analysed using a software analytical tool called Atlas ti. 6.1. Subsequently a cross-case analysis was performed on the four case studies. The research findings of this study indicated that the appropriate use of systems development methodologies in the development of e-government systems helps improve the quality of e-government systems, reduces development costs, and also makes the development process effective and efficient. Based on the information gathered from the four case studies, developers in government find it difficult to select a suitable systems development methodology to use when developing e-government systems. Therefore the study proposes a conceptual framework that can be used to select the appropriate systems development methodology when developing e-government systems. This framework is made up of characteristics of e-government systems and different types of systems development methodologies. / MSc (Computer Sciences), North-West University, Potchefstroom Campus, 2014

The development of e-government systems in South Africa has raised major concerns when coming to the systems development methodology used. Through the literature review conducted and the data collected, the study has indicated that there is lack of uniformity, isolated cost, models for choosing project teams and the overall control of the whole process of e-government systems development. As a result, this research investigates the use of systems development methodologies in the development of e-government systems. The study followed the qualitative research method; interviews were conducted in four case studies involved in the development of e-government systems. The collected data were then analysed using a software analytical tool called Atlas ti. 6.1. Subsequently a cross-case analysis was performed on the four case studies. The research findings of this study indicated that the appropriate use of systems development methodologies in the development of e-government systems helps improve the quality of e-government systems, reduces development costs, and also makes the development process effective and efficient. Based on the information gathered from the four case studies, developers in government find it difficult to select a suitable systems development methodology to use when developing e-government systems. Therefore the study proposes a conceptual framework that can be used to select the appropriate systems development methodology when developing e-government systems. This framework is made up of characteristics of e-government systems and different types of systems development methodologies. / MSc (Computer Sciences), North-West University, Potchefstroom Campus, 2014

According to recent surveys on the use of systems development methodologies, many organizations claim that they are adapting systems development methodologies (Hardy et al. 1995; Russo et al. 1996; Fitzgerald, 1998). The purpose of this dissertation is to investigate the adaptation of systems development methodologies in South Africa. This problem was investigated by addressing the following research questions: • What are the perceptions of system developers regarding systems development methodologies? • Why do system developers adapt system development methodologies? • How do they adapt the methodologies? • Is there a difference in the quality of the systems which are developed with these adapted systems development methodologies opposed to those systems which are developed according to a specific formalised methodology? In this dissertation, interpretive case studies have been used to add to the researcher's knowledge concerning how and why systems development methodologies in South Africa are adapted. Qualitative interviewing was used as a data collection method. All interviews were recorded and transcribed. The next step was to analyse the transcribed data. In this study, content analysis with cross-case analysis was used. The findings obtained were confirmed by making use of triangulation and member checking. The results indicated that although the use of systems development methodologies is mandatory in organizations, it is not enforced by senior employees. Organizations use multiple systems development methodologies. Systems development methodologies are adapted due to several reasons, i.e. financial gains that is obtained, the lack of knowledge, time limitations, the fact that methodologies are not universally applicable, etc. Systems development methodologies are statically and dynamically adapted by adding and removing steps. The combination of methodologies and switching between methodologies also occur. The results indicate that developers realize that formal systems development methodologies produce systems of a higher quality. However, because it is so time-consuming, they are prepared to accept a lower quality system in order to gain a faster delivery time. / Thesis (M.Sc. (Computer Science))--North-West University, Potchefstroom Campus, 2007.

Thesis (M.Sc. (Computer Science))--North-West University, Potchefstroom Campus, 2007.

The aim of this research is to investigate the relationship between organizational and national culture and the use and effectiveness of systems development methodologies. Various different aspects of both culture and systems development methodologies are analysed. The first aspect studied is the state of systems development methodology use in South Africa. The results indicate that 74% of the organizations that participated in this study use a systems development methodology. Relationships between horizontal use of systems development methodologies and the success of the IS system and the success of the development process are also found. This relationship shows that when the systems development methodology knowledge is used in a bigger proportion of projects and by a bigger proportion of people, then both the development process and the IS system will be more successful. A relationship is also found that exists between organizational culture and system development methodologies. Organizations with a more hierarchical culture have been using SDMs longer than other organizational cultures. Relationships between national culture and systems development methodologies are also studied. The results show that when people prefer to work in a group (low individualism), the systems development methodology knowledge will be used more horizontally in the organization. The results also show relationships between the success of the IS system, the success of development process and the national and organizational cultures. When managers involve people at lower levels in the organizations in the decision making process, the developed IS system is more successful. The results show that organizations with a more developmental culture will have a more successful development system. The more an organization have a rational culture the more successful the IS system is perceived to be. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2012.

The aim of this research is to investigate the relationship between organizational and national culture and the use and effectiveness of systems development methodologies. Various different aspects of both culture and systems development methodologies are analysed. The first aspect studied is the state of systems development methodology use in South Africa. The results indicate that 74% of the organizations that participated in this study use a systems development methodology. Relationships between horizontal use of systems development methodologies and the success of the IS system and the success of the development process are also found. This relationship shows that when the systems development methodology knowledge is used in a bigger proportion of projects and by a bigger proportion of people, then both the development process and the IS system will be more successful. A relationship is also found that exists between organizational culture and system development methodologies. Organizations with a more hierarchical culture have been using SDMs longer than other organizational cultures. Relationships between national culture and systems development methodologies are also studied. The results show that when people prefer to work in a group (low individualism), the systems development methodology knowledge will be used more horizontally in the organization. The results also show relationships between the success of the IS system, the success of development process and the national and organizational cultures. When managers involve people at lower levels in the organizations in the decision making process, the developed IS system is more successful. The results show that organizations with a more developmental culture will have a more successful development system. The more an organization have a rational culture the more successful the IS system is perceived to be. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2012.

According to recent surveys on the use of systems development methodologies, many organizations claim that they are adapting systems development methodologies (Hardy et al. 1995; Russo et al. 1996; Fitzgerald, 1998). The purpose of this dissertation is to investigate the adaptation of systems development methodologies in South Africa. This problem was investigated by addressing the following research questions: • What are the perceptions of system developers regarding systems development methodologies? • Why do system developers adapt system development methodologies? • How do they adapt the methodologies? • Is there a difference in the quality of the systems which are developed with these adapted systems development methodologies opposed to those systems which are developed according to a specific formalised methodology? In this dissertation, interpretive case studies have been used to add to the researcher's knowledge concerning how and why systems development methodologies in South Africa are adapted. Qualitative interviewing was used as a data collection method. All interviews were recorded and transcribed. The next step was to analyse the transcribed data. In this study, content analysis with cross-case analysis was used. The findings obtained were confirmed by making use of triangulation and member checking. The results indicated that although the use of systems development methodologies is mandatory in organizations, it is not enforced by senior employees. Organizations use multiple systems development methodologies. Systems development methodologies are adapted due to several reasons, i.e. financial gains that is obtained, the lack of knowledge, time limitations, the fact that methodologies are not universally applicable, etc. Systems development methodologies are statically and dynamically adapted by adding and removing steps. The combination of methodologies and switching between methodologies also occur. The results indicate that developers realize that formal systems development methodologies produce systems of a higher quality. However, because it is so time-consuming, they are prepared to accept a lower quality system in order to gain a faster delivery time. / Thesis (M.Sc. (Computer Science))--North-West University, Potchefstroom Campus, 2007.

Problem statement: There seem to be perceptual incongruence between systems development managers and developers. Research shows that while managers are more positive towards systems development methodologies, developers on the other hand seem to resist and not to use systems development methodologies in their entirety but instead adapt, tailor, modify and change them depending on the project at hand (contingent use). Systems development managers can exert power through a variety of influence bases. However, these power influences may be perceived differently by developers. While some might feel constrained, others might actually feel liberated by the existence of the same influence base. Main findings: IS managers are using systems development methodologies to gain control over team members. However, there was no clear perception on whether systems development methodologies were enslaving systems developers. This was indicated by the majority of the respondents neither agreeing nor disagreeing to that effect. The research showed that most organisations are adapting the use of systems development methodologies on a project to project basis, which is referred to as the contingent use of systems development methodologies. Research method followed: The positivistic research paradigm was used as it allowed the researcher to find out patterns and regularities between power, systems development methodologies’ use and success. A survey was conducted and a questionnaire was used for data collection purposes. Questionnaire data was analysed using IBM SPSS Statistics Version 21, Release 20.0.0 software package tools. Principal conclusion: Power is interpreted in terms of the type of power that can be exercised by IT professionals specifically IS developers and their respective managers at the workplace. The roles assumed and the different power types that may be exercised in organisations provide a link as to who has the final say when it comes to the use and success rate of systems development methodologies. The contingent use of systems development methodologies provides a form of “freedom” to systems developers. Based on the research findings, the research proposes an answer to the question – are systems development methodologies enslaving systems developers and empowering IS managers? / MSc (Computer Science), North-West University, Potchefstroom Campus, 2014

Problem statement: There seem to be perceptual incongruence between systems development managers and developers. Research shows that while managers are more positive towards systems development methodologies, developers on the other hand seem to resist and not to use systems development methodologies in their entirety but instead adapt, tailor, modify and change them depending on the project at hand (contingent use). Systems development managers can exert power through a variety of influence bases. However, these power influences may be perceived differently by developers. While some might feel constrained, others might actually feel liberated by the existence of the same influence base. Main findings: IS managers are using systems development methodologies to gain control over team members. However, there was no clear perception on whether systems development methodologies were enslaving systems developers. This was indicated by the majority of the respondents neither agreeing nor disagreeing to that effect. The research showed that most organisations are adapting the use of systems development methodologies on a project to project basis, which is referred to as the contingent use of systems development methodologies. Research method followed: The positivistic research paradigm was used as it allowed the researcher to find out patterns and regularities between power, systems development methodologies’ use and success. A survey was conducted and a questionnaire was used for data collection purposes. Questionnaire data was analysed using IBM SPSS Statistics Version 21, Release 20.0.0 software package tools. Principal conclusion: Power is interpreted in terms of the type of power that can be exercised by IT professionals specifically IS developers and their respective managers at the workplace. The roles assumed and the different power types that may be exercised in organisations provide a link as to who has the final say when it comes to the use and success rate of systems development methodologies. The contingent use of systems development methodologies provides a form of “freedom” to systems developers. Based on the research findings, the research proposes an answer to the question – are systems development methodologies enslaving systems developers and empowering IS managers? / MSc (Computer Science), North-West University, Potchefstroom Campus, 2014

在重視集體智慧、重視服務、且需要因應環境快速變遷的年代，傳統的系統開發方法論雖然有其不可磨滅的價值，但已經顯露出其不足之處。為了順應時代的潮流，方法論必須指引企業去聆聽大眾的心聲，以期確保系統提供優質的服務，方法論也必須指引資訊人員運用有異於以往的手法與步驟，與其他部門和大眾共同合作，來持續不斷地維護系統，使得系統得以注入新的生命力而不斷演進。 為了提出一套不斷吸納使用者的新需求來規劃系統演進的功能需求分析方法論，本研究以哲學詮釋學為基礎，並佐以軟體工程相關文獻，將持續吸納新需求來促進系統演進的抽象概念，化為具體可執行的步驟。本需求分析方法論是針對使用者提議的需求進行初步分析與確認，可分為兩個主要部分：需求形成流程、與衝突處理流程。需求形成流程是分析使用者所提出之功能性需求的主要方式，其中包含了提出新需求、分析新需求在商業活動與科技層次的影響、估計新需求的成本效益來決定是否實作、排序實作的優先權、並且了解新功能的釋出時間的期望。而衝突解決流程是為了解決各方人馬的歧見所造成的爭端，衝突解決的方式包含了自行協商、第三方中間人介入協調、以及高層決策小組的裁決。 為了讓企業外界的大眾提議新需求，本研究發展了一套以部落格為基礎的新需求提議工具，讓網友可在部落格上提出自己對新功能的想法。此外，為了協助企業判斷新需求是否會觸發衝突解決流程，本研究根據哲學詮釋學，將使用案例（Use cases）加以延伸修改，提出一套後設模型，並輔以知識本體，據此來提出一套規則，讓本工具能自動偵測新需求與系統既有設計之間是否有所抵觸，而規則亦可進一步應用在新需求間的衝突上。 為了初步瞭解本研究所提之方法論與工具的優缺點，本研究與中時電子報和民視購物網合作，來試用此方法論與工具。透過試用之後的訪談得知，本方法論與工具有其價值，而也獲得了不少寶貴的試用意見。最後，本研究根據試用的諸多意見，對方法論與工具的改善上，提出了具體的改良作法與方向。 / Nowadays, companies have to respect collective knowledge and improve service quality for adapt their rapidly changing environment. Traditional systems development methodologies may be still valuable but have shortcomings. To accommodate customer-driven trend, new methodologies must guide enterprises to listen to customers for ensuring high-quality system services. New methodologies also have to guide developers to carry out cross-department and customer-centered collaboration in new ways for maintaining systems cyclically. This research proposes a user requirements analysis methodology according on philosophical hermeneutics and software engineering literature. The proposed methodology includes requirements formation and conflict resolution. Requirements formation process involves new user requirement proposition, commercial and technical impact analysis, cost benefit estimation, coding prioritization, and new version release scheduling. Conflict resolution process involves negotiation, mediation, and arbitration. Besides the proposed methodology, this research also develops a blog-based tool for collecting user requirements on Internet. This research extends and modifies use cases diagram and use philosophical hermeneutics as a foundation to propose a meta-model. This research also proposes a set of rules for conflict detection. Base on the proposed meta-model, ontologies, and the proposed rules, the blog-based tool can automatically detect conflicts between new requirements and existing design. These proposed rules also can apply to detect conflicts among new requirements. An online newspaper company and an online shopping mall try to use this methodology and the blog-based tool. In the interviews, they confirm this methodology’s and tool’s values and give several suggestions for improving the methodology and the tool. Finally, this research discusses the improvements and future research directions according to these suggestions.