Term
| A context diagram does the following: (4) |
|
Definition
1) establishes the context for the information in the rest of the view
2) Provides a view of the element being documented and its environment
3) Depicts the scope of the rest of the documentation
4) Bounds the problem that the element or system is responsible for |
|
|
Term
| At the top level a context diagram: (5) |
|
Definition
1) establishes scope
2) defines boundaries
3) shows how the system interacts
4) identifies sources/destinations of data
5) clarifies other systems of interest |
|
|
Term
| Things a "pure" context diagram does not show: (5) |
|
Definition
1) Architectural details
2) Temporal information
3) Data transfer conditions
4) Stimuli fired
5) Messages transferred |
|
|
Term
| Architectural Style (definition) |
|
Definition
A named collection of architectural design decisions that
1) are applicable in a given development context
2) constrain design decisions specific to a particular system within that context
3) elicit beneficial qualities in each resulting system |
|
|
Term
| Categories of architectural styles (3) |
|
Definition
1) Module styles
2) Component and connector styles
3) Allocation styles |
|
|
Term
| Architectural Patterns (definition) |
|
Definition
| A set of architectural design decisions that are applicable to a recurring design problem and applicable for different software development contexts where the problem appears. |
|
|
Term
| Architectural pattern expresses a relationship between which 3 things: |
|
Definition
1) context
2) problem
3) solution |
|
|
Term
| Model-View-Controller (MVC) Pattern: |
|
Definition
| Has separation between information, presentation, and user interaction. |
|
|
Term
| Difference of Style vs Pattern: (3) |
|
Definition
1) Scope: style has strategic design, pattern has tactical design
2) Abstraction: styles are too abstract, patterns are more contrete
3) Relationship: patterns have context |
|
|
