Log in

Relevant bibliographies by topics / Software refactoring. Software engineering

Contents

Journal articles
Dissertations / Theses
Books
Book chapters
Conference papers
Reports

Academic literature on the topic 'Software refactoring. Software engineering'

Author: Grafiati

Published: 4 June 2021

Last updated: 15 February 2022

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 'Software refactoring. 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 "Software refactoring. Software engineering"

1

Chen, Le Yang, Yang Li, and Wu Jian. "Study on Surface Refactoring Based on Reverse Engineering Software - Imageware." Applied Mechanics and Materials 215-216 (November 2012): 652–55. http://dx.doi.org/10.4028/www.scientific.net/amm.215-216.652.

Full text

Abstract:

In this article, based on the research of point cloud acquisition, data preprocessing and surface refactoring of reverse engineering, we analyzed the function and process of the reversing software—IMAGEWARE so as to provide reverse engineering design methods to reversing style design of curved surface refactoring and re-design of products.

APA, Harvard, Vancouver, ISO, and other styles

2

Et.al, Abdullah Almogahed. "Empirical Studies on Software Refactoring Techniques in the Industrial Setting." Turkish Journal of Computer and Mathematics Education (TURCOMAT) 12, no. 3 (2021): 1705–16. http://dx.doi.org/10.17762/turcomat.v12i3.995.

Full text

Abstract:

Software refactoring is an approach that aims to improve software system quality by restructuring its internal design without altering the functionality of the software system. The software refactoring has gained comprehensive attention from the research community in software engineering since its emerging in 1999. Empirical studies were carried out to investigate whether the software refactoring indeed can achieve improvement in the software system quality. It is widely believed that refactoring has a favorable quality impact. However, several researchers have opposed this belief. This paper presents a systematic literature review (SLR) of the empirical studies that have been conducted in the industrial setting. Twenty studies were chosen and analyzed in depth as primary studies.The objectives of this SLR are to identify the refactoring techniques examined, and software quality attributes investigated as well as to analyze the connection between the refactoring techniques and the software quality attributes based on the selected empirical studies to understand the situation. The findings showed a lack of empirical research on the effect of the refactoring on software quality. Additionally, the relationship between the refactoring techniques and software quality attributes is unclear. Thus, several recommendations have been proposed to address these gaps.

APA, Harvard, Vancouver, ISO, and other styles

3

JÓŹWIAK, IRENEUSZ, MAKSYMILIAN KOWALCZYK, and ANDRZEJ PIOTROWICZ. "REFACTORIZATION'S IMPACT ON SOFTWARE RELIABILITY." International Journal of Reliability, Quality and Safety Engineering 13, no. 01 (2006): 47–60. http://dx.doi.org/10.1142/s0218539306002136.

Full text

Abstract:

Software refactorization is a process of changing program's source code structure without changing its functionality. The purpose of the refactorization is to make program's source code easier to understand and maintain, which in turn influence the fact that in a long term such code should have fewer errors (be more reliable). In recent years many works described refactorization, but till now there are no researches, which would assess long term influence of refactoring on reliability. In this work we try to depict our fundamental study on software systems reliability improvement in context of refactoring. We tried to find the answer to the question: What are benefits of using refactorization as far as reliability is concerned?

APA, Harvard, Vancouver, ISO, and other styles

4

Nguyen, Ai G., and Richard L. Sohn. "Refactoring administrative services module platform software." Bell Labs Technical Journal 8, no. 3 (2003): 105–10. http://dx.doi.org/10.1002/bltj.10080.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Zhang, Yang, Shixin Sun, Dongwen Zhang, Jing Qiu, and Zhihong Tian. "A consistency-guaranteed approach for Internet of Things software refactoring." International Journal of Distributed Sensor Networks 16, no. 1 (2020): 155014772090168. http://dx.doi.org/10.1177/1550147720901680.

Full text

Abstract:

The software architecture of Internet of Things defines the component model and interconnection topology of Internet of Things systems. Refactoring is a systematic practice of improving a software structure without altering its external behaviors. When the Internet of Things software is refactored, it is necessary to detect the correctness of Internet of Things software to ensure its security. To this end, this article proposes a novel refactoring correction detection approach to ensure software security. Control flow analysis and data flow analysis are used to detect code changes before and after refactoring, and synchronization dependency analysis is used to detect changes in synchronization dependency. Three detection algorithms are designed to detect refactoring correctness. Four real-world benchmark applications are used to evaluate our approach. The experimental results show that our proposed approach can ensure correctness of Internet of Things software refactoring.

APA, Harvard, Vancouver, ISO, and other styles

6

Ouni, Ali, Marouane Kessentini, Houari Sahraoui, Katsuro Inoue, and Kalyanmoy Deb. "Multi-Criteria Code Refactoring Using Search-Based Software Engineering." ACM Transactions on Software Engineering and Methodology 25, no. 3 (2016): 1–53. http://dx.doi.org/10.1145/2932631.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Pan, Wei-Feng, Bo Jiang, and Bing Li. "Refactoring Software Packages via Community Detection in Complex Software Networks." International Journal of Automation and Computing 10, no. 2 (2013): 157–66. http://dx.doi.org/10.1007/s11633-013-0708-y.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Dao, Thi-Huong, Xuan-Truong Nguyen, and Ninh-Thuan Truong. "Preservation of Class Invariants in Refactoring UML Models." International Journal of Software Engineering and Knowledge Engineering 29, no. 02 (2019): 221–44. http://dx.doi.org/10.1142/s0218194019500104.

Full text

Abstract:

In the field of software engineering, the term class invariants is known as a valuable term employed to delineate the semantic of UML class diagram elements (attributes and relationships) and must be held throughout the life-time of instances of the class. Refactoring, the activities of re-distributing classes, attributes and methods across the class hierarchy, is a powerful technique that is used to improve the quality of software systems. Performing refactoring on UML class diagrams obviously requires a special investigation of invariant-preserving on the refactored models. In this paper, we propose an approach to preserve class invariants in refactoring UML models. In order to achieve this aim, we first formalize the class diagram along with class invariants by mathematical notations. We then constitute the rules for five refactoring operations (deal with class hierarchies) in such a way to guarantee class invariants as well as proving correctness of the refactoring rules. Finally, the paper also makes provision of the proposed approach for practical applications in software re-engineering development process.

APA, Harvard, Vancouver, ISO, and other styles

9

Alenezi, Mamdouh, Mohammed Akour, and Osama Al Qasem. "Harnessing deep learning algorithms to predict software refactoring." TELKOMNIKA (Telecommunication Computing Electronics and Control) 18, no. 6 (2020): 2977. http://dx.doi.org/10.12928/telkomnika.v18i6.16743.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Durak, Umut. "Pragmatic model transformations for refactoring in Scilab/Xcos." International Journal of Modeling, Simulation, and Scientific Computing 07, no. 01 (2016): 1541004. http://dx.doi.org/10.1142/s1793962315410044.

Full text

Abstract:

Model-Based Development has become an industry wide standard paradigm. As an open source alternative, Scilab/Xcos is being widely employed as a hybrid dynamic systems modeling tool. With the increasing efficiency in implementation using graphical model development and code generation, the modeling and simulation community is struggling with assuring quality as well as maintainability and extendibility. Refactoring is defined as an evolutionary modernization activity where, most of the time, the structure of the artifact is changed to alter its quality characteristics, while keeping its behavior unchanged. It has been widely established as a technique for textual programming languages to improve the code structure and quality. While refactoring is also regarded as one of the key practices of model engineering, the methodologies and approaches for model refactoring are still under development. Architecture-Driven Modernization (ADM) has been introduced by the software engineering community as a model-based approach to software modernization, in which the implicit information that lies in software artifacts is extracted to models and model transformations are applied for modernization tasks. Regarding refactoring as a low level modernization task, the practices from ADM are adaptable. Accordingly, this paper proposes a model-based approach for model refactoring in order to come up with more efficient and effective model refactoring methodology that is accessible and extendable by modelers. Like other graphical modeling tools, Scilab/Xcos also possesses a formalized model specification conforming to its implicit metamodel. Rather than proposing another metamodel for knowledge extraction, this pragmatic approach proposes to conduct in place model-to-model transformations for refactoring employing the Scilab/Xcos model specification. To construct a structured model-based approach, the implicit Scilab/Xcos metamodel is explicitly presented utilizing ECORE as a meta-metamodel. Then a practical model transformation approach is established based on Scilab scripting. A Scilab toolset is provided to the modeler for in-place model-to-model transformations. Using a sample case study, it is demonstrated that proposed model transformation functions in Scilab provide a valuable refactoring tool.

APA, Harvard, Vancouver, ISO, and other styles

More sources

Dissertations / Theses on the topic "Software refactoring. Software engineering"

1

Patterson, Andrew Joseph 1974. "Tool support for introductory software engineering education." Monash University, School of Computer Science and Software Engineering, 2002. http://arrow.monash.edu.au/hdl/1959.1/7738.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Murphy-Hill, Emerson. "Programmer Friendly Refactoring Tools." PDXScholar, 2009. https://pdxscholar.library.pdx.edu/open_access_etds/2672.

Full text

Abstract:

Tools that perform semi-automated refactoring are currently under-utilized by programmers. If more programmers adopted refactoring tools, software projects could make enormous productivity gains. However, as more advanced refactoring tools are designed, a great chasm widens between how the tools must be used and how programmers want to use them. This dissertation begins to bridge this chasm by exposing usability guidelines to direct the design of the next generation of programmer-friendly refactoring tools, so that refactoring tools fit the way programmers behave, not vice-versa.

APA, Harvard, Vancouver, ISO, and other styles

3

Lif, Ruben, and Wilhelm Handberg. "Converting Outdated Software." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-176788.

Full text

Abstract:

The goal of this paper is to present a methodology for rewriting outdated software systems. We developed this method based on a work assignment from the company SSAB AB, where we were tasked with rewriting one of their outdated systems to fit modern standards. This paper discusses the reasons for rewriting outdated systems, and the steps of planning, analysing source code, the rewriting procedure, documenting the rewritten code, and evaluating it. By using the method we developed, we were able to produce a satisfactory rewritten application for SSAB, and believe that it can be reused for similar purposes in the future.

APA, Harvard, Vancouver, ISO, and other styles

4

Gilliland, Sean M. (Sean Michael). "Empirical analysis of software refactoring motivation and effects." Thesis, Massachusetts Institute of Technology, 2015. http://hdl.handle.net/1721.1/100376.

Full text

Abstract:

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2015.<br>Cataloged from PDF version of thesis.<br>Includes bibliographical references (pages 68-69).<br>As complexity and levels of technical debt within software systems increase over time the incentive of an organization to refactor legacy software likewise increases. However, the opportunity cost of such refactoring in terms of engineering time and monetary investment have proven difficult to effectively trade against the long term benefits of such refactoring. The research investigates the empirical effects of a multi-year refactoring effort performed at a world-leading software development organization. DSM architectural representations of software pre- and post-refactoring were compared using core-periphery analysis, and various quantitative metrics were identified and compared to identify leading indicators of refactoring. The research finds several uniquely identifying properties of the area of the software system identified for refactor, and performs a comparison of these properties against the architectural complexity of those modules. The paper concludes with suggestions for additional areas of research.<br>by Sean M. Gilliland.<br>S.M. in Engineering and Management

APA, Harvard, Vancouver, ISO, and other styles

5

Dersten, Sara. "Towards a guideline for refactoring of embedded systems." Licentiate thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-14592.

Full text

Abstract:

The electronics in automotive systems give great possibilities. It has contributed to environmental improvements through reduced emissions and reduced fuel consumption, safety, driver assistance, and quality through better diagnostic capabilities. Automotive systems are today distributed embedded systems that consist of several nodes that communicate with each other. The increasing possibilities have led to a situation where functions that used to be stand-alone, are today dependent on several inter-connected systems which all contribute to the desired functionality. This has increased the costs and the complexity to deal with the systems. The automotive industry is adopting a new open software architecture, called AUTOSAR, that is intended to reduce the complexity. AUTOSAR also gives possibilities for coping with large product ranges and for component sharing. The introduction of AUTOSAR is an example of an architecture change without modifying the external functionality. We have chosen to call such changes system refactoring. However, if the introduction of AUTOSAR is not successfully performed, there are risks for delayed development projects, which are costly for the automotive companies. Unfortunately, existing engineering standards and literature focus mostly on new product development and less on system re-factoring, and this gap needs to be filled. The goal of this research is to provide guidelines for refactoring, which provides support throughout the complete process of system architects in efforts to refactor the system. This thesis identifies the characteristics of refactoring processes. This is done by empirical studies of the drivers behind refactoring, the effects we can expect from refactoring, and the process activities and characteristics. The result can be used to create guidelines for improving the work of refactoring.

APA, Harvard, Vancouver, ISO, and other styles

6

Hopfner, Marbod. "Source Code Analysis, Management, and Visualization for PROLOG." Doctoral thesis, kostenfrei, 2008. http://www.opus-bayern.de/uni-wuerzburg/volltexte/2009/3630/.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Dobrzanski, Lukasz. "UML Model Refactoring : Support for Maintenance of Executable UML Models." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5715.

Full text

Abstract:

One of the inevitable negative effects of software evolution is design erosion. Refactoring is a technique that aims at counteracting this phenomenon by successively improving the design of software without changing its observable behaviour. Design erosion occurs also in the context of executable UML models, i.e. models that are detailed enough to be automatically compiled to executable applications. This thesis presents results of a study on applying refactoring to the area of maintenance of executable UML models. It contains an overview of recent approaches to UML model refactoring and to executable modelling, followed by identification of refactoring areas in models built in Telelogic TAU, a state-of-the art UML CASE tool. It proposes a systematic approach to specification of both executable UML model refactorings as well as associated bad smells in models. Additionally, it shows how refactorings can be implemented in Telelogic TAU.

APA, Harvard, Vancouver, ISO, and other styles

8

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

9

An, Kijin. "The Client Insourcing Refactoring to Facilitate the Re-engineering of Web-Based Applications." Diss., Virginia Tech, 2021. http://hdl.handle.net/10919/103391.

Full text

Abstract:

Developers often need to re-engineer distributed applications to address changes in requirements, made only after deployment. Much of the complexity of inspecting and evolving distributed applications lies in their distributed nature, while the majority of mature program analysis and transformation tools works only with centralized software. Inspired by business process re-engineering, in which remote operations can be insourced back in house to restructure and outsource anew, this dissertation brings an analogous approach to the re-engineering of distributed applications. Our approach introduces a novel automatic refactoring---Client Insourcing---that creates a semantically equivalent centralized version of a distributed application. This centralized version is then inspected, modified, and redistributed to meet new requirements. This dissertation demonstrates the utility of Client Insourcing in helping meet the changed requirements in performance, reliability, and security. We implemented Client Insourcing in the important domain of full-stack JavaScript applications, in which both the client and server parts are written in JavaScript, and applied our implementation to re-engineer mobile web applications. Client Insourcing reduces the complexity of inspecting and evolving distributed applications, thereby facilitating their re-engineering. This dissertation is based on 4 conference papers and 2 doctoral symposium papers, presented at ICWE 2019, SANER 2020, WWW 2020, and ICWE 2021.<br>Doctor of Philosophy<br>Modern web applications are distributed across a browser-based client and a remote server. Software developers need to optimize the performance of web applications as well as correct and modify their functionality. However, the vast majority of mature development tools, used for optimizing, correcting, and modifying applications work only with non-distributed software, written to run on a single machine. To facilitate the maintenance and evolution of web applications, this dissertation research contributes new automated software transformation techniques. These contributions can be incorporated into the design of software development tools, thereby advancing the engineering of web applications.

APA, Harvard, Vancouver, ISO, and other styles

10

Nylander, Amy. "Kodrefaktorisering." Thesis, Örebro universitet, Institutionen för naturvetenskap och teknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-44875.

Full text

Abstract:

Denna rapport har sitt ursprung i det kodefaktoriseringsarbete som utfärdats våren 2013 som examensarbete i dataingenjörsprogrammet vid Örebro Universitet. Arbetet utfärdades på Nethouse i Örebro, och hade stort fokus på koddesign och kodkvalitet. I rapporten diskuteras vilka faktorer som påverkar hur underhållbar och läsbar en kod är, men också hur man på ett rimligt sätt kan utvärdera och mäta kodkvalitet. Den teoretiska biten blandas med den praktiska, där läsaren introduceras för ett flertal metoder, och hur dessa sedan implementerades i det faktiska projektet som Nethouse tillhandahöll.<br>This report has its origins in the code refactoring work issued in spring 2013 as a Degree Project in the Computer Engineering Programme, at Örebro University. The work took place at Nethouse in Örebro, and had a major focus on code design, and code quality. The report discusses the factors that affect how maintainable and readable a code is, but also how to reasonably evaluate and measure code quality. The theory is mixed with the practical, where the reader is introduced to a variety of methods, and how these were then implemented in the actual project that Nethouse provided.

APA, Harvard, Vancouver, ISO, and other styles

More sources

Books on the topic "Software refactoring. Software engineering"

1

Refactoring to agility. Addison Wesley Professional, 2006.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

2

Laplante, Phillip A. AntiPatterns: Identification, refactoring, and management. Taylor & Francis, 2005.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

3

Refactoring workbook. Addison-Wesley Professional, 2004.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

4

Lippert, Martin. Refactoring in Large Software Projects. John Wiley & Sons, Ltd., 2006.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

5

Fields, Jay. Refactoring. Addison-Wesley, 2010.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

6

Refactoring to patterns. Addison-Wesley, 2005.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

7

Wake, William C. Refactoring in Ruby. Addison-Wesley, 2010.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

8

Wake, William C. Refactoring in Ruby. Addison-Wesley, 2009.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

9

Wake, William C. Refactoring in Ruby. Addison-Wesley, 2010.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

10

Fields, Jay. Refactoring. Addison-Wesley, 2010.

Find full text

APA, Harvard, Vancouver, ISO, and other styles

More sources

Book chapters on the topic "Software refactoring. Software engineering"

1

Romanovsky, Konstantin, Dmitry Koznov, and Leonid Minchin. "Refactoring the Documentation of Software Product Lines." In Software Engineering Techniques. Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22386-0_12.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

de Jonge, Maartje, and Eelco Visser. "An Algorithm for Layout Preservation in Refactoring Transformations." In Software Language Engineering. Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-28830-2_3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

McComb, Tim. "Refactoring Object-Z Specifications." In Fundamental Approaches to Software Engineering. Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24721-0_5.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Adams, Mark. "Refactoring Proofs with Tactician." In Software Engineering and Formal Methods. Springer Berlin Heidelberg, 2015. http://dx.doi.org/10.1007/978-3-662-49224-6_6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Ghannem, Adnane, Ghizlane El Boussaidi, and Marouane Kessentini. "Model Refactoring Using Interactive Genetic Algorithm." In Search Based Software Engineering. Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39742-4_9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Wynn-Williams, Stephen, Zinovy Diskin, Vera Pantelic, et al. "SL2SF: Refactoring Simulink to Stateflow." In Fundamental Approaches to Software Engineering. Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-16722-6_15.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Ghaith, Shadi, and Mel Ó Cinnéide. "Improving Software Security Using Search-Based Refactoring." In Search Based Software Engineering. Springer Berlin Heidelberg, 2012. http://dx.doi.org/10.1007/978-3-642-33119-0_10.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Simons, Chris, Jeremy Singer, and David R. White. "Search-Based Refactoring: Metrics Are Not Enough." In Search-Based Software Engineering. Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-22183-0_4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Moghadam, Iman Hemati. "Multi-level Automated Refactoring Using Design Exploration." In Search Based Software Engineering. Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-23716-4_9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Mahouachi, Rim, Marouane Kessentini, and Mel Ó. Cinnéide. "Search-Based Refactoring Detection Using Software Metrics Variation." In Search Based Software Engineering. Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-39742-4_11.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software refactoring. Software engineering"

1

Mealy, E., and P. Strooper. "Evaluating software refactoring tool support." In Australian Software Engineering Conference (ASWEC'06). IEEE, 2006. http://dx.doi.org/10.1109/aswec.2006.26.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Samarthyam, Ganesh, Girish Suryanarayana, and Tushar Sharma. "Refactoring for software architecture smells." In ASE'16: ACM/IEEE International Conference on Automated Software Engineering. ACM, 2016. http://dx.doi.org/10.1145/2975945.2975946.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Alizadeh, Vahid, Mohamed Amine Ouali, Marouane Kessentini, and Meriem Chater. "RefBot: Intelligent Software Refactoring Bot." In 2019 34th IEEE/ACM International Conference on Automated Software Engineering (ASE). IEEE, 2019. http://dx.doi.org/10.1109/ase.2019.00081.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Ge, Xi, and Emerson Murphy-Hill. "Manual refactoring changes with automated refactoring validation." In ICSE '14: 36th International Conference on Software Engineering. ACM, 2014. http://dx.doi.org/10.1145/2568225.2568280.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Mealy, Erica, David Carrington, Paul Strooper, and Peta Wyeth. "Improving Usability of Software Refactoring Tools." In 2007 18th Australian Software Engineering Conference. IEEE, 2007. http://dx.doi.org/10.1109/aswec.2007.24.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Winters, Titus. "Non-atomic refactoring and software sustainability." In ICSE '18: 40th International Conference on Software Engineering. ACM, 2018. http://dx.doi.org/10.1145/3194793.3194794.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Pandimurugan, Mathavi Parvathi, and Aslin Jenila. "A survey of software testing in refactoring based software models." In International Conference on Nanoscience, Engineering and Technology (ICONSET 2011). IEEE, 2011. http://dx.doi.org/10.1109/iconset.2011.6168034.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Stoiber, Reinhard, Samuel Fricker, Michael Jehle, and Martin Glinz. "Feature Unweaving: Refactoring Software Requirements Specifications into Software Product Lines." In 2010 IEEE 18th International Conference on Requirements Engineering (RE). IEEE, 2010. http://dx.doi.org/10.1109/re.2010.59.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Kiezun, Adam, Michael D. Ernst, Frank Tip, and Robert M. Fuhrer. "Refactoring for Parameterizing Java Classes." In 29th International Conference on Software Engineering. IEEE, 2007. http://dx.doi.org/10.1109/icse.2007.70.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

Ratzinger, Jacek, Thomas Sigmund, Peter Vorburger, and Harald Gall. "Mining Software Evolution to Predict Refactoring." In First International Symposium on Empirical Software Engineering and Measurement (ESEM 2007). IEEE, 2007. http://dx.doi.org/10.1109/esem.2007.9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software refactoring. Software engineering"

1

Eslinger, S. Software Acquisition and Software Engineering Best Practices. Defense Technical Information Center, 1999. http://dx.doi.org/10.21236/ada371477.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Ardis, Mark, and Gary Ford. SEI (Software Engineering Institute) Report on Graduate Software Engineering Education, 1989. Defense Technical Information Center, 1989. http://dx.doi.org/10.21236/ada219018.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Cohen, Herbert E. Software Engineering in Ada. Defense Technical Information Center, 1988. http://dx.doi.org/10.21236/ada286826.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Johnson, Albert L. Software Engineering Education Directory. Defense Technical Information Center, 1988. http://dx.doi.org/10.21236/ada200630.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

McSteen, Bill, and Mark Schmick. Software Engineering Education Directory. Defense Technical Information Center, 1989. http://dx.doi.org/10.21236/ada207545.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Schultz, Herman P. Software Engineering Exercise Guidelines. Defense Technical Information Center, 1989. http://dx.doi.org/10.21236/ada212510.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Murphy, Carl. Parallel Software Engineering Assessment. Defense Technical Information Center, 1995. http://dx.doi.org/10.21236/ada303034.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Basili, Victor R., Jr Selby, Hutchens Richard W., and David H. Experimentation in Software Engineering. Defense Technical Information Center, 1985. http://dx.doi.org/10.21236/ada226830.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Basili, Victor R., Richard W. Selby, Hutchens Jr., and David H. Experimentation in Software Engineering,. Defense Technical Information Center, 1985. http://dx.doi.org/10.21236/ada170840.

Full text

APA, Harvard, Vancouver, ISO, and other styles

10

McSteen, Bill, Brian Gottier, and Mark Schmick. Software Engineering Education Directory. Defense Technical Information Center, 1990. http://dx.doi.org/10.21236/ada223740.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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