To see the other types of publications on this topic, follow the link: AUTOMATED SOFTWARE ENGINEERING.
Dissertations / Theses on the topic 'AUTOMATED SOFTWARE ENGINEERING'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'AUTOMATED SOFTWARE ENGINEERING.'
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
Thomas, Mathew. "Semi-Automated Dental Cast Analysis Software." Wright State University / OhioLINK, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=wright1310404863.
Full text
2
Djurström, Ann-Chatrin, Ewa Holgersson, and Isabell Jonsson. "Automated Test Activity for Software." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2001. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-1612.
Full textAbstract:
Software producing companies want to increase their quality and efficiency. They often look at automated test tools as a part of a solution. Not many company's use test tools, the time it takes to evaluate which test tool that suites the company best costs much in both money and time. The development process within the IT world is so fast, this makes it difficult for any enterprise to put money in a test tool that may be useless within a few years. For a test tool to be valuable for a company it must be used during at least a few years. An automated test takes a lot of time to implement and introduce in the company. To get the whole picture when to automate test we have looked at different test methodologies. Step-by Step Method uses tables and lists to create the test document. Product Life Cycle Method (CPU) describes implementing of software test in the product life cycle. Well-developed test methods can save a lot of time and make it possibly for developers to work effectively. We have also investigated some general information about automated test like cost and when to automate. ATLM (Automated Test Life-Cycle Methodology) is a methodology that is used in order to take the correct decisions such as when to automate or not, (ATLM) is a structured methodology aiming toward ensuring a successful implementation. We have also described some methods of automated tools. The Record/Playback Method is a feature that executes the test manually while the test tool sits in the background and remembers what has happened. It generates a script that can re-execute the test. The Functional Decomposition Method and The Key-Word Driven Method are a data-driven automated testing methodology. That allows developing automated test scripts that are more "generic". It requires only that the input and the expected results have been updated. In this study we have examined automated test tools offered by Rational, Segue Software Inc and Mercury Interactive to survey the tools on the market. Segue Software Inc is aimed for e-business systems. Rational is a big company and has solutions for all parts in a software project. Mercury Interactive has several test solutions for testing and monitoring business- critical Web applications, and the WinRunner is most complex of the offered tools.Mjukvaruutvecklande företag vill öka sin kvalité och effektivitet. De tittar ofta på automatiserade testverktyg som en del av lösningen. Inte så många företag använder testverktyg, tiden det tar att utvärdera vilket testverktyg som passar företaget bäst kostar mycket vad gäller både tid och pengar. Utvecklingen i IT världen är snabb, det gör det svårt för vilket företag som helst att lägga pengar på ett testverktyg som kan vara värdelöst om ett par år. För att ett testverktyg ska vara värdefullt för ett företag måste det användas under minst ett par år. Automatiserade testverktyg tar mycket tid att implementera och introducera i ett företag. För att få en helhetsbild när man ska automatisera tester har vi tittat på olika test metoder. Step-by Step metoden använder sig av listor för att skapa testdokument. Product Life Cycle Method (CPU) beskriver implementeringen av test i hela produktutvecklings cykeln. Väl utvecklade testmetoder kan spara mycket tid och gör det möjligt för utvecklarna att jobba mer effektivt. Vi har även undersökt lite mer allmän information om automatiserade test. som kostnaden och när man ska automatisera. ATLM (Automated Test Life-Cycle Methodology) är en metodik som används för att kunna ta de korrekta besluten som när man ska automatisera eller inte, ATLM är en strukturerad metodik som siktar mot att garantera en lyckad implementering. Vi har också beskrivit några metoder av automatiserade testverktyg. Record/Playback metoden är en metod som exekverar testen manuellt medan testverktyget spelar in vad som händer. Det genererar ett script som kan exekvera testet igen. Functional Decomposition metoden och The Key-Word Driven metoden är datadrivna automatiserade testmetodiker. Dessa tillåter automatiserade test script som är mer ?generiska?. De kräver bara ett indata och de förväntade resultaten har blivit uppdaterade. I denna uppsats har vi undersökt automatiserade testverktyg som erbjuds av Rational, Segue Software Inc och Mercury Interactive för att granska verktygen som finns på marknaden. Segue Software Inc siktar på e-handels system. Rational är ett stort företag som har lösningar för alla delar i ett mjukvaru projekt. Mercury Interactive har flera lösningar för testning och kontrollering av affärs kritiska web-applikationer, WinRunner är den mest komplexa av de erbjudna verktygen.
3
Shaw, Hazel Anne. "Automated test of evolving software." Thesis, University of Bedfordshire, 2005. http://hdl.handle.net/10547/305743.
Full textAbstract:
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.
4
Wiklund, Kristian. "Impediments for Automated Software Test Execution." Doctoral thesis, Mälardalens högskola, Inbyggda system, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-27830.
Full textAbstract:
Automated software test execution is a critical part of the modern software development process, where rapid feedback on the product quality is expected. It is of high importance that impediments related to test execution automation are prevented and removed as quickly as possible. An enabling factor for all types of improvement is to understand the nature of what is to be improved. The goal with this thesis is to further the knowledge about common problems encountered by software developers using test execution automation, in order to enable improvement of test execution automation in industrial software development. The research has been performed through industrial case studies and literature reviews. The analysis of the data have primarily been performed using qualitative methods, searching for patterns, themes, and concepts in the data. Our main findings include: (a) a comprehensive list of potential impediments reported in the published body of knowledge on test execution automation, (b) an in-depth analysis of how such impediments may affect the performance of a development team, and (c) a proposal for a qualitative model of interactions between the main groups of phenomena that contribute to the formation of impediments in a test execution automation project. In addition to this, we contribute qualitative and quantitative empirical data from our industrial case studies. Through our results, we find that test execution automation is a commonly under-estimated activity, not only in terms of resources but also in terms of the complexity of the work. There is a clear tendency to perform the work ad hoc, down-prioritize the automation in favor of other activities, and ignore the long-term effects in favor of short-term gains. This is both a technical and a cultural problem that need to be managed by awareness of the problems that may arise, and also have to be solved in the long term through education and information. We conclude by proposing a theoretical model of the socio-technical system that needs to be managed to be successful with test execution automation.Syftet med denna avhandling är att utöka den vetenskapliga kunskapen om problem som kan uppstå under användning av automatiserad testning i industriell programvaruutveckling. Utveckling av programvara består principiellt av ett antal processteg: kravbehandling, detaljerad systemkonstruktion, implementation i form av programmering, och slutligen testning som säkerställer att kvaliteten på programvaran är tillräcklig för dess tilltänkta användare. Testning representerar en stor del av tiden och kostnaden för utveckling av programvaran, och detta gör att det är attraktivt att automatisera testningen. Automatiserade tester kan bidra med många positiva effekter. Testning som utförs om och om igen, för att säkerställa att gammal funktionalitet inte slutar att fungera när ändringar görs i programvaran, kan med fördel göras automatiserat. Detta frigör kvalificerad personal till kvalificerat arbete. Automatisering kan även minska ledtiden för testningen och därmed möjliggöra snabbare leveranser till kund. Ett annat mål med testautomatisering är att vara säker på att samma tester utförs på ett likartat sätt varje gång produkten testas, så att den håller en jämn och stabil kvalitetsnivå. Automatiserad testning är dock en mer komplex och kostsam verksamhet än vad man kan tro, och problem som uppstår under dess användning kan ha stora konsekvenser. Detta gäller i ännu större utsträckning i organisationer som använder moderna utvecklingsmetoder där automatisering är grundstenen för en effektiv kvalitetskontroll. För att kunna undvika så många problem som möjligt, är det därför mycket viktigt att förstå vad som händer när man använder testautomatisering i stor skala. Denna avhandling presenterar resultat från fallstudier i svensk industri, som, kombinerat med en systematisk genomgång av befintlig forskning inom området, har utförts för att söka djupare kunskap och möjligheter till generalisering. Arbetet har varit beskrivande, och förklarande, och bygger på empirisk forskningsmetodik. I avhandlingen bidrar vi med (a) information om de problem relaterade till automatiserad testning som vi har identifierat i de empiriska fallstudierna, (b) en diskussion av dessa problem i relation till andra studier i området, (c) en systematisk litteraturstudie som ger en översikt över relevanta publikationer i området, (d) en analys av bevisen som insamlats genom litteraturstudien, samt (e) en modell av det organisatoriska och tekniska system som måste hanteras för att man skall nå framgång med ett testautomatiseringsprojekt. Resultaten tyder på att rent tekniska problem inte utgör huvuddelen av de problem som upplevs med testautomatisering. Istället handlar det till stora delar om organisationell dynamik: hantering av förändringen det innebär att införa automatisering, planering av automatisering och dess användning, samt vilka finansiella förväntningar man har på automatiseringen.
ITS-EASY Post Graduate School for Embedded Software and Systems
5
Khatchadourian, Raffi Takvor. "Techniques for Automated Software Evolution." The Ohio State University, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=osu1304885155.
Full text
6
Holbrook, Elizabeth Ashlee. "SATISFACTION ASSESSMENT OF TEXTUAL SOFTWARE ENGINEERING ARTIFACTS." UKnowledge, 2009. http://uknowledge.uky.edu/gradschool_diss/712.
Full textAbstract:
A large number of software projects exist and will continue to be developed that have textual requirements and textual design elements where the design elements should fully satisfy the requirements. Current techniques to assess the satisfaction of requirements by corresponding design elements are largely manual processes that lack formal criteria and standard practices. Software projects that require satisfaction assessment are often very large systems containing several hundred requirements and design elements. Often these projects are within a high assurance project domain, where human lives and millions of dollars of funding are at stake. Manual satisfaction assessment is expensive in terms of hours of human effort and project budget. Automated techniques are not currently applied to satisfaction assessment.
This dissertation addresses the problem of automated satisfaction assessment for English, textual documents and the generation of candidate satisfaction assessments that can then be verified by a human analyst with far less effort and time expenditure than is required to produce a manual satisfaction assessment. Validation results to date show that automated satisfaction methods produce candidate satisfaction assessments sufficient to greatly reduce the effort required to assess the satisfaction of textual requirements by textual design elements.
7
Wong, Kwok-Leung, and Fredrik Nilsson. "Intelligent resource handling scheduling of automated test execution." Thesis, Department of Science and Technology, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-19768.
Full textAbstract:
The unit RTH, Radio Access Network Transmission and Home at Ericsson site in Linkoping uses today different test tool which are divided between different projects. Today they do not have any optimal solution for in an easy way execute the test cases from different projects concurrently, and share the test tools between the these projects.
All the execution of test cases which a test tool is needed needs to be configured and started manually which cost both time and money. Since the test tools are very expensive to use, it is desirable to increase the utilization. The purpose of this thesis is to provide RTH a working prototype which can in an intelligent way schedule and then automatically execute the test cases. The prototype shall consist of a web user interface and a scheduler part. The web user interface is going to be that part which the user works in, and the scheduler handles the prioritization and make sure that the test cases are executed.
To reach the goal with a working prototype, PHP and Java were picked as framework for the prototype. The theory behind these programming languages and more can be read in the theory chapter, and all the different methods which were used. The result of the working process can be read in the Result chapter.
The end prototype fulfills the customer’s requirement. Improvement and new functionalities are given as suggestion at the end of this thesis, where we also discuss the working process.
8
Poller, Andreas. "Approaches for Automated Software Security Evaluations." Master's thesis, Universitätsbibliothek Chemnitz, 2006. http://nbn-resolving.de/urn:nbn:de:swb:ch1-200601872.
Full textAbstract:
As a consequence of the highly increasing cross-linking of computer systems in computer networks, the possibilities for accessing programs operated at these machines is becoming more and more independent from the possibilities of having physical access to them. Thus the former existing physical access controls have to be replaced by logical access controls which ensure that computer systems are only used for the intended purpose and that the stored data are handled securely and confidentially. The efficiency of such logical protection mechanism is verified by applying software security tests. During such tests it is proved whether security functions can be bypassed especially by exploiting software errors. In this diploma thesis approaches for the automation of software security tests are examined regarding their effectiveness and applicability. The results are used to introduce a requirement and evaluation model for the qualitative analysis of such security evaluation automation approaches. Additionally, the assertion is made that a highly automated software security evaluation is not a sensible development goal referring to the estimated cost-benefit ratio which is gained by trying to realise this goal. Based on this assertion, this diploma thesis discusses how to join the capabilities of a human tester and a software evaluation assistance system in an efficient test process. Based on this considerations, the design and implementation of a software security evaluation system which has been developed prototypically for this diploma thesis is described. This system significantly involves the human tester in the evaluation process but provides approaches for automation where possible. Furthermore this proof-of-concept prototype is evaluated regarding its practical applicabilityDurch die zunehmende starke Vernetzung von Computertechnologie wird die Möglichkeit des Zugriffs auf einzelne Computersysteme und den darauf ablaufenden Programmen zunehmend ebenso stark unabhängig von den physischen Zugangsmöglichkeiten des Zugreifenden zu diesen Systemen. Diese wegfallenden physischen Zugangsbarrieren müssen deshalb durch logische Zugriffsbeschränkungen ersetzt werden, die sicherstellen, dass Computersysteme nur zu den vorgesehen Zwecken verwendet und die darin gespeicherten Daten sicher und vertraulich verarbeitet werden. Die Wirksamkeit dieser logischen Schutzmechanismen wird mit Hilfe von s.g. Softwaresicherheitstests verifiziert. Dabei wird insbesondere überprüft, inwiefern Schutzfunktionen durch Zuhilfenahme von in der Software vorhandenen Programmfehlern umgangen werden können. Diese Diplomarbeit überprüft bestehende Ansätze für die Automatisierung solcher Sicherheitstests hinsichtlich ihrer Wirksamkeit und Anwendbarkeit. Aus den Resultaten dieser Untersuchung wird ein allgemeines Anforderungs- und Bewertungsmodell entwickelt, welches die qualitative Bewertung von Ansätzen zur Sicherheitstestautomatisierung zulässt. Desweiteren wird die Behauptung aufgestellt, dass die Forderung nach einer zu starken Automatisierung des Testverfahrens sich ungünstig gegenüber des Kosten-Nutzen-Verhältnisses auswirkt, welches bei der Realisierung dieser Forderungen zu erwarten ist. Darauf aufbauend versucht die Diplomarbeit abzugrenzen, wie sich die Fähigkeiten des menschlichen Testers und eines teilautomatisierbaren Softwaresystems effizient in einem Sicherheitstestprozess verbinden lassen. Basierend auf diesen Betrachtungen wird beschrieben, wie ein Sicherheitsevaluierungssystem, welches prototypisch für diese Diplomarbeit entwickelt wurde, den Menschen zur Erstellung von Testalgorithmen einbindet aber, wenn dies zweckmäßig ist, Automatisierungen ermöglicht. Dieses System wird daraufhin auf seine praktische Anwendbarkeit untersucht
9
Cullum, James J. "Performance analysis of automated attack graph generation software." Thesis, Monterey, Calif. : Naval Postgraduate School, 2006. http://bosun.nps.edu/uhtbin/hyperion.exe/06Dec%5FCullum.pdf.
Full textAbstract:
Thesis (M.S. in Computer Science)--Naval Postgraduate School, December 2006.Thesis Advisor(s): Cynthia Irvine, Timothy Levin. "December 2006." Includes bibliographical references (p. 137- 138). Also available in print.
10
Gottlieb, David Bendix 1982. "Software development of the Automated Law Review Submission System." Thesis, Massachusetts Institute of Technology, 2004. http://hdl.handle.net/1721.1/29406.
Full textAbstract:
Thesis (M. Eng.)--Massachusetts Institute of Technology, Dept. of Civil and Environmental Engineering, 2004.Includes bibliographical references (p. 79-80).
Organizing article data and information as well as streamlining communications are the most important goals of any submission system. The submission process used by law professors and law review journals severely fails to meet those goals. The Automated Law Review Submission System (ALRSS) has been developed in order to meet those goals. Many potential ALRSS users were interviewed and a rigorous set of requirements was developed. ALRSS successfully provides an easily accessible, central document and information repository, and also would nearly eliminate the use of phone, fax, mail or personal email. Furthermore, the system enables editors of law reviews l;o control the workflow of the review process. With further development, ALRSS will compete commercially with ExpressOTM in the law article community and strive to operate as effectively as MonsterTrakTM and LSDASTM do in their respective communities. The long term goal of ALRSS is to function as a general submission system that can be customized for a specific submission processes.
by David Bendix Gottlieb.
M.Eng.
11
Chen, Mingda, and Yao He. "Exploration on Automated Software Requirement Document Readability Approaches." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-14816.
Full textAbstract:
Context. The requirements analysis phase, as the very beginning of software development process, has been identified as a quite important phase in the software development lifecycle. Software Requirement Specification (SRS) is the output of requirements analysis phase, whose quality factors play an important role in the evaluation work. Readability is a quite important SRS quality factor, but there are few available automated approaches for readability measurement, because of the tight dependency on readers' perceptions. Low readability of SRS documents has a serious impact on the whole process of software development. Therefore, it's extremely urgent to propose effective automated approaches for SRS documents readability measurement. Using traditional readability indexes to analyze readability of SRS documents automatically is a potentially feasible approach. However, the effectiveness of this approach is not systematically evaluated before. Objectives. In this study, firstly, we aim to understand the readability of texts and investigate approaches to score texts readability manually. Then investigate existing automated readability approaches for texts with their working theories. Next, evaluate the effectiveness of measuring the readability of SRS documents by using these automated readability approaches. Finally, rank these automated approaches by their effectiveness. Methods. In order to find out the way how human score the readability of texts manually and investigate existing automated readability approaches for texts, systematic literature review is chosen as the research methodology. Experiment is chosen to explore the effectiveness of automated readability approaches. Results. We find 67 articles after performing systematic literature review. According to systematic literature review, human judging the readability of texts through reading is the most common way of scoring texts readability manually. Additionally, we find four available automated readability assessments tools and seven available automated readability assessments formulas. After executing the experiment, we find the actual value of effectiveness of all selected approaches are not high and Coh-Metrix presents the highest actual value of effectiveness of automated readability approach among the selected approaches. Conclusions. Coh-Metrix is the most effective automated readability approach, but the feasibility in directly applying Coh-Metrix in SRS documents readability assessments cannot be permitted. Since the actual value of evaluated effectiveness is not high enough. In addition, all selected approaches are based on metrics of readability measures, but no semantic factors are blended in readability assessments. Hence studying more on human perception quantifying and adding semantic analysis in SRS documents readability assessment could be two research directions in future.
12
Tlemcani, Ismail. "SYSTEM-LEVEL AUTOMATED TESTING FOR HOME DIGITAL VOICE ASSISTANTS." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-51050.
Full textAbstract:
Home Digital Voice Assistants (HDVA) are devices that are performing tasks based on voice commands. A normal user can use these devices to perform daily tasks like sending an email, play a song or check for an event online, just to name a few. These systems got very popular in recent years due to their ease of use and the evolution of their technology that is now handling many commands and is able to perform complex tasks. HDVA devices are also nowadays used in some critical cases like for door opening and in some healthcare services. On the other hand, software testing is an important verification and validation activity used to reveal software faults in systems that include a software part. This activity is used to make sure that the expected behavior of the system matches the actual software execution. This activity results in the creation of test cases that are run as scripts in an automatic way. Because of the fact that HDVA devices are used nowadays in some critical use cases, it is of utmost importance that these devices are thoroughly tested to make sure that they are behaving in the correct way. In this thesis, we first investigated the current automation testing frameworks for HDVA devices that exist in the market by doing a multivocal literature review. This is an important step to do in order to discover what are the existing frameworks in the market and therefore decide on the most appropriate research that can be carried out on these. We have, after doing the multivocal literature review and listing the available automation testing tools for HDVA devices, evaluated one tool selected from this review and assessed its usefulness and applicability for professionals and researchers in terms of ease of use and resources it uses during test execution. During the evaluation, we focused on automation testing tools for the Amazon Echo device because of its popularity on the market and the great amount of resources that are available online on this device and we focused on system testing. After doing the multivocal literature review, we found that the Botium framework is the only framework available to use to test the Amazon Echo device on a system level. We took the Botium framework as the framework to be evaluated and we performed an evaluation on it from a test automation capability perspective. The evaluation was done on a virtual machine which was set up locally with the VMware software. The evaluation showed a slow test execution capability of the Botium tool. More studies are needed on testing the other popular HDVA devices and on the lower testing levels.
13
Tan, Roy Patrick. "Programming Language and Tools for Automated Testing." Diss., Virginia Tech, 2007. http://hdl.handle.net/10919/28684.
Full textAbstract:
Software testing is a necessary and integral part of the software quality process. It is estimated that inadequate testing infrastructure cost the US economy between $22.2 and $59.5 billion.
We present Sulu, a programming language designed with automated unit testing specifically in mind, as a demonstration of how software testing may be more integrated and automated into the software development process. Sulu's runtime and tools support automated testing from end to end; automating the generation, execution, and evaluation of test suites using both code coverage and mutation analysis. Sulu is also designed to fully integrate automatically generated tests with manually written test suites. Sulu's tools incorporate pluggable test case generators, which enables the software developer to employ different test case generation algorithms.
To show the effectiveness of this integrated approach, we designed an experiment to evaluate a family of test suites generated using one test case generation algorithm, which exhaustively enumerates every sequence of method calls within a certain bound. The results show over 80\% code coverage and high mutation coverage for the most comprehensive test suite generated.Ph. D.
14
Jagerfield, Trevor. "A Method and Tool for Automated Analysis of Heavy Vehicle RequirementsA Method and Tool for Automated Analysis of Heavy Vehicle Requirements." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-29620.
Full textAbstract:
The introduction of the functional safety standard ISO 26262 was motivated by an increasing demand to ensure reliability and correctness of safety-critical systems in the automotive industry. However, the adoption of this standard in the automotive industry is hindered by a number of obstacles. Scania is an industrial partner in the VeriSpec project which studies these obstacles and proposes relevant tools and methods compliant with academic and industrial needs. This thesis is within the scope of the VeriSpec project, and aims to address one of the project’s goals, which is to provide tool support for a pattern-based requirement formalization process. The Specification Property System (SPS) proposed by Konrad and Cheng is a patterning method that provides automatic translation of system properties into temporal logics. The SPS also helps in restricting the introduction of ambiguities and inconsistencies in system specification properties. However, the adoption of the SPS in the industry is hindered due to some issues. These issues are, a long learning curve, Constrained Natural Language (CNL) ambiguities, and the lack of tool-support for real-time SPS patterns. In this thesis, a qualitative research study with a literature survey has been performed to find and select state-of-the-art supportive methods to provide feedback on the formalized requirements’ semantics. The Scania Specifier tool has been extended and modified to support a requirement formalization process using the SPS qualitative and real-time patterns. In addition, three supportive methods that resulted from the research study have been integrated into the Specifier tool to provide different feedback options for the users. Finally, the performance of the Specifier tool and the feedback of the supportive methods have been evaluated. The outcome of the study shows that the feedback of the supportive methods helped in guaranteeing the intended behavior of the requirement developers. In addition supportive methods’ feedback enhanced user-friendliness, and aided the users in shortening the SPS learning curve. Finally, an additional outcome of the study is in the form of a number of suggestions and emerged patterns with regard to the SPS usage and supportive methods’ feedback.
15
Gump, Brandon Adam. "Automated Transforms of Software Models: A Design Pattern Approach." Wright State University / OhioLINK, 2009. http://rave.ohiolink.edu/etdc/view?acc_num=wright1260287805.
Full text
16
Palmér, Tobias, and Markus Waltré. "Automated end-to-end user testing on single page web applications." Thesis, Linköpings universitet, Medie- och Informationsteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-119968.
Full textAbstract:
Competencer wants to be sure users experience their web product as it was designed. With the help of tools for end-to-end user testing, interactions based on what a user would do is simulated to test potential situations. This thesis work is targeting four areas of end-to-end user testing with a major focus on making it automatic. A study is conducted on test case methods to gain an understanding of how to approach writing tests. A coverage tool is researched and built to present a measure of what is being tested of the product. To ease the use for developers a solution for continuous integration is looked at. To make tests more automatic a way to build mocks through automation is implemented. These areas combined with the background of Competencers application architecture creates a foundation for replacing manual testing sessions with automatic ones.
17
Egerton, David. "Automated generation of SW design constructs from MESA source code /." Online version of thesis, 1993. http://hdl.handle.net/1850/12144.
Full text
18
Rothenhaus, Kurt Joseph. "Data strategies to support automated multi-sensor data fusion in a service oriented architecture." Monterey, Calif. : Naval Postgraduate School, 2008. http://handle.dtic.mil/100.2/ADA483454.
Full textAbstract:
Dissertation (Ph.D. in Software Engeineering)--Naval Postgraduate School, June 2008.Dissertation Advisor(s): Michael, James Bret. "June 2008." Description based on title screen as viewed on August 27, 2008. Includes bibliographical references (p. 221-223). Also available in print.
19
Kirschenbaum, Jason P. "Investigations in Automating Software Verification." The Ohio State University, 2011. http://rave.ohiolink.edu/etdc/view?acc_num=osu1306862918.
Full text
20
CAVALCANTI, Yguaratã Cerqueira. "An automated approach to assign software change requests." Universidade Federal de Pernambuco, 2014. https://repositorio.ufpe.br/handle/123456789/12391.
Full textAbstract:
Submitted by Nayara Passos (nayara.passos@ufpe.br) on 2015-03-13T13:04:40Z
No. of bitstreams: 2
TESE Yaguaratã Cerqueira Cavalcanti.pdf: 2989671 bytes, checksum: cdde3d6cea6de1cabb90748865421b78 (MD5)
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)Made available in DSpace on 2015-03-13T13:04:40Z (GMT). No. of bitstreams: 2 TESE Yaguaratã Cerqueira Cavalcanti.pdf: 2989671 bytes, checksum: cdde3d6cea6de1cabb90748865421b78 (MD5) license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5) Previous issue date: 2014
The efficient management of Change Requests (CRs) is fundamental for successful software maintenance; however the assignment of CRs to developers is an expensive aspect in this regard, due to the time and expertise demanded. To overcome this, researchers have proposed automated approaches for CR assignment. Although these proposals present advances to this topic, they do not consider many factors inherent to the assignments, such as: developers’ workload, CRs severity, interpersonal relationships, and developers know-how. Actually, as we demonstrate in this work, CR assignment is a complex activity and automated approaches cannot rely on simplistic solutions. Ideally, it is necessary to consider and reason over contextual information in order to provide an effective automation. In this regarding, this work proposes, implements, and validates a context-aware architecture to automate CR assignment. The architecture emphasizes the need for considering the different information available at the organization to provide a more context-aware solution to automated CR assignment. The development of such architecture is supported by evidence synthesized from two empirical studies: a survey with practitioners and a systematic mapping study. The survey provided us with a set of requirements that automated approaches should satisfy. In the mapping study, in turn, we figured out how state-of-the-art approaches are implemented in regarding to these requirements, concluding that many of them are not satisfied. In addition, new requirements were identified in this mapping study. For the implementation of the proposed architecture, we developed a strategy to automate CR assignments which is based on two main components: a Rule-Based Expert System (RBES) and an Information Retrieval (IR) model. The strategy coordinately applies these two components in different steps to find the potential developer to a CR. The RBES takes care of the simple and complex rules necessary to consider contextual information in the assignments, e.g., to prevent assigning a CR to a busy or unavailable developer. Since these rules vary from one organization/project to another, the RBES facilitates their modification for different contexts. On the other hand, the IR model is useful to make use of the historical information of CR assignments to match CRs and developers. Results from the validation study showed that our solution is promising. It is, by comparing the solution with an approach that uses only a machine learning algorithm, such as the Support Vector Machine (SVM), we could improve the accuracy of assignments by almost 50%. The analysis of the solution’s payoff also pointed that such an accuracy is able to pay for the efforts necessary to deploy the solution.-------------------------------------O gerenciamento eficiente de solicitações de mudança (SM) é fundamental para o sucesso das atividades de manutenção e evolução de software. Entretanto, a atribuição de SMs a desenvolvedores é um aspecto custoso desse gerenciamento, pois demanda tempo e conhecimento apropriado do projeto de software. Várias pesquisas já propuseram métodos de atribuição automática de SMs. Embora representem avanços na área, existem fatores inerentes a atribuição de SMs que não são considerados nessas pesquisas e são essenciais para a automação. Como demonstrado nesse trabalho, a atribuição automática deve, por exemplo, considerar a carga de trabalho, a experiência e o conhecimento dos desenvolvedores, a prioridade e a severidade das SMs, a afinidade dos desenvolvedores com os problemas descritos nas SMs, e até mesmo os relacionamentos interpessoais. Para tornar esse cenário ainda mais complexo, esses fatos podem variar de acordo com o projeto de software que está sendo desenvolvido. Assim, uma solução para o problema de atribuição de SMs depende de informações contextuais. Assim, esse trabalho propõe, implementa e valida uma solução arquitetural sensível ao contexto para atribuição automática de SMs. Dado o aspecto contextual da solução, a arquitetura considera diversas fontes de informações presentes na organização, assim como a necessidade de se desenvolver algorítimos que implementem diferentes estratégias de atribuição. Nossa proposta de solução é embasada em resultados de duas pesquisas quantitativas: um estudo de mapeamento sistemático da literatura, e uma pesquisa de questionário com desenvolvedores de software. Esse último forneceu um conjunto de requisitos que a solução automatizada deve satisfazer para que as estratégias de atribuição sejam atendidas, enquanto o mapeamento da literatura identificou técnicas, algoritmos, e outros requisitos necessários a automação. A implementação da arquitetura segue uma estratégia de automação, definida nesse trabalho, que possui dois componentes principais: um sistema especialista baseado em regras (SEBR); e um modelo de recuperação de informação (MRI) com técnicas de aprendizagem. Em nossa estratégia, esses dois componentes são executados alternadamente em momentos diferentes a fim de atribuir uma SM automaticamente. O SEBR processa regras, considerando informações contextuais do projeto de software e da organização que o desenvolve. O MRI é utilizado para fazer o casamento entre SMs e desenvolvedores de acordo com o histórico de atribuições. Os resultados do estudo de validação apontaram que a solução é promissora. Isto é, ao compararmos nossa solução com uma abordagem que utiliza apenas um algoritmo de aprendizado de máquina, como o Support Vector Machine (SVM), pudemos melhorar em quase 50% a acurácia de atribuição. Já a análise de custo de implantação apontou que a acurácia atingida pela solução possui um bom custo benefício.
21
Holden, Jeffrey. "A STUDY OF SEMI-AUTOMATED TRACING." DigitalCommons@CalPoly, 2011. https://digitalcommons.calpoly.edu/theses/574.
Full textAbstract:
Requirements tracing is crucial for software engineering practices including change analysis, regression testing, and reverse engineering. The requirements tracing process produces a requirements traceability matrix(TM) which links high- and low-level document elements. Manually generating a TM is laborious, time consuming, and error-prone. Due to these challenges TMs are often neglected. Automated information retrieval(IR) techniques are used with some efficiency. However, in mission- or safety-critical systems a human analyst is required to vet the candidate TM. This introduces semi-automated requirements tracing, where IR methods present a candidate TM and a human analyst validates it, producing a final TM. In semi-automated tracing the focus becomes the quality of the final TM. This thesis expands upon the research of Cuddeback et al. by examining how human analysts interact with candidate TMs. We conduct two experiments, one using an automated tracing tool and the other using manual validation. We conduct formal statistical analysis to determine the key factors impacting the analyst’s tracing performance. Additionally, we conduct a pilot study investigating how analysts interact with TMs generated by automated IR methods. Our research statistically confirms the finding of Cuddeback et al. that the strongest impact on analyst performance is the initial TM quality. Finally we show evidence that applying local filters to IR results produce the best candidate TMs.
22
Rai, Poonam. "Extending Automated Testing To High-level Software Requirements : A study on the feasibility of automated acceptance-testing." Thesis, Mittuniversitetet, Avdelningen för informations- och kommunikationssystem, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-28041.
Full textAbstract:
Automated acceptance testing is the testing of software done in higher level to test whether the system abides by the requirements desired by the business clients by the use of piece of script other than the software itself. This project is a study of the feasibility of acceptance tests written in Behavior Driven Development principle. The project includes an implementation part where automated accep- tance testing is written for Touch-point web application developed by Dewire (a software consultant company) for Telia (a telecom company) from the require- ments received from the customer (Telia). The automated acceptance testing is in Cucumber-Selenium framework which enforces Behavior Driven Development principles. The purpose of the implementation is to verify the practicability of this style of acceptance testing. From the completion of implementation, it was concluded that all the requirements from customer in real world can be converted into executable specifications and the process was not at all time-consuming or difficult for a low-experienced programmer like the author itself. The project also includes survey to measure the learnability and understandability of Gherkin- the language that Cucumber understands. The survey consist of some Gherkin exam- ples followed with questions that include making changes to the Gherkin exam- ples. Survey had 3 parts: first being easy, second medium and third most difficult. Survey also had a linear scale from 1 to 5 to rate the difficulty level for each part of the survey. 1 stood for very easy and 5 for very difficult. Time when the partic- ipants began the survey was also taken in order to calculate the total time taken by the participants to learn and answer the questions. Survey was taken by 18 of the employers of Dewire who had primary working role as one of the programmer, tester and project manager. In the result, tester and project manager were grouped as non-programmer. The survey concluded that it is very easy and quick to learn Gherkin. While the participants rated Gherkin as very easy.
23
Bertilsson, Henrik, and Gustav Näsman. "Improving progress tracking using automated testing techniques." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3863.
Full textAbstract:
One of the problems when developing software is the difficulty of knowing how much that is done in a project. This is a basic condition to be able to estimate the remaining efforts with increased accuracy over time. To get accurate progress information it is important that the progress tracking is done in an objective way and also in an as simple way as possible. Our focus in this work has been software projects in general but a case study has also been performed at Ericsson Software Technology AB in Ronneby. We have studied the organization and performed interviews with project managers to find out if this really is a problem and if the process can be improved in some way to ease the task of progress tracking. This case study together with our literature study has resulted in a proposition for a solution. Our approach has been to use automated testing as a way to make progress tracking more objective. The result presented in this thesis is a base for a system that could ease the tracking of progress. In short, the system extracts information from an automated testing process and compares it with estimated figures to be able to automatically generate progress information.0708-574327
24
Stobart, Simon. "Automated support for the implementation phase of the software development cycle : an investigation." Thesis, University of Sunderland, 1997. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.361205.
Full text
25
Schulz, Henning [Verfasser], and André van [Akademischer Betreuer] Hoorn. "Automated generation of tailored load tests for continuous software engineering / Henning Schulz ; Betreuer: André van Hoorn." Stuttgart : Universitätsbibliothek der Universität Stuttgart, 2021. http://d-nb.info/1234452804/34.
Full text
26
Rafi, Dudekula Mohammad, and Kiran Moses Katam Reddy. "Automated Software Testing : A Study of the State of Practice." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3375.
Full textAbstract:
Context: Software testing is expensive, labor intensive and consumes lot of time in a software development life cycle. There was always a need in software testing to decrease the testing time. This also resulted to focus on Automated Software Testing (AST), because using automated testing, with specific tools, this effort can be dramatically reduced and the costs related with testing can decrease [11]. Manual Testing (MT) requires lot of effort and hard work, if we measure in terms of person per month [11]. Automated Software testing helps to decrease the work load by giving some testing tasks to the computers. Computer systems are cheap, they are faster and don‘t get bored and can work continuously in the weekends. Due to this advantage many researches are working towards the Automation of software testing, which can help to complete the task in less testing time [10]. Objectives: The main aims of this thesis is to 1.) To systematically classify contributions within AST. 2.) To identify the different benefits and challenges of AST. 3.) To identify the whether the reported benefits and challenges found in the literature are prevalent in industry. Methods: To fulfill our aims and objectives, we used Systematic mapping research methodology to systematically classify contributions within AST. We also used SLR to identify the different benefits and challenges of AST. Finally, we performed web based survey to validate the finding of SLR. Results: After performing Systematic mapping, the main aspects within AST include purpose of automation, levels of testing, Technology used, different types of research types used and frequency of AST studies over the time. From Systematic literature review, we found the benefits and challenges of AST. The benefits of AST include higher product quality, less testing time, reliability, increase in confidence, reusability, less human effort, reduction of cost and increase in fault detection. The challenges include failure to achieve expected goals, difficulty in maintenance of test automation, Test automation needs more time to mature, false expectations and lack of skilled people for test automation tools. From web survey, it is observed that almost all the benefits and challenges are prevalent in industry. The benefits such as fault detection and confidence are in contrary to the results of SLR. The challenge about the appropriate test automation strategy has 24 % disagreement from the respondents and 30% uncertainty. The reason is that the automation strategy is totally dependent on the test manager of the project. When asked “Does automated software testing fully replace manual testing”, 80% disagree with this challenge. Conclusion: The classification of the AST studies using systematic mapping gives an overview of the work done in the area of AST and also helps to find research coverage in the area of AST. These results can be used by researchers to use the gaps found in the mapping studies to carry on future work. The results of SLR and web survey clearly show that the practitioners clearly realize the benefits and challenges of AST reported in the literature.Mobile no: +46723069909
27
Patil, Mayur. "Test Scenario Development Process and Software-in-the-Loop Testing for Automated Driving Systems." The Ohio State University, 2019. http://rave.ohiolink.edu/etdc/view?acc_num=osu1574794282029419.
Full text
28
Shah, Anuj Ramesh. "Web-CAT: A Web-based Center for Automated Testing." Thesis, Virginia Tech, 2003. http://hdl.handle.net/10919/33109.
Full textAbstract:
The fundamentals of software testing and related activities are often elusive in undergraduate curricula. A direct consequence of the lack of software testing efforts during education is the huge losses suffered by the software industry when applications are not sufficiently tested. Software practitioners have exhorted faculty members and institutions to teach more software testing in universities.
The purpose of this research is to provide answers to the needs of such practitioners and introduce software-testing activities throughout the curriculum. The most important goal is to introduce software-testing education without requiring a significant amount of extra effort on behalf of faculty members or teaching assistants.
The approach taken comprises the development of the Web-based Center for Automated Testing (Web-CAT) and the introduction of test-driven development (TDD) in courses. Web-CAT serves as a learning environment for software testing tasks and helps automatically assess student assignments.
A comparison of student programs developed using Web-CAT with historical records indicated a significant decrease in the number of bugs in submitted programs. Undergraduate students also received exposure to the principles of software testing and were able to write test cases that were on an average better than those generated by an automated test case generator designed specifically for the assignment.Master of Science
29
Baca, Dejan. "Automated static code analysis : A tool for early vulnerability detection." Licentiate thesis, Karlskrona : Department of Systems and Software Engineering, School of Engineering, Blekinge Institute of Technology, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00429.
Full text
30
Tienaho, Marjaana, and Jesus Barrio. "Automated testing in changeable systems -Techniques to support modifications." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2585.
Full textAbstract:
Due to the fast enlargement and complexity of systems used among telecommunication companies, the need for automatically testing has grown. The changeable nature of these systems makes implementation of automated testing to a difficult task. Finding an automated testing technique that is suitable for these types of systems is the subject of this thesis and several different types of scripting techniques has been considered. To be able to conduct this, an industrial case study is used; which shows how scripting techniques are affected by different types of changeability occurring in a system.Marjaana Tienaho E-mail: Marjaana_tienaho@spray.se Jesús Barrio E-mail: jesus_barrio@hotmail.com E-mail: jesus_barrio@hotmail.com
31
Le, Borgne Alexandre. "ARIANE : Automated Re-Documentation to Improve software Architecture uNderstanding and Evolution." Thesis, IMT Mines Alès, 2020. http://www.theses.fr/2020EMAL0001.
Full textAbstract:
Tout au long de son cycle de vie, un logiciel peut connaître de nombreux changements affectant potentiellement sa conformité avec sa documentation originelle. De plus, bien qu'une documentation à jour, conservant les décisions de conception prises pendant le cycle de développement, soit reconnue comme une aide importante pour maîtriser les évolutions, la documentation des logiciels est souvent obsolète. Les modèles d’architectures sont l’une des pièces majeures de la documentation. Assurer leur cohérence avec les autres modèles d’un logiciel (incluant son code) pendant les processus d’évolution (co-évolution) est un atout majeur pour la qualité logicielle. En effet, la compréhension des architectures logicielles est hautement valorisable en termes de capacités de réutilisation, d'évolution et de maintenance. Pourtant les modèles d’architectures sont rarement explicitement disponibles et de nombreux travaux de recherche visent à les retrouver à partir du code source. Cependant, la plupart des approches existantes n'effectuent pas un strict processus de rétro-documentation afin de re-documenter les architectures "comme elles sont implémentées" mais appliquent des étapes de ré-ingénierie en regroupant des éléments de code dans de nouveaux composants. Ainsi, cette thèse propose un processus de re-documentation des architectures telles qu’elles ont été conçues et implémentées, afin de fournir un support d’analyse des décisions architecturales effectives. Cette re-documentation se fait par l’analyse du code orienté objet et les descripteurs de déploiement de projets. Le processus re-documente les projets dans le langage de description d’architecture Dedal, qui est spécialement conçu pour contrôler et guider l’évolution des logiciels.Un autre aspect très important de la documentation des logiciels est le suivi de leurs différentes versions. Dans de nombreuses approches et gestionnaires de version actuels, comme Github, les fichiers sont versionnés de manière agnostique. S’il est possible de garder une trace de l’historique des versions de n’importe quel fichier, aucune information ne peut être fournie sur la sémantique des changements réalisés. En particulier, lors du versionnement d’éléments logiciels, il n’est fourni aucun diagnostic de retro-compatibilité avec les versions précédentes. Cette thèse propose donc un mécanisme de versionnement d’architectures logicielles basé sur le métamodèle et les propriétés formelles de l’ADL Dedal.Il permet d’analyser automatiquement les versions en termes de substituabilité, de gérer la propagation de version et d’incrémenter automatiquement les numéros de versions en tenant compte de l’impact des changements. En proposant cette approche formelle, cette thèse vise à prévenir le manque de contrôle des décisions architecturale (dérive / érosion).Cette thèse s’appuie sur une étude empirique appliquant les processus de re-documentation et de versionnement à de nombreuses versions d’un projet industriel extrait de GitHubAll along its life-cycle, a software may be subject to numerous changes that may affect its coherence with its original documentation. Moreover, despite the general agreement that up-to-date documentation is a great help to record design decisions all along the software life-cycle, software documentation is often outdated. Architecture models are one of the major documentation pieces. Ensuring coherence between them and other models of the software (including code) during software evolution (co-evolution) is a strong asset to software quality. Additionally, understanding a software architecture is highly valuable in terms of reuse, evolution and maintenance capabilities. For that reason, re-documenting software becomes essential for easing the understanding of software architectures. However architectures are rarely available and many research works aim at automatically recovering software architectures from code. Yet, most of the existing re-documenting approaches do not perform a strict reverse-documenting process to re-document architectures "as they are implemented" and perform re-engineering by clustering code into new components. Thus, this thesis proposes a framework for re-documentating architectures as they have been designed and implemented to provide a support for analyzing architectural decisions. This re-documentation is performed from the analysis of both object-oriented code and project deployment descriptors. The re-documentation process targets the Dedal architecture language which is especially tailored for managing and driving software evolution.Another highly important aspect of software documentation relates to the way concepts are versioned. Indeed, in many approaches and actual version control systems such as Github, files are versioned in an agnostic manner. This way of versioning keeps track of any file history. However, no information can be provided on the nature of the new version, and especially regarding software backward-compatibility with previous versions. This thesis thus proposes a formal way to version software architectures, based on the use of the Dedal architecture description language which provides a set of formal properties. It enables to automatically analyze versions in terms of substitutability, version propagation and proposes an automatic way for incrementing version tags so that their semantics corrrespond to actual evolution impact. By proposing such a formal approach, this thesis intends to prevent software drift and erosion.This thesis also proposes an empirical study based on both re-documenting and versioning processes on numerous versions on an enterprise project taken from Github
32
Adcock, Bruce M. "Working Towards the Verified Software Process." The Ohio State University, 2010. http://rave.ohiolink.edu/etdc/view?acc_num=osu1293463269.
Full text
33
Stenvi, Teddie. "An automated testing strategy targeted for efficient use in the consulting domain." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2863.
Full textAbstract:
Test automation can decrease release cycle time for software systems compared to manual test execution. Manual test execution is also considered inefficient and error-prone. However, few companies have gotten far within the field of test automation. This thesis investigates how testing and test automation is conducted in a test consulting setting. It has been recognized that low test process maturity is common in customer projects and this has led to equally low system testability and stability. The study started with a literature survey which summarized the current state within the field of automated testing. This was followed by a consulting case study. In the case study it was investigated how the identified test process maturity problems affect the test consulting services. The consulting automated testing strategy (CATS) been developed to meet the current identified challenges in the domain. Customer guidelines which aim to increase the test process maturity in the customer organization have also been developed as a support to the strategy. Furthermore, the study has included both industrial and academic validation which has been conducted through interviews with consultant practitioners and researchers.
34
Haider, Zulqarnain. "Continuous Deployment for Complex Software Intensive Industrial Systems." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-36518.
Full textAbstract:
Processes to develop and deliver software have been evolved over the years. One of the primary motivations of this evolution, is gaining the benefits of shorter time-to-market. Continuous deployment is a recent trend to deploy software to the customers automatically and in continuous fashion. Organizations adopting this trend could reach the customers faster through quick deliveries and improve the quality and productivity of the delivered product by an early feedback, and hence achieve increased customer satisfaction. Complex software intensive industrial systems are large-scale, distributed over heterogeneous platforms and interact with several sensors and actuators. Enabling continuous deployment for these industrial systems needs a stable deployment process able to cope with domain specific requirements and challenges. Notably, the required quality attributes of the deployed software product as well as the challenges introduced by the customer-specific nature of the domain. In this thesis, we formalize continuous deployment for industrial systems by identifying the main factors of an appropriate deployment process. In particular, we investigate high-level requirements, required quality attributes of the software product, and challenges in the deployment. Based on this, we propose a continuous deployment pipeline and a set of activities incorporated in the stages of the pipeline, in particular deployment and post-deployment stages. Moreover, we suggest automation support for the activities to both shorten the delivery time and to preserve repeatability and reliability of the deployment process. The aim of such a process is to maintain the quality attributes of the deployed software. We perform a case study to validate the proposed model by implementing a prototype in an industrial system
35
Grayson, Marisa Rose. "Approaching Overload: Diagnosis and Response to Anomalies in Complex and Automated Production Software Systems." The Ohio State University, 2018. http://rave.ohiolink.edu/etdc/view?acc_num=osu1543495231467142.
Full text
36
Folkler, Andreas. "Automated Theorem Proving : Resolution vs. Tableaux." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2002. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5531.
Full textAbstract:
The purpose of this master thesis was to investigate which of the two methods, resolution and tableaux, that is the most appropriate for automated theorem proving. This was done by implementing an automated theorem prover, comparing and documenting implementation problems, and measuring proving efficiency. In this thesis, I conclude that the resolution method might be more suitable for an automated theorem prover than tableaux, in the aspect of ease of implementation. Regarding the efficiency, the test results indicate that resolution is the better choice.Syftet med detta magisterarbete var att undersöka vilken av de två metoderna, resolution och tablå, som är mest lämpad för automatisk teorembevisning. Detta gjordes genom att implementera en automatisk teorembevisare, jämföra och dokumentera problem, samt att mäta prestanda för bevisning. I detta arbete drar jag slutsatsen att resolutionsmetoden förmodligen är mer lämpad än tablåmetoden för en automatisk teorembevisare, med avseende på hur svår den är att implementera. När det gäller prestanda indikerar utförda tester att resolutionsmetoden är det bästa valet.
37
Khan, Rizwan Bahrawar. "Comparative Study of Performance Testing Tools: Apache JMeter and HP LoadRunner." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-12915.
Full textAbstract:
Software Testing plays a key role in Software Development. There are two approaches to software testing i.e. Manual Testing and Automated Testing which are used to detect the faults. There are numbers of automated software testing tools with different purposes but it is always a problem to select a software testing tool according to the needs. In this research, the author compares two software testing tools i.e. Apache JMeter and HP LoadRunner to determine their usability and efficiency. To compare the tools, different parameters were selected which guide the tool evaluation process. To complete the objective of the research, a scenario-based survey is conducted and two different web applications were tested. From this research, it is found that Apache JMeter got an edge over HP Loadrunner in different aspects which include installation, interface and learning.
38
Nilsson, Simon. "Automated Culling of Data in a Relational Database for Archiving." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-18261.
Full textAbstract:
Background. Archiving of legacy information systems is challenging. When no options exist for extracting the information in a structured way, the last resort is to save the database. Optimally only the information that is relevant should be saved and the rest of the information could be removed. Objectives. The goal is to develop a method for assisting the archivist in the process of culling a database before archiving. The method should be described as rules defining how the tables can be identified.Methods. To get an overview of how the process works today and what archivists think can be improved, a number of interviews with experts in database archiving is done. The results from the interviews are then analysed, together with test databases to define rules that can be used in a general case. The rules are then implemented in a prototype that is tested and evaluated to verify if the method works. Results. The results point to the algorithm being both faster and able to exclude more irrelevant tables than a person could do with the manual method. An algorithm for finding candidate keys has also been improved to decrease the number of tests and execution time in the worst case. Conclusions. The evaluation shows results that point to the method working as intended while resulting in less work for the archivist. More work should be done on this method to improve it further.
39
Olofsson, Niclas. "Automated testing of a dynamic web application." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-107745.
Full textAbstract:
Software testing plays an important role in the process of verifying software functionality and preventing bugs in production code. By writing automated tests using code instead of conducting manual tests, the amount of tedious work during the development process can be reduced and the software quality can be improved. This thesis presents the results of a conducted case study on how automated testing can be used when implementing new functionality in a Ruby on Rails web application. Different frameworks for automated software testing are used as well as test-driven development methodology, with the purpose of getting a broad perspective on the subject. This thesis studies common issues with testing web applications, and discuss drawbacks and advantages of different testing approaches. It also looks into quality factors that are applicable for tests, and analyze how these can be measured.
40
Ozturk, Can. "Software Tool Development For The Automated Configuration Of Flexray Networks For In-vehicle Communication." Master's thesis, METU, 2013. http://etd.lib.metu.edu.tr/upload/12615568/index.pdf.
Full textAbstract:
The increasing use of electronic components in today&rsquos automobiles demands more powerful in-vehicle network communication protocols. FlexRay protocol, which is expected to be the de-facto standard in the near future, is a deterministic, fault tolerant and fast protocol designed for in vehicle communication. For proper operation of a FlexRay network the communication schedule needs to be computed and the nodes need to be configured before startup. Current software tools that are geared towards FlexRay only deal with the configuration process. The schedule needs to be computed by a network designer manually and it is necessary to input the designed schedule and the configurable parameters by hand. This thesis improves upon a previous scheduling software to automatically compute the network schedule, and then generate a universally acceptable FIBEX file that can be imported to available software tools to produce the necessary FlexRay node configuration files.
41
Rasheed, Amer, and Muhammad Mustansar Ali Khan. "Dispatching strategies to evaluate performance for automated guided vehicles in the transport of containers." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3398.
Full text
42
Lewis, Matt. "Precise verification of C programs." Thesis, University of Oxford, 2014. http://ora.ox.ac.uk/objects/uuid:34b5ed5a-160b-4e2c-8dac-eab62a24f78c.
Full textAbstract:
Most current approaches to software verification are one-sided -- a safety prover will try to prove that a program is safe, while a bug-finding tool will try to find bugs. It is rare to find an analyser that is optimised for both tasks, which is problematic since it is hard to know in advance whether a program you wish to analyse is safe or not. The result of taking a one-sided approach to verification is false alarms: safety provers will often claim that safe programs have errors, while bug-finders will often be unable to find errors in unsafe programs. Orthogonally, many software verifiers are designed for reasoning about idealised programming languages that may not have widespread use. A common assumption made by verification tools is that program variables can take arbitrary integer values, while programs in most common languages use fixed-width bitvectors for their variables. This can have a real impact on the verification, leading to incorrect claims by the verifier. In this thesis we will show that it is possible to analyse C programs without generating false alarms, even if they contain unbounded loops, use non-linear arithmetic and have integer overflows. To do this, we will present two classes of analysis based on underapproximate loop acceleration and second-order satisfiability respectively. Underapproximate loop acceleration addresses the problem of finding deep bugs. By finding closed forms for loops, we show that deep bugs can be detected without unwinding the program and that this can be done without introducing false positives or masking errors. We then show that programs accelerated in this way can be optimised by inlining trace automata to reduce their reachability diameter. This inlining allows acceleration to be used as a viable technique for proving safety, as well as finding bugs. In the second part of the thesis, we focus on using second-order logic for program analysis. We begin by defining second-order SAT: an extension of propositional SAT that allows quantification over functions. We show that this problem is NEXPTIME-complete, and that it is polynomial time reducible to finite-state program synthesis. We then present a fully automatic, sound and complete algorithm for synthesising C programs from a specification written in C. Our approach uses a combination of bounded model checking, explicit-state model checking and genetic programming to achieve surprisingly good performance for a problem with such high complexity. We conclude by using second-order SAT to precisely and directly encode several program analysis problems including superoptimisation, de-obfuscation, safety and termination for programs using bitvector arithmetic and dynamically allocated lists.
43
Oskarsson, Andreas. "Efficient transformation from general flow into a specific test case in an automated testing environment." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3718.
Full textAbstract:
SIMON is an automated testing application developed by WM-Data Consulting in Växjö, Sweden. Previously the test cases, called BIFs, run by SIMON to test the applications under test has been written manually in a very time consuming manner offering no protection against errors in the structure or misspellings. This thesis investigates a replacement to the manual method when creating the BIFs; my own developed application called the BIF-Editor. The usage of the BIF-Editor guaranteed correct syntax and structure and made the creation of the BIFs faster, but did it increase the quality of the BIFs? So to evaluate the BIF-Editor, the quality regarding path coverage of BIFs manually created was compared with BIFs created during the same elapsed time using the BIF-Editor. This evaluation showed that the usage of the BIF-Editor increased the quality of the BIFs by making the creation safer, but primarily faster which enabled the user to produce more BIFs than previously possible resulting in a raised path cover.
44
Mahmood, Shahid. "A Systematic Review of Automated Test Data Generation Techniques." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4349.
Full textAbstract:
Automated Test Data Generation (ATDG) is an activity that in the course of software testing automatically generates test data for the software under test (SUT). It usually makes the testing more efficient and cost effective. Test Data Generation (TDG) is crucial for software testing because test data is one of the key factors for determining the quality of any software test during its execution. The multi-phased activity of ATDG involves various techniques for each of its phases. This research field is not new by any means, albeit lately new techniques have been devised and a gradual increase in the level of maturity has brought some diversified trends into it. To this end several ATDG techniques are available, but emerging trends in computing have raised the necessity to summarize and assess the current status of this area particularly for practitioners, future researchers and students. Further, analysis of the ATDG techniques becomes even more important when Miller et al. [4] highlight the hardship in general acceptance of these techniques. Under this scenario only a systematic review can address the issues because systematic reviews provide evaluation and interpretation of all available research relevant to a particular research question, topic area, or phenomenon of interest. This thesis, by using a trustworthy, rigorous, and auditable methodology, provides a systematic review that is aimed at presenting a fair evaluation of research concerning ATDG techniques of the period 1997-2006. Moreover it also aims at identifying probable gaps in research about ATDG techniques of defined period so as to suggest the scope for further research. This systematic review is basically presented on the pattern of [5 and 8] and follows the techniques suggested by [1].The articles published in journals and conference proceedings during the defined period are of concern in this review. The motive behind this selection is quite logical in the sense that the techniques that are discussed in literature of this period might reflect their suitability for the prevailing software environment of today and are believed to fulfill the needs of foreseeable future. Furthermore only automated and/or semiautomated ATDG techniques have been chosen for consideration while leaving the manual techniques as they are out of the scope. As a result of the preliminary study the review identifies ATDG techniques and relevant articles of the defined period whereas the detailed study evaluates and interprets all available research relevant to ATDG techniques. For interpretation and elaboration of the discovered ATDG techniques a novel approach called ‘Natural Clustering’ is introduced. To accomplish the task of systematic review a comprehensive research method has been developed. Then on the practical implications of this research method important results have been gained. These results have been presented in statistical/numeric, diagrammatic, and descriptive forms. Additionally the thesis also introduces various criterions for classification of the discovered ATDG techniques and presents a comprehensive analysis of the results of these techniques. Some interesting facts have also been highlighted during the course of discussion. Finally, the discussion culminates with inferences and recommendations which emanate from this analysis. As the research work produced in the thesis is based on a rich amount of trustworthy information, therefore, it could also serve the purpose of being an upto- date guide about ATDG techniques.Shahid Mahmood Folkparksvägen 14:23 372 40 Ronneby Sweden +46 76 2971676
45
Sedgwick, Brandon M. "Automated Source Code Structure Feedback Using srcML and RelaxNG." University of Akron / OhioLINK, 2013. http://rave.ohiolink.edu/etdc/view?acc_num=akron1376558188.
Full text
46
Lindgren, Jonas. "Analysis of requirements for an automated testing and grading assistance system." Thesis, Linköpings universitet, Datorteknik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-105692.
Full textAbstract:
This thesis analyzes the configuration and security requirements of an auto-mated assignment testing system. The requirements for a flexible yet powerfulconfiguration format is discussed in depth, and an appropriate configurationformat is chosen. Additionally, the overall security requirements of this systemis discussed, analyzing the different alternatives available to fulfill the require-ments.Framläggningen redan avklarad.
47
Petersén, Elin. "Examining maintenance cost of automated GUI tests : An empirical study of how test script design affects the maintenance of automated visual GUI tests." Thesis, Linköpings universitet, Programvara och system, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-171783.
Full textAbstract:
GUI testing is expensive to perform manually. Software systems involving a heterogeneous set of components exclude the applicability of specific GUI testing techniques. Visual GUI Testing (VGT) is a test automation technique that combines image recognition with scripts. It applies to almost any GUI driven application. VGT is proven to be cost-effective in comparison with manual testing. Still, it is expensive to maintain. This study investigates if test script design by following specific guidelines positively affects maintenance costs. A case study was conducted to identify best practices for VGT w.r.t. maintenance time. Four VGT versions were developed for each manual test case. These consisted of two design versions, with/without guidelines, for the two VGT-tools EyeAutomate and Sikuli. Data was collected using time measurements, observations, and interviews. Results highlighted differences in initial development time and maintenance time between the two design versions. In total, 44 observations were collected. 17 were related to the design versions, 17 to the VGT-tools, and 10 to VGT in general, initial development, and the system under test. The interviews collected the perceptions of VGT in general, maintenance of the different VGT versions, and guidelines. In conclusion, the combination of the guidelines did not have a positive effect on maintenance in terms of costs and experience. However, some of the individual guidelines did. A rationale why the guidelines did not give the desired result was identified. Future research is necessary to investigate other combinations of guidelines, such as those identified as beneficial.
48
Clettborn, Adam, and Edwin Wallin. "An exploration of the test prioritization process on large software projects with no requirement specification." Thesis, Jönköping University, JTH, Datateknik och informatik, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-51391.
Full textAbstract:
Software projects with a larger code base can be hard to maintain, and testing could therefore be a necessity. But how would one prioritize tests in their existing software project, if their project never had any tests? The purpose of this study is to find concrete steps of how to prioritize tests in a software project, independent of project type and development language. Said steps were found through two iterations of the Action Learning method. The results were found without any requirements specification, which lead to using intuition, together with code complexity, to prioritize test cases, after breaking down the project into its modules. As the study was conducted on only one specific software project, the result is limited to that specific software project until further research is conducted.
49
Rotting, Tjädermo Viktor, and Alex Tanskanen. "System Upgrade Verification : An automated test case study." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-165125.
Full textAbstract:
We live in a society where automatization is becoming more common, whether it be cars or artificial intelligence. Software needs to be updated using patches, however, these patches have the possibility of breaking components. This study takes such a patch in the context of Ericsson, identifies what needs to be tested, investigates whether the tests can be automated and assesses how maintainable they are. Interviews were used for the identification of system and software parts in need of testing. Then tests were implemented in an automated test suite to test functionality of either a system or software. The goal was to reduce time of troubleshooting for employees without interrupting sessions for users as well as set up a working test suite. When the automated testing is completed and implemented in the test suite, the study is concluded by measuring the maintainability of the scripts using both metrics and human assessment through interviews. The result showed the testing suite proved maintainable, both from the metric point of view and from human assessment.
50
Mehrmand, Arash. "A Factorial Experiment on Scalability of Search-based Software Testing." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4224.
Full textAbstract:
Software testing is an expensive process, which is vital in the industry. Construction of the test-data in software testing requires the major cost and knowing which method to use in order to generate the test data is very important. This paper discusses the performance of search-based algorithms (preferably genetic algorithm) versus random testing, in software test-data generation. A factorial experiment is designed so that, we have more than one factor for each experiment we make. Although many researches have been done in the area of automated software testing, this research differs from all of them due to sample programs (SUTs) which are used. Since the program generation is automatic as well, Grammatical Evolution is used to guide the program generations. They are not goal based, but generated according to the grammar we provide, with different levels of complexity. Genetic algorithm is first applied to programs, then we apply random testing. Based on the results which come up, this paper recommends one method to use for software testing, if the SUT has the same conditions as we had in this study. SUTs are not like the sample programs, provided by other studies since they are generated using a grammar.