Analysis Object Model

Analysis Object Model

1. PROPERTIES and RELATIONSHIPS of individual concepts manipulated by the system

   • Separate related concepts
   • Concepts visible to user
   • Depicted in UML
     • <<entity>>        Year        

2. Entity Objects

   • PERSISTENT info tracked by the system
   • Heuristic for Identifying
     • Terms developers or users need to clarify in the use case
     • Recurring nouns in use cases
     • Data sources or sinks
     • Real-world entities sys. needs to track
     • Real-world activities sys. needs to track
   • Start w/ names used by end users
   • Tentative name + brief description
     • Add non-obvious attribute + repsonsibilities
     • NO extensive details + attributes

3. Control Objects

   • Coordinate boundary + entity objects
     • Transfer info from boundary to entity objects
   • Heuristics for Identifying
     • Identify 1 control object per use case
     • Identify 1 control object per actor in the use case
     • Life span of the object = extent of the use case or user session
       • If hard to identify object beginning + end --> use case entry + exit not well defined

4. Boundary Objects

   • INTERACTIONS between actors and system
   • Heuristics for Identifying
     • UI controls user needs to initiate use case
     • Forms user needs to enter data into sys.
     • Notices and messages sys. uses to respond to user
     • Actor terminals when >1 actor in use case
     • Do NOT model visual aspects of interface
     • A:WAYS use end user terms
   • System interface w/ actor
     • At least 1 per use case
     • NOT detailed description of visual UI