Not available / text

Not available / text

M. Tech. Professional Practice in Information Technology. Tshwane University of Technology, 2011. / Service Oriented Architecture is touted to be the architecture that can provide organisations with the ability to respond more quickly to changes in their business environments than otherwise. This is because Service Oriented Architecture design principles encourage applications to be designed for dynamic reuse, communication and integration with other applications thereby reducing the time-to-market of applications that support new or changed business processes. One of the ways of using Service Oriented Architecture principles when developing applications is by using web-services. The web-services used in composing or building Service Oriented Architecture applications may be developed by different teams using different programming languages, may reside in geographically dispersed areas and be connected and communicate by using a variety of communications infrastructure. As a result, Service Oriented Architecture applications often have a dynamic, heterogeneous and distributed architecture. This architecture poses a difficult challenge with resolution of issues experienced with Service Oriented Architecture applications in operations environments. In this research, literature review is conducted to firstly, investigate challenges of Service Oriented Architecture applications in operations environments. Secondly, root-causes of these challenges are identified. Then a framework for management of challenges of Service Oriented Architecture applications in operations environments is developed based on the identified challenges and their root-causes. Elements of this framework are then compared with Information Technology Infrastructure Library (ITIL) processes to evaluate the extent to which Information Technology Infrastructure Library can be used to manage Service Oriented Architecture applications in operations environments.

Scientific software, by which we mean application software that has a large computational component, models physical phenomena and provides data for decision support. This can be software that calculates loads on bridges, provides predictions for weather systems, images bone structures for surgical procedures, models subsystems at nuclear generating stations, or processes images from ground-based telescopes. There is no consensus on what the best practices for the development of scientific software are. We carried out a study at two Canadian universities in which we interviewed scientists and engineers who develop or use scientific software to identify characteristics of current development and usage. Through qualitative analysis, I identified key characteristics of scientific software development and usage and observed correlations between these characteristics. The results are a collection of observations about how scientific software is documented and designed; the nature of the scientific software lifecycle; the selection of development languages; approaches to testing, especially validation testing; and sources of risk. I also examine concerns scientists have with commercial software they use to determine what quality factors are of interest to them and also which seem to require special trade-offs. I find that scientific software development and use differs fundamentally from development in most other domains. / Thesis (Master, Computing) -- Queen's University, 2008-04-27 11:54:00.268

In recent years many tools and techniques have been proposed and even implemented which support maintenance programmers to gain an understanding of existing source code. However, studies have found that some tools are of marginal benefit and not appropriate for all maintenance tasks. This may be due to tools having been designed with little regard to the common behavioural practices that occur during software maintenance tasks because the current state of knowledge of such practices is quite limited. The aim of this study is to alleviate the above situation by performing a detailed behavioural analysis of software maintenance tasks undertaken under laboratory experiment conditions. To support this aim an experiment was conducted in which twenty-nine student subjects experienced in C programming independently undertook one of two maintenance tasks on the same C program in a university environment. The data produced from the experiment included subjects??? interactions with documents and code and their responses to program comprehension questions at the end of the task. The results indicate that maintenance task success is associated with a heightened concentration on high-level procedures that control the execution of lower level procedures. Among subjects, IT industry experience was linked to efficient comprehension of program and task documentation and the performance of more code searches. In general, code searches mainly involved searches for procedure name references. Compared to subjects undertaking the enhancement task, subjects performing the complex corrective task utilised program documentation more but also obtained a greater understanding of the elementary operations and control-flow of the program. In addition, this study illustrates a method to identify common information usage strategies from the recorded maintenance behaviour of subjects. Largely unsuccessful attempts were also made to sequentially analyse maintenance behaviour. This lack of success is possibly attributable to the as-needed comprehension approach adopted by subjects. The results of this research suggest that cost-effective maintenance of software is best supported using tools implementing facilities for feature location and visualisation of the control-flow of a program. The former facility would be most helpful to maintainers undertaking corrections, whereas the latter would particularly assist maintainers undertaking enhancements.

Proefschrift Universiteit van Amsterdam. / Met lit.opg. en samenvatting in het Nederlands.

Proefschrift Universiteit van Amsterdam. / Research carried out under the auspices of the research school IPA (Institute for Programming research and Algorithmics) Met lit. opg. - Met samenvatting in het Nederlands.

Thesis (M.S.S.I.S.)--Regis University, Denver, Colo., 2007. / Title from PDF title page (viewed on Nov. 02, 2007). Includes bibliographical references.

Project report (M.S.)--Virginia Polytechnic Institute and State University, 1990. / Abstract. Includes bibliographical references (leaf 73). Also available via the Internet.

Thesis (Ph.D) - Swinburne University of Technology, Faculty of Information & Communication Technologies, 2006. / A thesis submitted for the degree of PhD, Faculty of Information and Communication Technologies, Swinburne University of Technology, 2006. Typescript. Bibliography: p. 126-133.