I am equally overwhelmed by the unflinching support of all my other professors, lecturers and administrative staff and the library staff at the _____________ University and thank them profusely. Their slightest disarrangement would have distracted my focus from the research.
As early as 1960’s the object-oriented programming (OOP) emerged in the computer software arena, when “data abstraction, polymorphism and modularisation were being applied to the procedural paradigm” (Cardelli, 1996). By 1980’s, research predicted that what structured programming was in the 1970’s, object-oriented programming will be in the 1980’s (Booch, 1986). Object-oriented software development not only prevailed all through the 1980’s, but also through the next two decades. But in a globalised market, as the software market becomes more and more competitive with ever increasing pressure on shortening software development cycles and for improved software productivity, an important dilemma has engulfed the software developers across the world. Can the object-oriented programming stand the test of the time? The present section deals with the issues pertaining to using software methodologies and the implications for object-oriented software projects.
Booch (1986) defined object-oriented development as “a partial-lifecycle software development method in which decomposition of a system is based upon the concept of an object” (Booch, 1986, p.211). Booch in his paper “Object-Oriented Development” argued that the object-oriented technology is fundamentally different from the traditional functional approaches in respect of designing, serving and managing massive software-intensive systems as well (Booch, 1986). Nearly one and a half decade later, Montlick (1999) supports Booch’s argument and suggests that “object oriented software is all about objects” (Montlick, 1999). While defining an object as a