No description available.

The internal logistics system includes all activities connected with managing the flow of materials within the physical limits of a facility. This system is an important part of operations in need of increased focus and continuous improvements. Automation is one possible tool with a previously confirmed great potential to improve internal logistics. Despite this great potential and a growing trend of using automation in the area, internal logistics activities are still not automated to the same extent as other parts of operations. The overall aim of this research is therefore to develop knowledge that supports the successful use of automation in internal logistics systems. The automation development process has been identified as critical for the success of the use of automation. With the overall aim of the research in mind, the objective of this thesis is to develop a framework facilitating the automation development process in internal logistics systems. To help fulfil the objective, empirical data have been collected through five case studies and a survey study. During the empirical studies, the process of improving the internal logistics system and the automation development process have been analysed and the focus has been on identifying challenges and facilitators for the successful use and development of automation in internal logistics systems. The findings indicate a poor awareness of both current and desired performance of the internal logistics system at the companies studied. In addition, automation development is often conducted in an unstructured and poorly supported manner and there is often insecurity regarding what steps and actions to take. Foremost, the findings indicate a poor base for proper evaluation and decisions during automation development in internal logistics systems. This is analysed and concluded as a cause of unclear goals and requirements and the lack of a strategic view with regard to both internal logistics operations and the use and development of automation. A framework, including proposed guidelines to overcome the observed challenges by including identified factors facilitating successful automation development in internal logistics systems has been developed. The core of the framework is a proposed process model for automation development in an internal logistics context. Due to the identified importance and the lack of a strategy linked to and supporting the automation development process, the framework also includes a proposed model for an internal logistics strategy as well as a proposed model for an automation strategy. / LEAD - Lean Automation Development

Although methodology use generally leads to fewer software defects and reductions in development time, the introduction of a formalized systems development methodology is often met with substantial resistance. Motivated by the purported benefits of methodology use, yet resistance to the introduction of a methodology, this study explains developer attitude toward using a formalized commercial methodology. An important variable for explaining attitude is perceived usefulness, defined as the degree to which using a methodology will enhance a developer's job performance. If, however, a benefit of using a methodology is different than increased job performance, then limiting the definition of perceived usefulness to beliefs surrounding job performance may provide an incomplete representation of what makes a methodology useful to developers. A methodology may be perceived as a rational process, used to achieve objectives such as increasing job performance or as a political process used to achieve objectives particular to one person or group. In order to determine what makes a methodology useful to developers, the perceived usefulness construct was expanded to include benefits of methodology use related toward achieving political objectives. In addition to broadening the perceived usefulness construct, this research also broke down perceived usefulness into its referent dimensions. Decomposing perceived usefulness provided a deeper understanding of what makes a methodology useful to developers and revealed the relative importance of each dimension of perceived usefulness. The study surveyed 120 developers. Partial least squares regression was used to test the antecedents of developer attitude as well as the hypothesized structure of perceived usefulness. Results indicate that developers will have more favorable attitudes toward methodologies they perceive as useful, easy to use, and consistent with the way they like to develop systems. Additionally, findings suggest that developers may find methodologies not only useful for achieving rational goals such as increasing system quality, raising productivity, and enhancing communication, but also useful for achieving political goals such as increasing career opportunities, showing others that professional development practices are being used, reducing anxiety, and defending against unreasonable user demands. / Ph. D.

Over the years, organizations have seen fit to adopt the use of agile systems development methodologies (ASDMs) because of the benefits that they offer, such as flexibility and the ability to deliver products faster, in constantly changing environments. When ASDMs are used in projects, they are made to fit or be suitable for a project‟s unique aspects, such as its size, requirements, scope and outcomes. This is known as the contingent use of ASDMs. Little is known about the contingent use of ASDMs in South African organizations. It is not known whether it is happening, its procedure and its success. It is important to know this because quality and control need to be maintained in systems produced. There is always a danger that the benefits of using a system development methodology (SDM) would be lost if ASDMs are highly adapted. This led to an investigation of three organizations in South Africa that use contingent ASDMs. With the help of semi-structured interviews, focus groups and documents, data was collected that was analysed, using the tool ATLAS.ti, and the analysis methods content and cross-case analysis. It was found that some South African organizations in the telecommunications, consulting, technological, outsourcing and agricultural sectors use ASDMs in combination with the still popular waterfall SDM. Compatibility between the SDM and the project is a factor in some organizations. Scrum was cited to be the ASDM that was used in some of the organizations interviewed due to its maturity. They make ASDMs contingent by using aspects in the methods, such as Scrum, that are useful for their unique projects. These aspects are in some cases combined with other SDMs to form hybrid methodologies. Some organizations use criteria, such as project needs, outcomes, size and complexity to make ASDMs contingent. Some organizations have measures and facilities in place to manage, monitor, control and document the process used to make ASDMs contingent. They make use of contingent ASDMs as they have experienced more success with them and they will continue to do so. / Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.

Over the years, organizations have seen fit to adopt the use of agile systems development methodologies (ASDMs) because of the benefits that they offer, such as flexibility and the ability to deliver products faster, in constantly changing environments. When ASDMs are used in projects, they are made to fit or be suitable for a project‟s unique aspects, such as its size, requirements, scope and outcomes. This is known as the contingent use of ASDMs. Little is known about the contingent use of ASDMs in South African organizations. It is not known whether it is happening, its procedure and its success. It is important to know this because quality and control need to be maintained in systems produced. There is always a danger that the benefits of using a system development methodology (SDM) would be lost if ASDMs are highly adapted. This led to an investigation of three organizations in South Africa that use contingent ASDMs. With the help of semi-structured interviews, focus groups and documents, data was collected that was analysed, using the tool ATLAS.ti, and the analysis methods content and cross-case analysis. It was found that some South African organizations in the telecommunications, consulting, technological, outsourcing and agricultural sectors use ASDMs in combination with the still popular waterfall SDM. Compatibility between the SDM and the project is a factor in some organizations. Scrum was cited to be the ASDM that was used in some of the organizations interviewed due to its maturity. They make ASDMs contingent by using aspects in the methods, such as Scrum, that are useful for their unique projects. These aspects are in some cases combined with other SDMs to form hybrid methodologies. Some organizations use criteria, such as project needs, outcomes, size and complexity to make ASDMs contingent. Some organizations have measures and facilities in place to manage, monitor, control and document the process used to make ASDMs contingent. They make use of contingent ASDMs as they have experienced more success with them and they will continue to do so. / Thesis (MCom (Computer Science & Information Systems))--North-West University, Potchefstroom Campus, 2013.

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

The use of systems development methods are, by many, seen as the way to solve development problems, decrease development time, and improve the quality of software systems. Despite this, little is known about how development methods are actually used in the software industry. The aim of this project is to investigate how a widespread development method is implemented and used in an organisational setting. The result of this project is a case study description of how Volvo Information Technology implements, adapts, and uses the commercial development method Rational Unified Process® (RUP®) in combination with other methods. The implementation is centrally administered and done incrementally over several years in order to build competence in the organisation. RUP is also adapted to the specific situation of the organisation, each division, each development project, and even adapted by individual developers.

Software specification by scenarios has grown with the popularity of object-oriented software engineering. Scenarios such as use cases provide a bridge from the informal descriptions gathered from user interviews toward the more formal software model. Yet, practitioners still request more explicit methodological guidance and more adequate tool support for authoring quality scenarios. Researchers have been seeking a means to overcome the limitations of use cases such as partialness and incompleteness. One of such research streams is an extension of scenarios with more formal representation schemes. This approach may reduce incompleteness of scenarios; however, applicability of the approach to practice remains open to discussion, considering that the current usage of formal scenario representations is very low. This research takes software reuse approach to assist scenario-building process. In the proposed approach, a software analyst defines an initial description of a scenario. An automated tool support then presents a set of similar use cases retrieved from a database of use cases. The analyst adapts a retrieved use case to the current purpose. This dissertation research is expected to have unique contributions to research and practice. The proposed automated scenario reuse provides a viable solution to guide scenario-authoring process without imposing an additional burden of adding formal annotations to system specifications on system analysts. By adopting a machinelearning algorithm based on relational structure matching, the scenario reuse places more focus on UML semantics, relational information among UML elements rather than syntactic attributes of scenarios or natural language descriptions. In addition, the proposed scenario reuse can be augmented with other approaches and design artifacts, depending on customized needs in a given context of problem domains. In terms of research methodology, this dissertation research takes four steps. First, I develop prototype software for the automated tool support. It can be incorporated into a CASE tool as an add-in program. Second, preliminary case studies are taken to evaluate the feasibility of the proposed approach. Third, expert opinions are collected regarding the effectiveness and efficiency of the tool support. Finally, a lab experiment and a free simulation experiment are conducted for more rigorous empirical validation.

<p>This work concerns ethics applied to computer technology, emphasizing the use of this technology within organizations. Computer technology has created the possibility to do things not possible before, for good and bad. Ethical reasoning can be used as a tool to provide guidance, in order to create Computerized Information Systems (CIS) that are sustainable with respect to the ethical demands that can be put upon them.</p><p>If one wants to integrate ethical considerations into a CIS, it is reasonable that ethical issues should be taken account of in systems development. As a general methodology for developing a CIS, the Systems Development Life Cycle (SDLC) will be examined. The SDLC is the place and moment when it is possible to integrate ethical considerations into a CIS.</p><p>This work will focus on, and try to explain, what characteristics are necessary in order to be able to apply ethical considerations to a methodology. This is done by examining five methodologies adopting the SDLC. It will also be examined how the three major ethical theories utilitarianism, deontologism and rights ethics will affect the SDLC, and thus eventually a CIS being implemented.</p><p>The outcome of this work are that there are limited possibilities of integrating ethical considerations into methodologies adopting a hard system approach, compared to those adopting a soft one. The ethical standards of a CIS must be established early on in the SDLC. Integration of ethical issues requires a system approach to be applied in the SDLC. Participation becomes an important feature of systems development in order to adopt ethical reasoning. The different ethical theories will put different emphasis on the group or the individual in systems development.</p>