Ivar Jacobson citations

Ivar Jacobson est un informaticien suédois. Il est principalement connu pour être l'un des concepteurs du langage de modélisation UML. Wikipedia  

✵ 2. septembre 1939
Ivar Jacobson photo
Ivar Jacobson: 6   citations 0   J'aime

Ivar Jacobson: Citations en anglais

“The analysis model will not be a reflection of what the problem domain looks like… The reason is simply to get a more maintainable structure where changes will be local and thus manageable. We thus do not model reality as it is, as object orientation is often said to do, but we model the reality as we want to see it and to highlight what is important in our application.”

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 185: cited in: " Object Oriented Software Engineering: A Use Case Driven Approach Ivar Jacobson, et al. (1992) http://tedfelix.com/software/jacobson1992.html", Book review by Ted Felix on tedfelix.com, 2006.

“People regard their environment in terms of objects. Therefore it is simple to think in the same way when it comes to designing a model.”

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 42; cited in: Sten Carlsson and Benneth Christiansson. (1999) " The Concept of Object and its Relation to Human Thinking: Some Misunderstandings Concerning the Connection between Object-Orientation and Human Thinking http://www.vits.org/publikationer/dokument/289.pdf." Informatica, Lith. Acad. Sci. 10.2. p. 147-160.

“A use case is a complete course of events in the system, seen from a user’s perspective.”

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 157.

“When a user uses the system, she or he will perform a behaviorally related sequence of transactions in a dialogue with the system. We call such a special sequence a use case.”

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 127; as cited in: Journal of Object-oriented Programming Vol 10, Nr 2-9. p. 32.

“The control objects model functionality that is not naturally tied to any other object… We do not believe that the best (most stable) systems are built by only using objects that correspond to real-life entities, something that many other object-oriented analysis and design techniques claim… Behavior that we place in control objects will, in other methods, be distributed over several other objects, making it hard to change this behavior.”

Source: Object-Oriented Software Engineering: A Use Case Driven Approach (1992), p. 133 as cited in: " Object Oriented Software Engineering: A Use Case Driven Approach Ivar Jacobson, et al. (1992) http://tedfelix.com/software/jacobson1992.html", Book review by Ted Felix on tedfelix.com, 2006.