Block 2 - From analysis to design Flashcards
action
an atomic momentaneous execution changing the model state;
activity
a non-atomic durative execution repping a set of actions;
aggregate (composite) object
where an object is composed of other objects;
analysis class
reps a solution entity but with no SOs;
assertion
= {precons, postcons, invariants}
association loop invariant
reps relation between two paths around a loop;
baseline
a config-version on which further development can take place;
Cascade pattern
where objects form a chain of messaging responsibilities;
check(ing) in
where an edited config-item is returned to the repository;
check(ing) out
where a config-item is removed from the repository for editing;
class diagram
a static rep of a domain or SS;
class-responsibility-collaboration cards
where a card template is used to identify classes:
- class name = …
- class responsibilities = …
- (other) class collaborations = …
compiler
translates a program from one language to another;
concept(tual) model
reps the static part of the domain;
correctness
where a SS meets its spec.;
defect
where a SS doesn’t meet a requirement(s);
defensive programming
precons should always be checked;
Design by Contract (DbC)
assume precons have been checked;
design model
a static rep of a solution with a class diagram including SOs;
domain model
an static rep of a domain with a class diagram;