Summary.

“Things” in the Problem Domain

  • Problem domain–the specific area (or domain) of the users’ business need that is within the scope of hte new system.
  • “Things” are those items users work with when accomplishing tasks that need to be remembered
    • Examples of “Things” are products, sales, etc. …

Two techniques to identify “things”:

  • Brainstorming technique
    • Use a checklist of usual types of things typically found and brainstorm domain classes of each type
  • Noun Technique
    • Identify all nouns that come up when system is described and determine if each is a:
      • domain class
      • an attribute
      • or something we don’t need to remember

Brain Storming Technique: Steps

  • Any tangible things?
  • Organizational units (OU)? Sites/locations?
  • Incidents or events that need to be recorded?

Structured like this: Things: - Tangible things: airplane, book, etc - Roles played: employee customer, etc - Organizational units (OUs): dvision, department, etc - Devices: sensor, timer, etc - Sites/locations: warehouse, branch office, etc - Incidents, events, or interactions: flight, service call, etc