Chapter 3 - Class Libraries

Question 1

Why collection classes?

Answer 1

programming languages provide only limited functionality - additional functionality implemented as libraries

Question 2

what are advantages of using class libraries?

Answer 2

less in-house development, less testing effort and broader test coverage, less maintenance and improvements for free

Question 3

what are the rules of design?

Answer 3

using interfaces (specifies type, always develop against interfaces), abstract class (implementation skelekton), concrete classes (complete type implementation based on abstraction

Question 4

what is good API design?

Answer 4

in-parameter: type should be as abstract as possible, return paramter: type should be as concrete as possible

Question 5

what is fluent API?

Answer 5

using chaining, is flexible and readable

Question 6

how can class libraries be structured?

Answer 6

by dividing systems into subsystems

Question 7

which sorts of GUI are there?

Answer 7

Modal applications with user-guidance (only few or even only one action possible), event-driven applications: events (by user, OS) trigger actions, challenge: handling control flow

Question 8

Explain the Model-view-Controller approach (MVC)

Answer 8

model: comprises domain data and logic, view: responsible for visualization, controller: in charge of event handling

Question 9

Explain the Presentation Model in more detail (MVC)

Answer 9

user interface state is handled, all dependent views are notified about state change

Question 10

What are the limitations of class libraries?

Answer 10

complexity: class libraries tend to be large, good design comes with time (when to release first version?)