User Tools
teaching:reverse:2018:references
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
teaching:reverse:2018:references [2018/12/12 09:22] blay [Etudes] |
teaching:reverse:2018:references [2018/12/13 10:42] blay [Etudes] |
||
|---|---|---|---|
| Line 13: | Line 13: | ||
| - http://blog.cleancoder.com/ relativement au livre : Clean Code: A Handbook of Agile Software Craftsmanship | - http://blog.cleancoder.com/ relativement au livre : Clean Code: A Handbook of Agile Software Craftsmanship | ||
| by Robert C. Martin | by Robert C. Martin | ||
| + | - [[http://www.allitebooks.com/your-code-as-a-crime-scene/|Your Code as a Crime Scene ; Use Forensic Techniques to Arrest Defects, Bottlenecks, and Bad Design in Your Programs (The Pragmatic Programmers)]] Adam Tornhill | ||
| </panel> | </panel> | ||
| </accordion> | </accordion> | ||
| Line 125: | Line 126: | ||
| * keywords = "Software reuse, Software component, Object-oriented, API, Reverse engineering, Frequent usage pattern", | * keywords = "Software reuse, Software component, Object-oriented, API, Reverse engineering, Frequent usage pattern", | ||
| * Object-oriented Application Programing Interfaces (APIs) support software reuse by providing pre-implemented functionalities. Due to the huge number of included classes, reusing and understanding large APIs is a complex task. Otherwise, software components are accepted to be more reusable and understandable entities than object-oriented ones. Thus, in this paper, we propose an approach for reengineering object-oriented APIs into component-based ones. We mine components as a group of classes based on the frequency they are used together and their ability to form a quality-centric component. To validate our approach, we experimented on 100 Java applications that used four APIs." | * Object-oriented Application Programing Interfaces (APIs) support software reuse by providing pre-implemented functionalities. Due to the huge number of included classes, reusing and understanding large APIs is a complex task. Otherwise, software components are accepted to be more reusable and understandable entities than object-oriented ones. Thus, in this paper, we propose an approach for reengineering object-oriented APIs into component-based ones. We mine components as a group of classes based on the frequency they are used together and their ability to form a quality-centric component. To validate our approach, we experimented on 100 Java applications that used four APIs." | ||
| - | - [[https://www.researchgate.net/publication/325176682_Architectural_Technical_Debt_Identification_the_Research_Landscape|Architectural Technical Debt Identification: the Research Landscape]]}, | + | - [[https://www.researchgate.net/publication/325176682_Architectural_Technical_Debt_Identification_the_Research_Landscape|Architectural Technical Debt Identification: the Research Landscape]], |
| * author = {Verdecchia, Roberto and Malavolta, Ivano and Lago, Patricia}, | * author = {Verdecchia, Roberto and Malavolta, Ivano and Lago, Patricia}, | ||
| * year = {2018}, | * year = {2018}, | ||
teaching/reverse/2018/references.txt · Last modified: 2018/12/16 17:40 by blay
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
