Now that the DFD has been created, it is time to build an object model for our
Question:
Now that the DFD has been created, it is time to build an object model for our new system. When thinking about SIM's objects, use the entities already identified: the technicians, customers, and appointment setters. Since SIM is also interfacing with the Parts Department, it is important to use that department also as an entity.
Also, create a Use Case diagram. Make sure to identify the entities as actors and show the interaction between each of the actors. Be sure to identify at least two processes and show all the actions between them. Don't forget to include a system boundary so we can determine which actions occur within the system and which are external to SIM.
Hope you had a relaxing weekend!
Carlie
Hi ,
With the creation of the use case diagram, you should be able to create a model (or table) showing each object. For each object, be sure to outline associated attributes and methods. Hopefully, the use case diagram and the DFD will make this process fairly straightforward.
Please send this information to me quickly so it can be passed on to the developers.
Thanks!
Carlie
Hi
I almost forgot to mention that the developers need 3 instance examples for each of the entities. I suggest that you use the data library and previously developed organizational chart to find examples.
Please include this with your object modeling.
Don't forget that there is a retirement lunch on Thursday for Tim Stafford. I hope to see you there!
Carlie
Remember, an object is a person, a place, an event or a transaction that is significant to the information system. An object includes data and processes that affect that object, and objects belong to classes. See figure 6-8 in your text for an example of attributes and methods for a class object
There are many objects in the new SIM system, you just need to identify 4 actors, or people, who interact with the SIM program. Your DFD that you created for the last assignment should help you identify 4 actors. Then draw a Use Case diagram of them interacting with SIM. The boundary shows what the system does while actors are outside the boundary.
2. Now you need to create a table of these actors (from #1 - customer for example) and describe their attributes (personal info is one) and their methods (customer requests service is one). You should be able to create a table of 4 actors, their attributes and their methods.
3. The actors you have identified are actually classes - customer for example. So an instance of a customer is a specific customer. So take the actors from #1 and find 3 instances or examples of each. Use your organizational chart back from assign #1 for employees - technicians, parts dept. personnel etc. and download the service records from the resources tab of Appliance Warehouse to find customer names. These are the instances of the objects or actors of this exercise.
Service Records Sample
Date Called | Date of Service | Appliance type | Appliance serial number | Parts Needed | Technician assigned | Customer Name | Customer Address | Customer Phone |
1/6 | 1/6 | Refrigerator | KN-78-215-896 | KN-1256 | Robles | Sophie Goldberg | 123 Main St, Hopkinton, MA | 508-555-1256 |
1/6 | 1/7 | Dishwasher | WP-55-311-698 | WP-1788 | Wong | Mitch Chu | 5525 Winter Rd, Medford, MA | 617-555-9898 |
1/7 | 1/7 | Refrigerator | WP-78-956-694 | WP-8877 | Henson | Jamie Fernandez | 2 Hope St, Hull, MA | 617-555-4125 |
1/8 | 1/10 | Microwave | AB-99-357-753 | AB-3321 | Wong | Mike Singh | 15 Arch St, Tewksbury, MA | 508-555-3596 |
1/9 | 1/9 | Washing machine | GE-10-122-542 | GE-2119 | Robles | George Kostanza | 369 Pike Circle, Danvers, MA | 508-555-6235 |
1/9 | 1/10 | Dishwasher | KN-55-396-477 | KN-5511 | Robles | Felicia Parkinson | 50 Central Ave, Hopedale, MA | 508-555-2144 |