Sofrware Design

Question 1

White Box Test

Answer 1

Takes into account code, internal mechanism, it is usually done for unit testing. Sometimes part of integration tests.

Question 2

Waterfall Development

Question 3

Visitor Pattern

Answer 3

Separate an algorithm from an object structure, increase cohesion by removing processing code, visitor calls accept me, and element replies visit me.

Question 4

Vertical Slice

Question 5

Unit Testing

Question 6

UML Sequence Diagram

Answer 6

Shows messages between objects

Question 7

UML class relationships

Answer 7

There are six kinds of relationships. Dependency: changes to the definition of a class imply changes to another. Association: Dependency + Can’t imagine using one class without the other. Aggregation: Association+ an object includes objects from another class. Composition: Association + an object is built with objects from another class

Question 8

UML Class Diagrams

Answer 8

Best communication tool between analysts and users. Has three parts Name, Attributes, Methods. + and - are used to show visibility of the methods.

Question 9

Two Way Merg

Question 10

Triangulation and Faking

Answer 10

Triangulation: If you don’t know the solution and you’re exploring, go step by step, from the simplest cases to the most complicated ones - from very specific, stupid implementations to the one that solves all your requirements.

Faking: Cheating tests by not calculating but returning the “excepted” result. Coding is complicated so fake answers until you are happy.

Question 11

Top Down Integration Testing

Answer 11

Top-down approaches can be useful in testing software that is intended to be generic, tests in layers going down the dependency graph

Question 12

Too Many Comments Smell

Answer 12

Refactor so some comments not needed

Question 13

Too Few Comments Smell

Answer 13

You have to few comments

Question 14

Three Way Merge

Question 15

Test Harness

Question 16

TDD(Test Driven Development)

Answer 16

-Always have working code
-Write code and test it at same time
TDD Cycle:
-Write test
-Compile test
-Write just enough code to get test to compile
-Run test and watch it fail
-Run all tests few times
-Refactor
-Repeat from step 1

Question 17

Task

Question 18

System Testing

Answer 18

-Block-box testing
-Tests high level design
-Done by an independent testing team in the candidate release branch
-Scale is whole system

Question 19

System Prototype

Question 20

Sync Merge

Question 21

Structural Design Pattern

Question 22

Stress Testing

Answer 22

-When: in systems that are intended to react in real-time like control systems
-How: