No description available.

The study analyzes that how information systems facilitate football clubs. To fulfill these purposes this study adopts a design strategy which contains theoretical and empirical parts. It gives a way how to operate and improve works to solve and avoid problems in various sectors in order to facilitate football clubs. This study chooses a suitable information system development methodology and designs a general football club information system model. In the empirical study a questionnaire survey is made to check and complete a general football club information system model. This study proves that information systems can facilitate football clubs in business processes and operations, internal communication and decision-making; furthermore, it supports football club business strategies and helps establish a powerful human resource management project. / Program: Magisterutbildning i informatik

The world we live in today demands systems that make our lives easier and help us make the right choices on time. There exists a growing need for quality products that help us in our day to day activities. Easy-to-use computer-based decision support systems apply all available and applicable data with the correct model, knowledge and skill of decision makers to support the user to choose the best solution. It is therefore important to develop decision support systems correctly to be of value to the user. Looking at other information system developments, the author tries to suggest ways to develop decision support systems. System development methodologies are investigated to determine if they are able to address the development of the very important decision support system components. Five methodologies were discussed and researched for their theoretical suitability to address the development of decision support systems. The author performed qualitative research using case studies and semi-structured interviews to assess the use or non-use of system development methodologies in the development of decision support systems in a South African context. Content and cross-case analyses were used to achieve results that are discussed to broaden the knowledge on the development of decision support systems. The author provides some explanations to why system development methodologies were not used in the development of the case studies. This research not only contributes to the academic body of knowledge about using system development methodologies in the development of decision support systems, but could also be useful to developers embarking on a new decision support system development. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2011.

The world we live in today demands systems that make our lives easier and help us make the right choices on time. There exists a growing need for quality products that help us in our day to day activities. Easy-to-use computer-based decision support systems apply all available and applicable data with the correct model, knowledge and skill of decision makers to support the user to choose the best solution. It is therefore important to develop decision support systems correctly to be of value to the user. Looking at other information system developments, the author tries to suggest ways to develop decision support systems. System development methodologies are investigated to determine if they are able to address the development of the very important decision support system components. Five methodologies were discussed and researched for their theoretical suitability to address the development of decision support systems. The author performed qualitative research using case studies and semi-structured interviews to assess the use or non-use of system development methodologies in the development of decision support systems in a South African context. Content and cross-case analyses were used to achieve results that are discussed to broaden the knowledge on the development of decision support systems. The author provides some explanations to why system development methodologies were not used in the development of the case studies. This research not only contributes to the academic body of knowledge about using system development methodologies in the development of decision support systems, but could also be useful to developers embarking on a new decision support system development. / Thesis (MSc (Computer Science))--North-West University, Potchefstroom Campus, 2011.

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.

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.

目前資訊系統之建置多為求速成而以採購所謂解決方案的套裝系統或元件拼裝為主，雖然此舉帶來軟體再用效益使建置成本降低但由於實施過程抽象化不足使得欲讓系統適應用戶環境時客製化困難且各套裝系統詞彙標準不一也造成資料整合時語意混淆，導致空有外殼讓系統與組織扞格不入而無法帶來實質效益。本研究所提之系統發展方法即是為解決上述情況以本體論為概念描述基礎分從靜態資料觀點、動態流程觀點及資訊技術觀點出發進而彙整發展具彈性與再用性之資訊系統。 本研究過程是植基於設計科學的系統發展研究方法論，將資訊系統開發流程分為五個階段，並根據設計科學的定義，驗證研究結果的四項產出：構件、模型、方法與實例，希從學術的嚴謹面提昇產出結果的品質。並藉著探討分析運用本研究之發展方法建置出的個案，其所得到之結果足以供後繼者建置或改善知識管理相關系統做參考。 / In these few decades, many organizations pursued of e-Solutions by selecting so-call off-the-shelf packages or mixed 3rd party components to promote the reusing value and reduce the cost of implementation. However, there is no single solution suitable for all types of organization and customized or hybrid system must be inevitable to face the consistency problem. We believe the proper abstraction and ontological commitment can help in these situations. From this point of view, we propose the information system development methodology which is aiming to implement the flexible and reusable ontology driven information system from the view of static domain data, dynamic workflow and abstract technology. In this study, we conduct the system development research methodology based on design science. In order to easily note, we divide the research process into five stages. According to the criteria of design science, we will examine the research results: constructs, models, methods and instantiations for consolidating the quality of research outputs. Besides, we will show the cases which are implemented by proposed methodology for further study and suggestion of improving present system development issues.

The aim of this study is to investigate whether a combination of agile system development methodologies (ASDMs) and project management methodologies (PMMs) can be used to develop a hybrid APMM that will have the ability to deliver information technology (IT) projects successfully in a constantly changing business and project environment. To achieve this objective, a literature review was conducted on the relatively well–established ASDMs by firstly defining a SDM and an ASDM. Each ASDM and its effectiveness are described, after which ASDMs in general are evaluated by considering their area of application, advantages and disadvantages. A comparison is then done of the seven different ASDMs using the four elements of an SDM (Huisman & Iivari, 2006:32) to emphasise some of the main similarities and differences amongst the different ASDMs. The seven ASDMs investigated in this study are Dynamic System Development Methodology, Scrum, Extreme Programming, Feature Driven Development, Crystal ASDMs ? Crystal Clear and Crystal Orange in particular, Adaptive Software Development and Lean Development. A literature review was also conducted on two structured and relatively well–established PMMs, PMBOK and PRINCE2, and a relatively new PMM called Agile Project Management. Each PMM is evaluated by considering their area of application, advantages, disadvantages and integration with other methodologies, after which a comparison is made of the different PMMs. The research was conducted by following a mixed methods research plan, which included the mixed methods research paradigm (combination of the interpretive research paradigm and the positivistic research paradigm), research methods (design science, case study and survey), quantitative and qualitative data–collection techniques (interviews and questionnaires), and dataanalysis techniques (cross–case and statistical). The reasons that projects fail and critical project success factors were studied and summarised to form the critical project success criteria, which were used to create the agile project success criteria. The ASDM best practice and PMM best practice frameworks were created by identifying whether a certain ASDM or PMM would satisfy a specific agile project success factor (APSF) of the agile project success criteria. The findings of each APSF in the respective frameworks were used as a foundation to develop a hybrid APMM (ver. 0) that would address the agile project success criteria. The hybrid APMM (ver. 0) was developed interpretively using design science (research approach) and constructivism by combining the strengths, addressing the weaknesses and bridging the gaps identified in the frameworks. The hybrid APMM (ver. 0) was then evaluated and improved by conducting an interpretive case study, which entailed interviewing participants from large and small organisations. Once the qualitative data collected had been analysed using cross–case analysis, the findings were incorporated in order to create an improved hybrid APMM (ver. 1). The hybrid APMM (ver. 1) too was evaluated and improved by conducting a survey, which entailed administering questionnaires to various respondents in order to collect quantitative and qualitative data. The findings of the statistical analysis of the data were also used to improve the hybrid APMM (ver. 1), resulting in the final hybrid APMM (ver. 2). This study demonstrates that a combination of ASDMs and PMMs can be used to develop a hybrid APMM with the ability to deliver IT projects in a constantly changing project and business environment. / Thesis (Ph.D. (Computer Science))--North-West University, Potchefstroom Campus, 2012.

The aim of this study is to investigate whether a combination of agile system development methodologies (ASDMs) and project management methodologies (PMMs) can be used to develop a hybrid APMM that will have the ability to deliver information technology (IT) projects successfully in a constantly changing business and project environment. To achieve this objective, a literature review was conducted on the relatively well–established ASDMs by firstly defining a SDM and an ASDM. Each ASDM and its effectiveness are described, after which ASDMs in general are evaluated by considering their area of application, advantages and disadvantages. A comparison is then done of the seven different ASDMs using the four elements of an SDM (Huisman & Iivari, 2006:32) to emphasise some of the main similarities and differences amongst the different ASDMs. The seven ASDMs investigated in this study are Dynamic System Development Methodology, Scrum, Extreme Programming, Feature Driven Development, Crystal ASDMs ? Crystal Clear and Crystal Orange in particular, Adaptive Software Development and Lean Development. A literature review was also conducted on two structured and relatively well–established PMMs, PMBOK and PRINCE2, and a relatively new PMM called Agile Project Management. Each PMM is evaluated by considering their area of application, advantages, disadvantages and integration with other methodologies, after which a comparison is made of the different PMMs. The research was conducted by following a mixed methods research plan, which included the mixed methods research paradigm (combination of the interpretive research paradigm and the positivistic research paradigm), research methods (design science, case study and survey), quantitative and qualitative data–collection techniques (interviews and questionnaires), and dataanalysis techniques (cross–case and statistical). The reasons that projects fail and critical project success factors were studied and summarised to form the critical project success criteria, which were used to create the agile project success criteria. The ASDM best practice and PMM best practice frameworks were created by identifying whether a certain ASDM or PMM would satisfy a specific agile project success factor (APSF) of the agile project success criteria. The findings of each APSF in the respective frameworks were used as a foundation to develop a hybrid APMM (ver. 0) that would address the agile project success criteria. The hybrid APMM (ver. 0) was developed interpretively using design science (research approach) and constructivism by combining the strengths, addressing the weaknesses and bridging the gaps identified in the frameworks. The hybrid APMM (ver. 0) was then evaluated and improved by conducting an interpretive case study, which entailed interviewing participants from large and small organisations. Once the qualitative data collected had been analysed using cross–case analysis, the findings were incorporated in order to create an improved hybrid APMM (ver. 1). The hybrid APMM (ver. 1) too was evaluated and improved by conducting a survey, which entailed administering questionnaires to various respondents in order to collect quantitative and qualitative data. The findings of the statistical analysis of the data were also used to improve the hybrid APMM (ver. 1), resulting in the final hybrid APMM (ver. 2). This study demonstrates that a combination of ASDMs and PMMs can be used to develop a hybrid APMM with the ability to deliver IT projects in a constantly changing project and business environment. / Thesis (Ph.D. (Computer Science))--North-West University, Potchefstroom Campus, 2012.