Originally posted by xjl xu:
[QB]The problem is why my sample test question is different with the question provided by Liu Dong?
Originally posted by Axel Janssen:
(exam oriented) where does Larman say that?
In my understanding classes shall define operations (methods) in Analysis stage.
Originally posted by Vikrama Sanjeeva:
Does domain model class & conceptual classes are same thing? If yes, then there is no correct answer of question#01, because we cannot define methods in conceptual classes.
An operation is something that is invoked on an object (the procedure call), whereas a method is the body of procedure. The two are different when you have porymorphis. If you have a supertype with 3 subtypes, each of which overrides the supertype's "foo" operation, you have 1 operation and 4 methods that implement it.
Fowler, Uml Distilled, p. 59
the decomposition of a domain of interest into individual conceptual classes or objects [...] Using UML notation, a domain model is illustrated with a set of class diagrams in which no operations are defined.
"[...]Within conceptual models, you shouldn't use operations to specify the interface of a class. Instead, use them to indicate the principal responsibilities of that class, perhaps using a couple of words summarizing a CRC responsibility. (Larman, UML distilled, p. 59.
Analysis classes are classes that
- represent a crisp abstration in the problem domain.
- should map on to real-world business concepts (and be carefully named accordingly)
Arlow, Neustadt, UML and the Unified Process, p. 129