Relevant bibliographies by topics / Antipattern

Contents

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

Academic literature on the topic 'Antipattern'

Author: Grafiati
Published: 10 March 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 'Antipattern.'

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 "Antipattern"

1

Settas, Dimitrios L., Sulayman K. Sowe, and Ioannis G. Stamelos. "Detecting similarities in antipattern ontologies using semantic social networks: implications for software project management." Knowledge Engineering Review 24, no. 3 (September 2009): 287–307. http://dx.doi.org/10.1017/s0269888909990075.

Full text
Abstract:
AbstractOntology has been recently proposed as an appropriate formalism to model software project management antipatterns, in order to encode antipatterns in a computer understandable form and introduce antipatterns to the Semantic Web. However, given two antipattern ontologies, the same entity can be described using different terminology. Therefore, the detection of similar antipattern ontologies is a difficult task. In this paper, we introduce a three-layered antipattern semantic social network, which involves the social network, the antipattern ontology network and the concept network. Social Network Analysis (SNA) techniques can be used to assist software project managers in finding similar antipattern ontologies. For this purpose, SNA measures are extracted from one layer of the semantic social network to another and this knowledge is used to infer new links between antipattern ontologies. The level of uncertainty associated with each new link is represented using Bayesian Networks (BNs). Furthermore, BNs address the issue of quantifying the uncertainty of the data collected regarding antipattern ontologies for the purposes of the conducted analysis. Finally, BNs are used to augment SNA by taking into account meta-information in their calculations. Hence, other knowledge not included in the social network can be used in order to search the social network for further inference. The benefits of using an antipattern semantic social network are illustrated using an example community of software project management antipattern ontologies.
APA, Harvard, Vancouver, ISO, and other styles
2

Zmeev, D. O., O. A. Zmeev, and L. S. Ivanova. "Antipattern Practice for Essence Practice Library." Programmnaya Ingeneria 13, no. 7 (August 22, 2022): 311–21. http://dx.doi.org/10.17587/prin.13.311-321.

Full text
Abstract:
The Essence graphical representation language allows to describe various project management practices in software development. At the moment, the Practice Library describes the most popular development methodologies, but work with various risks, such as code smells or antipatterns, which may be cause of future problems, is not represented. This article presents an extension for the Practice Library of the Essence language in the form of a practice for working with antipatterns. To represent antipatterns in the system, the Antipattern subalpha, its states and checkpoints are proposed. Antipatterns states and checkpoints: 1. Detected: о Signs of poor-quality design or implementation of the Software System have been found. о The boundaries of the low-quality area in the Software System have been defined. о Work Products associated with the inferior part of the Software System have been defined. 2. Identified: о The Software System Elements included in the Antipattern have been determined. о The type of antipattern has been determined. о Dependencies of the Software System on the antipattern elements have been determined. о The impact of the antipattern on the Software System has been estimated. 3. Refactoring Method Defined: о Possible options for refactoring have been identified. о The cost of the refactoring options has been assessed. о The most suitable refactoring method has been selected. 4. Fixed: о The Software System elements included in the antipattern are completely covered by tests. о The antipattern has been refactored. о Tests confirm that the Software System remains operational. о The Work Products related to the changed part of the Software System have been updated. 5. Closed: о Tests, reviews or other appropriate activities have been undertaken to ensure that the antipattern has been corrected or shown not to actually be a fault or flaw. о The antipattern management has been finalized. о Technical debt has decreased. To record data about an antipattern, the work product Antipattern Report and its levels of details with checkpoints are proposed. Levels of details and checkpoints are: 1. Antipattern detected: о The components of the Software System included in the antipattern are defined. 2. Antipatterns properties are determined: о An antipattern type has been defined. 3. Antipattern influence determined: о The cost of antipattern fixing was estimated. о An assessment of possible losses associated with the presence of an antipattern was carried out. о The antipattern is recognized as mandatory for elimination. 4. Antipattern eliminated — optional: о Refactoring completed. о Testing showed the correct work of the components included in the antipattern. о Antipattern elimination activity completed. To analyze the architecture of the system, the Inspect Architecture activity is proposed. The Fix Architecture activity represents actions to fix architecture flaws. Code analysis is presented as a Review the Code activity, and correction of deficiencies found during the analysis is presented as a Refactor the Code activity. The influence of subalpha on the state of the Software System alpha is analyzed. Recommendations were given on the proposed activities. Information about activities is presented in the form of diagrams in the Essence language. The proposed practice allows to record information about the found flaws in the code, process them correctly and avoid problems with the project in the future. It is an example of working with entities that negatively affect the progress of the project.
APA, Harvard, Vancouver, ISO, and other styles
3

Saluja, Shivani, and Usha Batra. "Classification and Analysis of Static Metric Based Antipattern Detection in Service Computing." Recent Advances in Computer Science and Communications 13, no. 4 (October 19, 2020): 747–57. http://dx.doi.org/10.2174/2213275912666190809105751.

Full text
Abstract:
Background: Design Pattern is regarded as an essential component for enhancement of system design which can further improve the reusability and maintainability whereas antipattern degrades the quality of the program. Antipatterns are sub-optimal implementation choices which initially appears to be a good concept but later on leads to low code maintainability and higher maintenance costs. Objective: The identification of antipatterns which lead to performance degradation plays an important role in the reduction of expensive work and cost involved in maintenance, redesign, reimplementation, and redeployment. The main motivation is to refactor the source code in order to reduce maintenance efforts. Antipatterns impact reliability, testability and maintainability, but they still lack clear identification because of different interpretations and definition of each antipattern. There is a need for a benchmark to analyze the result generated by antipatterns. Methods: Static and dynamic analysis individually do not suffice for antipattern .A hybrid approach is proposed by combining rule based static analysis with dynamic run time analysis. Before applying the hybrid approach a simple manual validation was done to exclude the type of input which had the least probability of containing antipattern. The approach aims at optimizing the results by inclusion of response time metric measure which can be evaluated at runtime execution of the web service. Results and Conclusion: : The paper focusses on detection of antipatterns from web services based on code level and interface level static metrics .Only a brief overview of dynamic approach for detection is proposed. The future scope of this paper will focus on detection of antipattern based on more number of dynamic metrics and also a comparative analysis of the results generated from static, dynamic and hybrid approach.
APA, Harvard, Vancouver, ISO, and other styles
4

Cortellessa, Vittorio, Daniele Di Pompeo, Vincenzo Stoico, and Michele Tucci. "Software Model Refactoring Driven by Performance Antipattern Detection." ACM SIGMETRICS Performance Evaluation Review 49, no. 4 (June 2, 2022): 53–58. http://dx.doi.org/10.1145/3543146.3543159.

Full text
Abstract:
The satisfaction of ever more stringent performance requirements is one of the main reasons for software evolution. However, determining the primary causes of performance degradation is generally challenging, as they may depend on the joint combination of multiple factors (e.g., workload, software deployment, hardware utilization). With the increasing complexity of software systems, classical bottleneck analysis seems to show limitations in capturing complex performance problems. Hence, in the last decade, the detection of performance antipatterns has gained momentum as an effective way to identify performance degradation causes. In this tool paper we introduce PADRE (Performance Antipattern Detection and REfactoring), a tool for: (i) detecting performance antipattern in UML models, and (ii) refactoring models with the aim of removing the detected antipatterns. PADRE has been implemented within Epsilon, which is an open-source platform for model-driven engineering, and it grounds on a methodology that allows performance antipattern detection and refactoring within the same implementation context.
APA, Harvard, Vancouver, ISO, and other styles
5

Cortellessa, Vittorio, Daniele Di Pompeo, Vincenzo Stoico, and Michele Tucci. "Software Model Refactoring Driven by Performance Antipattern Detection." ACM SIGMETRICS Performance Evaluation Review 49, no. 4 (June 2, 2022): 53–58. http://dx.doi.org/10.1145/3543146.3543159.

Full text
Abstract:
The satisfaction of ever more stringent performance requirements is one of the main reasons for software evolution. However, determining the primary causes of performance degradation is generally challenging, as they may depend on the joint combination of multiple factors (e.g., workload, software deployment, hardware utilization). With the increasing complexity of software systems, classical bottleneck analysis seems to show limitations in capturing complex performance problems. Hence, in the last decade, the detection of performance antipatterns has gained momentum as an effective way to identify performance degradation causes. In this tool paper we introduce PADRE (Performance Antipattern Detection and REfactoring), a tool for: (i) detecting performance antipattern in UML models, and (ii) refactoring models with the aim of removing the detected antipatterns. PADRE has been implemented within Epsilon, which is an open-source platform for model-driven engineering, and it grounds on a methodology that allows performance antipattern detection and refactoring within the same implementation context.
APA, Harvard, Vancouver, ISO, and other styles
6

Bán, Dénes. "The Connection between Antipatterns and Maintainability in Firefox." Acta Cybernetica 23, no. 2 (2017): 471–90. http://dx.doi.org/10.14232/actacyb.23.2.2017.3.

Full text
Abstract:
The notion that antipatterns have a detrimental effect on source code maintainability is widely accepted, but there is relatively little objective evidence to support it. We seek to investigate this issue by analyzing the connection between antipatterns and maintainability in an empirical study of Firefox, an open source browser application developed in C++. After extracting antipattern instances and maintainability information from 45 revisions, we looked for correlations to uncover a connection between the two concepts. We found statistically significant negative values for both Pearson and Spearman correlations, most of which were under -0.65. These values suggest there are strong, inverse relationships, thereby supporting our initial assumption that the more antipatterns the source code contains, the harder it is to maintain. Lastly, we combined these data into a table applicable for machine learning experiments, which we conducted using Weka [10] and several of its classifier algorithms. All five regression types we tried had correlation coefficients over 0.77 and used mostly negative weights for the antipattern predictors in the models we constructed. In conclusion, we can say that this empirical study is another step towards objectively demonstrating that antipatterns have an adverse effect on software maintainability.
APA, Harvard, Vancouver, ISO, and other styles
7

Dhanaraj, Rajesh Kumar, Vinothsaravanan Ramakrishnan, M. Poongodi, Lalitha Krishnasamy, Mounir Hamdi, Ketan Kotecha, and V. Vijayakumar. "Random Forest Bagging and X-Means Clustered Antipattern Detection from SQL Query Log for Accessing Secure Mobile Data." Wireless Communications and Mobile Computing 2021 (November 24, 2021): 1–9. http://dx.doi.org/10.1155/2021/2730246.

Full text
Abstract:
In the current ongoing crisis, people mostly rely on mobile phones for all the activities, but query analysis and mobile data security are major issues. Several research works have been made on efficient detection of antipatterns for minimizing the complexity of query analysis. However, more focus needs to be given to the accuracy aspect. In addition, for grouping similar antipatterns, a clustering process was performed to eradicate the design errors. To address the above-said issues and further enhance the antipattern detection accuracy with minimum time and false positive rate, in this work, Random Forest Bagging X-means SQL Query Clustering (RFBXSQLQC) technique is proposed. Different patterns or queries are initially gathered from the input SQL query log, and bootstrap samples are created. Then, for each pattern, various weak clusters are constructed via X-means clustering and are utilized as the weak learner (clusters). During this process, the input patterns are categorized into different clusters. Using the Bayesian information criterion, the similarity measure is employed to evaluate the similarity between the patterns and cluster weight. Based on the similarity value, patterns are assigned to either relevant or irrelevant groups. The weak learner results are aggregated to form strong clusters, and, with the aid of voting, a majority vote is considered for designing strong clusters with minimum time. Experiments are conducted to evaluate the performance of the RFBXSQLQC technique using the IIT Bombay dataset using the metrics like antipattern detection accuracy, time complexity, false-positive rate, and computational overhead with respect to the differing number of queries. The results revealed that the RFBXSQLQC technique outperforms the existing algorithms by 19% with pattern detection accuracy, 34% minimized time complexity, 64% false-positive rate, and 31% in terms of computational overhead.
APA, Harvard, Vancouver, ISO, and other styles
8

Conklin, Darrell. "Antipattern Discovery in Folk Tunes." Journal of New Music Research 42, no. 2 (June 2013): 161–69. http://dx.doi.org/10.1080/09298215.2013.809125.

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

NAVARRO, ELENA, CARLOS E. CUESTA, DEWAYNE E. PERRY, and PASCUAL GONZÁLEZ. "ANTIPATTERNS FOR ARCHITECTURAL KNOWLEDGE MANAGEMENT." International Journal of Information Technology & Decision Making 12, no. 03 (May 2013): 547–89. http://dx.doi.org/10.1142/s0219622013500211.

Full text
Abstract:
Recent research on Software Architecture has recovered its original emphasis on keeping track of design decisions and their rationales during software development, compiling them under the name of architectural knowledge (AK). This knowledge is composed of decision assets, which relate to each other creating a decision network structure. We argue that relationships in these networks of AK contain valuable information, in particular when they describe negative semantics. We use antipatterns to exploit and manage these negative relationships systematically. After examining and classifying the kinds of AK relationships, we describe a method that enriches this network by means of antipattern structures. To show the feasibility and suitability of this approach, we provide a proof-of-concept by applying it to an existing process, ATRIUM, with a concrete example, the Gas Station metaphor. Results of the use of the presented approach into three different projects with different complexities show both its feasibility and applicability.
APA, Harvard, Vancouver, ISO, and other styles
10

Müller-Frączek, Iwona. "Proposition of Synthetic Measure." Przegląd Statystyczny 64, no. 4 (December 31, 2017): 421–36. http://dx.doi.org/10.5604/01.3001.0014.0830.

Full text
Abstract:
The aim of the study was to propose a new method for construction of synthetic variable. We analyzed distance between object and pattern (antipattern) in relation to sum of all distances between the pattern (antipattern) and other objects. This allowed us to characterize position of a region among others. The described measure is limited. Diagnostic variables do not require normalization or conversion to stimulants. Its main advantage is comparability of analyzes carried out for various years. The proposed method was illustrated by an empirical example. The values of measurement were compared with those obtained by Hellwig’s method. They were similar but not identical. Then two methods were compared in terms of correctness. None of them had a significant advantage.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Antipattern"

1

Lin, Chia-en. "Performance Engineering of Software Web Services and Distributed Software Systems." Thesis, University of North Texas, 2014. https://digital.library.unt.edu/ark:/67531/metadc500103/.

Full text
Abstract:
The promise of service oriented computing, and the availability of Web services promote the delivery and creation of new services based on existing services, in order to meet new demands and new markets. As Web and internet based services move into Clouds, inter-dependency of services and their complexity will increase substantially. There are standards and frameworks for specifying and composing Web Services based on functional properties. However, mechanisms to individually address non-functional properties of services and their compositions have not been well established. Furthermore, the Cloud ontology depicts service layers from a high-level, such as Application and Software, to a low-level, such as Infrastructure and Platform. Each component that resides in one layer can be useful to another layer as a service. It hints at the amount of complexity resulting from not only horizontal but also vertical integrations in building and deploying a composite service. To meet the requirements and facilitate using Web services, we first propose a WSDL extension to permit specification of non-functional or Quality of Service (QoS) properties. On top of the foundation, the QoS-aware framework is established to adapt publicly available tools for Web services, augmented by ontology management tools, along with tools for performance modeling to exemplify how the non-functional properties such as response time, throughput, or utilization of services can be addressed in the service acquisition and composition process. To facilitate Web service composition standards, in this work we extended the framework with additional qualitative information to the service descriptions using Business Process Execution Language (BPEL). Engineers can use BPEL to explore design options, and have the QoS properties analyzed for the composite service. The main issue in our research is performance evaluation in software system and engineering. We researched the Web service computation as the first half of this dissertation, and performance antipattern detection and elimination in the second part. Performance analysis of software system is complex due to large number of components and the interactions among them. Without the knowledge of experienced experts, it is difficult to diagnose performance anomalies and attempt to pinpoint the root causes of the problems. Software performance antipatterns are similar to design patterns in that they provide what to avoid and how to fix performance problems when they appear. Although the idea of applying antipatterns is promising, there are gaps in matching the symptoms and generating feedback solution for redesign. In this work, we analyze performance antipatterns to extract detectable features, influential factors, and resource involvements so that we can lay the foundation to detect their presence. We propose system abstract layering model and suggestive profiling methods for performance antipattern detection and elimination. Solutions proposed can be used during the refactoring phase, and can be included in the software development life cycle. Proposed tools and utilities are implemented and their use is demonstrated with RUBiS benchmark.
APA, Harvard, Vancouver, ISO, and other styles
2

Schönefeld, Marc. "Refactoring of security antipatterns in distributed Java components." Bamberg Univ. of Bamberg Press, 2010. http://d-nb.info/1003208398/34.

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

Schönefeld, Marc [Verfasser]. "Refactoring of security antipatterns in distributed Java components / von Marc Schönefeld." Bamberg : Univ. of Bamberg Press, 2010. http://d-nb.info/1003208398/34.

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

Andrzej, Tuchołka. "Methodology for assessing the construction of machine elements using neural models and antipatterns : doctoral dissertation." Rozprawa doktorska, [s.n.], 2020. http://dlibra.tu.koszalin.pl/Content/1317.

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

Larsson, Edvin, and Jesper Hägglund. "Studying the Relation between Linguistic and Design Quality in RESTful APIs." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-97696.

Full text
Abstract:
REST (REpresentational State Transfer) is commonly used for designing APIs. Two main categories of REST API quality have been identified in previous research: linguistic and design quality. Linguistic quality revolves around the design of the URIs. Design quality revolves around the metadata and body in HTTP requests and responses. For enabling and simplifying communications with REST, both linguistic and design quality are important, however, previous research has shown that even major APIs using REST are not always following best practices for linguistic and design quality. This study investigates if there is a statistical relation between linguistic and design quality. We selected 326 API endpoints from ten public APIs for this study. This study has reused and improved a Java-based tool in previous research for detecting aspects of linguistic quality in the APIs endpoints. For this study, we also developed a tool based on Node.js for detecting aspects of design quality in the API endpoints. These two tools are applied on the same API endpoints to be able to study the statistical relation. A Chi-Square test, implemented with R, showed that there is a significant statistical relation in our findings between linguistic and design quality. Pairwise phi-coefficient comparisons, implemented with Python, between each combination of the linguistic and design aspects used in this study identified eight weak and two moderate relations among the linguistic and design quality aspects. However, sample tests showed that the Java-based tool for detecting linguistic quality were not accurate, which made us fail to answer our problem formulation.
APA, Harvard, Vancouver, ISO, and other styles
6

Sadia, Ahmad, and Osama Zarraa. "Are APIs with Poor Design Subject to Poor Lexicon? : A Google Perspective." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-96846.

Full text
Abstract:
REST (Representational state transfer) is an architectural style for distributed hypermedia systems. The simplicity of REST allows straightforward communication between HTTP clients and servers using URIs (Uniform Resource Identifiers) and HTTP methods, e.g., GET, POST, PUT, and DELETE. To do the communication effectively between clients and servers, there is a set of best design practices (design and linguistic patterns) shall be followed, and a set of poor design practices (design and linguistic antipatterns) shall be avoided. This study aims to determine whether there is a relationship between design and linguistic quality in Google RESTful APIs. To find this relation, a tool is developed to detect patterns and antipatterns in REST APIs both in terms of design and linguistic quality. The input of this tool is qualitative data (Google APIs) and its output is quantitative data. Using this quantitative data, a statistical study is then performed to detect the relation. The tests that are conducted to obtain the final results are Chi-squared and Phi Coefficient tests. The result of Chi-squared that considered all the groups of patterns and antipatterns shows that there is a statistically significant relation between design and linguistic quality. However, when we assess the individual pair of patterns and antipatterns, our Phi Coefficient tests show that for most of the cases, there is no or negligible relationship between linguistic and design patterns and antipatterns.
APA, Harvard, Vancouver, ISO, and other styles
7

Régis, Hugo Nathan Barbosa. "Detecção dinâmica de antipadrões em sistemas baseados em serviços utilizando um sistema multiagente." Universidade Federal Rural do Semi-Árido, 2017. http://bdtd.ufersa.edu.br:80/tede/handle/tede/843.

Full text
Abstract:
Submitted by Lara Oliveira (lara@ufersa.edu.br) on 2018-03-20T21:54:36Z No. of bitstreams: 1 HugoNBR_DISSERT.pdf: 2536238 bytes, checksum: 0dfec391fbd30092d6d905cfe4301c34 (MD5)
Approved for entry into archive by Vanessa Christiane (referencia@ufersa.edu.br) on 2018-06-18T17:00:26Z (GMT) No. of bitstreams: 1 HugoNBR_DISSERT.pdf: 2536238 bytes, checksum: 0dfec391fbd30092d6d905cfe4301c34 (MD5)
Approved for entry into archive by Vanessa Christiane (referencia@ufersa.edu.br) on 2018-06-18T17:00:34Z (GMT) No. of bitstreams: 1 HugoNBR_DISSERT.pdf: 2536238 bytes, checksum: 0dfec391fbd30092d6d905cfe4301c34 (MD5)
Made available in DSpace on 2018-06-18T17:00:49Z (GMT). No. of bitstreams: 1 HugoNBR_DISSERT.pdf: 2536238 bytes, checksum: 0dfec391fbd30092d6d905cfe4301c34 (MD5) Previous issue date: 2017-08-31
Coordenação de Aperfeiçoamento de Pessoal de Nível Superior
During development of Service-Based Systems (SBS), bad solutions, design or implementation errors can lead to antipatterns that, as opposed to patterns, are bad specifications for recurring problems. Antipatterns result in deviations of functionality during the execution of the system, not adequately satisfying its requirements, which can degrade the Quality of Service (QoS) of the SBS. Its detection and correction are of extreme importance, the emergence of antipatterns may hinder future maintenance and evolution of SBS. As detection method, this work proposes the use of a Multiagent System (MAS), executing search at runtime and notifying the system administrator of QoS drops on the SBS caused by antipatterns. The detection of these antipatterns allows the agents to act in correction the project using the solution recommended by the MAS for the detected problem. The results show that, in the worst cases, the emergence of antipatterns reached extrapolate up to twice the response time of services in a Web Service. The MAS was able to detect, in execution time, the 3 antipatterns studied at work. When adopted, the solutions proposed by the MAS also normalized the response time
Durante o desenvolvimento de Sistemas Baseados em Serviços (SBS), soluções ruins, erros de projeto ou implementação podem conduzir ao surgimento de antipadrões, que em oposição aos padrões, são especificações ruins para problemas recorrentes. Antipadrões acarretam em desvios de funcionalidade durante a execução do sistema, não satisfazendo adequadamente aos seus requisitos, o que pode degradar a Qualidade de Serviço (QoS) de um SBS. Sua detecção e correção são de extrema importância pois o surgimento de antipadrões pode dificultar a manutenção e a futura evolução do SBS. Como método de detecção, este trabalho propõe o uso de um Sistema Multiagente (SMA), realizando buscas em tempo de execução e notificando ao administrador do sistema sobre quedas de QoS no SBS causadas por antipadrões. A detecção desses antipadrões permite a atuação dos agentes na correção do projeto, usando a solução recomendada pelo SMA para o problema detectado. Os resultados mostraram que, nos piores casos, o surgimento de antipadrões chegou a extrapolar em até o dobro de tempo de resposta dos serviços em um Web Service. O SMA foi capaz de detectar, em tempo de execução, os 3 antipadrões estudados no trabalho. Quando adotadas, as soluções propostas pelo SMA também normalizaram o tempo de resposta
2018-03-20
APA, Harvard, Vancouver, ISO, and other styles
8

Pavlíčková, Jarmila. "Model zralosti zdrojového kódu objektových aplikací." Doctoral thesis, Vysoká škola ekonomická v Praze, 2007. http://www.nusl.cz/ntk/nusl-191816.

Full text
Abstract:
The goal of this disertation was to develop a maturity model for source code of object-oriented applications and to use this model to verify the quality of the source code of student's applications. The starting point of the thesis was devoted to the analysis of existing standards, norms, methodologies and summaries of best practice for assessing the quality of software products and analysis of the factors that affect the quality of the source code of object applications. To validate the results of the analysis of these factors, the analysis was complemented with a field research conducted among specialist with programming experience. The model to determine the maturity of source code of object-oriented applications was designed according to the analysis and the questionnaire. The statistical method of cluster analysis was used in the design of the model. The model was designed and the procedure of its use in the evaluation of source code was described. This model was pilot tested in education program at the University of Economics in Prague.
APA, Harvard, Vancouver, ISO, and other styles
9

Stephan, Matthew. "Detection of Java EE EJB Antipattern Instances using Framework-Specific Models." Thesis, 2009. http://hdl.handle.net/10012/4362.

Full text
Abstract:
Adding flexibility to a process or technology often comes with a price. This holds true in the case of the amendments made to Java EE platform to upgrade to version 5. Java EE 5 allows Enterprise Java Bean (EJB) developers the ability to configure EJBs via Java 5 annotations, through XML deployment descriptors, or through a combination of both. While this adds flexibility to the EJB configuration process, it also comes with the price of an EJB project's stakeholder not being able to ascertain the current configuration of an EJB project until runtime, due to the multiple sources of configuration and the complex overriding rules. Furthermore, to detect errors in configuration or perform antipattern instance detection it is clearly beneficial to have a representation of an EJB project that accurately represents the current configuration of the system. This thesis first presents an EJB Framework Specific Modeling Language (FSML) that formalizes the EJB domain's specific components in the form of a cardinality-based feature model. By having such a model and using and extending the existing FSML infrastructure, one retrieves a Framework Specific Model (FSM) through reverse engineering that represents all the information from the various sources of EJB configuration. By analyzing this FSM, we can create another model that represents the resolved configuration of an EJB project. We employ model filtration to highlight specific sources of configuration. We then use open-source and custom EJB projects to evaluate the EJB FSML and the resolved model. Models admit antipattern instance detection. This thesis presents two methods for running antipattern instance detection on an EJB project using existing EJB antipatterns in literature: 1) queries in Java that execute against the resolved configuration model; and 2) queries written in .QL, an object-oriented query language, against the EJB project's source code. We compare these two techniques qualitatively and propose a new approach based on this comparison that entails modeling the antipatterns and their symptoms within an FSML model declaratively.
APA, Harvard, Vancouver, ISO, and other styles
10

Fioravanti, Sara. "Performance engineering of multi-level meta-modeling architectures based on J2EE stack." Doctoral thesis, 2018. http://hdl.handle.net/2158/1119732.

Full text
Abstract:
Non-functional requirements of changeability and adaptability have primary relevance for a large class of software intensive systems that are intended for managing great volumes of data with a high degree of variety in the structure of contents. The attainment of these qualities can be largely facilitated by the assumption of a tailored software architecture. The Reflection architectural pattern is an elegant reusable solution to design software applications based on a meta-model that provides a self-representation of the types used in the domain model. This provides significant benefits in terms of adaptability, maintainability, self-awareness, and direct involvement of domain experts in the configuration stage. However, design by patterns does not account for performance as first-class requirement, and naturally incurs in well-known performance anti-patterns, which may become crucial when volume and variety must meet also velocity. The complexity is further exacerbated when the object oriented domain model is mapped to a relational database. The aim of this dissertation is to address performance engineering of a meta-modeling architecture based on J2EE technological stack, documenting common performance issues connected to the persistence layer and proposing some solutions. In this work are presented four selected performance anti-patterns about object-relational mapping strategies and proposed refactoring solutions. This research project also reports comparative experimental performance results attained by combining the pattern-based domain logic with a persistence layer based on NoSQL paradigm, and proposes techniques to identify and improve performance issues in a J2EE architecture. Experimental results are obtained by applying proposed solutions in the concrete case of a real application of data management in Healthcare context based on Reflection architectural pattern. Those results indicate the gain obtained in several use cases by using refactoring actions in the relational database scenario, and by replacing the persistence layer with NoSql technology (in particular MongoDB) in the secondo scenario.
APA, Harvard, Vancouver, ISO, and other styles

Books on the topic "Antipattern"

1

Laplante, Phillip A. Antipatterns. London: Taylor and Francis, 2005.

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

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

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

A, Laplante Phillip, and DeFranco Joanna F, eds. Antipatterns: Managing software organizations and people. 2nd ed. Boca Raton, FL: Auerbach Publications, 2011.

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

Malveau, Raphael C. AntiPatterns: Refactoring Software, Architectures, and Projects in Crisis. New York, New York, USA: John Wiley & Sons, 1998.

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

Tammer, Saleh, ed. Rails antipatterns: Best practice Ruby on Rails refactoring. [United States?]: Addison-Wesley Professional, 2009.

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

SQL antipatterns: Avoiding the pitfalls of database programming. Raleigh, N.C: Pragmatic Bookshelf, 2010.

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

1954-, Brown William J., ed. AntiPatterns: Refactoring software, architectures, and projects in crisis. New York: Wiley, 1998.

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

Pytel, Chad. Rails antipatterns: Best practice Ruby on Rails refactoring. Upper Saddle River, NJ: Addison-Wesley, 2011.

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

Neill, Colin J., Philip A. Laplante, and Joanna F. DeFranco. Antipatterns. Auerbach Publications, 2011. http://dx.doi.org/10.1201/b11509.

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

Neill, Colin J., and Philip A. Laplante. Antipatterns. Auerbach Publications, 2005. http://dx.doi.org/10.1201/9781420031249.

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

Book chapters on the topic "Antipattern"

1

Settas, Dimitrios, Georgios Meditskos, Nick Bassiliades, and Ioannis G. Stamelos. "Detecting Antipatterns Using a Web-Based Collaborative Antipattern Ontology Knowledge Base." In Lecture Notes in Business Information Processing, 478–88. Berlin, Heidelberg: Springer Berlin Heidelberg, 2011. http://dx.doi.org/10.1007/978-3-642-22056-2_50.

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

Conklin, Darrell, and Stéphanie Weisser. "Antipattern Discovery in Ethiopian Bagana Songs." In Discovery Science, 62–72. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-11812-3_6.

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

Conklin, Darrell, and Stéphanie Weisser. "Pattern and Antipattern Discovery in Ethiopian Bagana Songs." In Computational Music Analysis, 425–43. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-25931-4_16.

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

Calinescu, Radu, Vittorio Cortellessa, Ioannis Stefanakos, and Catia Trubiani. "Analysis and Refactoring of Software Systems Using Performance Antipattern Profiles." In Fundamental Approaches to Software Engineering, 357–77. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-45234-6_18.

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

Sarcar, Vaskaran. "AntiPatterns." In Design Patterns in C#, 601–8. Berkeley, CA: Apress, 2020. http://dx.doi.org/10.1007/978-1-4842-6062-3_29.

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

Palma, Francis. "Detection of SOA Antipatterns." In Service-Oriented Computing, 412–18. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-37804-1_43.

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

Sarcar, Vaskaran. "AntiPatterns: Avoid the Common Mistakes." In Java Design Patterns, 467–74. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-4078-6_28.

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

Stephens, Matt, and Doug Rosenberg. "Unit Testing Antipatterns (The “Don’ts”)." In Design Driven Testing, 203–26. Berkeley, CA: Apress, 2010. http://dx.doi.org/10.1007/978-1-4302-2944-5_9.

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

Jones, Capers. "Root Causes of Poor Software Quality." In Software Development Patterns and Antipatterns, 67–83. Boca Raton: Auerbach Publications, 2021. http://dx.doi.org/10.1201/9781003193128-4.

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

Jones, Capers. "Achieving Software Excellence." In Software Development Patterns and Antipatterns, 247–77. Boca Raton: Auerbach Publications, 2021. http://dx.doi.org/10.1201/9781003193128-11.

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

Conference papers on the topic "Antipattern"

1

Kaur, Harvinder, and Puneet Jai Kaur. "Optimized Unit Testing for Antipattern Detection." In the 2014 International Conference. New York, New York, USA: ACM Press, 2014. http://dx.doi.org/10.1145/2677855.2677909.

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

Dugan, Robert F., Ephraim P. Glinert, and Ali Shokoufandeh. "The Sisyphus database retrieval software performance antipattern." In the third international workshop. New York, New York, USA: ACM Press, 2002. http://dx.doi.org/10.1145/584369.584372.

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

Abramson, Mark, Stephan Kolitz, and Alexander Kahn. "Coordination Manager - Antidote to the Stovepipe Antipattern." In AIAA Infotech@Aerospace 2010. Reston, Virigina: American Institute of Aeronautics and Astronautics, 2010. http://dx.doi.org/10.2514/6.2010-3404.

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

Arcelli, Davide, Luca Berardinelli, and Catia Trubiani. "Performance Antipattern Detection through fUML Model Library." In the 2015 Workshop. New York, New York, USA: ACM Press, 2015. http://dx.doi.org/10.1145/2693561.2693565.

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

Arcelli, Davide, Vittorio Cortellessa, and Catia Trubiani. "Antipattern-based model refactoring for software performance improvement." In the 8th international ACM SIGSOFT conference. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2304696.2304704.

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

Kaur, Harvinder, and Puneet Jai Kaur. "A GUI based unit testing technique for antipattern identification." In 2014 5th International Conference- Confluence The Next Generation Information Technology Summit. IEEE, 2014. http://dx.doi.org/10.1109/confluence.2014.6949316.

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

Stephan, Matthew, and James R. Cordy. "Identification of Simulink model antipattern instances using model clone detection." In 2015 ACM/IEEE 18th International Conference on Model Driven Engineering Languages and Systems (MODELS). IEEE, 2015. http://dx.doi.org/10.1109/models.2015.7338258.

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

Settas, Dimitrios, Antonio Cerone, and Stefan Fenz. "Towards Automatic Generation of Ontology-Based Antipattern Bayesian Network Models." In 2011 9th International Conference on Software Engineering Research, Management and Applications (SERA). IEEE, 2011. http://dx.doi.org/10.1109/sera.2011.15.

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

Fontana, Francesca Arcelli, Jens Dietrich, Bartosz Walter, Aiko Yamashita, and Marco Zanoni. "Antipattern and Code Smell False Positives: Preliminary Conceptualization and Classification." In 2016 IEEE 23rd International Conference on Software Analysis, Evolution and Reengineering (SANER). IEEE, 2016. http://dx.doi.org/10.1109/saner.2016.84.

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

Arcelli, Davide, Vittorio Cortellessa, and Daniele Di Pompeo. "Automating Performance Antipattern Detection and Software Refactoring in UML Models." In 2019 IEEE 26th International Conference on Software Analysis, Evolution and Reengineering (SANER). IEEE, 2019. http://dx.doi.org/10.1109/saner.2019.8667967.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Antipattern' for particular source types:
Journal articles 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