Thursday, September 29, 2011

What is a CMS?

By: Blake Haas, Andrew Kuehl, Rachel Moorehead, Berecia Stevens

Definition:
A system providing oversight to manage work flows in a collaborative environment.

Advantages:
  • Control - Content Ownership  and Accessibility 
  • Decrease Costs - Content Creation, Management, and Publishing 
  • Increase Revenues - Time Sensitive Opportunities and Fresh Content 
  • Improve Accountability - Audit Trail and Version Control
  • Maintain Consistency - Presentation Consistency and Brand Integrity 

Disadvantages: 

  • Contains hundreds of files
  • Limited Flexibility in Design 
  • Limited SEO of Web Pages 
  • SEO Maintenance 
  • Slow Loading 
  • Expensive Design 
  • Maintenance Costs

Key Features:
  • A Centralized Repository
  • Workflow Automation
  • Rapid Content Import
  • Dynamic Tracking and Alerts
  • Version Control
  • Automatic Distribution
  • Security

Choosing a CMS:
  • Scope
  • Type of Projects
  • Buy or Rent
  • Quick and easy installation
  • Simple administration interface
  • Quick and easy extension of CMS for extra functionality
  • Simple template manipulation
  • Helpful user community


Examples:

Friday, September 23, 2011

APIs Gaining Ground with Businesses

Most people by now in the Internet Technology field have at least heard the acronym API.  An API (Application Programming Interface) is used to transfer data from product to product or service to service.  It's used to allow developers to integrate your product's offerings into another product or service creating a continuous network of connections.  APIs are new cloud-based libraries in a sense and can help bring together your business's connection to the cloud, mobile devices, and social networks.  Sam Ramji from Apigee, a company that "develops API tools for developers who use APIs", gave a presentation on this topic that can be found here.  In his presentation, he talks about how APIs help businesses stay ahead of the fast changing markets and the continuously fractured interest groups they are trying to reach.



The ideas behind APIs and API development are openness and distributing data as quickly and efficiently as possible.  This comes with risks and control issues.  Businesses need to send out their typically legacy information for use by outside sources that might not be under their control to manage.  Business though can control abuse by setting rate limits for information transfer or by setting access restrictions.  Innotas, a cloud based PMO, developed their API offerings with Apigee.  Innotas was looking for a solution to get their customers consistent service delivery and to gather information on in-bound and out-bound traffic.  They approached the risk of control by implementing separate analytics and traffic control to manage data transfer.



The benefits of APIs though far out weigh the risks.  In the same sense that businesses can push information out, they can also draw information in.  This new stream of information can be used to adapt and innovate their current business offerings and its APIs and develop the business's model around its API offerings.  Innotas, in their implementation, provided operational and business-level visibility into their APIs.  This gave them access to customer usage reports, helped to provide the quality they were striving for, and stayed competitive over their on-premise counterparts.  In conclusion, I leave you with the words of Chris Anderson from Wired Magazine:  "The Web is Dead.  Long Live the Internet."

For more information:
Another presentation by Sam Ramji
http://www.slideshare.net/samramji/punctuated-equilibrium-celestial-navigation-and-ap-is
The API Evangelist
http://www.apievangelist.com/

Tuesday, September 6, 2011

Welcome to the Future

This week in class we are talking about the Future of the Internet.  In preparation for class, we are reading the UK Future Internet Strategy Group's "Future Internet Report - May 2011".  In this report, the group charged defines the future of the Internet, the opportunities and challenges faced moving forward toward this future, and what the UK can do to prepare for it.  The group defines the "Future of the Internet" in terms of three emerging components: combined service offerings, shared data amongst services, and a revamped network infrastructure.



Combined Service Offerings:

As the Internet grows and expands so grows the number and type of devices that are connected to it.  Sensors and mobile connected devices and items are becoming a more integral part of the Internet and the way it is utilized.  With so many connected devices, a new type of data is being collected:  sensor collected data.  In conjunction with human entered data, sensor and device data can be used to provide a better picture of the services utilized and customize your service offerings at lower costs at anytime.  Also with this increase of data comes the breaking down of barriers between systems to make the data needed readily accessible to the person who needs it and not stored in an isolated system.

Shared Data Management:

More companies than ever are collecting data about your web browsing and purchasing history.   They turn around and use that data to customize your experience with their services or sell it to other companies to do the same.  As more and more services combine, lots of data is being passed back and forth.  This can be good, and this can be bad.  One of the main concerns with storing all your data in a readily available packet of information is the security used to move the packet from place to place and the controls to determine who gets which piece of data.  How this process develops will be a big driving factor for what services can go to a cloud environment and which ones need to stay on-premise.  Another aspect of the shared data component includes centralizing access to ease service integration into an already developed access control system.



Revamping the Network:

With scenarios for communications (machine-to-machine, machine-to-man, and man-to-machine) increasing, the network that these communications move across needs to be growing and scalable too.  More and more of the data provided to end-users are large on-demand, real-time products, and the network needs to be able to handle that much information as quick as possible.  Also a large wireless network needs to be created and implemented to maintain an always-connected environment, but this also comes with challenges such as the handling of wireless spectrum interference and the need for broadly accepted IPv6 implementation.

I feel that this report accurately represents where the Internet is going: a centralized, cloud-based service provider.  I am excited about the progress being made, but I'm also hesitant about being "there" now as there is not a lot of legislation developed yet to consider the consumer's wants and needs versus the wants of the service provider.  This report, while mentioning a few big names in their case studies, also did not look at the big stake holders currently highly invested in the Internet such as Microsoft, Google, and Apple, and how their choices as companies would effect the Internet "market" and how it grows. 

The topics that we are covering in my MIST7500 class go hand-in-hand with this report.  We've so far reviewed cloud-based service offerings.  We've implemented many integrated services.  And coming up later in the semester, we will be looking at different networking technologies.  This class covers a good bit of the leading edge technology currently being developed and utilized while showing you where we've been too.

Where to next?