Making an appointment and verifying parts availability

Should be able to identify the users of the systems and most requests into and out of the system.

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 exam; 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 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 issed on to the developers. Thanks! Carlie 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