Final deck

Question 1

What is factory method pattern?

Answer 1

A creational pattern (under design pattern), that deals with object creation mechanisms.

Basic form of object creation could result in design problems or added complexity. Factory pattern solves this by controlling this object creation

Question 2

What is the intent of builder design pattern?

Answer 2

Separate the construction of a complex object from its representation so that the same construction process can create different representations.

Question 3

What is adapter design pattern? (Structural Design pattern)

Answer 3

Convert interface of a class into another interface clients expect. Adapter lets classes work together that couldn’t otherwise because of incompatible interfaces.

Question 4

What are structural design patterns?

Answer 4

Structural design patterns are all about class and object composition. Structural class-creating patterns use inheritance to compose interfaces. Structural object-patterns define ways to compose objects to obtain new functionality.

Question 5

What are Behavioral design patterns?

Answer 5

Behavioral design patterns are all about Class’s objects communication. Behavioral patterns are those patterns that are most specifically concerned with communication between objects.

Question 6

What is Equivalence partitioning?

Answer 6

Software testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived.
Goal is to reduce test cases that must be developed.

Question 7

What are the steps of spiral?

Answer 7

Combination of waterfall and iterative model. Each phase begins with design goal and ends with client reviewing the progress.

1. Planning - includes estimating the cost, schedule and resources for the iteration. Involves udnerstanding the system requirements for continuous communication between the system analyst and the customer
2. Risk analysis - Identification of potential risk is done while risk mitigation strategy is planned and finalized
3. Engineering - Testing, coding, deploying software at the customer site
4. Evaluation - Evaluation by the customer. Includes identifying and monitoring risks such as schedule slippage and cost overrun.

Question 8

When to use spiral?

Answer 8

When project is large
When releases are required to be frequent
When creation of a prototype is applicable
When risk and costs evaluation is important
for medium-high risk projects
when requirements are unclear and complex
when changes may require at any time
when long term project commitment is not feasible due to changes in economic priorities

Question 9

Advantages of spiral

Answer 9

Additional functionality can be done at later stage

Cost estimation becomes easy as the prototype building is done in small fragments

continuous or repeated development helps in risk management

Development is fast and features are added in a systematic way

Question 10

Disadvantages of spiral

Answer 10

Risk of not meeting the schedule or budget

works best for large projects, demands risk assessment expertise

for smooth spiral, protocol needs to be followed strictly

More documentation