Relevant bibliographies by topics / AUTOMATED SOFTWARE ENGINEERING

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'AUTOMATED SOFTWARE ENGINEERING'

Author: Grafiati
Published: 4 June 2021
Last updated: 31 January 2023

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources 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.

Journal articles on the topic "AUTOMATED SOFTWARE ENGINEERING"

1

Jackson, Michael. "Automated software engineering: supporting understanding." Automated Software Engineering 15, no. 3-4 (August 21, 2008): 275–81. http://dx.doi.org/10.1007/s10515-008-0034-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Crnkovic, Ivica, Heinz W. Schmidt, Judith Stafford, and Kurt Wallnau. "Automated Component-Based Software Engineering." Journal of Systems and Software 74, no. 1 (January 2005): 1–3. http://dx.doi.org/10.1016/j.jss.2003.11.016.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Carver, Jeffrey C., and Alexander Serebrenik. "Software Maintenance and Evolution and Automated Software Engineering." IEEE Software 35, no. 2 (March 2018): 102–4. http://dx.doi.org/10.1109/ms.2018.1661318.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

He, Shilin, Pinjia He, Zhuangbin Chen, Tianyi Yang, Yuxin Su, and Michael R. Lyu. "A Survey on Automated Log Analysis for Reliability Engineering." ACM Computing Surveys 54, no. 6 (July 2021): 1–37. http://dx.doi.org/10.1145/3460345.

Full text
Abstract:
Logs are semi-structured text generated by logging statements in software source code. In recent decades, software logs have become imperative in the reliability assurance mechanism of many software systems, because they are often the only data available that record software runtime information. As modern software is evolving into a large scale, the volume of logs has increased rapidly. To enable effective and efficient usage of modern software logs in reliability engineering, a number of studies have been conducted on automated log analysis. This survey presents a detailed overview of automated log analysis research, including how to automate and assist the writing of logging statements, how to compress logs, how to parse logs into structured event templates, and how to employ logs to detect anomalies, predict failures, and facilitate diagnosis. Additionally, we survey work that releases open-source toolkits and datasets. Based on the discussion of the recent advances, we present several promising future directions toward real-world and next-generation automated log analysis.
APA, Harvard, Vancouver, ISO, and other styles
5

PAGE, REX. "Engineering Software Correctness." Journal of Functional Programming 17, no. 6 (November 2007): 675–86. http://dx.doi.org/10.1017/s095679680700634x.

Full text
Abstract:
AbstractDesign and quality are fundamental themes in engineering education. Functional programming builds software from small components, a central element of good design, and facilitates reasoning about correctness, an important aspect of quality. Software engineering courses that employ functional programming provide a platform for educating students in the design of quality software. This pearl describes experiments in the use of ACL2, a purely functional subset of Common Lisp with an embedded mechanical logic, to focus on design and correctness in software engineering courses. Students find the courses challenging and interesting. A few acquire enough skill to use an automated theorem prover on the job without additional training. Many students, but not quite a majority, find enough success to suggest that additional experience would make them effective users of mechanized logic in commercial software development. Nearly all gain a new perspective on what it means for software to be correct and acquire a good understanding of functional programming.
APA, Harvard, Vancouver, ISO, and other styles
6

Gileva, L. Yu, N. A. Spirin, V. Yu Rybolovlev, A. V. Krasnobaev, and I. E. Kosachenko. "Software for automated engineering workstations at blast furnaces." Steel in Translation 39, no. 12 (December 2009): 1060–63. http://dx.doi.org/10.3103/s0967091209120055.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Chechik, Marsha, and Paul Grünbacher. "Guest editorial: selected areas in automated software engineering." Automated Software Engineering 25, no. 1 (August 16, 2017): 45–46. http://dx.doi.org/10.1007/s10515-017-0222-5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Grunske, Lars, and Mike Whalen. "Guest editorial: advanced topics in automated software engineering." Automated Software Engineering 25, no. 4 (September 21, 2018): 743–44. http://dx.doi.org/10.1007/s10515-018-0245-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Carrillo de Gea, Juan Manuel, Joaquín Nicolás, José L. Fernández-Alemán, and Ambrosio Toval. "Automated support for reuse-based requirements engineering in global software engineering." Journal of Software: Evolution and Process 29, no. 8 (May 3, 2017): e1873. http://dx.doi.org/10.1002/smr.1873.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Alexander, Ian. "Ian Alexander: Column for the Automated Software Engineering Journal." Automated Software Engineering 14, no. 3 (August 22, 2007): 365–68. http://dx.doi.org/10.1007/s10515-007-0014-4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "AUTOMATED SOFTWARE ENGINEERING"

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
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
3

Shaw, Hazel Anne. "Automated test of evolving software." Thesis, University of Bedfordshire, 2005. http://hdl.handle.net/10547/305743.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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
APA, Harvard, Vancouver, ISO, and other styles
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
APA, Harvard, Vancouver, ISO, and other styles
6

Holbrook, Elizabeth Ashlee. "SATISFACTION ASSESSMENT OF TEXTUAL SOFTWARE ENGINEERING ARTIFACTS." UKnowledge, 2009. http://uknowledge.uky.edu/gradschool_diss/712.

Full text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:

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.

APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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 applicability
Durch 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
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
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 text
Abstract:
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.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "AUTOMATED SOFTWARE ENGINEERING"

1

N, Earl Anthony, and McDermid John, eds. Software engineering environments: Automated support for software engineering. London: McGraw-Hill, 1992.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Schumann, Johann M. Automated Theorem Proving in Software Engineering. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-662-22646-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Satapathy, Suresh Chandra, Ajay Kumar Jena, Jagannath Singh, and Saurabh Bilgaiyan. Automated Software Engineering: A Deep Learning-Based Approach. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-38006-9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

1962-, Liu Jiming, Cheung Yiuming 1971-, and Yin Hujun 1962-, eds. Intelligent data engineering and automated learning: Revised papers. Berlin: Springer, 2003.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

J, Berndt Donald, and Kandel Abraham, eds. Automated database applications testing: Specification representation for automated reasoning. Singapore: World Scientific, 2010.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Ito, Takayuki. Complex Automated Negotiations: Theories, Models, and Software Competitions. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

service), SpringerLink (Online, ed. Automated Configuration Problem Solving. New York, NY: Springer New York, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

IEEE International Automated Software Engineering Conference (19th 2004 Linz, Austria). 19th IEEE International Conference on Automated Software Engineering: Proceedings : September 20-24, 2004, Linz, Austria. Los Alamitos, Calif: IEEE Computer Society, 2004.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
9

Sunazuka, Toshihiko. Integrating automated support for a software management cycle into the TAME system. College Park, Md: University of Maryland, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Society, IEEE Computer, SIGART, ACM Sigsoft, University of California, Irvine. Institute for Software Research., City University (London, England). School of Informatics., and University of California, Irvine. Dept. of Information and Computer Science., eds. The 20th IEEE/ACM International Conference on Automated Software Engineering: Long Beach, California, USA, November 7-11, 2005. New York, N.Y: Association for Computing Machinery, 2005.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "AUTOMATED SOFTWARE ENGINEERING"

1

Fischer, Bernd, and Johann M. Ph Schumann. "SETHEO goes software engineering: Application of ATP to software reuse." In Automated Deduction—CADE-14, 65–68. Berlin, Heidelberg: Springer Berlin Heidelberg, 1997. http://dx.doi.org/10.1007/3-540-63104-6_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Schumann, Johann M. "Formal Methods in Software Engineering." In Automated Theorem Proving in Software Engineering, 11–22. Berlin, Heidelberg: Springer Berlin Heidelberg, 2001. http://dx.doi.org/10.1007/978-3-662-22646-9_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Basu, Samik, and Tevfik Bultan. "Automated Choreography Repair." In Fundamental Approaches to Software Engineering, 13–30. Berlin, Heidelberg: Springer Berlin Heidelberg, 2016. http://dx.doi.org/10.1007/978-3-662-49665-7_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Söderberg, Emma, and Görel Hedin. "Automated Selective Caching for Reference Attribute Grammars." In Software Language Engineering, 2–21. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-19440-5_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Di Ruscio, Davide, Ralf Lämmel, and Alfonso Pierantonio. "Automated Co-evolution of GMF Editor Models." In Software Language Engineering, 143–62. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-19440-5_9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Tamburrelli, Giordano, and Alessandro Margara. "Towards Automated A/B Testing." In Search-Based Software Engineering, 184–98. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-09940-8_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Mallet, Frédéric, François Lagarde, Charles André, Sébastien Gérard, and François Terrier. "An Automated Process for Implementing Multilevel Domain Models." In Software Language Engineering, 314–33. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12107-4_22.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Franců, Jan, and Petr Hnětynka. "Automated Generation of Implementation from Textual System Requirements." In Software Engineering Techniques, 34–47. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22386-0_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Lukasczyk, Stephan, Florian Kroiß, and Gordon Fraser. "Automated Unit Test Generation for Python." In Search-Based Software Engineering, 9–24. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-59762-7_2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Batory, Don, Rui Gonçalves, Bryan Marker, and Janet Siegmund. "Dark Knowledge and Graph Grammars in Automated Software Design." In Software Language Engineering, 1–18. Cham: Springer International Publishing, 2013. http://dx.doi.org/10.1007/978-3-319-02654-1_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "AUTOMATED SOFTWARE ENGINEERING"

1

Murphy, Gail C. "Is software engineering research addressing software engineering problems?" In ASE '20: 35th IEEE/ACM International Conference on Automated Software Engineering. New York, NY, USA: ACM, 2020. http://dx.doi.org/10.1145/3324884.3417103.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Visser, Willem, Nikolaj Bjørner, and Natarajan Shankar. "Software engineering and automated deduction." In ICSE '14: 36th International Conference on Software Engineering. New York, NY, USA: ACM, 2014. http://dx.doi.org/10.1145/2593882.2593899.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Estublier, Jacky, and Sergio Garcia. "Concurrent Engineering support in Software Engineering." In 21st IEEE/ACM International Conference on Automated Software Engineering (ASE'06). IEEE, 2006. http://dx.doi.org/10.1109/ase.2006.28.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

van Deursen, Arie. "Software engineering without borders." In 2017 32nd IEEE/ACM International Conference on Automated Software Engineering (ASE). IEEE, 2017. http://dx.doi.org/10.1109/ase.2017.8115612.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Cook, Michael. "Software Engineering For Automated Game Design." In 2020 IEEE Conference on Games (CoG). IEEE, 2020. http://dx.doi.org/10.1109/cog47356.2020.9231750.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Tantithamthavorn, Chakkrit Kla, and Jirayus Jiarpakdee. "Explainable AI for Software Engineering." In 2021 36th IEEE/ACM International Conference on Automated Software Engineering (ASE). IEEE, 2021. http://dx.doi.org/10.1109/ase51524.2021.9678580.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Islam, Md Rakibul, and Minhaz F. Zibran. "Leveraging Automated Sentiment Analysis in Software Engineering." In 2017 IEEE/ACM 14th International Conference on Mining Software Repositories (MSR). IEEE, 2017. http://dx.doi.org/10.1109/msr.2017.9.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Menzies, Tim, Oussama Elrawas, Jairus Hihn, Martin Feather, Ray Madachy, and Barry Boehm. "The business case for automated software engineering." In the twenty-second IEEE/ACM international conference. New York, New York, USA: ACM Press, 2007. http://dx.doi.org/10.1145/1321631.1321676.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

"Proceedings 12th IEEE International Conference Automated Software Engineering." In Proceedings 12th IEEE International Conference Automated Software Engineering. IEEE, 1997. http://dx.doi.org/10.1109/ase.1997.632817.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

"14th IEEE International Conference on Automated Software Engineering." In 14th IEEE International Conference on Automated Software Engineering. IEEE, 1999. http://dx.doi.org/10.1109/ase.1999.802086.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "AUTOMATED SOFTWARE ENGINEERING"

1

Smith, Douglas R. Automated Support for Software Engineering. Fort Belvoir, VA: Defense Technical Information Center, March 1995. http://dx.doi.org/10.21236/ada294965.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Eastman, Brittany. Legal Issues Facing Automated Vehicles, Facial Recognition, and Privacy Rights. SAE International, July 2022. http://dx.doi.org/10.4271/epr2022016.

Full text
Abstract:
Facial recognition software (FRS) is a form of biometric security that detects a face, analyzes it, converts it to data, and then matches it with images in a database. This technology is currently being used in vehicles for safety and convenience features, such as detecting driver fatigue, ensuring ride share drivers are wearing a face covering, or unlocking the vehicle. Public transportation hubs can also use FRS to identify missing persons, intercept domestic terrorism, deter theft, and achieve other security initiatives. However, biometric data is sensitive and there are numerous remaining questions about how to implement and regulate FRS in a way that maximizes its safety and security potential while simultaneously ensuring individual’s right to privacy, data security, and technology-based equality. Legal Issues Facing Automated Vehicles, Facial Recognition, and Individual Rights seeks to highlight the benefits of using FRS in public and private transportation technology and addresses some of the legitimate concerns regarding its use by private corporations and government entities, including law enforcement, in public transportation hubs and traffic stops. Constitutional questions, including First, Forth, and Ninth Amendment issues, also remain unanswered. FRS is now a permanent part of transportation technology and society; with meaningful legislation and conscious engineering, it can make future transportation safer and more convenient.
APA, Harvard, Vancouver, ISO, and other styles
3

Tao, Yang, Amos Mizrach, Victor Alchanatis, Nachshon Shamir, and Tom Porter. Automated imaging broiler chicksexing for gender-specific and efficient production. United States Department of Agriculture, December 2014. http://dx.doi.org/10.32747/2014.7594391.bard.

Full text
Abstract:
Extending the previous two years of research results (Mizarch, et al, 2012, Tao, 2011, 2012), the third year’s efforts in both Maryland and Israel were directed towards the engineering of the system. The activities included the robust chick handling and its conveyor system development, optical system improvement, online dynamic motion imaging of chicks, multi-image sequence optimal feather extraction and detection, and pattern recognition. Mechanical System Engineering The third model of the mechanical chick handling system with high-speed imaging system was built as shown in Fig. 1. This system has the improved chick holding cups and motion mechanisms that enable chicks to open wings through the view section. The mechanical system has achieved the speed of 4 chicks per second which exceeds the design specs of 3 chicks per second. In the center of the conveyor, a high-speed camera with UV sensitive optical system, shown in Fig.2, was installed that captures chick images at multiple frames (45 images and system selectable) when the chick passing through the view area. Through intensive discussions and efforts, the PIs of Maryland and ARO have created the protocol of joint hardware and software that uses sequential images of chick in its fall motion to capture opening wings and extract the optimal opening positions. This approached enables the reliable feather feature extraction in dynamic motion and pattern recognition. Improving of Chick Wing Deployment The mechanical system for chick conveying and especially the section that cause chicks to deploy their wings wide open under the fast video camera and the UV light was investigated along the third study year. As a natural behavior, chicks tend to deploy their wings as a mean of balancing their body when a sudden change in the vertical movement was applied. In the latest two years, this was achieved by causing the chicks to move in a free fall, in the earth gravity (g) along short vertical distance. The chicks have always tended to deploy their wing but not always in wide horizontal open situation. Such position is requested in order to get successful image under the video camera. Besides, the cells with checks bumped suddenly at the end of the free falling path. That caused the chicks legs to collapse inside the cells and the image of wing become bluer. For improving the movement and preventing the chick legs from collapsing, a slowing down mechanism was design and tested. This was done by installing of plastic block, that was printed in a predesign variable slope (Fig. 3) at the end of the path of falling cells (Fig.4). The cells are moving down in variable velocity according the block slope and achieve zero velocity at the end of the path. The slop was design in a way that the deacceleration become 0.8g instead the free fall gravity (g) without presence of the block. The tests showed better deployment and wider chick's wing opening as well as better balance along the movement. Design of additional sizes of block slops is under investigation. Slops that create accelerations of 0.7g, 0.9g, and variable accelerations are designed for improving movement path and images.
APA, Harvard, Vancouver, ISO, and other styles
4

Chamberlain, C. A., and K. Lochhead. Data modeling as applied to surveying and mapping data. Natural Resources Canada/CMSS/Information Management, 1988. http://dx.doi.org/10.4095/331263.

Full text
Abstract:
The Geodetic Survey Division of the Canada Centre for Surveying is replacing the National Geodetic Data Base (NGDB) with the National Geodetic Information System (NGIS). For the NGIS to be successful, it was recognized that a sound, well engineered data mode was essential. The methodology chosen to design the data mode! was Nijssen's Information Analysis Methodology (NIAM), a binary modeling technique that is supported by a Computer Aided Software Engineering (CASE) tool, PC-IAST. An NGIS prototype has also been developed using Digital Equipment of Canada's Relational Database (Rdb) management system and COGNOS Corporations POWERHOUSE 4th generation language. This paper addresses the need for, and the advantages of using a strong engineering approach to data modeling and describes the use of the NIAM methodology in NGIS development. The paper identifies the relationship between the data mode!, data structures, the design and development of a database and the use of automated tools for systems development. In conclusion, critical success factors for the continuation of the N.G.I.S. developments are identified and the benefits that will accrue are enumerated.
APA, Harvard, Vancouver, ISO, and other styles
5

Chien, Stanley, Yaobin Chen, Lauren Christopher, Mei Qiu, and Zhengming Ding. Road Condition Detection and Classification from Existing CCTV Feed. Purdue University, 2022. http://dx.doi.org/10.5703/1288284317364.

Full text
Abstract:
The Indiana Department of Transportation (INDOT) has approximately 500 digital cameras along highways in populated areas of Indiana. These cameras are used to monitor traffic conditions around the clock, all year round. Currently, the videos from these cameras are observed one-by-one by human operators looking for traffic conditions and incidents. The main objective of this research was to develop an automatic, real-time system to monitor traffic conditions and detect incidents automatically. The Transportation and Autonomous Systems Institute (TASI) of the Purdue School of Engineering and Technology at Indiana University-Purdue University Indianapolis (IUPUI) and the Traffic Management Center of INDOT developed a system that monitors the traffic conditions based on the INDOT CCTV video feeds. The proposed system performs traffic flow estimation, incident detection, and classification of vehicles involved in an incident. The research team designed the system, including the hardware and software components added to the existing INDOT CCTV system; the relationship between the added system and the currently existing INDOT system; the database structure for traffic data extracted from the videos; and a user-friendly, web-based server for showing the incident locations automatically. The specific work in this project includes vehicle-detection, road boundary detection, lane detection, vehicle count over time, flow-rate detection, traffic condition detection, database development, web-based graphical user interface (GUI), and a hardware specification study. The preliminary prototype of some system components has been implemented in the Development of Automated Incident Detection System Using Existing ATMS CCT (SPR-4305).
APA, Harvard, Vancouver, ISO, and other styles
6

Striuk, Andrii M. Software engineering: first 50 years of formation and development. [б. в.], December 2018. http://dx.doi.org/10.31812/123456789/2880.

Full text
Abstract:
The article analyzes the main stages of software engineering (SE) development. Based on the analysis of materials from the first SE conferences (1968-1969), it was determined how the software crisis prompted scientists and practitioners to join forces to form an engineering approach to programming. Differences in professional training for SE are identified. The fundamental components of the training of future software engineers are highlighted. The evolution of approaches to the design, implementation, testing and documentation of software is considered. The system scientific, technological approaches and methods for the design and construction of computer programs are highlighted. Analysis of the historical stages of the development of SE showed that despite the universal recognition of the importance of using the mathematical apparatus of logic, automata theory and linguistics when developing software, it was created empirically without its use. The factor that led practitioners to turn to the mathematical foundations of an SE is the increasing complexity of software and the inability of empirical approaches to its development and management to cope with it. The training of software engineers highlighted the problem of the rapid obsolescence of the technological content of education, the solution of which lies in its fundamentalization through the identification of the basic foundations of the industry. It is determined that mastering the basics of computer science is the foundation of vocational training in SE.
APA, Harvard, Vancouver, ISO, and other styles
7

Chien, Stanley, Lauren Christopher, Yaobin Chen, Mei Qiu, and Wei Lin. Integration of Lane-Specific Traffic Data Generated from Real-Time CCTV Videos into INDOT's Traffic Management System. Purdue University, 2023. http://dx.doi.org/10.5703/1288284317400.

Full text
Abstract:
The Indiana Department of Transportation (INDOT) uses about 600 digital cameras along populated Indiana highways in order to monitor highway traffic conditions. The videos from these cameras are currently observed by human operators looking for traffic conditions and incidents. However, it is time-consuming for the operators to scan through all video data from all the cameras in real-time. The main objective of this research was to develop an automatic and real-time system and implement the system at INDOT to monitor traffic conditions and detect incidents automatically. The Transportation and Autonomous Systems Institute (TASI) of the Purdue School of Engineering and Technology at Indiana University-Purdue University Indianapolis (IUPUI) and the INDOT Traffic Management Center have worked together to research and develop a system that monitors the traffic conditions based on the INDOT CCTV video feeds. The proposed system performs traffic flow estimation, incident detection, and the classification of vehicles involved in an incident. The goal was to develop a system and prepare for future implementation. The research team designed the new system, in­cluding the hardware and software components, the currently existing INDOT CCTV system, the database structure for traffic data extracted from the videos, and a user-friendly web-based server for identifying individual lanes on the highway and showing vehicle flowrates of each lane automatically. The preliminary prototype of some system components was implemented in the 2018–2019 JTRP projects, which provided the feasibility and structure of the automatic traffic status extraction from the video feeds. The 2019–2021 JTRP project focused on developing and improving many features’ functionality and computation speed to make the program run in real-time. The specific work in this 2021–2022 JTRP project is to improve the system further and implement it on INDOT’s premises. The system has the following features: vehicle-detection, road boundary detection, lane detection, vehicle count and flowrate detection, traffic condition detection, database development, web-based graphical user interface (GUI), and a hardware specification study. The research team has installed the system on one computer in INDOT for daily road traffic monitoring operations.
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'AUTOMATED SOFTWARE ENGINEERING' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography