Sunday, November 21, 2010

Week 13: Clear

This week we learned about Computer Security, Ethics, and Privacy. Computer security is an important issue and one that many people do not take seriously enough. There are different types of security risks that a computer user should be aware of. These include loss of data due to hardware loss such as your laptop or phone getting stolen, preventing yourself from hacker attacks, viruses, and Phishing and also email and message security.

People create viruses for a number of reasons. Some are to make money by giving a user the virus then selling that same person a removal tool. Others make viruses to get credit on the internet, for bragging rights, or just because they can. It is very important that users protect themselves by running a anti virus program on their computer, installing a router and closing off vulnerable ports on their router. 

A Phishing scam is when someone makes a fake email or website which looks and appears real in all ways except it is not. Its only purpose it to get user information. Users are especially vulnerable when connecting to open wireless networks in which their network data can more easily be redirected or captured.

We also learned about software piracy. Piracy is a breach in contract of the EULA in which case the user usually illegally copies the data and may make money distributing it. It is important to know that software piracy costs companies a lot of money and raises prices for normal paying users. It is illegal and pirates face jail time for their actions. It is also important never to reply to SPAM. Spammers send out random emails to addresses and if you reply you are showing them that you are a real person and you will continue to get bombarded by even more SPAM. It is recommended to use a free email which you don't care about to sign up for services which may sell or use your email.

That's it for this week. :)

Secure Email Project

Screen capture below showing both project emails from the Professor.
 Click on image to enlarge.


For the secure email project we were required to find an article that talked about a company and secure email. The article I found was on the Wall Street Journal. The article can be found here:
http://online.wsj.com/article/SB10001424052748703628204575618620657780244.html

This article talked about how Deutsche Post AG, a German company and Europe's largest postal service, is trying to get consumers to use online mail instead of conventional paper. Although there are many free email services such as Gmail and Yahoo the company is trying to sell their "E-Post letter" service on the grounds that it is very secure email. The mailbox is free but it costs 75 USD cents to send a letter. Currently 1 million people have signed up for the service.

To test the security of their E-Post letter system Deutsche Post invited "teams of hackers, academics and security experts" to try and break into their system. If any problems are found they are immediately fixed without the public even knowing. Deutsche Post says that so far 100 large companies have signed up for the service for activities such as "employee pay stubs and sending legally binding information."

Personally I think that this is a very interesting article. It is shocking to me in a way that companies and individuals would pay so much for a service but it also shows the value of secure email at the same time. 

Sunday, November 14, 2010

Week 12: Clear

This week we learned about networks and electronic communication. I had an understanding of networks before this week and therefore I my understanding of the topic is clear.

In order for any node (network attached device) to communicate with the outside world it has to have a NIC card or Network Interface Controller.

There are a few different types of networks. A PAN or Personal Area Network is the smallest and can be composed of up to 6 nodes. A LAN or Local Area Network is slightly larger and should be a home, building or office. A MAN is a Metropolitan area network and is larger then  LAN. It covers a city or another large area. A WAN stands for Wide Area Network and is the largest. An example would be multiple cities or even larger still. The Internet is an example of a WAN.

There are two basic types of network architecture. The most common is client / server. This is when a client ( perhaps a personal computer ) talks to a server. The server serves the data and gives it back to the client. The other types of basic but common network architecture is peer to peer. This is when a personal computer talks directly to another personal computer. An example of this could be the famous Kazaa network.

In combination with the networks that were previously mentioned it should also be noted that a network can be wired or wireless. Most wireless networks are LAN and fairly small. One of the first cities and therefore MAN to go wireless is San Francisco. Here Internet is completely free and wireless.

Thats it for this week!

Sunday, November 7, 2010

Week 11: Clear

This week we learned about Information Systems Development. At first this topic seemed really easy but I was surprised how much information there was to learn. Overall though I feel that I got a good understand of the material presented. I have a background as a programmer and this is in my opinion is closely related to system development.

There are five phases in the system development cycle; all of which are also used in programming. Planning, Analysis, Design, Implementation, and Operation, Support, and Security. It is important to understand these steps because without this you can not build on more material.  Planning covers making, reviewing project requests, allocating resources, and forming a team. Planning is the most important step to me and I am glad that the lectures stressed the importance of this. Although it can take time, it really is necessary. Analysis consists of conducting an investigated and detailed analysis. Design consists of acquiring hardware/software and figuring out the details. I feel that I do not have the best grasp on design. One questions which I am unsure of is why you would be acquiring hardware if you have yet to figure out all the details? Perhaps I am misunderstand some detail here. The next step is Implementation is when stuff actually happens and is built. Lastly operation, support and security are very vital. Operation is basically maintenance. Supporting is monitoring to make sure its ok, and security is making sure the system is secure. Security is really important in my opinion and definitely ties in with previous lectures regarding physically where data is stored.

This week in the material was a lecture with Christine Schoaff who is a UF Systems Analyst. She gave an interesting presentation. It was easy to tell that she had a lot of experience working with people and managing them. She joked that her job was to nag people. I completely agree with her that if you do not plan ahead with all parties involved everything will fall through. This goes along with the fact that if she does a good job it will look like she is actually doing nothing. One of the topics which Schoaff talked about which I was not familiar with was making people feel good. I have never been a manger before and she talked about how it is important to make sure that everyone feels happy and accomplished at the end of the day. Schoaff said her job sometimes requires her to smile even at stupid idea. This make me think back to my job experiences as a worker and not a manager and question a few decisions managers made differently. I also enjoyed her comment on how workers are much less efficient late at night or under stress.

In some of the previous projects and group projects that I have been involved in I wish that I had of known the information presented here. It really is valuable to have a project manager in every group project. I think overall though the most important thing for all parties is thinking ahead and making logical decisions. I really enjoyed the material presented in this topic. I feel that in the future it will help me think more rigidly when faced with projects, groups and of course time! Until next week!

Saturday, November 6, 2010

Database Project

This was an interesting and frustrating project. Before this project I was not comfortable or familiar with Access. Now I feel a lot more competent.

Through this project I leaned a number of new things. One of the easiest things that I did learn but had trouble with was renaming a table. I figured out you simply have to close it first. Importing data was not as easy as I thought it would be. I tried to use the text import feature multiple times but the data was not correctly inserted and errors would come up. I ended up making two new files. One for my own data and the other for the 1000 files. Then I just put them both into a new documents. I finally figured out that I needed to "Paste Append" instead of just "Paste", as this also caused me some problems too. 

I learned that it is important to backup data. If you somehow delete or change the data type all data can be lost with no undo. I also learned how to create filters and sort data. It took me a long time to figure out how to lock a field in a form, but I finally did. One really useful thing I learned was how to create a report from a query.

I think that this database could be enhanced by creating more fields. Since this is a gym perhaps they could make a new table which could track workout routine.You could also have a weight loss table. Other information could be added such as how often a member visits. From the interpret-ability end of viewing the data perhaps Pivot Charts could be added. This would create fancier reports which are easier to read.

Sunday, October 31, 2010

Week 10: Muddy

Correction: Last weeks blog post should have been titled "Week 9" instead of "Week 8" - I forgot to skip over the Midterm week. 

This week we talked about Database Management and the program Microsoft Access. I would also like this point out that this is my first ever "Muddy" blog post. That is due in part to not completely understanding Access. I have worked with MySQL a lot and understand how databases work. However I have never used Access before this week. I thought that it would be very easy to pick up. I was wrong. Its not that easy to pick up. I do understand the basics such as Design View and Datasheet view and how it stores the data. I think the real problem that I am having trouble with is that there is a lot of different task planes and that makes it easy to get confused. I understand what I want to do but not sure how to use the program to accomplish that.

Now I would like to talk a bit about some of the things which I did learn this week and did understand. A database can be defined as a "collection of data organized in a manner that allows access, retrieval, and use of that data" (Discovering Computer 2010, p.514). A database table is similar to what you may see in Excel.
Data can be stored in different ways. It can be in a file processing environment in which every department in a company has its own set of data. Or in a database which is shared throughout the company. Obviously a database is the more efficient choice. In a file processing environment the terms used are different then in a relational database. A file is a table, a record is a row, and a field is a column respectively. Data can also be stored in different dimensions. A relational database stores data in two dimensions but a multidimensional database stores data in more then two. I would like to learn more about multidimensional database since I have never heard of them before but the book does not talk a lot about them.

Microsoft Access is a GUI program that is a relational database management system (DBMS). This means that users can add, delete and sort data. The relational part means that the database stores data in tables using rows and columns. It also means that the database uses relationships. Relationships can be built which connect data and link it together. An easy example of a relationship might be that of a Key Field. A Key Field contains an identification number which is unique to that Record. The only data in a database that should ever be in more then one place is that Key Field. This is because the Key Field is necessary to identity data in different tables. Any other data which is needed in more then one place can be joined together.

In order to manipulate data in a database you need a Query Language. This Query Language is similar in respects to a formula in Excel. It can be typed out by hand but most DBMS such as Access let the user use a wizard. One of the most common Query Languages is SQL where the S stands for Structured. Using a Query Language format data can also be taken out of a DBMS and inserted into a text file. This is an important to do especially for backups. It is also important to note that you don't have to backup the entire database, only certain tables can be backed up if you wish. The text file can then be inserted back into a database. To make sure the data gets transferred correctly is why you would need a SQL. Without it the data may not get put in the correct spot. 

Well that is it for now. There is a lot to talk about when discussing database. Hopefully next weeks topic will be easier. :) Happy Halloween!

Sunday, October 24, 2010

Presentations and Web 2.0 Project

To start off I would like to say how much I enjoyed working on this project. Here is a link to my presentation on Kiva.org. http://www.slideboom.com/presentations/227265/Kiva .

Now I would like to evaluate my own project.

Is there a logical flow and sequence of content? How could it be improved?
Yes, I feel that there is a logical flow of ideals and sequence of content. I do not think that I could have improved any.

Does the presenter anticipate questions and answer them in the right place? At what points did you have questions that were not answered? Yes, I feel that I did try to anticipate questions in the right place. It can be hard since you are the one that researched the project. Now you have to go back and see it from the perspective of someone who knows nothing about it. I did not have any questions that were left unanswered.

Did the presenter grab your attention in the first 30-60 seconds? I think that I definitely grabbed peoples attention when in the first slide with the slogan "loans that changes lives." Anyone would questions what this could mean and what is Kiva. I also grabbed peoples attention with explaining microloans since it may be a new and interesting concept for them.

Did the presenter ask questions and spark your curiosity? I asked questions that went along with the logical flow and I feel that I did spark curiosity in Kiva and microloans.

Did the presenter set the context with a concise explanation? Is it clear what the presenter is trying to share?
Yes I feel that it is clear what I was trying to share.

Did the presenter validate any claims? Yes the claims were validated since I say that the information is directly from kiva.org.

Did the presenter avoid inconsistencies and errors, typos and unbelievable claims? I do not believe there is any typos.

How well did the presenter avoid clutter? I think that I avoided clutter well by limiting the amount of text per slide.

What did the presenter do to ensure readability? I used a white background with black text and easy triadic color on the side.

Did the presenter say it, and then show it or did he/she read the slides? I did read along with the slides however I tried to add and show information that was not written.

Overall I think the biggest thing that I learned was how to make a presentation in powerpoint with narrative audio. Before this project I had never even heard about doing that or even seen it before. I also learned how to upload my presentation to slideboom.com. I had already made a storyboard before since I am in advertising but it definitely helped with this project. I could see myself making a presentation like this for a company. It is easy to do and you never have to worry about messing up your lines or stage fright anxiety. This is important for me because I really do not like getting up in front of people.  I wish that I had of leaned about this a long time ago.