Object-Oriented Programming and Java

Poo, Danny Chiang Choon; Kiong, Derek; Ashok, Swarnalatha

doi:10.1007/978-1-84628-963-7

Cited by 8 publications

(7 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In the list of these books, we carefully inspected the table of contents and often the book contents (offered for free review by the Google Books or Amazon.com) to determine if UML was a major focus of books having "objectoriented" in their titles, but not "UML" exactly. As another example, in a book entitled "Object-Oriented Programming and Java" [15], a search in the contents for UML returns no results, meaning that there is no discussion of UML in this book. Many UML concepts (e.g., metamodels) are also discussed in this book.…”

Section: Search Methodsmentioning

confidence: 99%

Classification and trend analysis of UML books (1997–2009)

Garousi

2011

Softw Syst Model

View full text Add to dashboard Cite

Technical books of each subject area denote the level of maturity and knowledge demand in that area. According to the Google Books database, about 208 Unified Modeling Language (UML) books have been published from its inception in 1997 until 2009. While various book reviews are frequently published in various sources (e.g., IEEE Software Bookshelf), there are no studies to classify UML books into meaningful categories. Such a classification can help researchers in the area to identify trends and also reveal the level of activity in each sub-area of UML. The statistical survey reported in this article intends to be a first step in classification and trend analysis of the UML books published from 1997 to 2009. The study also sheds light on the quantity of books published in different focus areas (e.g., UML's core concepts, patterns, tool support, Object Constraint Language and Model-Driven Architecture) and also on different application domains (e.g., database modeling, web applications, and real-time systems). The trends of book publications in each sub-area of UML are also used to track the level of maturity, to identify possible Hype cycles and also to measure knowledge demand in each area. Communicated by Prof. Robert France. Electronic supplementary materialThe online version of this article (

show abstract

Section: Search Methodsmentioning

confidence: 99%

Classification and trend analysis of UML books (1997–2009)

Garousi

2011

Softw Syst Model

View full text Add to dashboard Cite

show abstract

“…Unless the receiver is the pseudo-variable super, it considers the implementation that is nearest to the receiver's class. The mechanism regarding the method look-up corresponds to the implementation of the latebound-polymorphism in Java and C♯ [15,25]. Figure 10 illustrates the method look-up: when symbolically evaluating the sent message foo for a receiver of class B, the implementation in class B is considered.…”

Section: Message Sendsmentioning

confidence: 99%

Refactoring support for Smalltalk using static type inference

Unterholzner¹

2012

Proceedings of the International Workshop on Smalltalk Technologies

View full text Add to dashboard Cite

Refactoring is a crucial activity in agile software development. As a consequence, automated tools are expected to support refactoring, both for reducing the developer's effort as well as for avoiding errors due to manual changes. In this context, the chosen programming language has a major impact on the level of support that an automated refactoring tool can offer. One important aspect of a programming language concerning the automation of refactoring is the type system. While a static type system, present in languages such as Java, provides information about dependencies in the program, the dynamic type system of the Smalltalk programming language offers little information that can be used by automated refactoring tools.This paper focuses on the challenges in the context of refactoring raised by the dynamic type system of Smalltalk. It highlights the problems caused by the absence of static type information and proposes the use of static code analysis for performing type inference to gather information about the dependencies in the program's source code. It explains the mechanism of the static code analysis using sample code and presents a prototype of an enhanced refactoring tool, which uses the structural information extracted through static code analysis. Empirical samples build the base for evaluating the effectiveness of the approach.

show abstract

“…Other than Java reflection, other techniques such as polymorphism may also result in incomplete detection of APIs usages. Dynamic binding [21] enables methods to be bound during runtime but compilation. Any methods that adopts dynamic binding cannot be determined at compile time, and hence can escape from detection.…”

Section: Disguise Usage Of Apismentioning

confidence: 99%

On the effectiveness of API-level access control using bytecode rewriting in Android

Hao

Singh

2013

Proceedings of the 8th ACM SIGSAC Symposium on Information, Computer and Communications Security

View full text Add to dashboard Cite

Bytecode rewriting on Android applications has been widely adopted to implement fine-grained access control. It endows more flexibility and convenience without modifying the Android platform. Bytecode rewriting uses static analysis to identify the usage of security-sensitive API methods, before it instruments the bytecode to control the access to these API calls. Due to the significance of this technique, the effectiveness of its performance in providing fine-grained access control is crucial. We have provided a systematic evaluation to assess the effectiveness of API-level access control using bytecode rewriting on Android Operating System. In our evaluation, we have identified a number of potential attacks targeted at incomplete implementations of bytecode rewriting on Android OS, which can be applied to bypass access control imposed by bytecode rewriter. These attacks can either bypass the API-level access control or make such access control difficult to implement, exposing weak links in the bytecode rewriting process. Recommendations on engineering secure bytecode rewriting tools are presented based on the identified attacks. This work is the first systematic study on the effectiveness of using bytecode rewriting for API-level access control.

show abstract

Object-Oriented Programming and Java

Cited by 8 publications

References 0 publications

Classification and trend analysis of UML books (1997–2009)

Classification and trend analysis of UML books (1997–2009)

Refactoring support for Smalltalk using static type inference

On the effectiveness of API-level access control using bytecode rewriting in Android

Contact Info

Product

Resources

About