Siga este link para ver outros tipos de publicações sobre o tema: Computer software.
Teses / dissertações sobre o tema "Computer software"
Crie uma referência precisa em APA, MLA, Chicago, Harvard, e outros estilos
Veja os 50 melhores trabalhos (teses / dissertações) para estudos sobre o assunto "Computer software".
Ao lado de cada fonte na lista de referências, há um botão "Adicionar à bibliografia". Clique e geraremos automaticamente a citação bibliográfica do trabalho escolhido no estilo de citação de que você precisa: APA, MLA, Harvard, Chicago, Vancouver, etc.
Você também pode baixar o texto completo da publicação científica em formato .pdf e ler o resumo do trabalho online se estiver presente nos metadados.
Veja as teses / dissertações das mais diversas áreas científicas e compile uma bibliografia correta.
1
Wallace, Julia. "Quantum computer software." Thesis, University of Exeter, 2001. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.369975.
Texto completo da fonte
2
Quinn, Paul. "Computer aided software production." Thesis, Queen's University Belfast, 1986. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.317077.
Texto completo da fonte
3
Katiyar, Kirti. "CARES - Computer Aided Rehabilitation Software." CSUSB ScholarWorks, 2005. https://scholarworks.lib.csusb.edu/etd-project/2857.
Texto completo da fonteResumo:
This project was done with the vision that it would simplify and improve outpatient treatment of substance abusers through a rehabilitation software program with 24-7 access availability. By developing an easy-to-use interface for out-patient substance abuse patients, they along with their counselors, administrators and insurance agencies, will be able to facilitate continuous communication during the course of a patient's treatment.
4
Pei, Breivold Hongyu. "Software Architecture Evolution and Software Evolvability." Licentiate thesis, Mälardalen University, School of Innovation, Design and Engineering, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-4540.
Texto completo da fonteResumo:
<p>Software is characterized by inevitable changes and increasing complexity, which in turn may lead to huge costs unless rigorously taking into account change accommodations. This is in particular true for long-lived systems. For such systems, there is a need to address evolvability explicitly during the entire lifecycle, carry out software evolution efficiently and reliably, and prolong the productive lifetime of the software systems.</p><p>In this thesis, we study evolution of software architecture and investigate ways to support this evolution. The central theme of the thesis is how to analyze software evolvability, i.e. a system’s ability to easily accommodate changes. We focus on several particular aspects: (i) what software characteristics are necessary to constitute an evolvable software system; (ii) how to assess evolvability in a systematic manner; (iii) what impacts need to be considered given a certain change stimulus that results in potential requirements the software architecture needs to adapt to, e.g. ever-changing business requirements and advances of technology.</p><p>To improve the capability in being able to on forehand understand and analyze systematically the impact of a change stimulus, we introduce a software evolvability model, in which subcharacteristics of software evolvability and corresponding measuring attributes are identified. In addition, a further study of one particular measuring attribute, i.e. modularity, is performed through a dependency analysis case study.</p><p>We introduce a method for analyzing software evolvability at the architecture level. This is to ensure that the implications of the potential improvement strategies and evolution path of the software architecture are analyzed with respect to the evolvability subcharacteristics. This method is proposed and piloted in an industrial setting.</p><p>The fact that change stimuli come from both technical and business perspectives spawns two aspects that we also look into in this research, i.e. to respectively investigate the impacts of technology-type and business-type of change stimuli.</p>
5
Jhunjhunwala, Manish. "Software tool for reliability estimation." Morgantown, W. Va. : [West Virginia University Libraries], 2001. http://etd.wvu.edu/templates/showETD.cfm?recnum=1801.
Texto completo da fonteResumo:
Thesis (M.S.)--West Virginia University, 2001.<br>Title from document title page. Document formatted into pages; contains x, 125 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 72-74).
6
Le, Gal Thierry. "Re-engineering software for integration using computer aided software engineering." Thesis, This resource online, 1992. http://scholar.lib.vt.edu/theses/available/etd-06232009-063016/.
Texto completo da fonte
7
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.
Texto completo da fonte
8
Cook, Carl Leslie Raymond. "Towards Computer-Supported Collaborative Software Engineering." Thesis, University of Canterbury. Computer Science and Software Engineering, 2007. http://hdl.handle.net/10092/1140.
Texto completo da fonteResumo:
Software engineering is a fundamentally collaborative activity, yet most tools that support software engineers are designed only for single users. There are many foreseen benefits in using tools that support real time collaboration between software engineers, such as avoiding conflicting concurrent changes to source files and determining the impact of program changes immediately. Unfortunately, it is difficult to develop non-trivial tools that support real time Collaborative Software Engineering (CSE). Accordingly, the few CSE tools that do exist have restricted capabilities. Given the availability of powerful desktop workstations and recent advances in distributed computing technology, it is now possible to approach the challenges of CSE from a new perspective. The research goal in this thesis is to investigate mechanisms for supporting real time CSE, and to determine the potential gains for developers from the use of CSE tools. An infrastructure, CAISE, is presented which supports the rapid development of real time CSE tools that were previously unobtainable, based on patterns of collaboration evident within software engineering. In this thesis, I discuss important design aspects of CSE tools, including the identification of candidate patterns of collaboration. I describe the CAISE approach to supporting small teams of collaborating software engineers. This is by way of a shared semantic model of software, protocol for tool communication, and Computer Supported Collaborative Work (CSCW) facilities. I then introduce new types of synchronous semantic model-based tools that support various patterns of CSE. Finally, I present empirical and heuristic evaluations of typical development scenarios. Given the CAISE infrastructure, it is envisaged that new aspects of collaborative work within software engineering can be explored, allowing the perceived benefits of CSE to be fully realised.
9
Liberto, Samuel Matthew. "Computer software project management : an introduction." Thesis, Monterey, California. Naval Postgraduate School, 1991. http://hdl.handle.net/10945/26427.
Texto completo da fonteResumo:
This thesis addresses the general principles of computer software project management. The main objective is to aid perspective software project managers in dealing with the development and management of software projects. The definition of the classical software development life cycle is given. The components include system engineering, analysis, design, coding, testing, and maintenance. The thesis contains a description of the reasons why many software projects have cost overruns and late schedules. The variability of requirements and software complexity are two factors. Proper project management is one remedy to project cost overruns and late schedules. The components of software project management are planning, organizing, directing, and controlling. Many tables of comparisons and techniques for aiding software project management are given. State of the art software development techniques are discussed. Finally, a checklist to aid software managers when developing software is provided
10
Al-Ayoubi, Istabraq Dhia. "Stochastic models for computer software reliability." Thesis, University of Bradford, 1990. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.278826.
Texto completo da fonte
11
Antia, Yezdi F. "Personal computer development system software architecture." Thesis, Virginia Polytechnic Institute and State University, 1985. http://hdl.handle.net/10919/104287.
Texto completo da fonte
12
Chan, Pee Yuaw. "Software reliability prediction." Thesis, City, University of London, 1986. http://openaccess.city.ac.uk/18127/.
Texto completo da fonteResumo:
Two methods are proposed to find the maximum likelihood parameter estimates of a number of software reliability models. On the basis of the results from analysing 7 sets of real data, these methods are found to be both efficient and reliable. The simple approach of adapting software reliability predictions by Keiller and Littlewood (1984) can produce improved predictions, but at the same time, introduces a lot of internal noise into the adapted predictions. This is due to the fact that the adaptor is a joined-up function. An alternative adaptive procedure, which involves the parametric spline adaptor, can produce at least as good adapted predictions without the predictions being contaminated by internal noise as in the simple approach. Miller and Sofer (1986a) proposed a method for estimating the failure rate of a program non-parametrically. Here, these non-parametric rates are used to produce reliability predictions and their quality is analysed and compared with the parametric predictions.
13
Sayyad, Shirabad Jelber. "Supporting software maintenance by mining software update records." Thesis, University of Ottawa (Canada), 2003. http://hdl.handle.net/10393/29004.
Texto completo da fonteResumo:
It is well known that maintenance is the most expensive stage of the software life cycle. Most large real world software systems consist of a very large number of source code files. Important knowledge about different aspects of a software system is embedded in a rich set of implicit relationships among these files. Those relationships are partly reflected in system documentation at its different levels, but more often than not are never made explicit and become part of the expertise of system maintainers. Finding existing relations between source code components is a difficult task, especially in the case of legacy systems.
When a maintenance programmer is looking at a piece of code in a source file, one of the important questions that he or she needs to answer is: "which other files should I know about, i.e. what else might be relevant to this piece of code?". This is an example of a more general Relevance Relation that maps a set of entities in a software system into a relevance value.
How can we discover and render explicit these relationships without looking over the shoulder of a programmer involved in a maintenance task? We turn to inductive methods that are capable of extracting structural patterns or models from data. They can learn concepts or models from experience observed in the past to predict outcomes of future unseen cases.
This thesis lies at the intersection of two research fields, which has been widely ignored by researchers in the machine learning and software engineering communities. It investigates the application of inductive methods to daily software maintenance at the source code level. Therefore in this thesis we first lay out the general idea of relevance among different entities in a software system. Then using inductive learning methods and a variety of data sources used by maintenance programmers, we extract (i.e. learn) what we call a maintenance relevance relation among files in a large legacy system. In effect we learn from past maintenance experience in the form of problem reports and update records, to be able to make predictions that are useful in future maintenance activities. This relation, which is called the Co-update relation, predicts whether updating one source file may require a change in another file.
To learn the Co-update relation we have performed a large number of experiments using syntactic features such as function calls or variable definitions. We have also performed experiments that use text based features such as source code comments and problem reports, and the combination of these features. The results obtained show that while using syntactic features is encouraging in terms of the predictive power of the results of learning, using text based features yields highly accurate models, with precision and recall measures that make these models viable to be used in a real world setting. As part of the contribution of this thesis we also report on challenges encountered in the process and the lessons learned.
14
Hochstettler, William Henry. "A model for supporting multiple software engineering methods in a software environment /." The Ohio State University, 1986. http://rave.ohiolink.edu/etdc/view?acc_num=osu1487322984315003.
Texto completo da fonte
15
Dimovski, Aleksandar. "Compositional software verification based on game semantics." Thesis, University of Warwick, 2007. http://wrap.warwick.ac.uk/2398/.
Texto completo da fonteResumo:
One of the major challenges in computer science is to put programming on a firmer mathematical basis, in order to improve the correctness of computer programs. Automatic program verification is acknowledged to be a very hard problem, but current work is reaching the point where at least the foundational�· aspects of the problem can be addressed and it is becoming a part of industrial software development. This thesis presents a semantic framework for verifying safety properties of open sequ;ptial programs. The presentation is focused on an Algol-like programming language that embodies many of the core ingredients of imperative and functional languages and incorporates data abstraction in its syntax. Game semantics is used to obtain a compositional, incremental way of generating accurate models of programs. Model-checking is made possible by giving certain kinds of concrete automata-theoretic representations of the model. A data-abstraction refinement procedure is developed for model-checking safety properties of programs with infinite integer types. The procedure starts by model-checking the most abstract version of the program. If no counterexample, or a genuine one, is found, the procedure terminates. Otherwise, it uses a spurious counterexample to refine the abstraction for the next iteration. Abstraction refinement, assume-guarantee reasoning and the L* algorithm for learning regular languages are combined to yield a procedure for compositional verification. Construction of a global model is avoided using assume-guarantee reasoning and the L* algorithm, by learning assumptions for arbitrary subprograms. An implementation based on the FDR model checker for the CSP process algebra demonstrates practicality of the methods.
16
Ness, Paul Edward. "Creative software development : an empirical modelling framework." Thesis, University of Warwick, 1997. http://wrap.warwick.ac.uk/3059/.
Texto completo da fonteResumo:
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.
17
Mäkärä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.
Texto completo da fonte
18
Low, Gregory Norman. "A software licensing framework." Thesis, Queensland University of Technology, 1998.
Encontre o texto completo da fonte
19
Julian, Donald P. "Delaying-type responses for use by software decoys." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2002. http://library.nps.navy.mil/uhtbin/hyperion-image/02sep%5FJulian.pdf.
Texto completo da fonteResumo:
Thesis (M.S. in Computer Science)--Naval Postgraduate School, September 2002.<br>Thesis advisor(s): Neil C. Rowe, J. Bret Michael. Includes bibliographical references (p. 55-57). Also available online.
20
Mutha, Chetan V. "Software Fault Propagation And Failure Analysis For UML Based Software Design." The Ohio State University, 2014. http://rave.ohiolink.edu/etdc/view?acc_num=osu1404305866.
Texto completo da fonte
21
Bissland, Lesley. "Hardware and software aspects of parallel computing." Thesis, University of Glasgow, 1996. http://theses.gla.ac.uk/3953/.
Texto completo da fonteResumo:
Part 1 (Chapters 2,3 and 4) is concerned with the development of hardware for multiprocessor systems. Some of the concepts used in digital hardware design are introduced in Chapter 2. These include the fundamentals of digital electronics such as logic gates and flip-flops as well as the more complicated topics of rom and programmable logic. It is often desirable to change the network topology of a multiprocessor machine to suit a particular application. The third chapter describes a circuit switching scheme that allows the user to alter the network topology prior to computation. To achieve this, crossbar switches are connected to the nodes, and the host processor (a PC) programs the crossbar switches to make the desired connections between the nodes. The hardware and software required for this system is described in detail. Whilst this design allows the topology of a multiprocessor system to be altered prior to computation, the topology is still fixed during program run-time. Chapter 4 presents a system that allows the topology to be altered during run-time. The nodes send connection requests to a control processor which programs a crossbar switch connected to the nodes. This system allows every node in a parallel computer to communicate directly with every other node. The hardware interface between the nodes and the control processor is discussed in detail, and the software on the control processor is also described. Part 2 (Chapters 5 and 6) of this thesis is concerned with the parallelisation of a large molecular mechanics program. Chapter 5 describes the fundamentals of molecular mechanics such as the steric energy equation and its components, force field parameterisation and energy minimisation. The implementation of a novel programming (COMFORT) and hardware (the BB08) environment into a parallel molecular mechanics (MM) program is presented in Chapter 6. The structure of the sequential version of the MM program is detailed, before discussing the implementation of the parallel version using COMFORT and the BB08.
22
Addy, Edward A. "Verification and validation in software product line engineering." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=1068.
Texto completo da fonteResumo:
Thesis (Ph. D.)--West Virginia University, 1999.<br>Title from document title page. Document formatted into pages; contains vi, 75 p. : ill. (some col.). Includes abstract. Includes bibliographical references (p. 35-39).
23
Rush, Andrea Friedman. "Legal protection of computer software in Canada." Thesis, University of Ottawa (Canada), 1985. http://hdl.handle.net/10393/4750.
Texto completo da fonte
24
Turner, Michael. "Analysis of product upgrades in computer software." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1999. http://www.collectionscanada.ca/obj/s4/f2/dsk2/ftp01/MQ38551.pdf.
Texto completo da fonte
25
Race, Charles T. "Value engineering: an application to computer software." Thesis, Monterey, California. Naval Postgraduate School, 1995. http://hdl.handle.net/10945/7516.
Texto completo da fonteResumo:
The purpose of this thesis is to determine how and to what extent can the Department of the Department of the Navy's Value Engineering Program be utilized in the acquisition of computer software. A review of professional literature such as journals, perio
26
Deraman, Aziz B. "A computer-aided software maintenance process model." Thesis, University of Manchester, 1992. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.261996.
Texto completo da fonte
27
Conmy, Philippa Mary. "Safety analysis of computer resource management software." Thesis, University of York, 2005. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.428494.
Texto completo da fonte
28
Buell, Robert K. "A GENERIC TELEMETRY HOST COMPUTER SOFTWARE ARCHITECTURE." International Foundation for Telemetering, 1985. http://hdl.handle.net/10150/615739.
Texto completo da fonteResumo:
International Telemetering Conference Proceedings / October 28-31, 1985 / Riviera Hotel, Las Vegas, Nevada<br>A generic software architecture has been developed to support the typical functionality required of the host computer in a telemetry ground station system. The architecture provides sufficient flexibility to permit support of the wide spectrum of requirements typically placed on such systems, while at the same time providing a structural shell which helps to minimize the complexity of applications software. The general issues addressed by this architecture include:
- The need to interface to a wide variety of telemetry front end equipments.
- The need to provide a convenient consistent, and efficient operator interface to the integrated telemetry system.
- The need to support a variable amount and wide range of applications specific processing.
- The need to be adaptable across different sizes of host computers.
- The need to be adaptable across different host computer systems.
This paper defines, at a high level, the architecture that has been defined and the general data structure concepts required to make it work. It further addresses the standardized operator interface supported by the architecture and finally, summarizes the benefits that have been demonstrated to be derived through the use of this standardized approach in the development of telemetry host computer software.
29
Bhatia, Sanjay. "Software tools for computer-controlled fatigue testing." Thesis, Virginia Tech, 1986. http://hdl.handle.net/10919/45749.
Texto completo da fonteResumo:
Past efforts at implementing Load Spectrum Generation and Neuber Control have centered around minicomputers and analog circuits. The use of a personal computer to implement the tasks is presented. On implementation of the load Spectrum Generation software, the response of the Materials Testing System was investigated for distortion and attenuation. In particular, the effect of the resolution of the waveform on the test system response was noted. There was negligible attenuation for full scale frequencies of up to 20 Hz. Greater waveform resolution was required at lower frequencies than at higher frequencies. On implementation of the Neuber Control program, the accuracy obtained at the Neuber hyperbolas was noted. Better accuracy was obtained at ramp frequencies below 0.1 Hz.
Based on the results obtained after implementing the Load Spectrum Generator program and the Neuber Control program, the performance of the personal computer in controlling fatigue tests is evaluated. Cost effectiveness and versatility favor the use of a personal computer for the control of fatigue tests.<br>Master of Science
30
Griffin, Timothy R. "Computer-Aided Design Software for Torsional Analysis." Thesis, Virginia Tech, 1998. http://hdl.handle.net/10919/36548.
Texto completo da fonteResumo:
The goal of this research has been the development of an effective design tool for torsional analysis. In the hopes of achieving this goal the computer program, Torsion 1, has been created. This torsional transfer matrix program provides the user with the ability to easily model multi-rotor systems using a simple user-interface. The program is capable of modeling such components or system characteristics as continuously distributed mass, viscous and structural damping, vibration absorbers, and gear meshes with gear tooth flexibility. The analysis capabilities of the program include forcedresponse and free-vibration analyses. The forced-response analysis module is capable of determining a system’s response to a static or harmonic torsional load. The free-vibration analysis module allows is capable of determining the eigenvalues and eigenvectors for damped and undamped systems. This thesis includes an explanation of the multi-rotor transfer matrix technique employed in Torsion 1. The derivation of transfer matrices for visco-elastic vibration absorbers, pendulum absorbers, flexible gear meshes, and planetary gear trains are included in this work. Finally, the validity of the program results is verified with a set of benchmark examples.<br>Master of Science
31
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.
Texto completo da fonte
32
Abbas, Noura. "Software quality and governance in agile software development." Thesis, University of Southampton, 2009. https://eprints.soton.ac.uk/158357/.
Texto completo da fonteResumo:
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.
33
McGee, Robert W. "Accounting for software in the United States." Thesis, University of Warwick, 1986. http://wrap.warwick.ac.uk/59366/.
Texto completo da fonteResumo:
This thesis represents the first major research to be completed either in the United Kingdom or the United States on the subject of accounting for software. Part I concentrates on the financial aspects of software accounting, and consisted of in-person interviews with a number of individuals from software' vendor and user companies who are knowledgeable about software accounting. The interviews were followed by two mail questionnaires, one each to software vending company executives and software user company executives. The NAARS database was also used to determine how software accounting policies are disclosed for these two types of company. It was concluded that more than one policy exists in practice. While approximately 90% of the companies surveyed expense internally constructed software, about two-thirds capitalize the cost of purchased software. Reasons given for individual company policy seem to be based on expediency rather than good accounting theory. The interviews and questionnaire responses in Part I seemed to indicate that software vendor companies that capitaliize software find it easier to raise debt and equity capital than do companies which expense software costs. Part II presents the results of two questionnaires that were mailed to bank lending officers and one questionnaire that was mailed to financial analysts for the purpose of obtaining more information on this point. It was concluded that companies that capitalize software costs find it significantly easier to obtain bank loans than do companies that expense software costs. The effect on stock price was less clear cut, although the questionnaire responses did indicate that a company's software accounting policy does influence the value a financial analyst places on a company's stock. Part III discusses the United States federal and state tax aspects of software. Thirteen appendices giving supplementary data are also included.
34
Love, Randall James. "Predictive software design measures." Thesis, This resource online, 1994. http://scholar.lib.vt.edu/theses/available/etd-06112009-063248/.
Texto completo da fonte
35
Lim, Edwin C. "Software metrics for monitoring software engineering projects." Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 1994. https://ro.ecu.edu.au/theses/1100.
Texto completo da fonteResumo:
As part of the undergraduate course offered by Edith Cowan University, the Department of Computer Science has (as part of a year's study) a software engineering group project. The structure of this project was divided into two units, Software Engineering l and Software Engineering 2. ln Software Engineering 1, students were given the group project where they had to complete and submit the Functional Requirement and Detail System Design documentation. In Software Engineering 2, students commenced with the implementation of the software, testing and documentation. The software was then submitted for assessment and presented to the client. To aid the students with the development of the software, the department had adopted EXECOM's APT methodology as its standard guideline. Furthermore, the students were divided into groups of 4 to 5, each group working on the same problem. A staff adviser was assigned to each project group. The purpose of this research exercise was to fulfil two objectives. The first objective was to ascertain whether there is a need to improve the final year software engineering project for future students by enhancing any aspect that may be regarded as deficient. The second objective was to ascertain the factors that have the most impact on the quality of the delivered software. The quality of the delivered software was measured using a variety of software metrics. Measurement of software has mostly been ignored until recently or used without true understanding of its purpose. A subsidiary objective was to gain an understanding of the worth of software measurement in the student environment One of the conclusions derived from the study suggests that teams who spent more time on software design and testing, tended to produce better quality software with less defects. The study also showed that adherence to the APT methodology led to the project being on schedule and general team satisfaction with the project management. One of the recommendations made to the project co-ordinator was that staff advisers should have sufficient knowledge of the software engineering process.
36
Gupta, Neeraj. "Analyzing compute-intensive software performance." Thesis, Massachusetts Institute of Technology, 1995. http://hdl.handle.net/1721.1/36974.
Texto completo da fonte
37
Annavajjala, Karuna. "Java challenge software project." Morgantown, W. Va. : [West Virginia University Libraries], 1999. http://etd.wvu.edu/templates/showETD.cfm?recnum=893.
Texto completo da fonteResumo:
Thesis (M.S.)--West Virginia University, 1999.<br>Title from document title page. Document formatted into pages; contains viii, 107 p. : ill. (some col.) Vita. Includes abstract. Includes bibliographical references (p. 79-80).
38
Swart, Riaan. "A language to support verification of embedded software." Thesis, Stellenbosch : Stellenbosch University, 2004. http://hdl.handle.net/10019.1/49823.
Texto completo da fonteResumo:
Thesis (MSc)--University of Stellenbosch, 2004.<br>ENGLISH ABSTRACT: Embedded computer systems form part of larger systems such as aircraft or chemical processing
facilities. Although testing and debugging of such systems are difficult, reliability is often
essential. Development of embedded software can be simplified by an environment that limits
opportunities for making errors and provides facilities for detection of errors. We implemented
a language and compiler that can serve as basis for such an experimental environment. Both
are designed to make verification of implementations feasible.
Correctness and safety were given highest priority, but without sacrificing efficiency wherever
possible. The language is concurrent and includes measures for protecting the address spaces
of concurrently running processes. This eliminates the need for expensive run-time memory
protection and will benefit resource-strapped embedded systems. The target hardware is
assumed to provide no special support for concurrency. The language is designed to be
small, simple and intuitive, and to promote compile-time detection of errors. Facilities for
abstraction, such as modules and abstract data types support implementation and testing of
bigger systems.
We have opted for model checking as verification technique, so our implementation language
is similar in design to a modelling language for a widely used model checker. Because of
this, the implementation code can be used as input for a model checker. However, since the
compiler can still contain errors, there might be discrepancies between the implementation
code written in our language and the executable code produced by the compiler. Therefore
we are attempting to make verification of executable code feasible. To achieve this, our
compiler generates code in a special format, comprising a transition system of uninterruptible
actions. The actions limit the scheduling points present in processes and reduce the different
interleavings of process code possible in a concurrent system. Requirements that conventional
hardware places on this form of code are discussed, as well as how the format influences
efficiency and responsiveness.<br>AFRIKAANSE OPSOMMING: Ingebedde rekenaarstelsels maak deel uit van groter stelsels soos vliegtuie of chemiese prosesseerfasiliteite.
Hoewel toetsing en ontfouting van sulke stelsels moeilik is, is betroubaarheid
dikwels onontbeerlik. Ontwikkeling van ingebedde sagteware kan makliker gemaak word met
'n ontwikkelingsomgewing wat geleenthede vir foutmaak beperk en fasiliteite vir foutbespeuring
verskaf. Ons het 'n programmeertaal en vertaler geïmplementeer wat as basis kan dien vir
so 'n eksperimentele omgewing. Beide is ontwerp om verifikasie van implementasies haalbaar
te maak.
Korrektheid en veiligheid het die hoogste prioriteit geniet, maar sonder om effektiwiteit prys
te gee, waar moontlik. Die taal is gelyklopend en bevat maatreëls om die adresruimtes van
gelyklopende prosesse te beskerm. Dit maak duur looptyd-geheuebeskerming onnodig, tot
voordeel van ingebedde stelsels met 'n tekort aan hulpbronne. Daar word aangeneem dat
die teikenhardeware geen spesiale ondersteuning vir gelyklopendheid bevat nie. Die programmeertaal
is ontwerp om klein, eenvoudig en intuïtief te wees, en om vertaaltyd-opsporing van
foute te bevorder. Fasiliteite vir abstraksie, byvoorbeeld modules en abstrakte datatipes,
ondersteun implementering en toetsing van groter stelsels.
Ons het modeltoetsing as verifikasietegniek gekies, dus is die ontwerp van ons programmeertaal
soortgelyk aan dié van 'n modelleertaal vir 'n modeltoetser wat algemeen gebruik word.
As gevolg hiervan kan die implementasiekode as toevoer vir 'n modeltoetser gebruik word.
Omdat die vertaler egter steeds foute kan bevat, mag daar teenstrydighede bestaan tussen die
implementasie geskryf in ons implementasietaal, en die uitvoerbare masjienkode wat deur die
vertaler gelewer word. Daarom poog ons om verifikasie van die uitvoerbare masjienkode haalbaar
te maak. Om hierdie doelwit te bereik, is ons vertaler ontwerp om 'n spesiale formaat
masjienkode te genereer bestaande uit 'n oorgangstelsel wat ononderbreekbare (atomiese) aksies
bevat. Die aksies beperk die skeduleerpunte in prosesse en verminder sodoende die aantal
interpaginasies van proseskode wat moontlik is in 'n gelyklopende stelsel. Die vereistes wat
konvensionele hardeware aan dié spesifieke formaat kode stel, word bespreek, asook hoe die formaat effektiwiteit en reageerbaarheid van die stelsel beïnvloed.
39
Fragkos, Georgios. "An event-trace language for software decoys." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2002. http://library.nps.navy.mil/uhtbin/hyperion-image/02sep%5FFragkos.pdf.
Texto completo da fonteResumo:
Thesis (M.S. in Computer Science)--Naval Postgraduate School, September 2002.<br>Thesis advisor(s): James Bret Michael, Mikhail Auguston. Includes bibliographical references (p. 35). Also available online.
40
Bucchiarone, Antonio. "Dynamic software architectures for global computing system." Thesis, IMT Alti Studi Lucca, 2008. http://e-theses.imtlucca.it/11/1/Bucchiarone_phdthesis.pdf.
Texto completo da fonteResumo:
Modern software systems have changed from isolated static
devices to highly interconnected machines that execute their
tasks in a cooperative and coordinated manner. Therefore, the structure and the behavior of these systems are dynamic with continuous changes. These systems are known as Global Computing Systems (GCSs) and they use services as fundamental elements for developing them. Software architectural models are intended to describe the structure and behavior of a system in terms of computational entities, their interactions and its composition patterns, so to reason about systems at more abstract level, disregarding implementation details. Since a GCS may change at run-time, Software Architecture (SA) models for them should be able to describe the changes of each system and to enact modifications during system execution.
Such models are generally referred to as Dynamic Software Architectures (DSAs), to emphasize that the SA evolves during run-time. Several recent research efforts have focused on the dynamic aspects of software architectures providing suitable models and techniques for handling the run-time modification of the structure of a system. A large number of heterogeneous proposals for addressing dynamic architectures at many different levels of abstractions have been provided, such as programmable, ad-hoc, self-healing and self-repairing among others. It is then important to have a clear picture of the relations among these proposals by formulating them into a uniform framework. When this work started there were many questions that arise. How can we represent architectures? How can we formalise architectural styles? How can we construct style conformant architectures? How can we model softwarearchitecture reconfigurations? How can we ensure style consistency?
How can we express and verify structural and behavioral
architectural properties? This thesis tries to answer
them. In particular it presents a formal-based process that will be used to model and verify Software Architectures that are dynamic. The principal aspects that we have considered in this work are:
a) formalisms used in the design of SA that are dynamic;
b) mechanisms to express and verify structural and behavioral properties that we expect to be satisfied by each SA configuration;
c) a complete tool-supported process able to integrate previous aspects.
These aspects are firstly illustrated over an explanatory example and then applied and validated over a real-world case study.
41
Pereira, Ella Grishikashvili. "Impromptu : software framework for self-healing middleware services." Thesis, Liverpool John Moores University, 2006. http://researchonline.ljmu.ac.uk/5839/.
Texto completo da fonte
42
Forsyth, Henry Lee. "Evolutionary environmental modelling in self-managing software systems." Thesis, Liverpool John Moores University, 2010. http://researchonline.ljmu.ac.uk/6009/.
Texto completo da fonteResumo:
Over recent years, the increasing richness and sophistication of modem software systems has challenged conventional design-time software modelling analysis and has led to a number of studies exploring non-conventional approaches particularly those inspired by nature. The natural world routinely produces organisms that can not only survive but also flourish in changing environments as a consequence of their ability to adapt and therefore improve their fitness in relation to the external environments in which they exist. Following this biologically inspired systems' design approach, this study aims to test the hypothesis - can evolutionary techniques for runtime modelling of a given system's environment be more effective than traditional approaches, which are increasingly difficult to specify and model at design-time? This work specifically focuses on investigating the requirements for software environment modelling at runtime via a proposed systemic integration of Learning Classifier Systems and Genetic Algorithms with the well-known managerial cybernetics Viable Systems Model. The main novel contribution of this thesis is that it provides an evaluation of an approach by which software can create and crucially, maintain a current model of the environment, allowing the system to react more effectively to changes in that environment, thereby improving robustness and performance of the system. Detailed novel contributions include an evaluation of a variety of environmental modelling approaches to improving system robustness, the use of Learning Classifier Systems and genetic algorithms to provide the modelling element required of effective adaptive software systems. It also provides a conceptual framework of an Environmental Modelling, Monitoring and Adaptive system (EMMA) to manage the various elements required to achieve an effective environmental control system. The key result of this research has been to demonstrate the value of the guiding principles provided by the field of cybernetics and the potential of Beer's 2 cybernetically based Viable System Model in providing a learning framework, and subsequently a roadmap, to developing self-managing autonomic systems. The work is presented using a virtual world platform called "Second Life". This platform was used for experimental design and testing of results.
43
Abuseta, Yousef M. "AutoTaSC : model driven development for autonomic software engineering." Thesis, Liverpool John Moores University, 2009. http://researchonline.ljmu.ac.uk/5927/.
Texto completo da fonteResumo:
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.
44
McKnight, Walter Lee. "A meta system for generating software engineering environments /." The Ohio State University, 1985. http://rave.ohiolink.edu/etdc/view?acc_num=osu1487260531958418.
Texto completo da fonte
45
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.
Texto completo da fonteResumo:
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.
46
Cavalcante, Marcia Beatriz. "The impact of team software organizations on software quality and productivity." Thesis, National Library of Canada = Bibliothèque nationale du Canada, 1998. http://www.collectionscanada.ca/obj/s4/f2/dsk1/tape10/PQDD_0006/MQ44140.pdf.
Texto completo da fonte
47
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/.
Texto completo da fonteResumo:
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.
48
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.
Texto completo da fonteResumo:
Thesis (Ph. D.)--West Virginia University, 1999.<br>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).
49
Howard, Gary Allan. "Creating a software assembly line." [Denver, Colo.] : Regis University, 2007. http://165.236.235.140/lib/GHoward2007.pdf.
Texto completo da fonte
50
Allison, Ian K. "Software process improvement as emergent change : a structurational analysis." Thesis, University of Warwick, 2004. http://wrap.warwick.ac.uk/2638/.
Texto completo da fonteResumo:
This thesis differs from the technological perspective of SPI by identifying and analysing the organisational features of process improvement. A theoretical understanding is developed of how and why software process improvements occur and what are the consequences of the change process within a specific case. A packaged information systems organisation forms the basis for a substantive case study. Adding to the growing body of qualitative research, the study takes a critical hermeneutic perspective. In doing so it overcomes some of the criticisms of the interpretive studies especially the need for the research to be reflexive in nature. By looking at SPI as an emergent rather than deterministic activity, the design and action of the change process are shown to be intertwined and shaped by their context. This understanding is based upon a structurational perspective that highlights how the process improvements are enabled and constrained by their context. The work builds on the recent recognition that the improvements can be understood from an organisational learning perspective. Fresh insights to the improvement process are developed by recognising the role of the individual to facilitate or resist the improvement. The understanding gained here can be applied by organisations to enable them to improve the effectiveness of their SPI programmes, and so improve the quality of their software. Lessons are derived that show how software organisations can support the ongoing improvement through recognition of the learning and political aspects of the change by adopting an agile approach to SPI.