Encapsulation in object-oriented programs

Authors:
Jiun-Liang Chen;Feng-Jian Wang
Affiliations:
Institute of Computer Science and Information Engineering, National Chiao Tung University, HsinChu, 30050, Taiwan, R.O.C.;Institute of Computer Science and Information Engineering, National Chiao Tung University, HsinChu, 30050, Taiwan, R.O.C.
Venue:
ACM SIGPLAN Notices
Year:
1996

Citing 5
Cited 0

The program dependence graph and its use in optimization

ACM Transactions on Programming Languages and Systems (TOPLAS)
Interprocedural slicing using dependence graphs

ACM Transactions on Programming Languages and Systems (TOPLAS)
An extensible program representation for object-oriented software

ACM SIGPLAN Notices
The program dependence graph in a software development environment

SDE 1 Proceedings of the first ACM SIGSOFT/SIGPLAN software engineering symposium on Practical software development environments
Static Slicing of Concurrent Object-Oriented Programs

COMPSAC '96 Proceedings of the 20th Conference on Computer Software and Applications

Quantified Score

Hi-index	0.00

Visualization

Abstract

In stead of decomposing data and procedures, object-oriented (OO) programming encapsulates the both through an object. An object is instantiated from a class which defines attributes (related data) and methods (operational procedures). The definition of a class may be recursive since the class can encapsulate the instance(s) of another classes as its attributes. An object containing other objects is called a complex object. The form of a most primitive object, an object containing no other object, is nothing but a data entity and is called a simple object. Encapsulation solidates an object by hiding the details; it may also obstruct dependency analysis for complex objects by information hiding.