Classes could implement/inherit some interface

or abstract class

Classes are collaborating together

A and C

All the above

Classes aggregate each other

A risk process

A Phase in the process

None of the above

A Sprint in the process

you like to reuse code

you like to

have flexible

There is a Has-A relationship between classes

There is a IS-A relationship between classes

Requirements confusion

Requirements amalgamation

All of the above

Lack of clarity

None

Focus on sequence of scenarios.

Focus on static behavior.

Focus on non-functional requirements.

Focus on validation interfaces.

Focus on functional requirements.

Sequence Diagram

Class diagram

Use Case Diagram

State Diagram

None

a or d

Waterfall

Xp programming

Component reuse

Incremental

Organization requirement.

Product requirement

External requirement

Operational requirement

Environmental requirement

Association

Expanding

Inheritance

Aggregation

None

Functional requirement document

Requirements specification document

None of the above

Pre- proposal requirement document

Software design document