No description available.

No description available.

This paper presents first results from research into open source projects from a software engineering perspective. The research methodology employed relies on public data retrieved from the CVS-repository of the GNOME project and relevant discussion groups. This methodology is described in detail and some of the results concerning the special characteristics of open source software development are given. (author's abstract) / Series: Diskussionspapiere zum Tätigkeitsfeld Informationsverarbeitung und Informationswirtschaft

This thesis describes the process of writing a software application geared toward developing computer graphics in the Windows environment. The code is written using Visual C++ and the Microsoft Foundation Classes (MFC). As an illustration of this process we will walk through the development of a software application. This application will allow a user to create and edit an image composed of simple line graphics and geometric shapes. The user can select drawing colors, select drawing styles, and do area filling. This application also illustrates the use of menus and dialog boxes. / Department of Computer Science

Background: Exploring the ambidexterity literature in the context of agile software development organizations from the perspective of how the organizational characteristics that result from the application of agile methods affect the achievement of ambidexterity Aim: To gain insight into how agile software development organizations achieve ambidexterity. Methodology: How agile software development organizations achieve ambidexterity was studied through a multiple case study where the total of four case projects in two different organizations were examined. Findings: This study indicated how the characteristics of agile software development organizations have an essential role in how ambidexterity is achieved in these organizations.

M.Sc. (Computer Science) / The data processing crisis in software development today can be ascribed firstly to insufficient requirements defmition, which results from a lack of communication between developer and user, and secondly to insufficient project management. During the last decade we succeeded in adding more control and discipline to the traditional software development life cycle, but requirements specification remains a problem. The traditional software development life-cycle is long and inflexible and the results do not satisfy the requirements of the user. The prototyping approach can be part of a solution to the problems posed by this situation. The author proposes a four-dimensional conceptual model as a framework for a Prototyping methodology that was developed as basis for this study. In business practice today, confusion exists as to what prototypes are the best to use - prototypes that are developed to become the complete system, or prototypes that are thrown away. Dimension one of the model is discussed in terms of type of prototype. With type of prototype is meant one of the different approaches to prototyping in the software development process. The author standardized on throw-away prototypes and evolutionary prototypes. The most general and well-known usage of prototyping is during the requirements :definition phase. However, this is not the only use of prototyping. Dimension two of the model describes the different areas of usage of prototyping, e.g. requirements definition, as technique during JAD sessions, during simulation, during the minimizing of risk and in the development of working models. The development of prototypes should be an easy and rapid process, however, this is dependent on the tools that are used in the process. Dimension three of the model is discussed in terms of tools.

A dissertation submitted to the Faculty of Engineering, University of the Witwatersrand, Johannesburg, in fulfilment of the requirements for the degree of Master of Science in Engineering. Johannesburg, 1996. / This report examines the major factors influencing the development of embedded systems. The discussion covers, among other aspects, features of embedded systems that are common to software development in general, the main characteristics of embedded systems, some of the current development strategies, the mlcrocontroller market, language issues and development tools. Following the assessment study and a practical embedded system development, the report concludes that although: I embedded systems are typified by relatively few lines of codes, their complex nature necessitates the application of a disciplined development approach. The report presents a riskbased hardware-software co-design development approach in an attempt to reconcile the existing formal development models to the technical realities of embedded systems. A practical embedded system case study is presented, It involves the development of a microcontroller-based system for the three-phase inverter of an uninterruptible power supply (UPS).

A research report submitted to the Faculty of Engineering and the Built Environment, University of the Witwatersrand, in fulfilment for the degree of Master of Science in Engineering Johannesburg 2015 / The Analytic Hierarchy Process (AHP) is a Multi Criteria Decision-Making (MCDM) tool, which has gained wide acceptance in all disciplines in science and engineering. Although it has been used in mining engineering applications, it is only recently gaining significant momentum in the mining industry. Given its simplicity, it may seem surprising that it has not received wide acceptance, but this is probably due to a lack of both publicity and a user-friendly methodology. This report introduces a simple methodology that can be employed by anyone who possesses basic knowledge of arithmetic and spreadsheets, without having to know or understand fully the mathematics that the process is based on. / MT2017

A Virtual Software Development Team (VSDT) is a group team of Information Technology (IT) professionals working together to produce a software product and collaborating remotely with the use of information communication technology. In a VSDT, face-to-face contact is seldom required in order for these teams to fulfil their tasks. VSDTs in the software development business offer advantages compared to co-located teams which include the availability of a global talent pool, lower costs and a global presence. However, many aspects of managing these teams are still undiscovered and under-researched. Among them is the influence of cultural diversity on the work, productivity and sustainability of a VSDT. The purpose of this research was to define the main factors of the influence of cultural diversity on the effectiveness of a VSDT. The research was undertaken from an interpretive perspective. In agreement with this paradigm, the effectiveness factors were limited to the internal effectiveness of a team as perceived by its members. In order to define the factors of cultural diversity, existing theories of cultural diversity in a co-located workplace were used. I have conducted interviews with software developers, support professionals and their managers to probe the relevance of the existing theories in a virtual software development environment and to find other possible factors. In this research, a specific ’internet nerd’ culture was discovered which exists among the members of the virtual (internet) community. The members of this culture comfortably accept virtual work and share a lot of common context. The findings show the importance of frequent communication, emotional sharing and occasional face-to-face contact in bonding the team, building trust and understanding. From the team management perspective, there is evidence that agile methodologies can be used successfully in the virtual environment. The results of this research are beneficial for businesses looking to implement VSDTs, and can be used as a basis for the development of a theory of cultural diversity in a virtual environment.

The software artwork creation process is investigated using interviews with the artists, Brogan Bunt, Pierre Proske, Nathaniel Stern, Joshua Goldberg and Pall Thayer. This research asks the questions: How do practising software artist experience their development process? How does this process compare with the Agile software development process? How can conclusions made from a comparison between the Agile process and the discussions held with practising software artists shed light on the areas where the Agile process can assist artists and areas which might be avoided? The creative process was investigated from a cognitive psychological angle. The software development process was investigated from an Agile process point of view. Concepts connected with software as art medium provides the themes that face artists who choose software as medium. This study illuminates aspects of the Agile process that may assist software artists as well as highlight areas of the process that may disrupt the creative process. A process that is iterative, allows different cognitive styles and supports collaboration is recommended. Tools such as source code control and exploratory testing can support artwork documentation and exploration of the medium. The practical component of this research relates to the philosophical themes of the underlying software visibility in software art and a visual interpretation of the software development process.