Sneha

OBJECT ORIENTED MODEL:
The object-oriented model is based on a collection of objects, like the E-R model.
o An object contains values stored in instance variables within the object.

o Unlike the record-oriented models, these values are themselves objects.
o Thus objects contain objects to an arbitrarily deep level of nesting.
o An object also contains bodies of code that operate on the the object.
o These bodies of code are called methods.
o Objects that contain the same types of values and the same methods are
grouped into classes.
o A class may be viewed as a type definition for objects.
o Analogy: the programming language concept of an abstract data type.
o The only way in which one object can access the data of another object
is by invoking the method of that other object.
o This is called sending a message to the object.
o Internal parts of the object, the instance variables and method code, are
not visible externally.
o Result is two levels of data abstraction.
For example, consider an object representing a bank account.
o The object contains instance variables number and balance.

o The object contains a method pay-interest which adds interest to the
balance.
o Under most data models, changing the interest rate entails changing code
in application programs.
o In the object-oriented model, this only entails a change within the pay-
interest method.
2. Unlike entities in the E-R model, each object has its own unique identity,
independent of the values it contains:
o Two objects containing the same values are distinct.
o Distinction is created and maintained in physical level by assigning
distinct object identifiers.
Object-based Logical Models

1. Object-based logical models:
o Describe data at the conceptual and view levels.
o Provide fairly flexible structuring capabilities.
o Allow one to specify data constraints explicitly.
o Over 30 such models, including
 Entity-relationship model.
 Object-oriented model.
 Binary model.
 Semantic data model.
 Infological model.
 Functional data model.
2. At this point, we'll take a closer look at the entity-relationship (E-
R) and object-oriented models.
User interface design techniques which incorporate object-oriented modeling

techniques to depict the domain, core objects, and interactive capabilities of an
application have significant advantages, including the following:
1. Object models act as a reference to the current state of a system design, and
serve as a means of communication between user interface designers and
system analysts and designers.
2. Object models act as a focus for the user interface design process, providing a
framework in which to view user tasks and the interactive capabilities of a
putative system.
3. Object models of interactive systems enable the specification of tasks and/or
user actions. These specifications, which may be either formal or informal, are
written in terms of state changes in an object model of an interactive system.
4. The rigorous approach offered by the combination of object modeling and user
interface design form a solid foundation for subsequent implementation efforts.
Reuse models
Many metrics and models have been developed for software reuse and reusability. A metric is
a quantitative indicator of an attribute of a thing. A model specifies relationships among metrics. Reuse models
and metrics can be categorized into six types:
1. reuse cost-benefits models
2. maturity assessment
3. amount of reuse
4. failure modes
5. reusability
6. reuse library metrics
Reuse cost-benefits models include economic cost-benefit analysis as well as quality and productivity payoff.
Maturity assessment models categorize reuse programs by how advanced they are in implementing systematic
reuse. Amount of reuse metrics are used to assess and monitor a reuse improvement effort by tracking
percentages of reuse for life cycle objects. Failure modes analysis is used to identify and order the
impediments to reuse in a given organization. Reusability metrics indicate the likelihood that an artifact is
reusable. Reuse library metrics are used to manage and track usage of a reuse repository.
The basic premise behind the Reuse Model is that systems should be built using existing components, as opposed
to custom-building new components. The Reuse Model is clearly suited to Object-Oriented computing environments,
which have become one of the premiere technologies in today's system development industry.
Within the Reuse Model, libraries of software modules are maintained that can be copied for use in any system.
These components are of two types: procedural modules and database modules. When building a new system, the
developer will "borrow" a copy of a module from the system library and then plug it into a function or procedure. If the
needed module is not available, the developer will build it, and store a copy in the system library for future usage. If
the modules are well engineered, the developer with minimal changes can implement them.
The Reuse Model consists of the following steps:
 Definition of Requirements. Initial system requirements are collected. These requirements are usually a
subset of complete system requirements.
 Definition of Objects. The objects, which can support the necessary system components, are identified.
 Collection of Objects. The system libraries are scanned to determine whether or not the needed objects
are available. Copies of the needed objects are downloaded from the system.
 Creation of Customized Objects. Objects that have been identified as needed, but that are not available in
the library are created.
 Prototype Assembly. A prototype version of the system is created and/or modified using the necessary
objects.
 Prototype Evaluation. The prototype is evaluated to determine if it adequately addresses customer needs
and requirements.
 Requirements Refinement. Requirements are further refined as a more detailed version of the prototype is
created.
 Objects Refinement. Objects are refined to reflect the changes in the requirements.

Sneha

Uploaded by

Copyright:

Available Formats

Sneha

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Sneha

Uploaded by

Copyright:

Available Formats

OBJECT ORIENTED MODEL:

o An object contains values stored in instance variables within the object.

For example, consider an object representing a bank account.

o The object contains instance variables number and balance.

Object-based Logical Models

User interface design techniques which incorporate object-oriented modeling

1. reuse cost-benefits models

The Reuse Model consists of the following steps:

You might also like