Friday, May 17, 2019

Mr. Doe

* 1. Look over the scope report (PE blueprint 4-1). If you were an employee at Petries Electronics, would you want to work on this project? Why or why non? The project scope statement is to describe a high level overview of the project size, duration, and outcomes as a summary of the baseline project plan (BPP) study. A project scope statement and a baseline project plan are created during project initiation and planning * 2. If you were part of the management police squad at Petries Electronics, would you approve the project outlined in the scope statement in PE Figure 4-1?What changes, if some(prenominal), need to be made to the document? * 3. Identify a preliminary set of tangible and impalpable costs you think would occur for this project and the system it describes. What intangible benefits do you anticipate for the system? terms Benefit Analysis Spreadsheet Alternative C Chapter 5 Electronics Case * 1. What do you think are the sources of the information Jim and his tea m collected? How do you think they collected any of that information? * 3. If you were looking for alternative approaches for Petries customer loyalty program, where would you look for information?Where would you start? How would you know when you were simulatee? * 5. Why shouldnt Petries staff build their own unique system in-house? Chapter 6 Electronics Case * 1. Are the DFDs in PE Figures 6-1 and 6-2 equilibrate? Show that they are, or are not. If they are not balanced, how fecal matter they be fixed? * 5. Why is it valuable for the team to create DFDs if they are not going to write the actual system code themselves? Chapter 7 Electronics Case * 2. Again, review the DFDs you developed for the Petries Electronics case (or those devoted to you by your instructor). handling these DFDs to identify the attributes of distributively of the sestet entities listed in this case plus any additional entities identified in your answer to Question 1. release an unambiguous definition for each attribute. Then, redraw PE Figure 7-1 by placing the six (and additional) entities in this case on the diagram along with their associated attributes. * 3. Using your answer to Question 2, designate which attribute or attributes form the identifier for each entity type. develop why you chose each identifier. * 4.Using your answer to Question 3, draw the kinships between entity types needed by the system. Remember, a relationship is needed only if the system wants data about associated entity instances. Give a meaningful name to each relationship. Specify cardinalities for each relationship and explain how you decided on each minimum and maximum cardinality at each end of each relationship. State any assumptions you made if the Petries Electronics cases you have 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 diagram in Microsoft Visio. Chapter 8 Electronics Case * 1. In the questions associated with the Petries 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 Petries case. Review your answers to these questions, and add any additional needed relations to the document in PE Figure 9-1. * 5. Complete all table and force field definitions for the Petries 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 dont information systems projects work out as planned? What causes the differences between the plan and reality? * 5. development systems development projects are said to fail if they are late, go over budget, or do not contain all of the functionality they were designed to have. Is the customer loyalty program a failure? Justify your answer. If not, how can failure be prevented? Is it important to avert failure? Why or why not? Use Case Diagram (CRM)

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.