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;
dynamic model
models behaviour;
dynamic tool
a tool used at run-time;
enumeration type
a user-defined symbol alphabet;
external event
where a user acts on the SS in some way;
final state
a solid circle enclosed in an empty circle with only incoming transitions;
Fork pattern
where one object assumes all the messaging responsibilities;
formal technical review (FTR)
a critique of a SS with a view to improving it;
fragment (UML)
encapsulates behaviour inside a labelled (opt / alt / loop) box;
General Responsibility Assignment Software Patterns (GRASP)
guidelines on how to assign responsibilities to components;
grammatical parse
identifying noun phrases from a domain description to discern candidate classes;
GRASP Creator
provides guidance on which class should be responsible for creating new objects;
GRASP Expert
provides guidance on which class should be responsible for initialising and state-changing an object;
initial state
a solid circle with only one outgoing transition;
interaction diagram
= {sequence diagram, communication diagram}
interface
the SOs of a component;
self-transition
where a state transitions to itself;
Law of Demeter
on receipt of message m(p_1,…,p_n), an object O should only send messages the following objects:
- O itself;
- p_k;
- objects that m() tells O to create;
- objects O holds a reference to;
message numbering
shows chronological order of message-sends in a communication diagram;
namespace
a collection within which names are unique;
navigability
where 1+ associations / links can be hopped in order to reach an object(s);
non-deterministic
where 1+ outcomes is possible;
Object Constraint Language (OCL)
[UML + logic + sets] to rep invariants;
object diagram
an instance of a class diagram at time t;
package
a collection of components and / or other packages;
qualified association
where a qualifier is added to the Class_A end of the association but with the qualifier being derived from a Class_B end attribute;
recursive association
a relation between a class and itself;
role name
where the doer (or doee) of the association is labelled at the relevant end;
sequence diagram
reps the message-sends with time flowing downwards;
signature
the name, parameters and return type of an SO;
state machine
reps the states an object goes through during its life;
static analysis tools
tools that test SS at compile time;
UC realisation
mapping UCs to their SOs
