Ooad Faq
Ooad Faq
Diagram:
client server
(Active) (Passive)
? Aggregation: Its' the relationship between two classes which are related in the fashion that master and
slave. The master takes full rights than the slave. Since the slave works under the master. It is represented as
line with diamond in the master area.
ex:
car contains wheels, etc.
car
? Containment: This relationship is applied when the part contained with in the whole part, dies when the
whole part dies.
It is represented as darked diamond at the whole part.
example:
class A{
//some code
};
class B
{
A aa; // an object of class A;
// some code for class B;
};
In the above example we see that an object of class A is instantiated with in the class B. so the object class A
dies when the object class B dies.we can represnt it in diagram like this.
? Generalization: This relationship used when we want represents a class, which captures the common states
of objects of different classes. It is represented as arrow line pointed at the class, which has captured the
common states.
? Dependency: It is the relationship between dependent and independent classes. Any change in the
independent class will affect the states of the dependent class.
DIAGRAM:
class A class B
15. Whether unified method and unified modeling language are same or different?
Unified method is convergence of the Rumbaugh and Booch.
Unified modeling lang. is the fusion of Rumbaugh, Booch and Jacobson as well as Betrand Meyer (whose
contribution is "sequence diagram"). Its' the superset of all the methodologies.
16. Who were the three famous amigos and what was their contribution to the object community?
The Three amigos namely,
? James Rumbaugh (OMT): A veteran in analysis who came up with an idea about the objects and their
Relationships (in particular Associations).
? Grady Booch: A veteran in design who came up with an idea about partitioning of systems into
subsystems.
? Ivar Jacobson (Objectory): The father of USECASES, who described about the user and system
interaction.
Booch: In this method classes are represented as "Clouds" which are not very easy to draw as for as the
developer's view is concern.
Diagram:
In the above representation I, obj1 sends message to obj2. But in the case of II the data is transferred from
obj1 to obj2.
22. USECASE is an implementation independent notation. How will the designer give the implementation
details of a particular USECASE to the programmer?
This can be accomplished by specifying the relationship called "refinement" which talks about the two
different abstraction of the same thing.
Or example,
23. Suppose a class acts an Actor in the problem domain, how to represent it in the static model?
In this scenario you can use "stereotype". Since stereotype is just a string that gives extra semantic to the
particular entity/model element. It is given with in the << >>.
class A
<< Actor>>
attributes
methods.
Why OOA?
Looking from both management and technical perspective, OO offers numerous inherent benefits like high-
quality programming and ease maintenance due to decoupled nature of the structure. Object technologies are
easier to adopt and are easily scalable. But the most important benefit is the reuse facility and hence faster
development process.
What is a class?
Class is the building block of object oriented system. It is a template for an object and it specifies the
object’s structures and operations. It’s the blueprint from which individual objects are created. Class
contains all the statements needed to create an object, its attributes, as well as the statements to describe the
operations that the object will be able to perform.
A class has the following members: attributes and methods. A good example of a class is Human. A human
class would have characteristics (attributes) of gender, hands, legs, age, and so forth. It would also have
actions (methods) such as walking, eating, running, talking, and so on.
For instance, in the real world, there are many individual objects all of the same kind. There may be
thousands of cars in existence, all of the same make and model. Each car was built from the same set of
blueprints and therefore contains the same components. In object-oriented terms, one particular car is an
instance of the class of objects known as cars.
Technical management at Stylus Systems is aware that the maximum impact from OOAD is achieved when
used with the goal of designing reusable software. Another very important knowledge is that for objects
without significant reuse potential, OOAD techniques were more costly than traditional software
development methodologies.
What OOA does is to specify the structure and behavior of the object i.e. the requirements of that object. To
specify the requirements of the objects different types of models are required. The information or object
model will contain the definition of objects in the system, including: object name, object attributes, and
object relationships to other objects. This technology works best when used in new development.
OO Analysis involves the team to arrive at the description of the problem and subsequently identify the
requirements. The fundamental question to ponder over here is what the problem is about and what a system
must do. Analysis emphasizes and investigates the problem rather than how a solution is desired. Once this
is done, it’s time to move on to the next phase i.e. the design part.
The most important part of OOD is mapping the above mentioned things into an object-oriented
programming language (OOPL). OOD requires the specification of concepts that are not existent in analysis,
such as the types of the attributes of a class, or the logic of its methods.
Design can be thought of in two phases. The first, called high-level design, deals with the breaking up of the
system into large, complex objects. The second phase is called low-level design. In this phase, attributes and
methods are specified at the level of individual objects. This is also where a project can realize most of the
reuse of object-oriented products, since it is possible to guide the design so that lower-level objects
correspond exactly to those in existing object libraries or to develop objects with reuse potential.
OOD techniques are useful for development of large complex systems. It can yield the following benefits:
maintainability through simplified mapping to the problem domain, which provides for less analysis effort,
less complexity in system design, and easier verification by the user; reusability of the design artifacts,
which saves time and costs; and productivity gains through direct mapping to features of Object-Oriented
Programming. Ultimately designs can be implemented in software and hardware as well.
The use of object oriented technology requires formal training in OOA methods. A method of training that
has produced desired results at Stylus is to initiate pilot projects, conduct formal classes, and conduct team
reviews to properly train all the analysis and development staff as well as the program management team.
Technical management at Stylus Systems is aware that the maximum impact from OOAD is achieved when
used with the goal of designing reusable software. Another very important knowledge is that for objects
without significant reuse potential, OOAD techniques were more costly than traditional software
development methodologies.