Thursday, June 18, 2009

Seamlessness

              The object oriented approach is ambitious.It encompasses the entire software lifecycle When examining object oriented solutions, you should check that the method and language, as well as the supporting tools, apply to analysis and design as well as implementation and maintenance.The language in particular should be a vehicle for thought which will help you through all stages of your work.
 
                 The result is a seamless development process, where the generality of the concepts and notations helps reduce the magnitude of the transitions between successive steps in the lifecycle.These requirements exclude two cases, still frequently encountered but equally unsatisfactory.The use of object oriented concepts for analysis and design only, with a method and notation that cannot be used to write executable software.

                The use of an object oriented programming language which is not suitable for analysis and design.An object oriented language and environment together with the supporting method, should apply to the entire life cycle in a way that minimizes the gaps between successive activities.Object orientation is primarily an architectural technique.Its major effect is on the modular structure of software systems.

             The key role here is again played by classes. A class describes not just a type of objects but also a modular unit.In a pure object oriented approach.There is no notion of main program, and sub programs do not exist as independent modular units.There is also no need for the “packages” of languages such as Ada, although we may find it convenient for management purposes to group classes into administrative units, called clusters.

No comments:

Post a Comment