Abstract
Object-oriented languages originated in the late '60s and entered widespread industrial use in the early '90s. With this technology's advent came the hope and belief that life from a programming perspective would generally improve. We believed that these languages would foster reuse and, consequently, a reduction in the quantity of code written. We also believed that inheritance, an object-oriented language feature, would result in less testing effort, although D. Perry and G. Kaiser (1990) dispelled this notion. So, if we use object-oriented technology, what should we expect in terms of quality? What can we do to increase our chances of producing highly reliable software? This paper presents four ideas that will improve these chances regardless of the object-oriented language used.
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
