A research report submitted to the Faculty of Engineering, University of the Witwatersrand, Johannesburg, in partial fulfilment of the requirements for the degree of Master of Science in Engineering. / Due to the dynamic nature of the software engineering industry there is a constant move towards new strategies for solving design problems. More specifically there is a move towards Object Oriented (OO) methodologies, presumably because of the various advantages offered in terms of maintainability, and reuse of code produced this way. As with various other aspects of the software industry there are however also problems encountered in this transition and lessons to be learned from the experience of companies who have already performed this change. This research report investigates possible guidelines for companies who are currently contemplating a change to the OO software design methodologies, by covering a collection of issues one should know about prior to this change. It also summarises the problems faced in the transition so far, the reasons for these problems and suggests possible solutions. Lastly it also investigates new trends in the OO arena. The emphasis is on South African companies and projects. The results obtained are compared with results obtained overseas to find out what the differences and similarities are. Areas of concern are also identified, where theoreticians' views have been ignored, and both South African and overeeas companies have not implemented any of the suggestions made. / Andrew Chakane 2018

College campuses can be large, confusing, and intimidating for new students and visitors. Finding the campus may be easy using a GPS unit or Google Maps directions, but this is not the case when you are actually on the campus. There is no service that provides directional assistance for the campus itself. This thesis proposes a driver assistant application running on an Android platform that can direct drivers to different buildings and parking lots in the campus. The application's user interface lets the user select a user type, a campus, and a destination through use of drop down menus and buttons. Once the user submits the needed information, then the next portion of the application runs in the background. The app retrieves the Campus Map XML created by the mapping tool that was constructed for this project. The XML data containing all the map elements is then parsed and stored in a hierarchal data structure. The resulting objects are then used to construct a campus graph, on which an altered version of Dijkstra's Shortest Path algorithm is executed. When the path to the destination has been discovered, the campus map with the computed path overlaid is displayed on the user's device, showing the route to the desired destination. / by Iana Zankina. / Thesis (M.S.C.S.)--Florida Atlantic University, 2012. / Includes bibliography. / Mode of access: World Wide Web. / System requirements: Adobe Reader.

Os Métodos Ágeis surgiram no final da década de 90, como uma alternativa aos métodos prescritivos de desenvolvimento de software. Eles propõem uma nova abordagem de desenvolvimento, eliminando gastos com documentação excessiva e burocrática, enfatizando a interação entre as pessoas e as atividades que efetivamente trazem valor ao cliente. Nos últimos anos, diversos princípios e práticas baseados na indústria de manufatura foram incorporadas pelos Métodos Ágeis de desenvolvimento de software. Um dos princípios absorvidos é o de melhorar a eficácia de uma organização através de melhorias globais. Embora este princípio seja bem difundido nos Métodos Ágeis, utilizá-lo não é uma tarefa fácil. Nem sempre é fácil ter uma visão global do processo de desenvolvimento. Além disso, para realizar melhorias globais é necessário descobrir a causa para possíveis problemas, o que também pode ser uma tarefa difícil. Esse trabalho investiga duas abordagens da indústria de manufatura que enxergam uma organização como um sistema no qual todas as partes são inter-relacionadas. Com base nelas, três abordagens de desenvolvimento de software existentes são analisadas. Finalmente, um estudo comparativo foi feito para avaliar as principais características dos métodos de desenvolvimento estudados. Esse estudo estende o trabalho feito por Abrahamssom et al., no livro Agile Software Development: Current Research and Future Directions, avaliando o desempenho dos métodos seguindo o arcabouço proposto pelos mesmos autores. / Agile methods appeared in the late 90\'s as an alternative approach to the classic prescriptive planning approaches to software development. They propose a new style of development, eliminating excessive and bureaucratic documentation, and emphasizing the interactions between people collaborating to achieve high productivity and deliver high-quality software. In the last few years, several principles and practices based on the manufacturing industry were incorporated by Agile software development. One of the principles absorbed is to improve the effectiveness of an organization through an overall improvement. Although this principle is quite widespread in Agile Methods, using it is not an easy task. It is not easy to get the big picture of the development process. Moreover, to achieve overall improvements is necessary to discover the cause of possible problems, which can also be a difficult task. This work investigates two approaches in the manufacturing industry that shares the assumption that the whole organization is focused on overall throughput, not on micro-optimization. Based on then, three approaches to existing software development are analyzed. Finally, a comparative study was done to assess the main characteristics of the studied methods. This study extends the work done by Abrahamssom et al. In the book Agile Software Development: Current Research and Future Directions, evaluating the performance of the methods following the framework proposed by the same authors.

by Liu Shu Cheung, Jimmy. / Thesis (M.Ph.)--Chinese University of Hong Kong, 1988. / Bibliography: leaves 61-64.

Cai Xia. / Thesis (M.Phil.)--Chinese University of Hong Kong, 2002. / Includes bibliographical references (leaves 105-110). / Abstracts in English and Chinese. / Chapter 1 --- Introduction --- p.1 / Chapter 1.1 --- Component-Based Software Development and Quality Assurance Issues --- p.1 / Chapter 1.2 --- Our Main Contributions --- p.5 / Chapter 1.3 --- Outline of This Thesis --- p.6 / Chapter 2 --- Technical Background and Related Work --- p.8 / Chapter 2.1 --- Development Framework for Component-based Software --- p.8 / Chapter 2.1.1 --- Common Object Request Broker Architecture (CORBA) --- p.9 / Chapter 2.1.2 --- Component Object Model (COM) and Distributed COM (DCOM) --- p.12 / Chapter 2.1.3 --- Sun Microsystems's JavaBeans and Enterprise JavaBeans --- p.14 / Chapter 2.1.4 --- Comparison among Different Frameworks --- p.17 / Chapter 2.2 --- Quality Assurance for Component-Based Systems --- p.199 / Chapter 2.2.1 --- Traditional Quality Assurance Issues --- p.199 / Chapter 2.2.2 --- The Life Cycle of Component-based Software Systems --- p.255 / Chapter 2.2.3 --- Differences between components and objects --- p.266 / Chapter 2.2.4 --- Quality Characteristics of Components --- p.27 / Chapter 2.3 --- Quality Prediction Techniques --- p.32 / Chapter 2.3.1 --- ARMOR: A Software Risk Analysis Tool --- p.333 / Chapter 3 --- A Quality Assurance Model for CBSD --- p.35 / Chapter 3.1 --- Component Requirement Analysis --- p.38 / Chapter 3.2 --- Component Development --- p.39 / Chapter 3.3 --- Component Certification --- p.40 / Chapter 3.4 --- Component Customization --- p.42 / Chapter 3.5 --- System Architecture Design --- p.43 / Chapter 3.6 --- System Integration --- p.44 / Chapter 3.7 --- System Testing --- p.45 / Chapter 3.8 --- System Maintenance --- p.46 / Chapter 4 --- A Generic Quality Assessment Environment: ComPARE --- p.48 / Chapter 4.1 --- Objective --- p.50 / Chapter 4.2 --- Metrics Used in ComPARE --- p.53 / Chapter 4.2.1 --- Metamata Metrics --- p.55 / Chapter 4.2.2 --- JProbe Metrics --- p.57 / Chapter 4.2.3 --- Application of Metamata and Jprobe Metrics --- p.58 / Chapter 4.3 --- Models Definition --- p.61 / Chapter 4.3.1 --- Summation Model --- p.61 / Chapter 4.3.2 --- Product Model --- p.62 / Chapter 4.3.3 --- Classification Tree Model --- p.62 / Chapter 4.3.4 --- Case-Based Reasoning Model --- p.64 / Chapter 4.3.5 --- Bayesian Network Model --- p.65 / Chapter 4.4 --- Operations in ComPARE --- p.66 / Chapter 4.5 --- ComPARE Prototype --- p.68 / Chapter 5 --- Experiments and Discussions --- p.70 / Chapter 5.1 --- Data Description --- p.71 / Chapter 5.2 --- Experiment Procedures --- p.73 / Chapter 5.3 --- Modeling Methodology --- p.75 / Chapter 5.3.1 --- Classification Tree Modeling --- p.75 / Chapter 5.3.2 --- Bayesian Belief Network Modeling --- p.80 / Chapter 5.4 --- Experiment Results --- p.83 / Chapter 5.3.1 --- Classification Tree Results Using CART --- p.83 / Chapter 5.3.2 --- BBN Results Using Hugin --- p.86 / Chapter 5.5 --- Comparison and Discussion --- p.90 / Chapter 6 --- Conclusion --- p.92 / Chapter A --- Classification Tree Report of CART --- p.95 / Chapter B --- Publication List --- p.104 / Bibliography --- p.105

In this thesis work, we develop an optoelectronic holographic platform to facilitate otologists' ability to quantitatively study and diagnose disorders of the tympanic membrane (TM) and middle ear of humans in full-field-of-view. The holographic platform consists of a laser delivery system, a handheld interferometer, and corresponding software, which allow nanometer scale 3D measurements of deformations of the TM.

<p>Model-Driven Engineering (MDE) leverages models to first-class status by shifting the focus of software development from coding to modeling. This thesis extends Antonio Cicchettis paper Difference Representation and Conflict Management in Model-Driven Engineering, adding concrete research corresponding to sequential composition.Differences between models can be displayed as deltas in a metamodel independent way. Working with these deltas, a need for sequential composites appears. This means, that several sequently deltas are marged together to a new delta. Since this delta contains a lot of unnecessary information, it needs to be optimized regarding to the minimal paradigm which is mentioned in the corresponding paper. This paper supplies the reader with a broad overview of the basic concepts, the difference representation and application including the metamodel independent approach, and finally a narrow examination of the research topic, including constraints, examples and implementation details.</p>

<p>There is always a need for easy-to-follow processes that enable accurate and non-time consuming solutions. Nowadays we see a lot of different approaches to development processes in software engineering. This project is concerned with how to manage a software development process in a reliable, secure and efficient way. Software is available which provides some help for project managers / administrators to work more productively, with effective communication. Using such systems, it is possible to keep track of all the phases of development, including task distribution, making maximum use of previous hands-on experience and increasing productivity, to deliver a finished product in minimum time. No existing solution, however, fulfills all the desirable criteria. This paper describes the motivation, design and implementation of an improved development management system using Active Server Pages and Microsoft Internet Information Services with a backend Microsoft Access Database developed using a waterfall software development process. The resulting system is described and evaluated. This system will be beneficial for software houses, because they can communicate on the web, allowing efficiency gains by avoiding the need to call meetings for distribution of tasks among employees, with the additional advantage of location-transparent team management through the Internet.</p>

I introduce a compositional approach to application software development. In this approach, an extended entity-relationship diagram (EERD), which represents the component types and the relationship types within an application domain, is used as a template of executable programs in that application domain. As we use structural active objects as the components of a program, we can obtain an executable program if those components are instantiated and interconnected as dictated by an EERD. Furthermore, the graphical editor in the proposed software development environment, entity-relationship software development environment (ERSDE), uses EERDs as menus in constructing application software. An EERD used as a menu can enforce legitimate patterns of relationships among components, in addition to providing an intuitive view of available components and possible relationships among them. Two experiments were conducted in order to compare the effectiveness between EERDs and class diagrams of Object Modeling Technique (OMT) and between the ERSDE and the menu-based Structural-Active Object System (SAOS) graphical editors. From these experiments, we obtained the following results. 1. A significant proportion of the subjects who used EERDs to compose certain applications did so correctly, while only a small proportion of the students who used the OMT class diagrams composed these applications correctly. 2. Most of the subjects preferred EERDs to OMT class diagrams as design documents. 3. Although the proportion of the students who composed applications correctly with the ERSDE application editor was larger than the proportion of the students who did so with the menu-based SAOS graphical editors, this difference was statistically not significant. 4. The subjects took significantly longer time to compose applications with the menu-based SAOS editors than with the ERSDE editor. 5. All the subjects preferred the ERSDE application editor to the menu-based SAOS graphical editors as a software development environment. / Graduation date: 1998

In this thesis, the first section will talk about how to implement the software development environment for 8bit microprocessor, including Compiler, Assembler, and Debugging mechanism etc. The design of Debugging mechanism is based on in-circuit emulator. In-circuit emulator is a common debugging technique for microprocessor. The designed ICE contains hardware implement and debugging software for it in this thesis. ICE hardware is a control circuit from TAP Controller, IEEE 1149.1 std. and it control the scan cells on the data bus. The Debugging software uses JTAG port, IEEE 1149.1 std., to insert debug instruction from PC to ICE hardware. In this thesis, the second section will focus on the process of integrating ICE hardware circuit and software debugger issued by two ways, our own design version and business suit debugging software support. The examples are not only integrating our LAB¡¦s 32bit microprocessor and ICE hardware, but also verifying software debugger to control ICE circuit by FPGA to prove above two methods are work.