Object-Oriented Software Engineering
a use case driven approach
by Ivar Jacobson · first published 1992
5mentions
3recommended by
5HN commenters
2012–2024first – last mentioned
60% recommend40% neutral
Affiliate links. As an Amazon Associate I earn from qualifying purchases.
Object-Oriented Software Engineering is the title of Jacobson's 1992 book describing a reduced tool-less version of Objectory that was referred to as OOSE. ISBN 0-201-54435-0 To this day I still use OOSE notation when sketching a design,…
on “Why UML “Really” Died” ↗…around. The quality of the Lisp and Scheme texts I used, especially SICP, also probably made a difference (the OO texts I used were good, but not as great, with the exception of OOSE (http://www.amazon.com/Object-Oriented-Software-Engineering-A...), but that's as much about great design of your project as well as what the project is making).
on “Introducing .NET Core” ↗…coupling. Or trying to get programmers to write things down. I still remember laughing when he told them something to the effect of “programmers shouldn’t wear illiteracy as a badge of honor”. Essays on Object Oriented Software Engineering was a good book in the early 90s.
on “Ask HN: Why aren't business rules engines more popular?” ↗It's different than the command pattern, and I didn't make up the idea or the name. The whole idea of the Interactor came straight from http://www.amazon.com/Object-Oriented-Software-Engineering-A... which Uncle Bob bases a lot of his talk on.
on “Where's Your Business Logic?” ↗…Classes that came from the analysis model may mutate or even disappear entirely. This is the form of reification that I believe is more closely associated with how the term is used in classical OOD (f.e. Object Oriented Software Engineering: A Use Case Driven Approach), but I suppose people’s experiences may disagree. This is a kind of “right layer of abstraction” that has to be pontificated and not just put down as an object because it’s…
on “When objects are not enough (2021)” ↗