Term
| True or false: Layered style is one of the most common SA views and completely partitions the architecture |
|
Definition
|
|
Term
|
Definition
| groupings that provide a cohesive set of services through a public interface |
|
|
Term
| True or false: Layered style requires a strict ordering relation (unidirectional) |
|
Definition
| True: layers are hierarchical. Think of an onion. One layer does not touch the onion layer two levels down. However some layering schemes allow layer bridging |
|
|
Term
| Aspect Oriented programming (definition) |
|
Definition
|
|
Term
|
Definition
| shows aspect modules that implement crosscutting concerns and how they are bound to other modules in the system |
|
|
Term
|
Definition
| a specialized module that contains the implementation of a crosscutting concern |
|
|
Term
| Crosscutting functionality |
|
Definition
| Some functionality that a large part of a system depends on -- highly reused code. Examples: Transaction management, logging. |
|
|
Term
|
Definition
Describes static information structure in terms of entities and their relationships
Example: Entity relationship diagram |
|
|
Term
| 3 high-level parts of data modeling: |
|
Definition
1) conceptual (abstract)
2) logical
3) Physical |
|
|
