0% found this document useful (0 votes)
492 views7 pages

Ooad Faq

Object Oriented Analysis and Design (OOAD) involves determining system requirements before implementation (analysis) and choosing the best design among options to meet user needs (design). Key OOAD concepts are objects, classes, inheritance, polymorphism. Analysis identifies objects and relationships, while design partitions the system into subsystems and modules. Use cases describe actor-system interactions. The Unified Modeling Language (UML) is a standard modeling language used for OOAD.

Uploaded by

Prakhar Goyal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
492 views7 pages

Ooad Faq

Object Oriented Analysis and Design (OOAD) involves determining system requirements before implementation (analysis) and choosing the best design among options to meet user needs (design). Key OOAD concepts are objects, classes, inheritance, polymorphism. Analysis identifies objects and relationships, while design partitions the system into subsystems and modules. Use cases describe actor-system interactions. The Unified Modeling Language (UML) is a standard modeling language used for OOAD.

Uploaded by

Prakhar Goyal
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 7

OOAD

1. What do you mean by analysis and design?


Analysis:
Basically, it is the process of determining what needs to be done before how it should be done. In order to
accomplish this, the developer refers the existing systems and documents. So, simply it is an art of
discovery.
Design:
It is the process of adopting/choosing the one among the many, which best accomplishes the users needs. So,
simply, it is compromising mechanism.

2. What are the steps involved in designing?


Before getting into the design the designer should go through the SRS prepared by the System Analyst.
The main tasks of design are Architectural Design and Detailed Design.
In Architectural Design we find what are the main modules in the problem domain.
In Detailed Design we find what should be done within each module.

3. What are the main underlying concepts of object orientation?


Objects, messages, class, inheritance and polymorphism are the main concepts of object orientation.

4. What do u meant by "SBI" of an object?


SBI stands for State, Behavior and Identity. Since every object has the above three.
? State:
It is just a value to the attribute of an object at a particular time.
? Behaviour:
It describes the actions and their reactions of that object.
? Identity:
An object has an identity that characterizes its own existence. The identity makes it possible to distinguish
any object in an unambiguous way, and independently from its state.

5. Differentiate persistent & non-persistent objects?


Persistent refers to an object's ability to transcend time or space. A persistent object stores/saves its state in a
permanent storage system with out losing the information represented by the object.
A non-persistent object is said to be transient or ephemeral. By default objects are considered as non-
persistent.

6. What do you meant by active and passive objects?


Active objects are one which instigate an interaction which owns a thread and they are responsible for
handling control to other objects. In simple words it can be referred as client.
Passive objects are one, which passively waits for the message to be processed. It waits for another object
that requires its services. In simple words it can be referred as server.

Diagram:
client server
(Active) (Passive)

7. What is meant by software development method?


Software development method describes how to model and build software systems in a reliable and
reproducible way. To put it simple, methods that are used to represent ones' thinking using graphical
notations.

8. What are models and meta models?


Model:
It is a complete description of something (i.e. system).
Meta model:
It describes the model elements, syntax and semantics of the notation that allows their manipulation.

9. What do you meant by static and dynamic modeling?


Static modeling is used to specify structure of the objects that exist in the problem domain. These are
expressed using class, object and USECASE diagrams.
But Dynamic modeling refers representing the object interactions during runtime. It is represented by
sequence, activity, collaboration and statechart diagrams.

10. How to represent the interaction between the modeling elements?


Model element is just a notation to represent (Graphically) the entities that exist in the problem domain. e.g.
for modeling element is class notation, object notation etc.
Relationships are used to represent the interaction between the modeling elements.
The following are the Relationships.

? Association: Its' just a semantic connection two classes.


e.g.:

? 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

11. Why generalization is very strong?


Even though Generalization satisfies Structural, Interface, Behaviour properties. It is mathematically very
strong, as it is Antisymmetric and Transitive.
Antisymmetric: employee is a person, but not all persons are employees. Mathematically all As' are B, but
all Bs' not A.
Transitive: A=>B, B=>c then A=>c.
A. Salesman.
B. Employee.
C. Person.
Note: All the other relationships satisfy all the properties like Structural properties, Interface properties,
Behaviour properties.

12. Differentiate Aggregation and containment?


Aggregation is the relationship between the whole and a part. We can add/subtract some properties in the
part (slave) side. It won't affect the whole part.
Best example is Car, which contains the wheels and some extra parts. Even though the parts are not there we
can call it as car.
But, in the case of containment the whole part is affected when the part within that got affected. The human
body is an apt example for this relationship. When the whole body dies the parts (heart etc) are died.

13. Can link and Association applied interchangeably?


No, You cannot apply the link and Association interchangeably. Since link is used represent the relationship
between the two objects.
But Association is used represent the relationship between the two classes.
link :: student:Abhilash course:MCA
Association:: student course

14. what is meant by "method-wars"?


Before 1994 there were different methodologies like Rumbaugh, Booch, Jacobson, Meyer etc who followed
their own notations to model the systems. The developers were in a dilemma to choose the method which
best accomplishes their needs. This particular span was called as "method-wars"

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.

17. Differentiate the class representation of Booch, Rumbaugh and UML?


If you look at the class representaiton of Rumbaugh and UML, It is some what similar and both are very
easy to draw.
Representation: OMT UML.
Diagram:

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:

18. What is an USECASE? Why it is needed?


A Use Case is a description of a set of sequence of actions that a system performs that yields an observable
result of value to a particular action.
In SSAD process <=> In OOAD USECASE. It is represented elliptically.
Representation:

19. Who is an Actor?


An Actor is someone or something that must interact with the system.In addition to that an Actor initiates
the process(that is USECASE).
It is represented as a stickman like this.
Diagram:

20. What is guard condition?


Guard condition is one, which acts as a firewall. The access from a particular object can be made only when
the particular condition is met.
For Example,
customer check customer number ATM.
Here the object on the customer accesses the ATM facility only when the guard condition is met.

21. Differentiate the following notations?


I: :obj1 :obj2

II: :obj1 :obj2

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,

calculate pay calculate

class1 class2 class3

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.

24. Why does the function arguments are called as "signatures"?


The arguments distinguish functions with the same name (functional polymorphism). The name alone does
not necessarily identify a unique function. However, the name and its arguments (signatures) will uniquely
identify a function.
In real life we see suppose, in class there are two guys with same name, but they can be easily identified by
their signatures. The same concept is applied here.
ex:
class person
{
public:
char getsex();
void setsex(char);
void setsex(int);
};
In the above example we see that there is a function setsex() with same name but with different signature

FAQs on Object Oriented Architecture

What is Object Orientation?


It’s a way of thinking to understand the given problem by identifying various objects and their associations,
interaction among the objects, to model and solve the problem. It’s a point of view where systems are
constructed from objects, which themselves may be collection of smaller objects. It’s a system where
computation occurs by means of objects communicating with each other by message passing.

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 are Objects?


Objects are defined as tangible entity that exhibits some well-defined behavior. Objects are real world
entities as in they contain attributes and operations and they always represent a “state.” The behavior of an
object is invoked by sending a message to that object. The object then executes the appropriate method
(operation).

What are the benefits of ‘object’ approach?


An object becomes important in OOA because it is more than just a value or a record of values: it "knows"
what it can do, or, in other words, it has an associated behavior. The reason why objects are necessary is that
it is usually easy to model real world objects. They hide internal representation and expose only required
functionality. Generalized objects can help in reduced maintenance as they are less dependant and reusable.

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.

What are class instances?


Once a class is defined then as many objects as needed can be created. These objects are called instances of
this class. All the instances created with a given class will have the same structure and behavior. They will
only differ regarding their state, i.e regarding the value of their attributes.

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.

How do objects interact?


The object oriented approach really shows its worth in situations in which objects interact with each other.
Aside from inheritance (about which we will talk in later paragraphs), there are other ways for objects to
interact. For Instance, one object uses another object. Objects interact by passing messages that hold an
operation (method) invocation request. These messages can be Synchronous (wait for a response) and
Asynchronous (don’t wait for a response). The advantage OOA provides is low coupling, highly reusable
and easy maintainable.

How does everyone benefit from OOA method?


OOA is all about determining the best way to divide a program into an economical set of classes. The result
is speeding of the development time and proper class construction. Reuse results in far fewer lines of code,
which translates to less bugs and lower maintenance costs. OOA ensures better quality, better maintenance
due to decoupled nature of the structure and high productivity. The program becomes easily scalable and
easier to adopt.

Why choose Stylus to develop your software?


The use of object oriented technology requires formal training in OOAD 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.

A Real Life Picture of Object Oriented Analysis


and Design

Object Oriented Analysis


Object Oriented Analysis views the world as objects with data structures and behaviors and events that
trigger operations (object behavior changes). This in turn changes the state of objects. The idea that a system
can be viewed as a collection of interacting objects, each of which is a bundle of data and functionality, is
the foundation of this technology and provides an attractive alternative for the development of complex
systems. This is a far-reaching departure from prior methods of requirements specification, such as
structured analysis and design and functional decomposition.
We all know what objects are. For the uninitiated, object is a representation of a real-life entity or
abstraction. For instance, objects in a car rental system might include: a car, route, an icon on a screen, or
even a full screen with which a travel agent interacts.

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.

Object Oriented Design


Object-oriented design (OOD) is mainly concerned with developing an object-oriented model of a system to
implement the identified requirements. It involves arriving at detailed descriptions of logical solution to the
problem identified during the OOA stage. It seeks answers to questions like how the logical solution fulfills
requirements and constraints. It builds on the products developed during OOA by refining candidate objects
into classes, defining data structures and procedures, and defining message protocols for all objects.

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.

You might also like