• Refine Query
  • Source
  • Publication year
  • to
  • Language
  • 10
  • 6
  • Tagged with
  • 19
  • 19
  • 8
  • 5
  • 4
  • 4
  • 3
  • 3
  • 3
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • About
  • The Global ETD Search service is a free service for researchers to find electronic theses and dissertations. This service is provided by the Networked Digital Library of Theses and Dissertations.
    Our metadata is collected from universities around the world. If you manage a university/consortium/country archive and want to be added, details can be found on the NDLTD website.
1

Computer-assisted literary research on Jean-Paul Sartre's Les Mots : a presentation and proposals concerning the development and use of a hypertext system

Murray, Liam January 1994 (has links)
No description available.
2

INVESTIGANDO A RELAÇÃO ENTRE CODE SMELLS E PROBLEMAS DE DESIGN: ESTUDOS QUALITATIVOS EM MICROEMPRESAS DE SOFTWARE

Freitas, Mydiã Falcão 16 December 2016 (has links)
Submitted by Diogo Barreiros (diogo.barreiros@ufba.br) on 2017-06-08T11:28:18Z No. of bitstreams: 1 Dissertação Mydiã_Freitas.pdf: 3038925 bytes, checksum: 799df53dc64e5b455ed52bb760695ae2 (MD5) / Approved for entry into archive by Vanessa Reis (vanessa.jamile@ufba.br) on 2017-06-12T15:16:18Z (GMT) No. of bitstreams: 1 Dissertação Mydiã_Freitas.pdf: 3038925 bytes, checksum: 799df53dc64e5b455ed52bb760695ae2 (MD5) / Made available in DSpace on 2017-06-12T15:16:18Z (GMT). No. of bitstreams: 1 Dissertação Mydiã_Freitas.pdf: 3038925 bytes, checksum: 799df53dc64e5b455ed52bb760695ae2 (MD5) / Code smell é definido como um potencial problema de design localizado em determinada parte do código fonte de um sistema de software e pode indicar deficiências no design que podem influenciar a facilidade de manutenção, facilidade de teste e confiabilidade do software. Um bom exemplo de code smell que vai de encontro aos princípios do bom design definido na programação orientada a objetos é o Shotgun Surgery, que corresponde a classes cuja modificação implica em muitas pequenas alterações em muitas outras classes. Quando as modificações estão espalhadas, elas são difíceis de serem encontradas. Como resultado, é fácil perder uma mudança importante, causando assim, problemas na manutenção do sistema. A atividade de identificação de code smells é analisada e confirmada pelo próprio programador ou um revisor independente, contudo, a detecção manual de code smells por meio de inspeções de código consume muito tempo e é pouco escalável. Ferramentas que auxiliam a identificação de code smells têm sido bastante utilizadas em diversos estudos. Neste contexto, esta dissertação propõe investigar se a detecção automática de code smells por meio de ferramentas é considerada útil pelos desenvolvedores como forma de avaliar a qualidade do design de sistemas de software, principalmente em termos de facilidade de manutenção. Realizamos três estudos: sendo um estudo preliminar e dois estudos experimentais similares. O objetivo do estudo preliminar era nos auxiliar a perceber e corrigir problemas que pudessem surgir no decorrer do desenvolvimento dos estudos experimentais. O objetivo desses estudos era investigar a qualidade do design de sistemas de softwares e code smells através do uso de ferramentas de detecção. Os resultados desses estudos indicam que existe relação entre os code smells God Class, Data Class, Shotgun Surgery, Refused Bequest e Feature Envy com problemas de design associados a dificuldades no processo de manutenção de sistemas de softwares.
3

Definition and representation of requirement engineering/management : a process-oriented approach

Liaw, Judy-Audrey-Chui-Yik. January 2002 (has links)
Thesis (M.S.)--Mississippi State University. Department of Industrial Engineering. / Title from title screen. Includes bibliographical references.
4

Technique and automation for testing of commercial-off-the-shelf components /

Sówka, Michał January 1900 (has links)
Thesis (M.App.Sc.) - Carleton University, 2005. / Includes bibliographical references (p. 162-166). Also available in electronic format on the Internet.
5

Graphical interface design for equipment control in unstructured environments /

Seo, Jongwon, January 1998 (has links)
Thesis (Ph. D.)--University of Texas at Austin, 1998. / Vita. Includes bibliographical references (leaves 193-204). Available also in a digital version from Dissertation Abstracts.
6

Evaluation and diagnosis of concurrency architectures.

Scratchley, W. Craig, January 1900 (has links)
Thesis (Ph. D.)--Carleton University, 2000. / Also available in electronic format on the Internet.
7

Automated test of evolving software

Shaw, Hazel Anne January 2005 (has links)
Computers and the software they run are pervasive, yet released software is often unreliable, which has many consequences. Loss of time and earnings can be caused by application software (such as word processors) behaving incorrectly or crashing. Serious disruption can occur as in the l4th August 2003 blackouts in North East USA and Canadal, or serious injury or death can be caused as in the Therac-25 overdose incidents. One way to improve the quality of software is to test it thoroughly. However, software testing is time consuming, the resources, capabilities and skills needed to carry it out are often not available and the time required is often curtailed because of pressures to meet delivery deadlines3. Automation should allow more thorough testing in the time available and improve the quality of delivered software, but there are some problems with automation that this research addresses. Firstly, it is difficult to determine ifthe system under test (SUT) has passed or failed a test. This is known as the oracle problem4 and is often ignored in software testing research. Secondly, many software development organisations use an iterative and incremental process, known as evolutionary development, to write software. Following release, software continues evolving as customers demand new features and improvements to existing ones5. This evolution means that automated test suites must be maintained throughout the life ofthe software. A contribution of this research is a methodology that addresses automatic generation of the test cases, execution of the test cases and evaluation of the outcomes from running each test. "Predecessor" software is used to solve the oracle problem. This is software that already exists, such as a previous version of evolving software, or software from a different vendor that solves the same, or similar, problems. However, the resulting oracle is assumed not be perfect, so rules are defined in an interface, which are used by the evaluator in the test evaluation stage to handle the expected differences. The interface also specifies functional inputs and outputs to the SUT. An algorithm has been developed that creates a Markov Chain Transition Matrix (MCTM) model of the SUT from the interface. Tests are then generated automatically by making a random walk of the MCTM. This means that instead of maintaining a large suite of tests, or a large model of the SUT, only the interface needs to be maintained.
8

Using structured analysis and design technique (SADT) for simulation conceptual modelling

Ahmed, Fahim January 2016 (has links)
Conceptual Modelling (CM) has received little attention in the area of Modelling and Simulation (M&S) and more specifically in Discrete Event Simulation (DES). It is widely agreed that CM is least understood despite its importance. This is however, not the case in other fields of science and engineering (especially, computer science, systems engineering and software engineering). In Computer Science (CS) alone, CM has been extensively used for requirements specification and some well-established methods are in practice. The aim of the thesis is to propose a CM framework based on the principles of software engineering and CS. The development of the framework is adapted from a well-known software engineering method called Structured Analysis and Design Technique (SADT), hence it is called SADT CM. It is argued that by adapting approaches from CS, similar benefits can be achieved in terms of formality, understanding, communication and quality. A comprehensive cross-disciplinary review of CM in CS and M&S is undertaken, which highlights the dearth of standards within M&S CM when compared to CS. Three important sub-fields of CS are considered for this purpose namely, information systems, databases and software engineering. The review identifies two potential methods that could be adopted for developing a M&S CM framework. The first method called PREView was found unsuitable for M&S CM in DES domain. Hence, the thesis concentrates on developing the framework based on SADT. The SADT CM framework is evaluated on three-in depth test cases that investigate the feasibility of the approach. The study also contributes to the literature by conducting a usability test of the CM framework in an experimental setting. A comprehensive user-guide has also been developed as part of the research for users to follow the framework.
9

On Using UML Diagrams to Identify and Assess Software Design Smells

Haendler, Thorsten January 2018 (has links) (PDF)
Deficiencies in software design or architecture can severely impede and slow down the software development and maintenance progress. Bad smells and anti-patterns can be an indicator for poor software design and suggest for refactoring the affected source code fragment. In recent years, multiple techniques and tools have been proposed to assist software engineers in identifying smells and guiding them through corresponding refactoring steps. However, these detection tools only cover a modest amount of smells so far and also tend to produce false positives which represent conscious constructs with symptoms similar or identical to actual bad smells (e.g., design patterns). These and other issues in the detection process demand for a code or design review in order to identify (missed) design smells and/or re-assess detected smell candidates. UML diagrams are the quasi-standard for documenting software design and are often available in software projects. In this position paper, we investigate whether (and to what extent) UML diagrams can be used for identifying and assessing design smells. Based on a description of difficulties in the smell detection process, we discuss the importance of design reviews. We then investigate to what extent design documentation in terms of UML2 diagrams allows for representing and identifying software design smells. In particular, 14 kinds of design smells and their representability in UML class and sequence diagrams are analyzed. In addition, we discuss further challenges for UML-based identification and assessment of bad smells.
10

Test Driven Development: uma abordagem baseada em use cases

Milanez, Marcus Vinícius 20 September 2014 (has links)
Made available in DSpace on 2016-04-29T14:23:31Z (GMT). No. of bitstreams: 1 Marcus Vinicius Milanez.pdf: 1438354 bytes, checksum: 792d4f5889dafba8c4e2f71a02c050a0 (MD5) Previous issue date: 2014-09-20 / The development of computer programs is a complex activity, characterized by costs and deadlines that are difficult to estimate. Requirements change frequently, resulting in products of variable reliability. Currently, there are no formal theories that completely address these underlying challenges. Several approaches have been used over time to achieve incremental progress, leading to a significant number of programming languages, development processes, and techniques. Test Driven Development (TDD) is a recently-developed approach which extends the human capabilities to develop computer programs by providing tools to mitigate the difficulties mentioned. Although TDD aggregates a set of support and control elements, it does not include mechanisms that directly help developers with deriving implementations from a set of requirements previously captured and analyzed. As result of this absence, difficulties in understanding its nature and to elaborate the software through independent modules can be observed, ultimately limiting the impact of TDD on the reliability of software. The objective of this research is to overcome the shortcomings mentioned, complementing Kent Beck s TDD proposal by introducing a modeling stage guided by Use Cases, following the ideas of Ivar Jacobson and Wirfs-Brock. Through this approach, assessed by a case study conducted together with industry professionals, enhancements in TDD usage experience could be observed, altering the manner in which this proposal is commonly understood, used and evaluated / Desenvolver programa de computador é uma atividade complexa, cujos custos e prazos são difíceis de serem estimados, caracterizada por requisitos mutantes e que resulta em produtos sem garantias plenas de funcionamento. No atual estado de desenvolvimento desta área de pesquisa, ainda não existe teoria que estabeleça as bases dos conhecimentos necessários a prover soluções a estes problemas. Diversas abordagens foram utilizadas ao longo do tempo a fim de encontrar meios que culminassem em avanços, originando um conjunto expressivo de linguagens de programação, processos e técnicas de desenvolvimento. Uma tentativa recente que intenciona estender as capacidades humanas de desenvolver programas de computador, provendo elementos que permitiriam amenizar essas dificuldades, é uma ferramenta intelectual chamada Test Driven Development (TDD). Embora agregue um conjunto de elementos de apoio e controle ao desenvolvimento, TDD não dispõe de mecanismos que auxiliem desenvolvedores a derivar implementações a partir de um conjunto de requisitos previamente capturados e analisados. Como resultado dessa ausência, observam-se dificuldades em avaliar sua natureza e em propor a elaboração do software em módulos independentes, tornando TDD uma ferramenta questionável. O objetivo desta pesquisa reside em superar as lacunas citadas, complementando a proposta de Kent Beck sobre TDD por meio da introdução de uma etapa de modelagem guiada por modelos casos de uso (Use Cases), seguindo as ideias de Ivar Jacobson e Wirfs-Brock. Por meio desta abordagem, avaliada por estudo de caso realizado em conjunto com profissionais da indústria, observou-se um aprimoramento da experiência de utilização de TDD, alterando a maneira pela qual essa proposta é comumente compreendida, utilizada e avaliada

Page generated in 0.0793 seconds