Descriptions (what I do)
Str#116. "Describe Services with a Template" Strategy
- Describe each service, using a template as your
guide.
-
- input, output parameters
- description (including pseudo-code or actual code,
detailing the algorithm to be applied)
- traceability codes to preceding documentation, if
any
- visibility: public, protected, private.
Str#117. "Describe Real-Time Services" Strategy
- For each state-dependent service, specify:
-
- precondition <condition(s) for activation>
- postcondition <condition(s) for
termination>
- trigger condition <request, state change, value
change, time lapse>
- terminate condition <request, state change, value
change, time lapse>
- exception action <object.service to invoke, upon
detecting an exception>
- performance constraints (in addition to scenario
performance constraints, when needed).
Establishing responsibilities
/ what I do
Strategies for building object
models