'Mr. Doe\r'

'* 1. Look over the bea tilt (PE understand 4-1). If you were an employee at Petrie’s Electronics, would you requirement to work on this insure? wherefore or why not? The dispatch scope mastery is to describe a high level overview of the jump size, duration, and stunnedcomes as a summary of the baseline labor plan (BPP) knowledge. A project scope statement and a baseline project plan are created during project initiation and planning * 2. If you were part of the counseling team at Petrie’s Electronics, would you approve the project outlined in the scope statement in PE Figure 4-1?What changes, if either, need to be made to the chronicle? * 3. Identify a preliminary set of open and intangible costs you moot would occur for this project and the transcription it describes. What intangible benefits do you anticipate for the system? Cost Benefit Analysis Sp cross-filesheet Alternative C Chapter 5 Electronics Case * 1. What do you think are the sources of the information Jim and his team collected? How do you think they collected all of that information? * 3. If you were looking for choice approaches for Petrie’s guest loyalty program, where would you look for information?Where would you start? How would you know when you were done? * 5. wherefore shouldn’t Petrie’s staff build their own funny system in-house? Chapter 6 Electronics Case * 1. Are the DFDs in PE Figures 6-1 and 6-2 balanced? Show that they are, or are not. If they are not balanced, how can they be fixed? * 5. Why is it important for the team to create DFDs if they are not going to write the actual system enrol themselves? Chapter 7 Electronics Case * 2. Again, review the DFDs you developed for the Petrie’s Electronics case (or those given to you by your instructor).Use these DFDs to identify the attributes of severally of the six entities listed in this case plus whatsoever tackitional entities identified in your answer to challenge 1. Write an unambiguous definition for individually attribute. Then, redraw PE Figure 7-1 by placing the six (and additional) entities in this case on the plat along with their associated attributes. * 3. Using your answer to oppugn 2, designate which attribute or attributes form the identifier for each entity type. Explain why you chose each identifier. * 4.Using your answer to incertitude 3, draw the relationships between entity types needed by the system. Remember, a relationship is needed only if the system wants selective information about associated entity instances. Give a meaningful unwrap to each relationship. Specify cardinalities for each relationship and develop how you decided on each minimum and supreme cardinality at each end of each relationship. enjoin any assumptions you made if the Petrie’s Electronics cases you gestate read so far and the answers to questions in these cases do not provide the evidence to justify the cardinalities you choose.Redraw your final E-R draw in Microsoft Visio. Chapter 8 Electronics Case * 1. In the questions associated with the Petrie’s Electronics case at the end of Chapter 7, you were asked to modify the E-R diagram given in PE Figure 7-1 to include any other entities and the attributes you identified from the Petrie’s case. Review your answers to these questions, and add any additional needed relations to the written document in PE Figure 9-1. * 5. Complete all send back and field definitions for the Petrie’s Electronics case database using Microsoft Access.Besides the decisions you have made in answers to the preceding questions, fill in all other field definition parameters for each field of each table. Chapter 10 Electronics Case * 1. Why don’t information systems projects work out as planned? What causes the differences between the plan and ingenuousness? * 5. Information systems development projects are said to buy the farm if they are late, go over budget, o r do not contain all of the functionality they were designed to have. Is the customer loyalty program a failure? reassert your answer. If not, how can failure be prevented? Is it important to forbid failure? Why or why not? Use Case Diagram (CRM)\r\n'