The Object-Oriented (OO) process is an evolutionary approach to software engineering.

It encompasses the entire software life cycle, from operational concept through release. The OO paradigm focuses on classes that encapsulate data and algorithms for manipulating the data. OO classes promote reusability across applications.

 Object Oriented technologies are classified as below

 Object Oriented Design

 Object Oriented Languages

 Object Oriented Metrics

 Object Oriented Modeling

 Object Oriented Testing

Object Oriented Design Object-oriented analysis and design (OOAD) is a software engineering approach that models a system as a group of interacting objects. Each object represents some entity of interest in the system being modeled, and is characterised by its class, its state (data elements), and its behavior. Various models can be created to show the static structure, dynamic behavior, and run-time deployment of these collaborating objects. There are a number of different notations for representing these models, such as the Unified Modeling Language (UML). Object-oriented analysis (OOA) applies object-modeling techniques to analyze the functional requirements for a system. Object-oriented design (OOD) elaborates the analysis models to produce implementation specifications. OOA focuses on what the system does, OOD on how the system does it. Object Oriented Languages Object-oriented programming (OOP) is a programming paradigm using "objects" data structures consisting of data fields and methods together with their interactions to design applications and computer programs. Programming techniques may include features such as

data abstraction, encapsulation, messaging, modularity, polymorphism, and inheritance. Many modern programming languages now support OOP, at least as an option.

Object Oriented Metrics The metrics set refers to a basic structural mechanism of the OO paradigm as encapsulation, inheritance, polymorphisms message-passing and are expressed as quotients. The set includes the following metrics:

Method Hiding Factor ( MHF ) MHF is defined as the ratio of the sum of the invisibilities of all methods defined in all classes to the total number of methods defined in the system under consideration. The invisibility of a method is the percentage of the total classes from which this method is not visible. note : inherited methods not considered. Attribute Hiding Factor ( AHF ) AHF is defined as the ratio of the sum of the invisibilities of all attributes defined in all classes to the total

number of attributes defined in the system under consideration.

Method Inheritance Factor ( MIF ) MIF is defined as the ratio of the sum of the inherited methods in all classes of the system under consideration to the total number of available methods ( locally defined plus inherited) for all classes.

Attribute Inheritance Factor ( AIF ) AIF is defined as the ratio of the sum of inherited attributes in all classes of the system under consideration to the total number of available attributes ( locally defined plus inherited ) for all classes.

Polymorphism Factor ( PF ) PF is defined as the ratio of the actual number of possible different polymorphic situation for class Ci to the maximum number of possible distinct polymorphic situations for class Ci.

Coupling Factor ( CF ) CF is defined as the ratio of the maximum possible number of couplings in the system to the actual number

of couplings not imputable to inheritance.

Object Oriented Modeling Object-Oriented Modeling, or OOM, (Object Oriented Programming - OOP)is a modeling paradigm mainly used in computer programming. Prior to the rise of OOM, the dominant paradigm was procedural programming, which emphasized the use of discrete reusable code blocks that could stand on their own, take variables, perform a function on them, and return values.

The Object-Oriented paradigm assists the programmer to address the complexity of a problem domain by considering the problem not as a set of functions that can be performed but primarily as a set of related, interacting Objects. The modeling task then is specifying, for a specific context, those Objects (or the Class the Objects belongs to), their respective set of Properties and Methods, shared by all Objects members of the Class. For more discussion, see Object-oriented analysis and design and Object-oriented programming. The description of these Objects is a Schema. Object Oriented Testing

SYSTEM SAME AS TRADITIONAL STILL BASED ON REQRS SPEC UNIT TWO COMMON STRUCTURES USED METHOD* CLASS SAME AS TRADITIONAL(DRIVERS & STUBS)