ITM 305 Lecture Notes - Lecture 5: Ator, Activity Diagram, Domain Model

• School: Ryerson University
• Department: Information Technology Management
• Course: ITM 305
• Professor: Raymond Moss

Document Summary

The main objective of defining requirements in system development is understanding users" (cid:374)eeds, ho(cid:449) the (cid:271)usi(cid:374)ess pro(cid:272)esses are (cid:272)arried out, a(cid:374)d ho(cid:449) the syste(cid:373) (cid:449)ill (cid:271)e used to support those business processes. A list of use cases and use case diagrams provides an overview of all the use cases for a system. Detailed information about each use case is described with a use case description, which is a textual model that lists and describes the processing details for a use case. Use case descriptions tend to be written at two separate levels of detail: brief description and fully developed description. It gives enough detail for very simple use cases, especially when the system to be developed is a small, well-understood application. Examples of simple use cases are add product comment or send message. It"s the (cid:373)ost for(cid:373)al (cid:373)ethod for do(cid:272)u(cid:373)e(cid:374)ti(cid:374)g a use (cid:272)ase.