1. How do information systems projects get started in organizations?

2. How are organizational information systems related to company strategy?  How does strategy affect the information systems a company develops and uses?
4. What do you think Jim’s next step would be?

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 alternative approaches for Petrie’s customer loyalty program, where would you look for information? Where would you start? How would you know when you were done?
5. Why  shouldn’t  Petrie’s  staff  build  their  own unique system in-house?
Petrie’s Electronics Case, Chapter 6, Questions 1 and 5
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 code themselves?

MGMT 340 Week 4 Project: Systems Analysis SDLC Phase 2 Package

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 each of the six entities listed in this case plus any additional entities identified in your answer  to  Question  1.  Write  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. Explain why you chose each identifier
4. Using your answer to Question 3, draw the relationships 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 Petrie’s 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

MGMT 340 Week 5 Project: Systems Design SDLC Phase 3 Package

1. Using the guidelines from this chapter and other sources, evaluate the usability of the page design depicted in PE Figure 8-1.
2. Chapter 8 encourages the design of a help system early in the design of the human interface. How would you incorporate help into the interface as shown in PE Figure 8-1?
3. Describe  how  cookie  crumbs  could  be  used  in this system. Are cookie crumbs a desirable navigation aid for this system? Why or why not?
4. The page design depicted in PE Figure 8-1 links to an Order History page. Sketch a similar layout for the Order History page, following guidelines from Chapter 8.
5. Describe  how  the  use  of  template-based  HTML might be leveraged in the design of the “No Customer Escapes” system

1. Why don’t information systems projects work out as planned? What causes the differences between the plan and reality?
2. Why is it important to document change requests? What happens if a development team doesn’t?

3. When a project is late, do you think that adding more people to do the work helps or not? Justify your answer.
4. What is the role of a pilot project in information systems analysis? Why do you think the Petrie’s team decided to do a pilot project before rolling out the customer loyalty system for everyone?
5. Information 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?