CSC302H1 Lecture 10: 2014.02.06
Document Summary
Purpose: done: use cases, domain model, goal models, challenge: allocate responsibility for the use cases to, bridges the gap btwn requirements and design, sanity check. Tests the language in the use case description. Nouns from the use case get mapped onto objects cases. Verb from the use case get mapped onto actions: completeness check. Discover the objects you need to implement the use. Identify alternative courses of action: object identification, law of demeter each unit should only have limited. Decide which methods belong to which objects knowledge about other units only units closely related to it. A method m of an object o can only call methods of: A global variable, accessible by o, in the scope of m. Boundary objects used by actors when communicating w/ system. Actor control objects or entity objects. Boundary objects boundary objects or entity objects. Entity objects entity objects: constructing a robustness diagram. Add a boundary element for each major ui element.
