The owner and store manager have decided to offer customers a service plan were they pay a flat rate once a year. With this plan, customers only pay for the cost of parts when they have their appliance(s) serviced. They can only buy a service plan if they have purchased an appliance from Appliance Warehouse. With this new service plan, if they have service on their appliance more than 3 times during the year, they will have to pay the full amount of the service fee and cost of parts. If the customer does not buy a service plan but buys their appliance from us, we will give a 20% discount off the service fee for the life of their appliance. Everyone else will pay the full cost of the service plan and parts cost. Create a decision table from these rules. I would like to see your first pass at this by our next scheduled meeting.
I'm not sure how to start the Data Flow Diagram my instructor is requesting. This is the appliance Warehouse Case Study parts 2 and 3 for module week 3. I have seen similar DFD's but not the correct one. I'm not sure if you are familiar with this lesson. It is from CSIS351 Systems Analysis. The following is part of the instructions:
You should create a Data Flow Diagram (DFD). This diagram will help the programmers understand how information is flowing through the proposed system. I suggest that you use the notes from the JAD session. They have identified the entities and processes and you can use this information to create a context diagram.
2.
- The owner and store manager have decided to offer customers a service plan were they pay a flat rate once a year. With this plan, customers only pay for the cost of parts when they have their appliance(s) serviced. They can only buy a service plan if they have purchased an appliance from Appliance Warehouse.
- With this new service plan, if they have service on their appliance more than 3 times during the year, they will have to pay the full amount of the service fee and cost of parts.
- If the customer does not buy a service plan but buys their appliance from us, we will give a 20% discount off the service fee for the life of their appliance.
- Everyone else will pay the full cost of the service plan and parts cost.
Create a decision table from these rules. I would like to see your first pass at this by our next scheduled meeting.
Trending now
This is a popular solution!
Step by step
Solved in 2 steps with 1 images
I need to create a menu for the information that is given in this series of questions.
Not sure to how to start with a hierarchical drawing: This is the problem which is a continuence of the previous questions on this feed.
After your presentation last week, the manager thinks an in-house solution is the way to go. Although our programmers have much experience with system integration and development, they have little experience with user design. You'll have to lay out all the pages of the system. For now, just create a hierarchical drawing of all the pages needed for this system. Think of the menu on the top of the screen and what you'd click on to move to the next screen.
Once you finish the hierarchy, I'll need you to draw out examples of a few of the screens. For example, show a screen with a menu, another which requests user input, one that has methods to contact us, and the last one as an informational page. The menu screen can be an opening page or even a page to decide on types of reports to run. The user input page can be one for any of the users, such as the appointment setters or technicians. Make sure that you outline all of the required validation rules for this input page. The informational page can either be a static page or results from a search. Make sure that you include navigation buttons on each of these example pages.
by Bartleby ExpertThis is a continuation to the question above. The directions continue as follows:
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.
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.
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.
by Bartleby Expert
