Component diagram

Deployment diagram

Class diagram

Network diagram

Component diagram

Deployment diagram

Class diagram

Object diagram

Line with solid diamond at one end

Line with hollow diamond at one end

Line with an arrow at one end

Line without an arrow

Its name, attributes, operations and derived class

Its name, attributes and operations

Its name and operations

Its name and attributes

People, computer

Actor, use cases

People, classes and objects

None of them

In this pattern, a class behavior changes based on its state

In this pattern, a null object replaces check of NULL object instance

In this pattern, a class behavior or its algorithm can be changed at run time

In this pattern, an abstract class exposes defined way(s)/template(s) to execute its method

Builder Pattern

Bridge Pattern

Prototype Pattern

Composite Pattern

Composite Pattern

Facade Pattern

Adapter Pattern

Decorator Pattern

Factory pattern

Abstract factory pattern

Singleton Pattern

Builder Pattern

These design patterns are specifically concerned with communication between objects.

These design patterns provide a way to create objects while hiding the creation logic, rather than instantiating objects directly using new operator.

These design patterns concern class and object composition. Concept of inheritance is used to compose interface and define ways to compose objects to obtain new functionalities.

None of the above.

This pattern is used to get a way to access the elements of collection object in sequential manner without any need to know its underlying representation

This pattern is used to reduce communication complexity between multiple objects or classes

This pattern is used to restore state of an object to a previous state

This pattern is used when there is one-to-many relationship between objects such as if one object is modified, its dependent objects are to be notified automatically

This pattern builds a complex object using simple objects and using a step by step approach.

This pattern refers to creating duplicate object while keeping performance in mind.

This pattern is used when creation of object directly is costly.

This pattern is used when we need to decouple an abstraction from its implementation so that the two can vary independently

Composition Pattern

Facade Pattern

Adapter Pattern

Builder Pattern

True

False

This type of patterns provide a way to create objects while hiding the creation logic rather than instantiating objects directly using new operator

This type of patterns concern class and object composition. Concept of inheritance is used to compose interface and define ways to compose objects to obtain new functionalities.

This type of pattern are specifically concerned with communication between objects.

This type of pattern are specifically concerned with the presentation tier.

This type of design pattern comes under creational patterns

This pattern involves a single class which is responsible to create an object while making sure that only single objects gets created

Singleton class provides a way to access its only object which can be accessed directly without need to instantiate the object of the class

All of the above

In this pattern, a class behavior changes based on its state.

In this pattern, a null object replaces check of NULL object instance.

In this pattern, a class behavior or its algorithm can be changed at run time.

In this pattern, an abstract class exposes defined way(s)/template(s) to execute its methods.

Visitor pattern

MVC pattern

Business delegate pattern

Composite entity pattern

In this pattern, a class behavior changes based on its state.

In this pattern, a null object replaces check of NULL object instance.

In this pattern, a class behavior or its algorithm can be changed at run time.

In this pattern, an abstract class exposes defined way(s)/template(s) to execute its methods.

Java

C

Cobol

HTML

Synchronous Message

Asynchronous Message

Return Message

Activate Message

Actor

Include relationship

Extend relationship

Aggregate relationship

Incremental development

Agile nature

Stable requirements

Time-boxedscheduling

Extreme programming

Excellent programming

Extreme processing

Excellent processing

When the user clicks a “read me” link, the color of the link should change from blue to pink

When the user clicks a “read me” link, the next page should be opened with 5 seconds

When the user clicks a “read me” link, the mouse over should show the target page title in a tool tip

When the user clicks a “read me” link, the read me page should load successfully without errors

Software process model which is agile in nature

team pack in rugby where everyone in the pack act together to move the ball down the field

Both a and b

None of the above

re-design

re-engineering

post checking

maintance

Waterfall model

Spiral model

Iterative model

Incremental model

Structural diagrams

Behavioral diagrams

Non-behavioral diagrams

Non-structural diagrams

Structural diagrams

Behavioral diagrams

Non-behavioral diagrams

Non-structural diagrams

Activity diagram

Sequence diagram

Collaboration diagram

All of them

Activity diagram

Sequence diagram

Collaboration diagram

State chart diagram

+

_

@

~

#

+

—

@

~

#

Activity diagram

Sequence diagram

Collaboration diagram

State chart diagram

Communication diagram

True

False

Process

Entity

Level

Flow

process models

data models

flow models

flow charts

data flow

source

data store

process

data store

dataflow

process

source/sink

A fork in a data flow means that exa

source

data store

process

Compound flow

Composite flow

Control flow

Complex flow

Slides of the box: right - input, left - output, up - controls, down - mechanisms

Slides of the box: right -controls, left -mechanisms, up - input, down - output

Slides of the box: right -controls, left - output, up - input, down - mechanisms

Slides of the box: right - input, left - output, up - mechanisms, down - controls

is a process model

depicts the flow of data through a system

uses rounded rectangles to represent processes

depicts the processing performed by the system

Sequential

Iterative

Incremental

Both Iterative & Incremental

Both Iterative & Sequential

All of them

Saves time

Requires less planning and creates less documantation

Regular feedback from end users

Solves issue in advance by daily meeting

All the term

On request of customer

After system is ready

At the end of each iteration

Daily

Product owner

Scrum team

Scrum master

Users

Product owner

Scrum team

Scrum master

All of them

1,5,2,3,4

1,5,2,4,3

1,2,5,4,3

1,3,2,4,5

Chickens

Release people

Hen

Pigs

Unit, Integration, System, Acceptance

Unit, System, Integration, Acceptance

Unit, Integration, Acceptance, System

It depends on nature of a project.

Acceptance testing

Component testing

System testing

Integration testing

Black box testing

White box testing

Grey box testing

Both a and b

Black box testing

White box testing

Grey box testing

Both Black and White

Both Grey and White

None of them

Black box testing

White box testing

Grey box testing

Both a and b

requirement gathering

implementation

development

design

Integration testing

Acceptance testing

Unit testing

System testing

Waterfall

Code and fix

Iterative

Spiral

Waterfall

Code and fix

Iterative

Spiral