Content Development using Web Farms

The following diagram shows in our view a well structured team approach to developing eLearning or corporate content.
Interestingly, although Corporate Podcasting is not shown as an exclusive element, it should be considered as part of the mix for collaborative learning. We have to assume that there will be elements of the team accomodating its development.

  1. Shows a local (De-militarised Zone – A secure internal computer operations / development area) DMZ Web Farm.
  2. Shows a Co-located Web Farm.
  3. Using a Staging Server. This is an internal server on which the eLearning (eL) modules are assembled and usually tested (although in some cases an independent host is used for testing). Also acts as a back-up
  4. Here eLearning Developers and Content Authors work on their individual workstations (a PC or MAC) and at some point will upload their finished products to the Staging Server.
  5. Shows the Administrator replicating master content from the Staging Server to each and every content Server.
  6. Acts as Web operations (e.g: User Interface)

There is also a need to provide an additional layer, i.e: The quality assurance for each production, whether it be a piece of multimedia or text. One more thing, what about taxonomy standards and control (inc: standards) for meta data – We should think about who is considering this essential area especially in the context of controlling incoming content based on learner or listener interaction.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s