The design team of System development projects is facing cognition of these users to requirement function in several departments of a large organization. The mix of both domains¡¦ knowledge involves these users of various groups and technology knowledge by the capabilities of existing technology and consequently creates the artifact to support organizational process and job. Because of the risks and uncertainties associated with Skill Mix in large, complex system development, the purpose of this research argues that a Skill Mix problem and solution acquired in the building and application of an artifact in a timely and cost-effective manner. On the one hand, the artifact can effectively support organizational process and job. On the other hand, the artifact is facing a difficulty that meets user needs. Nevertheless, the amount of organizational departments and users participated in the IS project are much too difficult to reach a participative, consensus cognition. Software development risks become too high. Therefore, organizational users participate design in the IS project is a crucial factor in affecting performance outcome. For such software development environment, this research suggested that both the design team and users of IS project apply a TQM organizational system perspective to Management Infrastructure as a base for communication. In addition, this study proposed an organizational process to improve software productivity and quality in system development. This research argues the process has two parts. One is the TQM Perspective as the base for management infrastructure and stakeholder participation. The other is a skill mix process concerning the management to coordinate and manage the interaction between stakeholders. This research stressed a systemic approach of developing infrastructure capabilities to enable implementation of Skill Mix to conduct the stable and meaningful requirement. The artifact is able to perform regular function in order to improve Skill Mix process of both Organizational domain knowledge and technology knowledge in system development. For example, this research argues this process to develop ERP system meets the business needs. ERP system is able to support that sales department sells service with producing condition of an order for goods.

There is a wide gap between the users and the developers in terms of understanding an information system. The most important job scope of a system analyzer is to interview the users to fulfill the requirements and to produce the documentation in layman terms. Chaos theory, system dynamics, project management theory, etc. all tell the initial stage playing an important role during system development. If the users¡¦ requirements are not clearly understood, it will have a bitter consequence when the information system is online. Therefore, system analysis is the essential stage for changes and to understand the requirements of the users. Currently, approaches of system analysis are related to either database management or structured methodology. As for the acquisition of users¡¦ requirements, there are no clear steps and procedures. This has made the understanding of users¡¦ requirement more difficult. We hope that by using a tool of architecture, system analyzers can better comprehend users¡¦ requirements. Hence, we come up with the Architecture-Oriented-System-Analysis-Model (AOSAM) for analysis, design, implementation and testing of an information system. For this research, there are three portions: (1) the fundamental theory of the AOSAM, (2) the build up of the AOSAM, and (3) procedures of using the AOSAM. In this study, we find out AOSAM is able to combine structure with process during the system analysis stage. Furthermore, AOSAM also reaches three significant accomplishments: (1) system analysts grasp users¡¦ requirements firmly, (2) system designers easier to transform users¡¦ requirements to design documents, and (3) to reduce repeating System Development Life Cycle. In the future, we would like to advance the AOSAM to the area of user acceptability, integrated business information system, system design, etc.

No description available.

Internal communication is an important factor in organisations today. For many system development teams it’s critical that the communication works well. Without communication, success would be impossible. This study aims to highlight the effect communication has on the members of agile project teams. The theoretical data is gathered from a literature study in the fields of relevance. The empirical data in this study is gathered from interviews and observations at three different companies, all working with agile development methods. The results from the interviews and observations presents that all respondents were affected by the internal communication in their work. Our analysis show a clear resemblance between the empirical data and the data gathered in our theoretical study. Our conclusion show that internal communication has an effect on the agile project teams. A factor that became very clear is that the project teams feel more effective because of the communication. But our conclusion also shows that the internal communication improved relations, work became more fun, and the atmosphere in the project teams got more familiar. Communication helped the project teams spread their knowledge between each other in the project teams. The communication also created a common language for the system developers which meant they could understand the requirements better and easier, which leads to more effective communication.

The introduction of computers in working life has changed the very nature of many jobs and the entire work situation for a great number of people. How has this affected the individual´s health and well being? With the large increase in the use of computers we have witnessed an increase in reports on negative effects on users´health. The puropose of this thesis is to describe a number of studies on health effects of office computerisation conducted over a period of 20 years. The emphasis of the early studies was on psychosocial factors and stress effects while the focus in the more recent studies was to take into account occupational health in software development. The following conclusions have been drawn: We still face severe problems concerning the computer users´health and work environment. Much of the negative health effects are associated with stress. The introduction of new computer systems can result in an increase in various work-related health risks. These risks are related to several interacting factors, with two of the more important factors being work organisation and contents and design ot the computer system. Current methods, models and tools for system development are insufficient to prevent work environment and health problems encountered in administrative case handling work. To counteract these problems more attention needs to be given to social and organisational factors during system development.

As part of an internship at Ericsson, this report was written to enhance the understanding of how it is to develop a system that is well established at the workplace. To improve an already existing system is not always as easy as many developers may think. In this report the pros and cons of developing an already existing system has been researched and analyzed. Do note that the results are only from one development of a specific system and that comparison of other developments has been made from other reports and not from experiencing it firsthand. It was found that the choices made can have an impact on further developing and it is important to write down what has been done. Writing down why you choose to do something may help you further down the process why you did what you did. / Som en del av ett praktiskt examensarbete, har denna rapport skrivits för att öka förståelsen av hur det är vidareutveckla ett befintligt och etablerat system. Att förbättra ett redan befintligt system är inte alltid så lätt som många systemutvecklare har uppfattning om. I denna rapport har fördelar och nackdelar med utvecklingen av ett redan befintligt system undersökts och analyserat med hjälp av egna upplevelser. Notera att resultatet är framtaget från en enda upplevelse av en specifik utveckling av ett system. Detta betyder att jämförelser endast gjorts med andra rapporteringar av liknande fall och inte med egen erfarenhet då bara ett system utvecklats under denna tid. Resultatet visar att det är viktigt att du antecknar dina tankar kring de val du gör då det kan hjälpa dig med andra val senare i projektets process.

This study investigates the critical success factors involved in agile systems development projects. Various systems development methodologies and project management methodologies are presented with their underlying principles, strengths and weaknesses. Thereafter the critical success factors adopted from the work of Chow and Cao (2007) are presented. A positivistic research paradigm was chosen for data collection and analysis. The survey method was chosen for data collection. A questionnaire was sent to multiple respondents in a predominantly agile work environment, which resulted in a total of 129 respondents in various business sectors. The results were analysed by implementing multiple correlation and regression statistics as well as descriptive statistics. The results show that there are in fact 16 critical success factors that have a direct impact on the success of agile systems development projects. Agile systems development methodologies have been increasing in use during the last 3 years, and most organisations are implementing some form of project management methodology. The first recommendation is based on the findings that strong customer involvement and the appropriate management of the agile process with a satisfactory amount of documentation resulted in greater process success. Therefore, organisations should encourage these critical success factors when implementing an ASDM as this has a positive effect on the project outcome. The appropriate management of the agile process with a satisfactory amount of documentation, the application of good design practices and technical knowledge to a project, and a cooperative organizational culture instead of hierarchical are three of the key critical success factors that were positively related to the success of the product. By focussing on these critical success factors, the success of the entire project can be predicted. / Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.

This study investigates the critical success factors involved in agile systems development projects. Various systems development methodologies and project management methodologies are presented with their underlying principles, strengths and weaknesses. Thereafter the critical success factors adopted from the work of Chow and Cao (2007) are presented. A positivistic research paradigm was chosen for data collection and analysis. The survey method was chosen for data collection. A questionnaire was sent to multiple respondents in a predominantly agile work environment, which resulted in a total of 129 respondents in various business sectors. The results were analysed by implementing multiple correlation and regression statistics as well as descriptive statistics. The results show that there are in fact 16 critical success factors that have a direct impact on the success of agile systems development projects. Agile systems development methodologies have been increasing in use during the last 3 years, and most organisations are implementing some form of project management methodology. The first recommendation is based on the findings that strong customer involvement and the appropriate management of the agile process with a satisfactory amount of documentation resulted in greater process success. Therefore, organisations should encourage these critical success factors when implementing an ASDM as this has a positive effect on the project outcome. The appropriate management of the agile process with a satisfactory amount of documentation, the application of good design practices and technical knowledge to a project, and a cooperative organizational culture instead of hierarchical are three of the key critical success factors that were positively related to the success of the product. By focussing on these critical success factors, the success of the entire project can be predicted. / Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.

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.