Log in

Relevant bibliographies by topics / Computer software Development Australia / Dissertations / Theses

Dissertations / Theses on the topic 'Computer software Development Australia'

To see the other types of publications on this topic, follow the link: Computer software Development Australia.

Author: Grafiati

Published: 10 December 2022

Last updated: 29 January 2023

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the top 50 dissertations / theses for your research on the topic 'Computer software Development Australia.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.

1

Dick, Martin. "The benefits of object technology to Australian software development organisations." Monash University, School of Computer Science and Software Engineering, 2002. http://arrow.monash.edu.au/hdl/1959.1/9313.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Sutharshan, Anuradha. "Human factors and cultural influences in implementing agile philosophy and agility in global software development." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 2013. https://ro.ecu.edu.au/theses/587.

Full text

Abstract:

As software becomes increasingly important to all aspects of industry, developers should be encouraged to adopt best practice and hence improve the quality of the processes used, and achieve targets relating to time, budget and quality. In the software industry, several software methodologies have been used to address software development problems; however some of these processes may be too bureaucratic. The Agile Alliance formed in 2001, sought to address this problem; accordingly, they developed a manifesto and twelve principles, to which all agile software methods adhere. The purpose of the manifesto and its principles is to uncover better ways of developing software. Agile software development methods seem to address the software development industry’s need for more agile processes that are responsive to changes during software development. Agile values and principles require a major cultural change for software managers, e.g. collective team responsibility and self-organisation, especially in large organisations with a strong culture of planning and centralised power. In large global organisations, this issue is likely to be exacerbated by cultural diversity. The objective of this thesis is to analyse the possibility, of using agile methods or practices in different cultures, and study what changes are required, to adapt agile approaches to different global application development issues. The study found that certain agile practices can be useful in different cultures and some practices required major cultural adaptation. A study of suitable practices for different cultures such as Australia, India and the United Kingdom and the associated suggested changes required are the main areas of study. Human factors have been identified by researchers and practitioners to impact on software development projects. Similarly, cultural differences may also be influential in a global market. The principles of agile software development focus on iterative adaptation and improvement of the activities of individual software development teams to increase effectiveness. This research programme focused specifically on national culture based on Hofstede’s cultural dimensions, Hall’s cultural dimensions and the relationships between different aspects of national culture and the implementation of agile methods. To investigate this aspect of software development, a set of cultural dimensions and consolidated cultural agile attributes were developed, that are considered necessary for implementing agile methods. Based on relevancy, cultural dimensions such as Individualism/Collectivism, Power distance index, Uncertainty avoidance index, Time and Context were selected and studied. Some of cultural agile attributes studied include Transparency, Dedicated team, Decision making, Tolerance for change, Time keeping and Authoritative. This set was identified from a literature review on culture for agile methods, a detailed analysis of relevant commonly used agile methods and from feedback from agile experts. This thesis involves qualitative interviews conducted in Australia, India, and the UK using an interpretive paradigm and aims to identify cultural dimensions to implement agile methods in the software engineering community. The results of this research programme provide an analytical comparative framework for implementing agile methods in different cultures, and insight into how cultural differences may affect a software project and how these challenges can be addressed through agile principles.

APA, Harvard, Vancouver, ISO, and other styles

3

Sherwood, Patricia Ann. "Inspections : software development process for building defect free software applied in a small-scale software development environment /." Online version of thesis, 1990. http://hdl.handle.net/1850/10598.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Algan, Fatih Tuğlular Tuğkan. "Test driven software development/." [s.l.]: [s.n.], 2005. http://library.iyte.edu.tr/tezler/master/bilgisayaryazilimi/T000412.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Moland, Kathryn J. "An Effective Software Development Methodology for Quality Software Development in a Scheduling Department." NSUWorks, 1997. http://nsuworks.nova.edu/gscis_etd/731.

Full text

Abstract:

The research described in this document represents work performed in the area of software development methodologies as it applied to quality software development in a scheduling department. It addressed traditional methods in software development, current trends in software development, in addition to quality and software development at various companies. The literature suggested a correlation between using a software development methodology and quality software. However, there was limited literature that measured quantitatively the correlation between the effectiveness of the software development methodology and quality software. A software development methodology was developed for the scheduling department of a government contractor company in Aiken, South Carolina based on its needs and emerging technologies. An instrument was utilized to measure the effectiveness of the developed methodology. The methodology was compared with two other methodologies: a standard methodology from the literature and the current method of software development in the scheduling department. A population of computer professionals was divided into three equal groups. Each group was asked to apply the methodology to the case study. Individuals in each group were asked to review the case study and software development methodology. Then using the instrument, the individuals were asked to evaluate the effectiveness of the software development methodology, thereby providing a means for evaluated effectiveness, without conducting years of testing. The responses of the three groups were compared to one another. The results indicated a significantly higher level of approval for those methodologies that guided the development activities, standardized the development process, and identified the development phases and deliverables. It was concluded that utilizing a software development methodology that guides, standardizes, and defines the development phases and deliverables will result in an improved software development process and software quality. Further investigation could validate the findings of this research. The results actually achieved from utilizing the methodology developed for the scheduling department compared with the results achieved from utilizing some other methodology could further validate these research findings. Additional research could examine, over an extended time period, the success of the software development process and software quality of those projects utilizing the methodology described in this dissertation.

APA, Harvard, Vancouver, ISO, and other styles

6

Knapp, Chris H. "Unlocking test-driven development." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/CKnapp2006.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Antia, Yezdi F. "Personal computer development system software architecture." Thesis, Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/104287.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Abbas, Noura. "Software quality and governance in agile software development." Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.

Full text

Abstract:

Looking at software engineering from a historical perspective, we can see how software development methodologies have evolved over the past 50 years. Using the right software development methodology with the right settings has always been a challenge. Therefore, there has always been a need for empirical evidence about what worked well and what did not, and what factors affect the different variables of the development process. Probably the most noticeable change to software development methodology in the last 15 years has been the introduction of the word “agile”. As any area matures, there is a need to understand its components and relations, as well as the need of empirical evidence about how well agile methods work in real life settings. In this thesis, we empirically investigate the impact of agile methods on different aspects of quality including product quality, process quality and stakeholders’ satisfaction as well as the different factors that affect these aspects. Quantitative and qualitative research methods were used for this research, including semi-structured interviews and surveys. Quality was studied in two projects that used agile software development. The empirical study showed that both projects were successful with multiple releases, and with improved product quality and stakeholders’ satisfaction. The data analysis produced a list of 13 refined grounded hypotheses out of which 5 were supported throughout the research. One project was studied in-depth by collecting quantitative data about the process used via a newly designed iteration monitor. The iteration monitor was used by the team over three iterations and it helped identify issues and trends within the team in order to improve the process in the following iterations. Data about other organisations collected via surveys was used to generalise the obtained results. A variety of statistical analysis techniques were applied and these suggested that when agile methods have a good impact on quality they also has a good impact on productivity and satisfaction, also when agile methods had good impact on the previous aspects they reduced cost. More importantly, the analysis clustered 58 agile practices into 15 factors including incremental and iterative development, agile quality assurance, and communication. These factors can be used as a guide for agile process improvement. The previous results raised questions about agile project governance, and to answer these questions the agile projects governance survey was conducted. This survey collected 129 responses, and its statistically significant results suggested that: retrospectives are more effective when applied properly as they had more impact when the whole team participated and comments were recorded, that organisation size has a negative relationship with success, and that good practices are related together as when a team does one aspect well, they do all aspects well. Finally, the research results supported the hypotheses: agile software development can produce good quality software, achieve stakeholders’ satisfaction, motivate teams, assures quick and effective response to stakeholder’s requests, and it goes in stages, matures, and improves over time.

APA, Harvard, Vancouver, ISO, and other styles

9

Norman, Michael John. "SSDE : structured software development environment." Master's thesis, University of Cape Town, 1990. http://hdl.handle.net/11427/15899.

Full text

Abstract:

Bibliography: pages 219-230.
Software engineers have identified many problem areas regarding the development of software. There is a need for improving system and program quality at design level, ensuring that design costs remain within the budget, and increasing the productivity of designers. Structured Software Development Environment (SSDE) provides the system designer with an interactive menu-driven environment, and a framework within which he can conveniently express and manipulate his proposed solution. This representation is in terms of both a conceptual model and a detailed software logic definition. Thus SSDE provides tools for both high-level (or logical) and low-level (or physical) design. It allows a user to follow his own preferred methodology rather than restricting him to one specific strategy. SSDE builds and maintains databases that record all design decisions. It provides the system designer with a mechanism whereby systems can easily be modified and new systems can evolve from similar existing systems. There are several auxiliary facilities as productivity aids. SSDE generates PASCAL code for low-level design constructs, ·full documentation of both the high- and low-level designs for inclusion in the project file, as well as a skeleton manual. The system was evaluated by a number of independent users. This exercise clearly demonstrated its success as an aid in expressing, understanding, manipulating and solving software development problems.

APA, Harvard, Vancouver, ISO, and other styles

10

Abdullahi, Abdille. "Component-based Software development." Thesis, Växjö University, School of Mathematics and Systems Engineering, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:vxu:diva-2335.

Full text

Abstract:

Component-based Software development is a promising way to improve quality, time to market and handle the increasing complexity of software management. However, The component-based development is still a process with many problems, it is not well de_ned either from theoretical or practical point of view. This thesis gives a brief overview of Component-Based Software development and starts with brief historical evolution followed by a general explanation of the method. A detailed discussion of the underlying principles like components, component framework and compent system architecture are then presented. Some real world component stadards such as .net framework, CORBA CCM and EJB are given in detail. Finally, simple fille-sharing-program based on Apache's Avalon framework and another one based on .net framework are developed as a case study.

APA, Harvard, Vancouver, ISO, and other styles

11

Mäkäräinen, Minna. "Software change management processes in the development of embedded software /." Espoo [Finland] : Technical Research Centre of Finland, 2000. http://www.vtt.fi/inf/pdf/publications/2000/P416.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Baker, Wilfred G. "A software requirement development model." Master's thesis, This resource online, 1993. http://scholar.lib.vt.edu/theses/available/etd-12162009-020042/.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Kortetjärvi, Fredrik, and Rohullah Khorami. "Software development of visualizationsystem." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-44789.

Full text

Abstract:

Today wireless technologies are increasing in the automation systems used in homes and buildings. More electrical devices are used in a house to save time, money, and energy because they are relatively inexpensive and easy to install; these devices even allow smart components such as mobile tablets and computer connectivity. To connect all these devices for data transmission purposes and easy access, the KNX is the best choice. The KNX standard is an open standard for home and building automation. KNX standard supports different communication media such as Twisted pairs, Power line, Radio Frequency, and tunnelling IP. KNX system is a bus system for building control, making all electrical and smart devices in a KNX system use the same transmission method and exchange telegrams via a shared bus network. To check and control all the electrical devices in a home or an apartment takes time; that is why there is a massive need for applications to make every room’s controlling process much easier and take a much shorter time. This project is about designing and implementing a visualization application for windows and .NET for managing and comparing input data with the actual data. This application is equipped with a KNX bus driver to communicate with hardware in a building. The practical part of the application is to take some raw data and then sort them in a specific way to minimize the time of controlling the process of the KNX devices in a building.

APA, Harvard, Vancouver, ISO, and other styles

14

Hellström, Andreas, and Anatoly Chervyakov. "Global Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1687.

Full text

Abstract:

Global Software Development is an area that has been recently highlighted. Translation is usually an issue that people associate with adapting software for a specific country but it is much more than that. Through text representation and data formatting you can go deep into cultural aspects that affect the user interface and even the core functionality. In this thesis we will discuss just how these matters can affect development of global software. To carry out the investigation we analyzed current approaches and references and build up an extended methodology with suggestions to develop global software applications.
Utveckling av globala programvara är ett område som den senaste tiden har uppmärksammats. Översättning är vanligtvis en fråga som människor associerar med att anpassa programvaror för ett specifikt land men det är mycket mer än det. Man kan gå djupare in i kulturella aspekter som kan påverka användargränssnitt och även mjukvarans kärna. I den här uppsatsen diskuterar vi hur dessa aspekter kan påverka utveckling av global programvara. För att genomföra vårt arbete analyserades vi först befintliga metodologier och byggde upp en utökad metodologi med förslag på hur man kan utveckla global programvara.
0737 305407 0708 230374

APA, Harvard, Vancouver, ISO, and other styles

15

Yacoub, Sherif M. "Pattern-oriented analysis and design (POAD) a methodology for software development /." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=1026.

Full text

Abstract:

Thesis (Ph. D.)--West Virginia University, 1999.
Title from document title page. Document formatted into pages; contains xx, 343 p. : ill. (some col.). Vita. Includes abstract. Includes bibliographical references (p. 324-337).

APA, Harvard, Vancouver, ISO, and other styles

16

Traino, Anthony J. "Automation of software development metrics." [Denver, Colo.] : Regis University, 2008. http://165.236.235.140/lib/ATraino2008.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Ghali, Nagi. "Managing software development knowledge: A conceptually-oriented software engineering environment (COSEE)." Thesis, University of Ottawa (Canada), 1993. http://hdl.handle.net/10393/6565.

Full text

Abstract:

Software development, especially for large and complex systems, has long been recognized as a difficult and expensive process. Major software development problems (such as insufficient reuse of software, inadequate machine assistance for software developers, uncoordinated tools, excessive time spent during the maintenance phase, and poor documentation) have not yet been properly addressed. Most current software development environments do not provide satisfactory solutions for these problems. In our research, we investigated these problems and we will suggest a solution that will help to eliminate some of them. We built an environment called COSEE (Conceptually-Oriented Software Engineering Environment), on top of a knowledge management system (CODE). In COSEE, we captured three most important types of knowledge needed by software developers/maintainers: domain knowledge, design knowledge, and implementation knowledge. We dynamically linked COSEE to the programming environment (Smalltalk-80) to create a unified knowledge management system for software development. We used the object-oriented approach as our design methodology and Smalltalk-80 as our implementation language. We illustrated our approach using the ATM (Automated Teller Machine) example.

APA, Harvard, Vancouver, ISO, and other styles

18

Mkpong-Ruffin, Idongesit Okon Umphress David A. Hamilton John A. "Quantitative risk assessment model for software security in the design phase of software development." Auburn, Ala., 2009. http://hdl.handle.net/10415/1584.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Crunk, John. "Examining Tuckman's Team Theory in Non-collocated Software Development Teams Utilizing Collocated Software Development Methodologies." Thesis, Capella University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10929105.

Full text

Abstract:

The purpose of this qualitative, multi-case study was to explain Tuckman’s attributes within software development when using a collocated software designed methodology in a non-collocated setting. Agile is a software development methodology that is intended for use in a collocated setting; however, organizations are using it in a non-collocated setting, which is increasing the software errors in the final software product. The New Agile Process for Distributed Projects (NAPDiP) was developed to fix these software errors that arise when using Agile in a non-collocated setting but have not been effective. This research utilized Tuckman's team theory to explore the disparity related to why these errors still occur. The research question asked is how software development programmers explain Tuckman's attributes (i.e., forming, storming, norming, performing) on software development projects. The study adopted a qualitative model using nomothetic major and minor themes in the exploration of shared expressions of sentiments from participants. The study’s population came from seven participants located in the United States and India who met the requirement of using the Agile development methodology and work for organizations on teams with a size of at least thirty individuals from various organizations. A total of seven participants reached saturation in this multi-case study supporting the research question explored. The findings of the research demonstrated that development teams do not meet all stages and attributes of Tuckman’s team development. Future research should explore additional ways that software development teams satisfy a more significant number of Tuckman’s team development stages.

APA, Harvard, Vancouver, ISO, and other styles

20

Cornut, Francis. "The discursive constitution of software development." Thesis, London School of Economics and Political Science (University of London), 2009. http://etheses.lse.ac.uk/258/.

Full text

Abstract:

The successful development of software continues to be of central interest, both as an academic topic and in professional practice. Consequently, several software development approaches and methodologies have been developed and promoted over the past decades. However, despite the attention given to the subject and the methodical support available, software development and how it should be practiced continue to be controversial. This thesis examines how beliefs about software development come to be socially established as legitimate, and how they come to constitute software development practices in an organization. It is argued that the emergence of a dominant way of conceiving of and practicing software development is the outcome of power relations that permeate the discursive practices of organizational actors. The theoretical framework of this study is guided by Pierre Bourdieu’s theory of symbolic violence and organizational discourse theory. As a research method, ethnographic research techniques are utilized as part of a case study to gain deep insights into the standardization of software development practices. The research site is the IT division of a large financial services organization and is composed of ten units distributed across eight countries. The tumultuous development of a knowledge management programme intended to institutionalize a standard software development process across the organization’s units provides the case for this research. This thesis answers the call for studies providing detailed accounts of the sociopolitical process by which technically oriented practices are transferred and standardized within organizations. It is submitted that a discourse theoretical approach informed by Bourdieu’s thinking enables us to conceptualize this process in a more meaningful, and theoretically rigorous, manner. In providing this theoretical approach, the thesis seeks to contribute to current research on technology and innovation management, and to offer guidance on some issues concerning the management of the software development process.

APA, Harvard, Vancouver, ISO, and other styles

21

Martin, Timothy Patrick. "Flexible manufacturing system software development using simulation." Thesis, Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/101236.

Full text

Abstract:

This paper presents a hierarchical modeling method that can be used to simulate a Flexible Manufacturing System (FMS) at all levels of detail. The method was developed specifically to aid the software development needed for the hierarchy of computers that are present in an FMS. The method was developed by modeling an existing FMS. The models developed of the existing FMS are described in detail to provide an example of how to model other FMSs. The basic building blocks needed for designing other FMSs with this modeling method are provided. The models were written in the SIMAN simulation language. SIMAN was found to be an easy language to use for the hierarchical modeling of FMSs.
M.S.

APA, Harvard, Vancouver, ISO, and other styles

22

Ness, Paul Edward. "Creative software development : an empirical modelling framework." Thesis, University of Warwick, 1997. http://wrap.warwick.ac.uk/3059/.

Full text

Abstract:

The commercial success of software development depends on innovation [Nar93a]. However, conventional approaches inhibit the development of innovative products that embody novel concepts. This thesis argues that this limitation of conventional software development is largely due to its use of analytical artefacts, and that other activities, notably Empirical Modelling and product design, avoid the same limitation by using creative artefacts. Analytical artefacts promote the methodical representation of familiar subjects whereas creative artefacts promote the exploratory representation of novel subjects. The subjects, constraints, environments and knowledge associated with a design activity are determined by the nature of its artefacts. The importance of artefacts was discovered by examining the representation of different kinds of lift system in respect of Empirical Modelling, product design and software development. The artefacts were examined by identifying creative properties, as characterized in the theory of creative cognition [FWS92], together with their analytical counterparts. The processes of construction were examined by identifying generative and exploratory actions. It was found that, in software development, the artefacts were analytical and the processes transformational, whereas, in Empirical Modelling and product design, the artefacts were both creative and analytical, and the processes exploratory. A creative approach to software development using both creative and analytical artefacts is proposed for the development of innovative products. This new approach would require a radical departure from the established ideas and principles of software development. The existing paradigm would be replaced by a framework based on Empirical Modelling. Empirical Modelling can be though of as a situated approach to modelling that uses the computer in exploratory ways to construct artefacts. The likelihood of the new paradigm being adopted is assessed by considering how it addresses the topical issues in software development.

APA, Harvard, Vancouver, ISO, and other styles

23

Xiong, Jie 1974. "Addressing concurrency using UML-based software development." Thesis, McGill University, 2004. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=81457.

Full text

Abstract:

Distributed systems, systems that interact with real-time devices, responsive GUI interfaces, systems that interact with hundreds of clients simultaneously have to function correctly even in a concurrent environment. Complex concurrent activities and interactions however make the development, i.e. understanding, analyzing, designing and implementing, of such systems extremely difficult. It is important to have a systematic approach to treat the many issues when developing concurrent systems.
In this thesis, we describe an approach that addresses concurrency in all phases of object-oriented software development. We show how to identify inherent concurrency at early stages of the development, and we propose a way to systematically refine the resulting declarative specification into an object-oriented design, which controls concurrency and provides data consistency using transactions or monitors.

APA, Harvard, Vancouver, ISO, and other styles

24

Moran, Kevin Patrick. "Automating Software Development for Mobile Computing Platforms." W&M ScholarWorks, 2018. https://scholarworks.wm.edu/etd/1550153845.

Full text

Abstract:

Mobile devices such as smartphones and tablets have become ubiquitous in today's computing landscape. These devices have ushered in entirely new populations of users, and mobile operating systems are now outpacing more traditional "desktop" systems in terms of market share. The applications that run on these mobile devices (often referred to as "apps") have become a primary means of computing for millions of users and, as such, have garnered immense developer interest. These apps allow for unique, personal software experiences through touch-based UIs and a complex assortment of sensors. However, designing and implementing high quality mobile apps can be a difficult process. This is primarily due to challenges unique to mobile development including change-prone APIs and platform fragmentation, just to name a few. in this dissertation we develop techniques that aid developers in overcoming these challenges by automating and improving current software design and testing practices for mobile apps. More specifically, we first introduce a technique, called Gvt, that improves the quality of graphical user interfaces (GUIs) for mobile apps by automatically detecting instances where a GUI was not implemented to its intended specifications. Gvt does this by constructing hierarchal models of mobile GUIs from metadata associated with both graphical mock-ups (i.e., created by designers using photo-editing software) and running instances of the GUI from the corresponding implementation. Second, we develop an approach that completely automates prototyping of GUIs for mobile apps. This approach, called ReDraw, is able to transform an image of a mobile app GUI into runnable code by detecting discrete GUI-components using computer vision techniques, classifying these components into proper functional categories (e.g., button, dropdown menu) using a Convolutional Neural Network (CNN), and assembling these components into realistic code. Finally, we design a novel approach for automated testing of mobile apps, called CrashScope, that explores a given android app using systematic input generation with the intrinsic goal of triggering crashes. The GUI-based input generation engine is driven by a combination of static and dynamic analyses that create a model of an app's GUI and targets common, empirically derived root causes of crashes in android apps. We illustrate that the techniques presented in this dissertation represent significant advancements in mobile development processes through a series of empirical investigations, user studies, and industrial case studies that demonstrate the effectiveness of these approaches and the benefit they provide developers.

APA, Harvard, Vancouver, ISO, and other styles

25

Archer, Emory Scott. "Development of graphical software tools for molecular biology." Thesis, Hong Kong : University of Hong Kong, 1997. http://sunzi.lib.hku.hk/hkuto/record.jsp?B19974218.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Salvatore, Ricardo Brigatto. "Using open source software in visual simulation development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2005. http://library.nps.navy.mil/uhtbin/hyperion/05Sep%5FSalvatore.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Pullen, Andrew Mark. "Motion development for computer animation." Thesis, University of Cambridge, 1987. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.278403.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Teo, Ching Leong. "Bistatic radar system analysis and software development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03Dec%5FTeo%5FChing.pdf.

Full text

Abstract:

Thesis (M.S. in Engineering Science)--Naval Postgraduate School, December 2003.
Thesis advisor(s): David C. Jenn, D. Curtis Schleher. Includes bibliographical references (p. 95-96). Also available online.

APA, Harvard, Vancouver, ISO, and other styles

29

Hart, Charles Fredrick. "Construction software using feature contexts." Diss., Georgia Institute of Technology, 1991. http://hdl.handle.net/1853/8180.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Ziegenhagen, Lynzi. "Evaluating configuration management tools for high assurance software development projects." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03Jun%5FXiegenhagen.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Lindmark, Fanny, and Hanna Kvist. "Security in software : How software companies work with security during a software development process." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-130964.

Full text

Abstract:

This study is conducted, due to recent interest in privacy and software security, on how a number of software development companies work during a development process to develop secure software to the possible extent. The study is based on four interviews with four software companies located in Linköping, Sweden. The interviews followed a semi-structured format to ensure the possibility to compare the given answers from the companies to each other. This structure was chosen to give each company the liberty to express what they valued and thought were important during a software development process. The aim was to analyze how and if these companies work with security when developing software, and to see what differences and similarities that could be established. We found differences between the companies' perspective of security and on their methods of working. Some valued secure software more than others and performed more measures to ensure it. We also found some similarities on their view on importance of secure software and ways to work with it. The differences and similarities were related to the size of the companies, their resources, the types of products they develop, and the types of clients they have.

APA, Harvard, Vancouver, ISO, and other styles

32

Justin, Ken. "Development of electrocardiographic image processing software." Thesis, Massachusetts Institute of Technology, 1993. http://hdl.handle.net/1721.1/72288.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Allen, Gary. "Software development methods for educational use." Thesis, University of Huddersfield, 1994. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.385922.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Demir, Kadir Alpaslan. "Analysis of TLcharts for weapon systems software development." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2005. http://library.nps.navy.mil/uhtbin/hyperion/05Dec%5FDemir.pdf.

Full text

Abstract:

Thesis (M.S. in Computer Science and M.S. in Software Engineering)--Naval Postgraduate School, December 2005.
Thesis Advisor(s): Doron Drusinsky, Man-Tak Shing. Includes bibliographical references (p. 87-89). Also available online.

APA, Harvard, Vancouver, ISO, and other styles

35

King, Barbara M. "A Software Development Life-Cycle Model for Web-Based Application Development." NSUWorks, 2004. http://nsuworks.nova.edu/gscis_etd/636.

Full text

Abstract:

Software development life cycle models were believed to play a critical role in improving software quality by guiding tasks in the software development processes since being formally introduced and embraced in the 1970s. Many organizations attempted to deploy software development life cycle methodologies with the intent to improve the software development process from conception through implementation to delivery. Numerous established software development models exist, including the classic waterfall life cycle model, Spiral model, Prototyping, Evolutionary, (e.g., Staged, Phased, and Timebox models), object-oriented design (OOD) (e.g., Rational Unified Process), and agile processes (e.g., eXtreme Programming [XP]). The design and development of web-based applications introduced new problems and requirements that did not exist when traditional software development life-cycle models were being put into practice. This research presents empirical software development practice data pertaining to web-based application development. The goal of this project was to answer the question, "What is the general paradigm of an SDLC model for web-based application development?" The focus of the project was to derive an empirical SDLC model for web-based application development. Data from current practices was collected via a web-based application. Study participants used the web-based application to input data concerning the SDLC model of their web-based application development process. The empirical model was derived from the data provided by participants on current professional web-based application development practices. The results of this research showed that although web-based application development life-cycle does parallel traditional SDLCs in some phases, there were enough differences that an exact fit to an existing model does not exist. A modified version of the Classic Waterfall with some repetitiveness of the Spiral model with the addition of optional phases best met the situational requirements of web-based application development.

APA, Harvard, Vancouver, ISO, and other styles

36

Chipunza, Enciliah. "Quality management challenges in iterative software product development of a selected software development organisation in Cape Town, South Africa." Thesis, Cape Peninsula University of Technology, 2018. http://hdl.handle.net/20.500.11838/2779.

Full text

Abstract:

Thesis (MTech (Business Information Systems))--Cape Peninsula University of Technology, 2018.
Many software organisations using iterative software development approach use practices that relate to quality management. However, the quality management process has been inadequate. Despite many research studies conducted on quality management in iterative software product development none have adequately addressed the challenges and mitigation techniques to have an adequate process that leads to a quality software product. The objective of this study was to determine factors that affect the quality management process in iterative software development. The research followed a qualitative approach, a case of software organisation SasTech in Cape Town, South Africa. 22 interviews were conducted on three roles actively involved in the software product development process. These are product management, quality assurance and software developers. Themes were drawn from results and were tabulated. The duality of technology theory was used as a theoretical lens to data analysis. Several factors were identified to influence the software quality management process. These include planning, documentation, process ownership, technologies, testing, timelines and management support. Through the general proposed framework, facilities (human resources and technologies), interpretive schemes (architecture) and norms (practices) of software quality management can be institutionalised leading to adequate and effective quality management in iterative development for SasTech as well as other organisations in the same industry.

APA, Harvard, Vancouver, ISO, and other styles

37

Moyer, Daniel Raymond. "Software development resource estimation in the 4th generation environment." Thesis, Kansas State University, 1986. http://hdl.handle.net/2097/9956.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Flaten, Kayla. "The Progression of Agile Software Development." Scholarship @ Claremont, 2017. http://scholarship.claremont.edu/cmc_theses/1717.

Full text

Abstract:

This paper examines the use of Agile Software Development in the technology industry and how it came to be one of the leading models used in project management. By investigating the software development methods used in the late 1900s, it becomes clear where the system needed improvement in order to improve the efficiency in developing products. In investigating the Agile Manifesto, new and essential components are introduced that become vital in successfully producing a product. From this, it is easier to understand why Agile is so commonly used in the software development industry and how it became so effective.

APA, Harvard, Vancouver, ISO, and other styles

39

Nascimento, Maria Elenita Menezes. "SMM (Software Management Model) : a multidimensional and integrative software development management model." Thesis, University of Manchester, 1992. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.386037.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Fischer, Scott Edward. "Standard form 254 generation software." Thesis, Georgia Institute of Technology, 1991. http://hdl.handle.net/1853/22386.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Oluyomi, Ayodele. "Patterns and protocols for agent oriented software development /." Connect to thesis, 2006. http://eprints.unimelb.edu.au/archive/00002780.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Littlefair, Tim. "An investigation into the use of software code metrics in the industrial software development environment." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 2001. https://ro.ecu.edu.au/theses/1508.

Full text

Abstract:

This work describes a project that investigates the use of software metrics based on measurement of source code in industrial software development. Literature is examined relating to considerations of quality in industry; to software engineering; to emergent technologies in the software industry including the object-oriented paradigm and software patterns; to software product and process metrics; and to cultural factors affecting workplaces in the software industry. It then expounds theoretical and practical work aimed at specifying, designing and implementing a source code analyzer for use in a typical industrial project setting. There is an explanation of the design and outcomes of a questionnaire survey, conducted over the Internet, of developers with an interest in using metrics techniques to analyse source code. Finally, there is a description of a controlled experiment which attempts to detect a benefit from use of source code metrics as information to support a simple software engineering task.

APA, Harvard, Vancouver, ISO, and other styles

43

Geldrez, Cecilia. "Quality engineering activities in object-oriented software development." Thesis, University of Ottawa (Canada), 1996. http://hdl.handle.net/10393/9926.

Full text

Abstract:

Testability is a measure of how easy (less complex, less tedious, less boring, less costly) the effective testing of implementation is made. In Object-Oriented development, testability is a result of (1) the characteristics of Object-Oriented implementations, (2) the test support environment, (3) the characteristics of representations (i.e. notations) and (4) the software process in which testing is conducted (67). In this thesis, we examine in details the last two factors. When addressing the characteristics of notations, we determine that notations should exhibit the basic testability attributes of completeness, correctness, consistency and incorporation. In order for notations to exhibit these attributes, they must be verifiable, modifiable and traceable. The latter three are referred to as testability requirements. Testable notations provide the ability to (1) uncover errors early in the process, (2) generate test cases, (3) guide the testing of the implementation and (4) facilitate the location of source(s) of error(s) for modification. We identify testing activity types that are decoupled from the syntax of notations and from development methodologies. These testing activity types define what needs to be tested (e.g. different semantics) as well as coverage criteria. They are generic in the sense that they are refinable (i.e. adaptable to different levels of detail) in order to be uniformly applied at all phases of development. When addressing the software process in which testing is conducted, we propose that there must be an integration of development and testing activity types. Also, we propose a way of handling change in a consistent manner such that testability attributes are not lost. Examples of these changes include error correction, accommodation of new requirements, etc. (Abstract shortened by UMI.)

APA, Harvard, Vancouver, ISO, and other styles

44

Minton, Susan. "Model-driven software development techniques and case study /." [Denver, Colo.] : Regis University, 2007. http://165.236.235.140/lib/SMinton2007.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Bortz, Kent. "Coverage testing in a production software development environment." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/KBortz2006.pdf.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Walsh, Martha Geiger. "A system of automated tools to support control of software development through software configuration management." Thesis, Kansas State University, 1985. http://hdl.handle.net/2097/9892.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Cuin, Henri Mathieu. "Development of tax analysis software." Thesis, McGill University, 2000. http://digitool.Library.McGill.CA:80/R/?func=dbin-jump-full&object_id=33325.

Full text

Abstract:

The never-ending changes in the mineral industry environment require fast reactions on the part of governments in adapting their mining tax policies. The fiscal analysis software developed for this Master of Engineering and commissioned by the Quebec Ministry of Natural Resources provides the provincial authorities with a quick method of assessing the tax burden of a mining project located in Quebec. It also allows comparison of Quebec's tax burden with that of other Canadian mining provinces as well as the analysis of fiscal changes on a mine's profitability. The use of the software is illustrated by analyzing the effect of inflation and price cycles on the tax burden of a hypothetical mining project located in Quebec. The behavior of specific tax provisions with respect to these factors is emphasized.
The report starts with a general review of mineral resource taxation and fiscal instruments available to governments. This is followed by the documentation of mineral taxation in Quebec, Ontario and British Columbia, three important Canadian mining provinces. The general design and programming of tax analysis software is then described and discussed. The thesis concludes with an analysis of two major economic factors that impact on the tax burden of a mining project, inflation and commodity price cycles.

APA, Harvard, Vancouver, ISO, and other styles

48

Råman, Jari. "Regulating secure software development : analysing the potential regulatory solutions for the lack of security in software /." Rovaniemi : University of Lapland, 2006. http://www.loc.gov/catdir/toc/fy0803/2006499062.html.

Full text

APA, Harvard, Vancouver, ISO, and other styles

49

Abuseta, Yousef M. "AutoTaSC : model driven development for autonomic software engineering." Thesis, Liverpool John Moores University, 2009. http://researchonline.ljmu.ac.uk/5927/.

Full text

Abstract:

Whilst much research progress has been achieved towards the development of autonomic software engineering tools and techniques including: policy-based management, modelbased development, service-oriented architecture and model driven architecture. They have often focused on and started from chosen object-oriented models of required software behaviour, rather than domain model including user intentions and/or software goals. Such an approach is often reported to lead to "misalignment" between business process layer and their associated computational enabling systems. This is specifically noticeable in adaptive and evolving business systems and/or processes settings. To address this long-standing problem research has over the years investigated many avenues to close the gap between business process modelling and the generation of enactment (computation) layer, which is responsive to business changes. Within this problem domain, this research sets out to study the extension of the Model Driven Development (MOD) paradigm to business/domain model, that is, how to raise the abstraction level of model-driven software development to the domain level and provide model synchronisation to trace and analyse the impact of a given model change. The main contribution of this research is the development of a MOD-based design method for autonomic systems referred to as AutoTaSC. The latter consists of a series of related models, where each of which represents the system under development at a given stage. The first and highest level model represents the abstract model referred to as the Platform Independent Model (PIM). The next model encapsulates the PIM model for the autonomic system where the autonomic capabilities and required components (such as monitor, sensor, actuator, analyser, policy, etc.) are added via some appropriate transformation rules. Targeting a specific technology involves adding, also via transformation rules, specific information related to that platform from which the Platform Specific Model (PSM) for the autonomic system is extracted. In the last stage, code can be generated for the specific platform or technology targeted in the previous stage, web services for instance. In addition, the AutoTaSC method provides a situated model synchronisation mechanism, which is designed following the autonomic systems principles. For instance, to guarantee model synchronisation each model from each AutoTaSC stage has an associated policy-based feedback control loop, which regulates its reaction to detected model change. Thus, AutaTase method model transformation approach to drive model query, view and synchronisation. The Auto'Iast? method was evaluated using a number of benchmark case-studies to test this research hypothesis including the effectiveness and generality of AutaTaSe design method.

APA, Harvard, Vancouver, ISO, and other styles

50

Herrera, Acuna Raul. "Advanced computer vision-based human computer interaction for entertainment and software development." Thesis, Kingston University, 2014. http://eprints.kingston.ac.uk/29884/.

Full text

Abstract:

In this thesis we propose novel methods for 3D interaction on 3D environments. The evaluation of these methods was performed based on three interaction environments: 3D interaction using portable multi-touch devices, 3D hand gesture data manipulation using 3D database representation and 3D multi-threaded programing using hand gesture interaction. The three experiments provided qualitative and quantitative information to evaluate the features of the presented interfaces. The first experiment, based on the use on the use of portable multi-touch devices, aimed to evaluate the use of 3D movements to interact under a 3D environment. Also, the possibility of generate collaborative interaction under 3D interfacing (simulating a 3D multi-touch table top environment) was evaluated. The second experiment consisted on 3D touchless data manipulation, removing the intermediate device (portable multi-touch) and providing hand gesture data interaction using the Kinect device. Furthermore, this evaluation was conducted over a 3D cube database model, based on the concepts of multidimensional databases and graphic databases. The third experiment intended to evaluate the possibility of software generation using a 3D interaction environment, following a similar model of interaction from the second experiment, but providing a better two handed interaction. The environment aimed multi-threaded programing under a 3D interface. The three experiments provided valuable data about users’ interaction and preference, which were tested with users of different ages and levels of knowledge. The research process and results are summarized in this research work.

APA, Harvard, Vancouver, ISO, and other styles

We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!