Friday, April 15, 2011

Chapter 13

    Just two days ago and yesterday I was a part of creating a system to generate a report for a big shot guy in California. My manager gave me what needed to be done (the request from the user) which was the analysis part done for me. Then I started the design part to decide which categorical qualifications to pull for the report to be accurate and how to split the work up between myself and the other interns to get the job done quicker. The programming part included actually developing the string of qualifications and running the report and tallying how many tickets were open. The testing part of this project was sending that number to my supervisor to see if that sounded right, if it wasn't then I would run new strings and reports again. Then the conversion would have been sending the report in an email to the user in California and asking if they would like anything else done. Finally the production & maintenance would be any future enhancements (which I did have to make) to the report and strings to gain more accurate information.
    This week I read chapter 13. On Tuesday we discussed the chapter. Then I completed our Assessment over the case study on Chrysler's choice to outsource to TCS's information systems. After that, on Thursday we discussed a little bit about the case study and then we kind of went more in depth in the systems development process by deciding what the steps were for building a house (my group) and cooking (other group). Finally now I am finishing up my blog for the week.
    This week we learned about systems development. We learned that the steps for creating a system include Analysis, Design, Programming, Testing, Conversion, and Production & Maintenance. The main goal in the analysis stage is to locate and find problems or find what is needed. In the design stage, the company plans out how they are going to make the changes without actually making any change. Programming is the stage where the system actually gets changed or created. Conversion is the time it takes to start using the new system. There are a few different kinds of conversion techniques including the parallel strategy, where the new system is implemented alongside the old system simultaneously, the direct cutover technique, where the new system immediately replaces the old system, the pilot study, where the new system replaces the old system for only a small group of people before replacing the old system for everyone else, and the phased approach, which is where only one functionality of the new system replaces the same functionality on the old system at a time. This was a very interesting week of learning as this is probably what I plan to do when I have my degree (program and upkeep those programs). Well, I hope you enjoyed!

Saturday, April 2, 2011

Week 11

    I believe that these Web 2.0 tools would be a great source to add and distribute knowledge across a company. The more minds you have contributing to a cause, the more knowledgeable they will be. This would make a wiki a great idea for a company to have everyone contribute their knowledge to the company as a whole. They could add discussion on important topics or add to new ones. In addition, wiki's are always current because anyone can add anything at anytime. Blogs could be utilized too, however, they probably wouldn't be as efficient as a wiki or a portal since they are only updated by the administrator of the account or by adding comments which are hard to search through for specific information. All in all, Web 2.0 tools would definitely add to the efficiency of adding and distributing knowledge across a company in my opinion.
    This week I went over Chapter 11 and on Tuesday we took a clicker quiz over it. Then on Thursday we discussed the case study on Coke's knowledge management systems. This week I created a new account on the Student Dashboard and a new AdWords account and uploaded our pre-campaign report to it. We made a campaign with a couple of AdGroups that are paused until we can get our money from Google.
    This week we went over chapter 11 which was about knowledge management. We learned that the knowledge supply chain includes four major process the first being acquisition, how knowledge is being pulled into the company. The second is storage which is pretty self explanatory, how and where the knowledge is stored. It can be stored and tacit knowledge, people with knowledge without having it put anywhere physically, or explicit knowledge, knowledge that is wrote down for anyone to use. The third step is dissemination, how the company distributes the knowledge throughout for people to use. Then the final step is application, actually using the knowledge. We also went over a bunch of intelligent techniques such as fuzzy logic. Fuzzy logic is used when the answer to a decision isn't always a yes or no but has a varying scale. An example is if someone wants the room to be cool. This could mean any number of degrees that isn't always the same every time. That is basically what we went over along with some more knowledge applications and techniques.

Saturday, March 19, 2011

Week 10

This week we discussed chapter 10 which was over E-commerce, selling and buying goods online. We discussed this on Tuesday in class. Then on Thursday we went a little more in-depth with a case study over online groceries. We also took a clicker quiz over the chapter on Thursday which I did decent on. Ever since Thursday, our group has been trying to straighten things out with Google on our funds for our AdWords account since I put in the wrong CID thinking we were supposed to make our own CID up and stick with it. I was wrong and now we're in a big mess. Hopefully that will get worked out fairly soon so we can get our campaign up and running to meet our deadline or at least close to it. That was basically what I did this week. Hopefully the week after spring break runs a bit more smoothly.
    This week we learned about E-commerce. The main thing that I learned myself was the different business models businesses can take. I also learned that my groups business does not employ any of these models (information broker, portal, social networking, etc.) and that they don't really need to since it is more of a B2B, business to business, model and there is not a lot of interactivity needed other than a phone number. Also since it's B2B there's not a lot of need for information density on the site since the other business probably already knows what they need/want. That is basically a wrap up of what I have learned this week in CIST 3100. Have a great spring break!

Saturday, March 12, 2011

Week 9

    The biggest challenge a company faces when implementing an enterprise system is it's compatibility with their existing business processes. Enterprise systems take a long time to integrate into a company and they must be able to make a swift change in this long process. They have to be able to continue their services while moving into new processes for completing these services. Doing this change without any stalls in service can be crucial for the company as it has been shown that if there are any major hiccups in the implementation, it could mean loss of customers, profits, efficiency, or even complete failure of the company. This risk makes implementing any enterprise system into a company a very serious challenge and should be taken into account in the decision of using an enterprise system or not.
    This week I read Chapter 9. We went over customer relationship management systems on Tuesday in class. I aced the "quiz" we had on Tuesday by just showing up and writing my name on a paper. Then on Thursday we went over the other part of the section dealing with supply chain management. Now today I am collaborating with Justin Jones on the assessment over comparing two enterprise system software from two companies. We chose Oracle's Siebel Systems CRM 8.0 and Saleforce.com's CRM. Today I am also finishing up my blog for the week.
    This week I read Chapter 9 which was about enterprise systems, systems that span across multiple departments in a company. It was then broken down into supply chain management and customer relationship management systems. I learned that supply chain management systems include a company's upstream chain including their suppliers, their secondary suppliers (suppliers' suppliers), and their tertiary suppliers (suppliers' suppliers' suppliers). The company's downstream chain may include their distributors, retailers, and customers. These supply chains can be big or small depending on the kind of business a company does and how they approach that business. Supply chain management systems analyzes the date that flows through this chain and provides solutions to keep costs down, inventory not too high or too low, and keep the demands of the customers met. I also learned that customer relationship management systems look at the relationship with the companies customers and devises solutions on how to gain a higher intimacy with that customer and how to push products to the right people to raise profits. Overall I learned from this chapter that enterprise systems can be very helpful to companies. However, I also learned that they are often expensive, hard to implement, and only useful for certain business. That was my ninth week in Organizations, Applications, and Technology. It was a very hard week for me with all this midterm preparation at the same time but I believe I did my best and that my efforts were satisfactory for not only the class but for myself as well. I hope you enjoyed the reading!

Saturday, March 5, 2011

Chapter 8

    After going over my past blogs, I'm glad to see they show how I am learning. I believe I have learned so much and gained an understanding of how businesses work and the systems that allow those businesses to operate. I have learned some technical things such as the components of networking and computing. For the most part I don't think theres anything about the way I am studying or completing assignments that needs to change. The one thing that I may want to change is getting my assignments done a little bit earlier. So far I haven't had any late assignments but they do get close sometimes.
    This week I read Chapter 8. We talked about the chapter and took a quiz over it on Tuesday. Then on Thursday we went over the Case Study in this chapter which was about one of the biggest data theft in history. Some guys hacked into TJX networks outside TJX stores who didn't have firewalls set, no encryption, and sent financial information over the wireless network. They were able to gain 45 million credit and debit card numbers. We also went over commonly missed questions on the midterm and how the grading was done. Along with all that, I worked with my group to get our Precampaign Report done for our Google AdWords challenge and submitted that on the student dashboard and on Blackboard.
    This week I read the chapter over network security. I learned that every network can be unsecure and has a potential to be hacked or tapped into. Hackers/Crackers use all sorts of programs to obtain information, stop a system, or slow down a system until it is no longer useful. They can do this through the use of viruses, sniffer programs, and worms along with some other means of access into networks. I learned that a very unsecure network is a wireless network because of the ease of being in range to connect to the router and being able to gain access more easily than hard line networks. I also learned that there are plenty of countermeasures for these risks. Firewalls, encryption, and password protocols such as WPA all can stop unauthorized access into a network. That wraps up this blog, like always I hope you enjoyed.

Saturday, February 26, 2011

Week 7 Midterm and Chapter 4

    This week I studied for the midterm. Then I took the midterm on Tuesday with a 3X5 index "cheat sheet." Then I read chapter 4 on Wednesday and took the online quiz, and got a 100. On Thursday in class we went over the chapter which was basically over ethics. Finally today I am writing my blog for the week.
    This week I learned about ethics with information systems. We learned about how to go about deciding if an action is ethical for yourself, everyone else, and the company. We learned about liability and responsibility as well. Other than that, there wasn't a whole lot of terms or concepts that I learned about. That is pretty much it for this blog. I know it is kind of short but that's how the week went in CIST 3100. Hope you enjoyed.

Saturday, February 19, 2011

Chapter 7

    My stance on net neutrality is that it a right for everyone. It's true that some things the internet is being used for aren't necessary. It is the fact that it can be used for anything that makes the internet so profitable. If there is one thing that I have learned in this class, it is that advertisements on "non-necessary" sites pay for a great deal of business' expenses. If there were restrictions set on the priority of importance, anyone who wants to use the internet for recreational uses, most likely the primary "clickers" of those ads will have slower access. This could lead to them getting upset and using the internet less often and less clicks on those advertisements leading to less profits for companies utilizing that. In that sense, it is a lose-lose situation for the general public and businesses. Priority regulations would basically turn the internet into mostly a business tool taking away one of the biggest forms of entertainment for millions of people. This is why I believe that net neutrality should stay intact because if it does not, we will be moving backwards in terms of the internet.
    This week I skimmed the chapter (read paragraphs with bold print words) and then we took a paper quiz on Tuesday. We then listened to the TA (I can't remember his name) talk about all the different networking terms from the chapter. After that we broke up into groups and each talked about a topic of networking  explaining what it was, what the advantages are, and what some possible challenges would be. On Thursday we listened to the lecture while using clickers to answer questions. I really liked how that went and I would like to do that again since I'm not much of an outgoing person in the classroom. Technically I didn't accomplish this task, but Justin sent in the letter from Google getting formal permission from our company to do the group project. Finally, today I am typing out my journal for week 6.
    This week was a wealth of knowledge for me. I have always wanted to know what a lot of these networking terms we have discussed meant, but didn't want to take the time to individually look up every one of them. Just some of the terms that I learned are TCP/IP which stands for Transmission Control Protocol/ Internet Protocol, the set of rules used to define the way data moves from one place to another, TCP being the entire length and IP being the movement between nodes.Another important term I got a better understanding of was IP addresses. IP addresses are used to specify a device to which information or data is sent to. An IP address consists of four strings of numbers ranging from 0-255. We as a world community have actually run out of IP addresses and must now implement IPv6 which adds more strings and numbers to make over a quadrillion addresses. That is where I will wrap this blog up. There are many other terms that I have learned this week but those two were the most interesting to me and was something I have wanted to know for a while.