Friday, November 25, 2011

7.1 Security



There are many threats facing information systems. For example, if a fire were to burn down one of our restaurants, now only would Pizzarama lose property, but the sales data for that restaurant would be unrecoverable. In addition, an earthquake could hit our main data center and cause a loss of data there. To make sure our data is safe, we keep local backups as well as an online sync of backups with multiple datacenters located around the United States. Pizzarama employs many different people, For example, we have those who operate our business functions and those who work in our chains such as delivery personnel and cashiers. Employees must only be allowed to see the data that they are intended to see and to make no modifications beyond what is needed. To prevent unauthorized access and information modification, we require passwords for every change that is being made. Each password is signed to a specific user who must be authorized to access certain areas of the information system. In addition, we require keycards to ensure dual authentication. Although Pizzarama respects its partnerships with Kraft, we also want to protect our servers from corporate espionage. We use similar access-control restrictions to prevent our partners at Kraft from accessing any part of our information system other than the information required to fulfill our order.



Pizzarama must also protect itself from hackers and other outside attackers. It is important to maintain a secure network that is free from intruders. This is done by requiring passwords to login to any wireless network and encrypting data on that network. This helps prevent drive by packet sniffing. In addition, Pizzarama has firewalls on every network. Because a firewall allows us to only enable access to approved connections and applications, it helps secure each network from hackers. Pizzarama also has virus monitoring software installed on every computer used by the company. This software will set up a warning when an employee accidentally opens an email containing a virus or other malicious software and help prevent it from being installed. In addition, local systems are wiped daily so that every 24 hours they are restored to a clean state.



The picture above is demonstrating how encryption works. When someone wants to send data to someone else, but wants to ensure that only the intended receiver may access the file, they can encrypt it. After the file has been encrypted, the receiver will be the only one who can decrypt it. To do this, the receiver must have two keys, a public key and a private key. A public key is actually more like a lock. Anyone can access it and use it to lock or encrypt data. Once data has been encrypted with the public key, only the private key can decrypt it. Because only the receiver has the private key, the sender knows that only the intended recipient will have access to the data. In addition, if a Pizzarama Chef wants to send a recipe back, but they want to ensure that the person at the restaurant getting the recipe knows it is from them, they can encrypt the recipe with their private key. The restaurant would just use Pizzarama’s public key to decrypt the message. Because the public key will only decrypt messages scrambled with the private key, they know it is from a Pizzarama chef. Of course, the recipe will be able to be decrypted by anyone because the public key is public knowledge. However, the restaurant will be safe in knowing that the food cooked for our customers actually came from a Pizzarama chef and not a malicious third party.

6.1 Web 2.0 Pillars

At Pizzarama, we could harness collective intelligence by allowing our customers to look at stores, as well as vote on new recipes. This means that we would be using our customer’s contributions instead of paying money for marketing advice. In addition, we could implement innovative web capabilities to mashup a website, such as Facebook with our own site, so that when people buy a pizza, they may invite their friends to eat with them. This is an example of the many ways that Pizzarama could leverage the data we collect on our customers by applying it to business decisions. Although there is nothing that Pizzarama currently sells to customers that would allow them to use the web as a platform, we believe that Pizzarama should be the hub of every party. If we began to offer peer-to-peer technology, allowing sharing and streaming of media.

Monday, October 24, 2011

5.3 B2E Electronic Commerce

Pizzarama has many promotional events and is always trying out new recipes. In order for all of our stores to keep up, we utilize an intranet. Each store can log in to our main company’s server over the internet and access promotional tools as well as training to enable them to better serve our customers. To keep all private information being transferred over the internet safe, all access is done through a VPN. In addition, a firewall is set up to prevent unauthorized access to Pizzarama’s servers.

Sunday, October 23, 2011

5.2 B2B Electronic Commerce

Our company uses an extranet to share inventory data with our suppliers. For example, each store, acting as a client, can automatically send an order to Kraft over the internet when they are low on pizza ingredients. These requests go to our supplier’s servers where the order is automatically processed and sent out. To ensure no unauthorized third parties are able to access our company’s private data, a firewall is set up on both our network and our supplier’s network. In addition, we connect through a VPN, which allows us to secure our private information

5.1 Critique Your Competitor's E-Commerce Website

There are six rules to getting and keeping customers in e-commerce. I have looked at Papajohns.com to determine how our competitor’s site stacks up against them.

The first rule is that websites should offer something unique. Their site seems to differ very little from the websites of competitors. In addition, one can get basically the same service by calling or picking up. Other than industry standard pizza customization, their website offers nothing unique.

The second rule states that the site should be pleasing. The website isn’t bunched up, but it is poorly designed. The front page has a picture of Papa John holding a football behind a green background. On a widescreen monitor, there is also a picture of a football field. In addition, the bottom of the website has a poor fade to white which contrasts very poorly with the rest of the site.

The third rule is the website must be easy to use and fast. The three main options at the top make it fairly easy to make your own pizza or order from their menu. Making and ordering the pizza also seem to be easy. Once you get into making your own pizza, you can easily select toppings and choose whether or not you want the topping on the whole pizza or just half. Alexa claims the site is faster than 66% of all sites on the web.

The fourth rule is that the website must motivate people to visit. There is nothing unique about the site to get you to visit, but it is easy to make sure you get your order right. In addition, each Papa Johns has special offers for specific areas which can be easily customized to each community and demographic.
 
The fifth rule is that you must advertise your presence on the web. When searching for terms like Pizza or Pizza delivery, Papa was either 2 or 3 on Google with similar results on Bing. According to Alexa all but one query that led people to papajohns.com had the words Papa Johns in it. Because of this, I would argue they are doing a poor job pulling people not already looking for their website in.
 
The sixth rule is to learn from your website. It is difficult to tell how much they are using web analytics to focus their website on the things their users care about. They have updated their pizza customizer to make it more visual, allowing a customer to better see how their custom pizza is constructed. In addition, the focus on speed seems to show they know how quickly a customer will go to a competitor if they have to wait for a page to load.

4.4 Entity Relationship Diagram

            Pizzarama’s entity relationship diagram has been set up to show all of our company’s data relates to each other. There are four entities that we collect data on is the invoice, product, company, and customer. All the data of an entity is collected on their own database table. All of Pizzarama’s customers are listed as a record. All of the data we store on them are listed as attributes of their record. Each attribute has a meaning to the user and must be identified by its attribute type. This is what determines what the attribute is actually representing. In addition, different data types might be used to determine whether data being entered is alpha-numeric, a price, or a data.

            We identify customers by their customer key, which stays the same regardless of phone number change, name change, or address change. Each record has its own unique key that allows us to form a relationship with other database tables. An invoice, for example, will have its own unique key, the customer key of the customer who made the purchase, the product key of the product the customer purchased, as well as the company’s key. By doing this we allow newly created invoices to automatically display any information that has been updated such as a new address or phone number.

4.2 Packet Switching Technology

The picture above shows two clients requesting data from two servers. Each server and client is connected to a router which can be located via its IP address. Because of the large size of the data and limited amount of bandwidth, the data request must be broken up into packets in order to have packet-switching technology. Each packet must have a header that contains all the information required to find the client’s router and to allow that router to reassemble the data properly. It must also delete redundant packets and re-request missing packets. All of this is handled by the TCP, or transmission control protocol, of the router. When a packet fits this standard, it is considered an IP datagram. After being sent from the router, the actual transference of data occurs of the IP or Internet Protocol.