ITM 430 Lecture Notes - Class Diagram

• School: Ryerson University
• Department: Information Technology Management
• Course: ITM 430
• Professor: Markiyan Sloboda

Document Summary

Use cases: writing stories to describe functional requirements. Domain model: identify major concepts in a domain and express that visually. Example: you play dice game and then you get a face value (method) that is returned. Shows interactions among software objects in terms of messages and collabs in order to fulfill system requirements. Provides info as to how objects are going to interact. Domain models don"t have arrows, face values like class diagram does. Models are trying to shape out the scenario at hand. Trying to describe something in an abstract way. Iterative life cycles reduce risk and improves success rate of the project.