Strategy Design Pattern

Factory Design Pattern

Template Design Pattern

Command Design Pattern

Multiple developers

can work simultaneously on project.

Creational pattern creates

an object by calling a method instead of a constructor. 

Cannot update any

class

Create only one

object at time

Usability testing

Component testing

Acceptance testing

Unit testing

System testing

It focuses on risk assessment in each iteration

It elaborate requirements by extra analysis

It focuses on business models 

It focusses on planing of each iteration

Recursion

Overload

Override

Reuses existing components and does not need to write their own code from scratch.

Writes their own code even if similar components exist.

Does not declare the source of a component he/she reused from an open-source repository.

Writes their names on a file that was imported from an open-source repository to give the impression that he/she wrote it.

Should only be written by the developer and approval from the client is not needed.

A design document to show high-level as well as detailed design.

Concerned with what functionalities may exist and not how they are implemented.

Should be written at the end of the development cycle.

Actors

Objects and actors

System

Objects

Classes

Factory 

Decorative

Singleton

Strategy 

Both A and C.

The developer can deliver partially working system components to the customer more quickly.

Customers can get value from the product only at the end of the process.

The software developer does not need to care about changing customer requirements.