ITM 305 Chapter Notes - Chapter 12: Information Hiding, Message Passing, From Chaos

• School: Ryerson University
• Department: Information Technology Management
• Course: ITM 305
• Professor: Upal Nath

Document Summary

Object-oriented design: process by which a set of detailed object-oriented design models are built to be used for coding. Strength of object-oriented design is requirements models from chapters 3,4 and 5 are extended to design models. Design models are created in parallel to actual coding/implementation with iterative sdlc. Agile approach says create models only if they are necessary. Simple detailed aspects don"t need a design model after coding. Communication and complexity about the problem and the solution. All expressed in terms of concepts in a language. Concepts are needed to bring order; abstract idea or general notion. A model is a simplification of reality. Our simplification of our perception of reality (if it exists, otherwise, it is just a mere illusion) A model is an abstraction of something for the purpose of understanding, be it the problem or solution. To understand why a software system is needed, what it should do and how it should do it.