The document discusses object-oriented analysis and design (OOAD), including an introduction to basic OO principles like encapsulation, abstraction, hierarchy, and modularity. It then covers various techniques for object-oriented analysis like noun lists and use cases. Finally, it discusses the process of transforming analysis models into design models using object-oriented design.
32. Activity Diagram Activity diagrams describe the workflow behaviour of a system Start Fork Branch Merge Joint End
33.
34.
35.
36.
37.
38.
Notas do Editor
Before moving on, ask the students to name the four basic principles of OO (as a review).
Discuss what makes a good abstraction with the students: Concise, Represents a single coherent concept, etc.
Encapsulation is putting the “databits” and operations that manipulate them in the same place. Encapsulation DISALLOWS direct manipulation of things that have been encapsulated without utilising the supplied interface. Another example - the accelerator on a car. You put your foot down and car goes faster - this works on most cars, and you don’t worry about the cables, electronics, engine, etc.
Modularity supports separation of concerns. Another example of modularity is a car, which is made up of a body, chassis, engine, wheels, etc.
Hierarchy is not an organizational chart. Hierarchy is not a functional decomposition. Hierarchy is a taxonomic organization. The use of hierarchy makes it easy to recognize similarities and differences. For example, in botany, plants are organized into families, chemistry uses a periodic table to organize the elements. Another example -- telephone number, then a 0800 (free call) number, premium rate number, etc
Review the 4 basic principles of OO (abstraction, encapsulation, modularity, and hierarchy) and why they are good. Ask the students to name the OO concepts (e.g., class, package, interface, etc.) that support those principles. Emphasize that OO facilitates the following best practices: Develop Iteratively Model Visually Use Component Architecture