none
ADT (Abstract Data Type) RRS feed

  • Question

  • Hello, everybody :-)

    Recently, I've decided to give a deep dive into ADTs concept in order to get a better undertanding of it and, thus, construct more "perfect" classes.

    Here're my thoughts on this subject:

    - ADTs help developers to implement the idea of dealing with high-level abstraction. 

    - ADTs are encapsulated data + interface. Thus, ADTs implement the idea of data abstraction by encasulating data and, therefore, they give developers an opportunity to think in terms of interface only.

    MAIN QUESTION:

    Class is one of the ways to implement ADT. Class just adds more concepts to ADT (polymorphism, inheritance). Is it the right point of view??

    Thanks in advance.

    Monday, January 20, 2014 5:07 PM

Answers

  • Hi Igor,

    Yes, you are right. The purpose of ADT is to be inherited by other classes. Interface is related to, usually we use these two types to build a decoupled architecture system. So I assume you want to know something about how to build a strong designed software?

    The repository pattern is a well-known design pattern. Use a repository to separate the logic and data source. You can refer to the following link for more information. http://msdn.microsoft.com/en-us/library/ff649690.aspx. And a code sample from the following link. http://www.codeproject.com/Articles/631668/Learning-MVC-Part-5-Repository-Pattern-in-MVC3-App.

    Hope useful to you.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by Igor_Rastvorov Tuesday, January 21, 2014 2:41 PM
    Tuesday, January 21, 2014 6:35 AM
    Moderator

All replies

  • Hi Igor,

    Yes, you are right. The purpose of ADT is to be inherited by other classes. Interface is related to, usually we use these two types to build a decoupled architecture system. So I assume you want to know something about how to build a strong designed software?

    The repository pattern is a well-known design pattern. Use a repository to separate the logic and data source. You can refer to the following link for more information. http://msdn.microsoft.com/en-us/library/ff649690.aspx. And a code sample from the following link. http://www.codeproject.com/Articles/631668/Learning-MVC-Part-5-Repository-Pattern-in-MVC3-App.

    Hope useful to you.

    Regards,


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    • Marked as answer by Igor_Rastvorov Tuesday, January 21, 2014 2:41 PM
    Tuesday, January 21, 2014 6:35 AM
    Moderator
  • Thank you a lot :-)
    Tuesday, January 21, 2014 2:41 PM