![Deprecation in Java
package org.serg;
import java.util.Date;
public class DateUser {
public static void main(String args[]) {
Date date = new Date();
int year = date.getYear();
}
}pecific](https://image.slidesharecdn.com/spring-170403153034/85/APIs-APIs-and-more-APIs-101-320.jpg)
APIs, APIs and more APIs
- 1. APIs, APIs and more APIs! Anand Ashok Sawant
- 3. Software Engineering is the discipline wherein a software engineer “writes a software component that will be combined with components written by other software engineers to build a system”
- 6. So what’s an API? An Application Programming Interface (API) is a set of routines, protocols, and tools for building software applications
- 8. Approaches Used Till Date
- 9. Approaches Used Till Date
- 10. Text matching
- 12. Approaches Used Till Date
- 15. Approaches Used Till Date
- 16. Partial Program Analysis (PPA)
- 17. Partial Program Analysis (PPA) No support for Java 1.5+
- 18. Approaches Used Till Date
- 19. Abstract Syntax Tree (AST) parsing
- 20. Abstract Syntax Tree (AST) parsing
- 21. Abstract Syntax Tree (AST) parsing No type information
- 22. fine-GRAPE
- 23. Maven POM file <project xmlns=“http://maven.apache.org/POM/4.0.0” … <dependencies> <dependency> <groupId>junit</groupId> <artifactId>junit</artifactId> <version>3.8.1</version> <scope>test</scope> </dependency> … </dependencies> … </project>
- 24. fine-GRAPE
- 25. Popular JAVA APIs 0 5000 10000 15000 20000 25000 hibernate-entitymanager guava spring-test spring-context log4j junit Number of projects referencing the APIs APIartifactID
- 26. Selected APIs
- 27. Data collected API Total Method Invocations Annotation Usages Guava 1,148,412 - Guice 59,097 48,945 Spring 19,894 40,525 Hibernate 196,169 16,259 Easymock 38,523 -
- 28. Studies
- 29. Studies
- 30. Client Lag Time Study Goal: Analyze the upgrade behavior of a client to see if they move to the latest version of an API or not. Outcome: We see that in most cases clients do not transition to the latest version of the API.
- 32. Research Questions RQ: Do clients of APIs migrate to a new version of the API?
- 33. Lag time is defined as the amount of time elapsed between a client’s API reference and the release date
- 34. Lag Time Example
- 35. Results
- 36. Probability Density of Lag Time
- 37. Popular Releases
- 38. Release Frequency of APIs
- 40. Projects do not upgrade versions often The latest version is not the most popular version Clients of frequently releasing APIs display less lag time
- 41. Studies
- 42. API Usage Study Goal: Measure the number features of an API that are actually used and rank them based on popularity Outcome: We see that very small portion of the APIs are used by clients.
- 44. RQ: How much of an API is broadly used? Research Questions
- 45. Hotspot features are those in the top 15% of popularity that is ranked by usage
- 46. Neutral features are those that are used by clients of an API but do not figure in the top 15% in terms of popularity
- 47. Coldspot features are those that are not used by any client of the API
- 48. Results
- 51. Core features
- 53. Small portions of the API are actually used in practice There are very few features that can be marked as hotspots Most features are coldspots Over ~ 90% of popular features can be regarded as core features Newer features have a low adoption percentage
- 54. Studies
- 55. API Popularity and Bug Relationship Goal: See if more bug reports emanate from parts of the API that are more popularly used by clients. Outcome: We observe that popular parts of the API are better tested and are in general less buggy than more popular parts of the API.
- 57. • RQ1: Are tests made for APIs exhaustive? That is do they cover the API artifacts well? • RQ2: Is there a connection between API coverage and popularity of an API artifact? Are popular parts better covered? • RQ3: Is there a connection between bugs in an API and popular parts of the API? Are more bugs reported in popular parts? • RQ4: Are core features of an API the most popular parts? Research Questions
- 58. Initial Intuition Popular parts of the API Buggy parts of the API
- 59. Test Coverage of the API
- 60. Dynamic Static
- 61. Initial Intuition Correct? Popular parts of the API Buggy parts of the API
- 63. APIs are generally well tested Popular parts of the API appear to be better tested There are fewer bugs that originate from the popular parts
- 64. Studies
- 65. API Deprecation Study Goal: Analyze the reaction of an API client to deprecation of an API artifact. Outcome: We see that in most cases clients do not react to a deprecated artifact, in fact they may even add more calls to a deprecated artifact.
- 66. Deprecation is an attribute applied to a computer software feature, characteristic, or practice to indicate that it should be avoided (often because it is being superseded).
- 68. Specific dataset Dynamically typed language “Small” dataset Implicit versions
- 72. Research Questions RQ0: What API versions do clients use? RQ1: How does API method deprecation affect clients? RQ2: What is the scale of reaction in affected clients? RQ3: What proportion of deprecations does affect clients? RQ4: What is the time-frame of reaction in affected clients? RQ5: Do affected clients react similarly?
- 73. Example API goo boo f oo v4 goo boo f oo goo f oo goo f oo v5 v6 v7 Client 2 used API versions and API methods v6 f oo Client 4 used API versions and API methods v4 v5 v6 boo Client 1 used API versions and API methods v4 f oo f oo Client 5 used API versions and API methods v4 v5 v4 boo timetodeprecation timetoreact Client 3 used API versions and API methods v7v6v4 boo f oo boo boo v5 timetoreact timeto deprecation data collectionpoint & deprecated methods released versions, declared methods,
- 74. Results
- 75. Results
- 76. RQ0: What API versions do clients use? Example API goo boo f oo v4 goo boo f oo goo f oo goo f oo v5 v6 v7 Client 2 used API versions and API methods v6 f oo Client 4 used API versions and API methods v4 v5 v6 boo Client 1 used API versions and API methods v4 f oo f oo Client 5 used API versions and API methods v4 v5 v4 boo timetodeprecation timetoreact Client 3 used API versions and API methods v7v6v4 boo f oo boo boo v5 timetoreact timeto deprecation data collectionpoint & deprecated methods released versions, declared methods,
- 77. RQ0: What API versions do clients use?
- 78. Results
- 79. Results
- 80. RQ1: How does API method deprecation affect clients? Example API goo boo f oo v4 goo boo f oo goo f oo goo f oo v5 v6 v7 Client 2 used API versions and API methods v6 f oo Client 4 used API versions and API methods v4 v5 v6 boo Client 1 used API versions and API methods v4 f oo f oo Client 5 used API versions and API methods v4 v5 v4 boo timetodeprecation timetoreact Client 3 used API versions and API methods v7v6v4 boo f oo boo boo v5 timetoreact timeto deprecation data collectionpoint & deprecated methods released versions, declared methods,
- 81. RQ1: How does API method deprecation affect clients?
- 83. Results
- 84. Results
- 85. RQ2: What is the scale of reaction in affected clients? Example API goo boo f oo v4 goo boo f oo goo f oo goo f oo v5 v6 v7 Client 2 used API versions and API methods v6 f oo Client 4 used API versions and API methods v4 v5 v6 boo Client 1 used API versions and API methods v4 f oo f oo Client 5 used API versions and API methods v4 v5 v4 boo timetodeprecation timetoreact Client 3 used API versions and API methods v7v6v4 boo f oo boo boo v5 timetoreact timeto deprecation data collectionpoint & deprecated methods released versions, declared methods,
- 86. API Affected clients that react Median Max Easymock 17 11 109 Guava 161 3 283 Hibernate 40 5 59 Spring 10 31 131 RQ2: What is the scale of reaction in affected clients?
- 87. API Potentially affected clients Median Max Easymock 178 55 4,464 Guava 917 12 8,568 Hibernate 521 15 17,471 Spring 41 3 205 RQ2: What is the scale of reaction in affected clients?
- 88. Results
- 89. Results
- 90. RQ3: What proportion of deprecations does affect clients? Example API goo boo f oo v4 goo boo f oo goo f oo goo f oo v5 v6 v7 Client 2 used API versions and API methods v6 f oo Client 4 used API versions and API methods v4 v5 v6 boo Client 1 used API versions and API methods v4 f oo f oo Client 5 used API versions and API methods v4 v5 v4 boo timetodeprecation timetoreact Client 3 used API versions and API methods v7v6v4 boo f oo boo boo v5 timetoreact timeto deprecation data collectionpoint & deprecated methods released versions, declared methods,
- 91. 13% 7% 6% 11% RQ3: What proportion of deprecations does affect clients?
- 92. Results
- 93. Results
- 94. RQ4: What is the time-frame of reaction in affected clients? Example API goo boo f oo v4 goo boo f oo goo f oo goo f oo v5 v6 v7 Client 2 used API versions and API methods v6 f oo Client 4 used API versions and API methods v4 v5 v6 boo Client 1 used API versions and API methods v4 f oo f oo Client 5 used API versions and API methods v4 v5 v4 boo timetodeprecation timetoreact Client 3 used API versions and API methods v7v6v4 boo f oo boo boo v5 timetoreact timeto deprecation data collectionpoint & deprecated methods released versions, declared methods,
- 95. RQ4: What is the time-frame of reaction in affected clients?
- 96. Results
- 97. RQ5: Do all clients react similarly?
- 101. Deprecation in Java package org.serg; import java.util.Date; public class DateUser { public static void main(String args[]) { Date date = new Date(); int year = date.getYear(); } }pecific
- 102. Similar to Smalltalk Not many API clients change their version of the API Few clients react to deprecation APIs document deprecated changes well Clients tend to delete references to deprecated entities and not replace them Smalltalk clients actually replace deprecated calls
- 103. Results
- 104. Conclusion