By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,854 Members | 869 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,854 IT Pros & Developers. It's quick & easy.

What is ADT? (Abstract Data Type)

P: 3
I am currently studying about this ADT but I don't get the concept at all. Can someone please explain to me what this actually is?? Also what is collection, bag, and List ADT?? in simple terms? Thanks
Feb 1 '07 #1
Share this Question
Share on Google+
3 Replies


10K+
P: 13,264
I am currently studying about this ADT but I don't get the concept at all. Can someone please explain to me what this actually is?? Also what is collection, bag, and List ADT?? in simple terms? Thanks
A group of types and operations upon these types which collectively make up a new type.
Feb 2 '07 #2

100+
P: 168
I think it's a synonym for a class.

"abstract" == "dealing with a subject in its abstract aspects"
"data" == "information in numerical form that can be digitally transmitted or processed"
"type" == Java type

It's a way of combining attributes to represent something meaningful in your software model. If I decide to combine two Strings to create a Name class, I'd say that I'm abstracting that detail in my model and just dealing with a Name. It's easy to see how I might do it a different way and add more detail (e.g. ,salutation, middle name, suffix, etc.). It's all still a Name to me.

Collection, Bag, and List are examples of data structures. (Others are Map, Dictionary, Tree, Set, Queue, Stack, etc.) Any good book on the subject will tell you what the differences are. Worth a read.
Feb 2 '07 #3

100+
P: 168
> Collection, Bag, and List are examples of data
> structures. (Others are Map, Dictionary, Tree, Set,
> Queue, Stack, etc.) Any good book on the subject
> will tell you what the differences are. Worth a read.

All these data structures are abstract data types. What are you abstracting? Your shielding users from the details of how you've implemented the behavior that is characteristic of each type. Users can expect your object to "act like a List" and not worry about how you implemented that behavior.
Feb 2 '07 #4

Post your reply

Sign in to post your reply or Sign up for a free account.