1. Companies could use the System Development Life Cycle (SDLC) to get projects likes these started. The SDLC has four phases that a project will follow to be organized, developed, and executed. The phases are: · Phase 1- System Planning and Selection · Phase 2- Systems Analysis · Phase 2- System Design · Phase 3- Systems Implementation and Operation The SDLC is a tool that helps improve organization and techniques. The SDLC also helps your company strive to success. Information system projects get started in many ways though it really would depend on the organization needs and or goals. The goals set within the organization will drive the selection process of implementing a new information system in multiple ways; this include modifying an existing Information Systems to improve its performance, it could be that the organization want to take advantage of some opportunities. The main purpose of Information Systems is to Collects data, processes it into information then converts information into knowledge for a specific purpose. 2. An organizational information system relates to a companies strategy because the SDLC is made to fit the company not the company fit to the SDLC. What I mean by this is you can have two companies using the SDLC, this does not mean both plans will be the same. The plan chosen will be the one that will suit the company and employees best. Strategy affects the information systems a company develops and uses because that will be the plan that fit the company’s goals and needs for success. An efficient organizational information system and must align with the company strategy in order for it to work efficiently and correctly, the more related it is the better it is, if these are not related the success would be a lot less and hence we need the success of the company if not there would be no purpose of having am information system established and set in place as it should be set up to help the company be more efficient and successful. 4. Jim’s next step is to benchmarking the company this would help him determine how the company is fairing comparing to its competitors. After that Jim will have to implement a new information system that you would attract new traffic/customer to the organizations. Then Jim could create the SDLC chart, decide who he wants to be a part of his team, have a JAD session with his team and execute his plan. Set weekly or monthly goals to meet. Create a survey for customers to provide feedback from customers. Make sure his project is known by the community when it is ready to be launched. 1. There are many reasons that cause the difference between information system plans and the reality. To begin with, lack of understanding the user needs leads to failure of the whole project. Success of any project is usually governed by the scope of the project and the main objective underlying formulation of the project. When the management fails to understand the scope then the project is always doomed t ...

1. 1. Companies could use the System Development Life Cycle
(SDLC) to get projects likes these started. The SDLC has four
phases that a project will follow to be organized, developed,
and executed. The phases are:
· Phase 1- System Planning and Selection
· Phase 2- Systems Analysis
· Phase 2- System Design
· Phase 3- Systems Implementation and Operation
The SDLC is a tool that helps improve organization and
techniques. The SDLC also helps your company strive to
success. Information system projects get started in many ways
though it really would depend on the organization needs and or
goals. The goals set within the organization will drive the
selection process of implementing a new information system in
multiple ways; this include modifying an existing Information
Systems to improve its performance, it could be that the
organization want to take advantage of some opportunities. The
main purpose of Information Systems is to Collects data,
processes it into information then converts information into
knowledge for a specific purpose.
2. An organizational information system relates to a companies
strategy because the SDLC is made to fit the company not the
company fit to the SDLC. What I mean by this is you can have
two companies using the SDLC, this does not mean both plans
will be the same. The plan chosen will be the one that will suit
the company and employees best. Strategy affects the
information systems a company develops and uses because that
will be the plan that fit the company’s goals and needs for
success. An efficient organizational information system and

2. must align with the company strategy in order for it to work
efficiently and correctly, the more related it is the better it is, if
these are not related the success would be a lot less and hence
we need the success of the company if not there would be no
purpose of having am information system established and set in
place as it should be set up to help the company be more
efficient and successful.
4. Jim’s next step is to benchmarking the company this would
help him determine how the company is fairing comparing to its
competitors. After that Jim will have to implement a new
information system that you would attract new traffic/customer
to the organizations. Then Jim could create the SDLC chart,
decide who he wants to be a part of his team, have a JAD
session with his team and execute his plan. Set weekly or
monthly goals to meet. Create a survey for customers to provide
feedback from customers. Make sure his project is known by the
community when it is ready to be launched.
1. There are many reasons that cause the difference between
information system plans and the reality. To begin with, lack of
understanding the user needs leads to failure of the whole
project. Success of any project is usually governed by the scope
of the project and the main objective underlying formulation of
the project. When the management fails to understand the scope
then the project is always doomed to fail. Secondly, failure to
have management continuity and a system of incentives that
helps to motivate overly optimistic estimates the upbeat and
advantages gained from the project. Moreover, a poor alignment
between the end users and the information systems department
leads to failure of many projects in the end. This is because the
IT departments is usually responsible for provision of
information to all other people in the management of the
project. Some of the other factors that lead to lack of
achievement of success in information systems projects in lack
of user involvement, poor planning of the project, unrealistic
expectations from the project and lack of executive management

3. support.
2. Change requests within a project should always be
documented. The administrators of databases and IT controllers
support different business units that have different
requirements. Documenting and formalizing any of the changes
in the business units helps to prevent cases of
miscommunication that can occur between the database
administration and the application development areas.
Consequently, documenting of the changes is essential for even
remote database service providers. This means that if your
business does not have any formal change request process it
should be initiated. In the market today, there are a thousand
and other many source coding version tools and change
management tools that can be used. If the development team
does not not create a change within an organization, this poses a
threat to the success of the project in the end. For instance, the
failure to have change requests in the aforementioned Petrie’s
case led to increase in the costs of operation.
3. Adding people to the project when it is running out of time
does not help in the completion of the project. When a project is
running out of time, the current team does not have quality team
to introduce new people about the requirements of the actual
project. This makes the project a lose-lose situation for the new
people and the current management team for the project. This
means that the team misses from the actual development of the
project. The new people who come to the project do not
contribute positively to the project as they prevent the current
team from achieving their desired success. Addition of more
people also pushes the budget expenditure more than the
expected budget expenditure thus preventing positive
achievement of project success.
4. Pilot projects in information system analysis help to equip
the current team with the ability to share the available resources
and provide the management team with knowledge and
information on resource sharing. This helps the current project
team with information that is required in making decisions in

4. the larger projects. Having a collective structuring of the
knowledge helps to empower project team with the ability of
making logical decisions that will help to improve the
achievement of success in a project. Consequently, Petrie’s
team decided to have a pilot project before rolling out to the
customer’s loyalty system in order to test the users and their use
of the real project. This was beneficial to the project leaders
because they had adequate time to search for issues that would
lead to failure of the loyalty system. Furthermore, the team
wanted to investigate the areas of success in the project. This
would help them to concentrate their efforts in improving
success.
5. Information system development projects are said to fail
when they are late, they do not contain all the functionality or
even when they go over their budgets. Consequently, customer
loyalty program is a failure since it has run out of time.
However, the failure of the project could be prevented in many
ways. To begin with, the management needs to involve all its
users in the project. Secondly, there should be proper planning,
which is accompanied with complete specifications and leveling
of all resources available for the project. The project team
should also set aside realistic expectations aimed at
achievement of success within the project. This means that
chances of failure and running out of time should also be put
under consideration. The requirements of the project should not
be changed since any change within an information systems
project often leads to a failure of the whole project.
Petrie Electronic / Week 5
1. Using the guidelines from this chapter and other sources,
evaluate the usability of the page design depicted in PE Figure
8-1.
a. The words should all be in the same language. Some is in
English some is in a different language.
b. They have a click to act method
c. It has limited capabilities to help most Web browsers to

5. support finely grained user interactivity.
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?
When doing a help system you need to think about what the user
is likely to do if they do not know something. The help system
need to be simple organized and to show what to do. Help
messages should be short, to the point and be understood. It can
show the users how do to something. I would incorporate a help
by explaining to guests how to look at their points record. They
should be able to look at what they did to get those points.
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?
A cookie crumb can be used to show how far the user has gone
from the home page. I think that they can be desirable if there is
many different pages other than just the home page.
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.
I don’t know how to do this. Will you please let me know what
to do so I can do it and turn it in before Sunday.
5. Describe how the use of template-based HTML might be
leveraged in the design of the “No Customer Escapes” system.
A template-based HTML template to display and process
common attributes of higher level, more abstract items. It will
make it easy to make a project change or to add a new aspect of
the system.
2.
· Coupon – customer

6. · Customer – coupon, product, promotion, service
· Product – customer, coupon, promotion, service
· Promotion – customer, coupon, product, service
· Service – customer, coupon, product, transaction
· Transaction – service, customer, coupon
3. Service > Promotion > Coupon > Product > Customer >
Transaction. I felt that this is the order it should go when
selecting an immediate identifier. This is based on past
discussions and the goal of keeping the consumer based on the
information provided.
4.
Week 4 Chapter 7 Petrie’s Electronics Case Questions Grading
Rubric
Petrie’s Electronics Case Questions
Solution
s (15 Points)
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 Figure 7-1 by placing the six (and
additional) entities in this case on the diagram along with their

7. associated attributes. (5 points)
Answers will vary, I suggested List at least 2 attributes for
each of the six entities and describe then in a short sentence or
bullet statement. Then redraw PE Fig 7-1 to look like figure 7-
21 on page 223.
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.
(5 points)
Answers will vary, Look at page 199 for the definition of an
identifier – an attribute that will make each entity unique
(sometimes called candidates Key or primary keys; ie student
ID etc). Pick an identifier for each of the six entities that will
make them unique. Identifiers are underlined in attribute list in
entities – so look on pages 200-201 for some examples)
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

8. cardinality on 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. (5 points)
Answers will vary, I suggested Use the DFD on page 187, then
add the relationships like in figures 7-20 and 7-21 on page 223.
Example is promotion_is_earned would be the relationship
between customer and promotion…what about the rest?
Make sure you validate the cardinality for each relationship; for
instance customer does not have a cardinality for coupons or
transactions in PE figure 7-1 on page 230 – should you add
some?
Week 3 Chapter 6 Petrie’s Electronics Case Questions Grading
Rubric
Petrie’s Electronics Case Questions