Вы находитесь на странице: 1из 5

1.What is UML?

UML stands for the Unified Modeling Language.


It is a graphical language for
1) visualizing,
2) constructing, and
3) documenting the artifacts of a system.
It allows you to create a blue print of all the aspects of the system, before ac
tually physically implementing the system.
<p>2.What are the advantages of creating a model?
Modeling is a proven and well-accepted engineering technique which helps build a
model.
Model is a simplification of reality; it is a blueprint of the actual system tha
t needs to be built.
Model helps to visualize the system.
Model helps to specify the structural and behavior of the system.
Model helps make templates for constructing the system.
Model helps document the system.
3.What are the different views that are considered when building an object-orien
ted software system?
Normally there are 5 views.<br />
Use Case view &#8211; This view exposes the requirements of a system.
Design View &#8211; Capturing the vocabulary.<br />
Process View &#8211; modeling the distribution of the systems processes and thre
ads.<br />
Implementation view &#8211; addressing the physical implementation of the system
.<br />
Deployment view &#8211; focus on the modeling the components required for deploy
ing the system.</p>
<p>4.What are the major three types of modeling used?<br />
The 3 Major types of modeling are<br />
architectural,<br />
behavioral, and<br />
structural.<br />
5.Name 9 modeling diagrams that are frequently used?<br />
9 Modeling diagrams that are commonly used are<br />
Use case diagram<br />
Class Diagram<br />
Object Diagram<br />
Sequence Diagram<br />
statechart Diagram<br />
Collaboration Diagram<br />
Activity Diagram<br />
Component diagram<br />
Deployment Diagram.<br />
6.How would you define Architecture?<br />
Architecture is not only taking care of the structural and behavioral aspect of
a software system but also taking into account the software usage, functionality
, performance, reuse, economic and technology constraints.</p>
<p>7.What is SDLC (Software Development Life Cycle)?<br />
SDLC is a system including processes that are<br />
Use case driven,<br />
Architecture centric,<br />
Iterative, and<br />
Incremental.</p>
<h3><em><strong>UML VIVA Questions and Answers :-</strong></em></h3>
<p>8.What is the Life Cycle divided into?<br />
This Life cycle is divided into phases.<br />
Each Phase is a time span between two milestones.<br />
The milestones are<br />
Inception,<br />

Elaboration,<br />
Construction, and<br />
Transition.<br />
9.What are the Process Workflows that evolve through these phases?<br />
The Process Workflows that evolve through these phases are<br />
Business Modeling,<br />
Requirement gathering,<br />
Analysis and Design,<br />
Implementation,<br />
Testing,<br />
Deployment.<br />
Supporting Workflows are Configuration, change management, and Project managemen
t.<br />
10.What are Relationships?<br />
There are different kinds of relationships:<br />
Dependencies,<br />
Generalization, and<br />
Association.<br />
Dependencies are relationships between two entities.<br />
A change in specification of one thing may affect another thing.<br />
Most commonly it is used to show that one class uses another class as an argumen
t in the signature of the operation.</p>
<p>Generalization is relationships specified in the class subclass scenario, it
is shown when one entity inherits from other.<br />
Associations are structural relationships that are:<br />
a room has walls,<br />
Person works for a company.</p>
<p>Aggregation is a type of association where there is a has a relationship.<br
/>
As in the following examples: A room has walls, or if there are two classes room
and walls then the relation ship is called a association and further defined as
an aggregation.</p>
<p>11.How are the diagrams divided?<br />
The nine diagrams are divided into static diagrams and dynamic diagrams.</p>
<p>12.Static Diagrams (Also called Structural Diagram):<br />
The following diagrams are static diagrams.<br />
Class diagram,<br />
Object diagram,<br />
Component Diagram,<br />
Deployment diagram.<br />
13.Dynamic Diagrams (Also called Behavioral Diagrams):<br />
The following diagrams are dynamic diagrams.<br />
Use Case Diagram,<br />
Sequence Diagram,<br />
Collaboration Diagram,<br />
Activity diagram,<br />
Statechart diagram.<br />
14.What are Messages?<br />
A message is the specification of a communication, when a message is passed that
results in action that is in turn an executable statement.</p>
<p>15.What is an Use Case?<br />
A use case specifies the behavior of a system or a part of a system.<br />
Use cases are used to capture the behavior that need to be developed.<br />
It involves the interaction of actors and the system.</p>

1. What do you mean by analysis and design?</strong><br />


<strong>Analysis:</strong><br />
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 s
ystems and documents. So, simply it is an art of discovery.<br />
<strong>Design:</strong><br />
It is the process of adopting/choosing the one among the many, which best accomp
lishes the users needs. So, simply, it is compromising mechanism.</p>
<p><strong>2. What are the steps involved in designing?</strong><br />
Before getting into the design the designer should go through the SRS prepared b
y the System Analyst.<br />
The main tasks of design are Architectural Design and Detailed Design.<br />
In Architectural Design we find what are the main modules in the problem domain.
<br />
In Detailed Design we find what should be done within each module.</p>
<p><strong>3. What are the main underlying concepts of object orientation?</stro
ng><br />
Objects, messages, class, inheritance and polymorphism are the main concepts of
object orientation.</p>
<div id="attachment_7060" style="width: 239px" class="wp-caption aligncenter"><i
mg class=" wp-image-7060" src="http://interviewquestionsanswerspdf.com/wp-conten
t/uploads/2016/09/OOAD-Interview-Questions-and-Answers-300x225.jpg" alt="OOAD In
terview Questions and Answers" width="229" height="172" srcset="http://interview
questionsanswerspdf.com/wp-content/uploads/2016/09/OOAD-Interview-Questions-andAnswers-300x225.jpg 300w, http://interviewquestionsanswerspdf.com/wp-content/upl
oads/2016/09/OOAD-Interview-Questions-and-Answers.jpg 768w" sizes="(max-width: 2
29px) 100vw, 229px" /><p class="wp-caption-text">OOAD Interview Questions and An
swers</p></div>
<p><strong>4. What do u meant by SBI of an object?</strong><br />
SBI stands for State, Behavior and Identity. Since every object has the above th
ree.<br />
State:<br />
It is just a value to the attribute of an object at a particular time.<br />
Behaviour:<br />
It describes the actions and their reactions of that object.<br />
Identity:<br />
An object has an identity that characterizes its own existence. The identity mak
es it possible to distinguish any object in an unambiguous way, and independentl
y from its state.</p>
<p><strong>5. Differentiate persistent &amp; non-persistent objects?</strong><br
/>
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.<br />
A non-persistent object is said to be transient or ephemeral. By default objects
are considered as non-persistent.</p>
<p><strong>6. What are models and meta models?</strong><br />

<strong>Model:</strong><br />
It is a complete description of something (i.e. system).<br />
<strong>Meta model:</strong><br />
It describes the model elements, syntax and semantics of the notation that allow
s their manipulation.</p>
<p><strong>7. What do you meant by static and dynamic modeling?</strong><br />
Static modeling is used to specify structure of the objects that exist in the pr
oblem domain. These are expressed using class, object and USECASE diagrams.<br /
>
But Dynamic modeling refers representing the object interactions during runtime.
It is represented by sequence, activity, collaboration and statechart diagrams.
</p>
<p><strong>8. How to represent the interaction between the modeling elements?</s
trong><br />
Model element is just a notation to represent (Graphically) the entities that ex
ist in the problem domain. e.g. for modeling element is class notation, object n
otation etc.<br />
Relationships are used to represent the interaction between the modeling element
s.<br />
The following are the Relationships.<br />
Association: Its just a semantic connection two classes.<br />
e.g.:<br />
Aggregation: Its the relationship between two classes which are related in the fa
shion 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.<br />
ex:<br />
car contains wheels, etc.</p>
<p>car<br />
Containment: This relationship is applied when the part contained with in the wh
ole part, dies when the whole part dies.<br />
It is represented as darked diamond at the whole part.<br />
example:<br />
class A{<br />
//some code<br />
};</p>
<p>class B<br />
{<br />
A aa; // an object of class A;<br />
// some code for class B;<br />
};<br />
In the above example we see that an object of class A is instantiated with in th
e class B. so the object class A dies when the object class B dies.we can repres
nt it in diagram like this.<br />
Generalization: This relationship used when we want represents a class, which ca
ptures the common states of objects of different classes. It is represented as a
rrow line pointed at the class, which has captured the common states.<br />
Dependency: It is the relationship between dependent and independent classes. An
y change in the independent class will affect the states of t</p>
<p><strong>9. Why generalization is very strong?</strong><br />
Even though Generalization satisfies Structural, Interface, Behaviour properties
. It is mathematically very strong, as it is Antisymmetric and Transitive.<br />
Antisymmetric: employee is a person, but not all persons are employees. Mathemat
ically all As are B, but all Bs not A.<br />
Transitive: A=&gt;B, B=&gt;c then A=&gt;c.<br />
A. Salesman.<br />
B. Employee.<br />
C. Person.<br />
Note: All the other relationships satisfy all the properties like Structural pro
perties, Interface properties, Behaviour properties.</p>

<p><strong>10. Differentiate Aggregation and containment?</strong><br />


Aggregation is the relationship between the whole and a part. We can add/subtrac
t some properties in the part (slave) side. It won t affect the whole part.<br />
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.<br />
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.</p>
<p><strong>11. Can link and Association applied interchangeably?</strong><br />
No, You cannot apply the link and Association interchangeably. Since link is use
d represent the relationship between the two objects.<br />
But Association is used represent the relationship between the two classes.<br /
>
link. student:Abhilash course:MCA<br />
Association:: student course</p>
<p><strong>12. Why is planning too much up front a mistake in an OOSAD?</strong>
<br />
You cant plan only for the current phase of the project as<br />
your future activities are still coarse granular. To have<br />
good plannig you need to have fine granularity w.r.t the<br />
tasks to get clear WBS</p>
<p><strong>13. Why should project managers complete hard problems first in an OO
SAD project?</strong><br />
The query actually holds good in general for every situation in life. It is one
of the principles of good time management.<br />
The idea is to tackle hard (and important) problems first. This, if resolved wil
l pep up your confidence to deal with other not so hard issues. Also, this could
have cascading effect on other issues that may get resolved on its own.<br />
I would rather stress on important than hard issues. If a hard problem is not coming
n the way of your deliverables (means it is not important) keep it aside. There
is no need to spend a lot of time on it.</p>
<p><strong>14. Why does the function arguments are called as signatures?</strong
><br />
The arguments distinguish functions with the same name (functional polymorphism)
. The name alone does not necessarily identify a unique function. However, the n
ame and its arguments (signatures) will uniquely identify a function.<br />
In real life we see suppose, in class there are two guys with same name, but the
y can be easily identified by their signatures. The same concept is applied here
.<br />
ex:<br />
class person<br />
{<br />
public:<br />
char getsex();<br />
void setsex(char);<br />
void setsex(int);<br />
};<br />
In the above example we see that there is a function setsex<br />
() with same name but with different signature.</p>

Вам также может понравиться