Definition 13: Boundary classes connect users of the system to the system. Control classes
map to the processes that deliver the functionality of the system. Entity classes represent
the persistent things of the system, such as the database. (Jacobson, Christerson, Jonsson,
& Overgaard, 1992)
Entities are shared and have a life cycle outside any one use of the system, whereas control
instances typically are created, executed, and destroyed with each invocation. Entity properties
are mostly attributes, although operations that organise an entity??™s properties can also
often be found on them. Controllers do not specify attributes. Initially, their operations are
based on verb phrases in the use case specification and tend to represent functionality that
the user might invoke. In general, class diagrams can be defined as follows:
Definition 14: A class diagram is a graphic representation of the static view that shows a
collection of declarative (static) model elements, such as classes, types, and their contents
and relationships. (Rumbaugh, Jacobson & Booch, 2005, p. 217)
Use.Case.Realisation:.Sequence.and.Activity.Diagrams
Construction of behavioural diagrams that form the model??™s use case realisations help to
discover and elaborate the analysis classes.
Pages:
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263