ITM 305 Lecture Notes - Lecture 9: Abstract Type, Class Diagram, Problem Domain
Document Summary
Things in the problem domain: problem domain the specific area (or domain) of the users" business need that is within the scope of the new system. Things are those items users work with when accomplishing tasks that need to be remembered: examples of things are products, sales, shippers, customers, invoices, payments, etc, these things are modeled as domain classes or data entities. Two techniques for identifying things in the problem domain : brainstorming technique use a checklist of all of the usual types of things typically found and brainstorm to identify domain classes of each type, things. Tangible things airplane, book, vehicle, document, worksheets. Roles played employee, customer, doctor, patient, etc. Devices sensor, timer, controller, assembly line. Sites/locations warehouse, branch office, factory, retail store, desktop. Details about domain classes: attribute describe one piece of information about each instance of the class, customer has first name, last name, phone number.