In cooking, you have many different types of tools you can use to make a meal. For example, you have mixers, measuring cups, cutting boards, and so many other tools. Each tool is designed to meet the needs of the cooker and serve a specific purpose in the cooking process. An LMS is not different in that sense. There are several types of LMSs in the market being used for educational as well as training purposes, and one of the most difficult choices for organizations and institutions to make is deciding the type of LMS to select based on deployment or license (Pappas, 2014). Of course, many other factors (e.g., pricing, support, additional features, and others) must be considered and weighed in this decision. Still, the cost combined with financial and technical requirements are still the main focus when selecting an LMS (Croitoru & Dinu, 2016). Indeed, it is important to analyze and examine the type of LMS deployment because of its influence in the overall cost as well as other relevant requirements that can inform the decision about an LMS.

There are two main types of LMS deployment you need to be familiar with: (1) proprietary, and (2) open-source. Within those two solutions, there are two other distinct categories to be considered: (a) Software as a Service (SaaS) or cloud-based system and (b) Installed LMS. In order to determine what type of LMS is beneficial to an organization or institution, a clear understanding of the advantages and disadvantages of each solution must be reviewed. The following sections of this chapter will provide a definition for each main type of LMS deployment, compare their features based on the benefits and drawbacks, and discuss additional components/apps that can enhance an LMS.

Defining Proprietary (or Commercial) LMS

Imagine that you came up with an amazing recipe on your own, now you are faced with the dilemma: do I share this recipe with everyone? Or do I charge a fee to share my recipe partially with others? Well, if you choose the latter option, you follow a proprietary software model. In a proprietary software model, the "recipe," which is the source code, is composed of written commands developed by a programmer, and is often hidden from user’s view not only as a technical, but also as a legal matter (Zittrain, 2004). The reason for this secrecy on the source code is to prevent others from developing new software without the proper permission from the copyright holders.

In the case of an LMS, a solution is considered proprietary, also known as commercial, when its software is licensed under an exclusive legal right of the copyright holder (Pillai & Kevin, 2013). For example, if your organization has adopted an LMS such as Blackboard, which is a popular commercial LMS at the time this chapter has been written, then its company gives your organization the right to use the software under certain conditions based on a license fee. The conditions are stipulated by the LMS company in the form of a contract or agreement between the parties involved and the cost of the licensing fee is often based on annual per-user licenses. The license fees usually vary their cost between $15-$100 per user (Yupangco, 2018). In addition to the licensing fee, other fees might also be included for operation, maintenance and technical support of the LMS software.

In summary, the nature of a proprietary LMS is for profit, as schools and organizations pay a fee to use the software. And a proprietary software follows a “closed” source model in which the source code is kept in-house, i.e., within the company, and not released to the public (Pillai & Kevin, 2013). Going back to our cooking analogy, you can think of the software code as a famous restaurant’s secret recipe. The restaurant keeps that recipe “closed” in-house without sharing any particular details or information to the public. This closed information allows the recipe to be intact without any consumers/users’ alterations or any addition to the original recipe. The same goes for proprietary LMS. The company that developed the LMS software will not allow users to modify or add to their software source code. The LMS company either creates and manages the courses (Bran, 2017) or gives permission for an LMS administrator at the organization to do so, without sharing any access to the source code. This means that users cannot make any personal adjustments to the software because the LMS company controls its structure as well as the activities within their system (Wright, Lopes, Montgomerie, Reju, & Schomoller, 2014).

Furthermore, proprietary LMS solutions can either be installed or adopt a SaaS or cloud-based approach. Given that cloud-based LMS will be discussed in a separate section of this chapter, we will cover installed LMS in this part. An installed LMS is a software hosted on an organization’s local server (Pappas, 2017). After purchasing an LMS from a vendor and obtaining its license for a determined time, the organization’s internal IT team is usually in charge of installing and maintaining the LMS in-house (Johnston, 2015). This maintenance also includes making any additional upgrades and solving any technical issues within the LMS internally. Although it seems like a time-consuming and costly endeavor to an organization, this option can provide more customization, controlling and storing of data locally as well as compatibility with third-party applications (Pappas, 2017). Some drawbacks with this option involve the scalability of the LMS, which falls under the responsibility of the organization’s IT team organization. These considerations need to be analyzed and assessed by the organization’s team before deciding on an installed approach. If selecting this option, an organization should have an IT team in place to administer, provide support, customize the LMS as well as manage any other technical needs.

There are many proprietary LMSs available in the market. Some examples can be found in the Table 1 below:

Table 1

A List of Examples of Proprietary LMS

Defining Open-Source LMS

Now, imagine that you want to share with others the amazing recipe you created. In fact, you want others to modify and create new versions of that recipe and share it with other people. Well, that means you are following an open source model. Open-source LMS allows anyone to have access to the source code, so they can make modifications or enhance the software. Overall, many LMSs are open source as they initially emerged as a university project instead of a business model (Croitoru & Dinu, 2016). In essence, open-source involves a community of users who collaborate with the focus “on teaching and pedagogy on top of the technical proper functioning of the system” (Bran, 2017). Collaborators of the open-source have to accept the license terms when they access the software, and generally, it grants users permission to modify, use, study and distribute the software (Opensource, 1999; Wright et al., 2014). According to the GNU General Public License, any individual or company can modify the open source code as long as they do not prevent others from further modifying the code either by charging them or licensing them (Pillai & Kevin, 2013). With that license requirement, there is a “copyleft” stipulation that requires anyone who made modifications to the software must share the source code of those changes (Opensource, 1999).

In summary, the nature of an open-source LMS is non-profit, as schools and organizations can use the software without paying any fee. An open-source software follows an “open” source model in which the source code is open to the public and can be “re-distributed for free provided credit is given to the original manufacturer” (Pillai & Kevin, 2013, p. 4). Going back to our cooking analogy, you can think of the open source code as a generic recipe that is shared to the public by a cooker. People can take this recipe and customize it by making modifications or adding ingredients for dietary needs. They can share the recipe with their modifications to the public as long as they do not prevent others from modifying the recipe further or charge them for using it. Additionally, the recipe should give credit to the original creator. The same goes for the open-source LMS. For example, the developer(s) of the LMS software create and allow other users to modify or add to their software source code. Users can make personal adjustments to the software and redistribute to other users as long as they do not profit from it or prevent others from making modifications. Giving credit to the original creators of the source code is also a common practice. Some drawbacks with open-source LMS include the need to purchase servers to host the LMS platform as well as trained personnel and staff to operate, optimize and maintain the servers (Yupangco, 2018).

There are many open-source LMSs available in the market. Some examples can be found in the Table below:

Table 2

A List of Examples of Open-Source LMS

Defining Cloud-based LMS

Cloud-based LMS is a true gumbo because there are many cooks in the kitchen when making this type of LMS. Each cook has the ability to use an array of different cloud-based tools and software they believe will enhance their instruction, and consequently the learning process (Wright, Lopes, Montgomerie, Reju, & Schomoller, 2014). A more formal definition of cloud-based software proposes a model to enable convenient and on-demand network access to “a shared pool of configurable computing resources (e.g., networks, servers, storage, applications, and services) that can be rapidly provisioned and released with minimal management effort or service provider interaction” (Mell & Grance, 2011). In other words, cloud-based LMS provides a service to organizations that allow them to access the LMS “on-demand without investing a lot in setting up the IT infrastructure” (Lal, 2015).

A cloud-based LMS focuses on the teachers and pedagogy practices like in an open-source model; however, it also provides a direct focus on the learners (Bran, 2017).

What does it mean? It means that this type of LMS follows socio-constructivist premises in supporting a “collaborative learning environment for individual and collective learning through interactive learning activities” (Kumar & Sharma, 2016, n.d.). Although a cloud-based LMS is hosted on the web under a vendor, it allows learners to access it from anywhere and on any device (Dufresne, 2017). That is, users can access this type of LMS from any mobile technology (e.g., computers, smartphone, tablets, etc.) independent of their location as long as they have access to the internet. Cloud-based LMSs are often a low-cost solution for organizations because there is no need to invest in sufficient/heavy IT infrastructure. Thus, this type of solution is more appropriate for small and medium-size organizations (Dobre, 2015). This solution also allows instructional designers to upload courses, learning paths and implementation of an array of web-based tools. Students have the ability to use web-based tools that they may be familiar with as a result of social networking or workplace use.

Although many cloud-based LMSs can be free for users, there are some that charge a fee according to the usage (i.e., pay-per-user or pay-per-use) or a regular license fee. In a pay-per-user model, the LMS vendor can charge an organization in the following manner: (a) for each user that is actually registered to use the software, or (b) for each user that logins and uses the software. Conversely, in the pay-per-use approach, a charge fee is made everytime that the organization uses (i.e., the definition of use in this context will vary according to the vendor) the LMS (Simpson, 2017). Overall, cloud-based LMS involves “paying a fee to a 3rd party for the use of its software, computing power, and technical expertise instead of maintaining on your own” (Curran, 2011, n.d.). Interestingly, cloud-based services are not limited to proprietary software, some vendors also operate open source software as well (Curran, 2011). However, when using an open source LMS, the user only pays for the “cloud” uptime and support services. Some examples of cloud-based LMS can be found in the Table below:

Table 3

A List of Examples of Cloud-Based LMS

Comparing the types of LMS

When deciding which meal to cook, you probably weigh the strengths and weaknesses of the tools you have available in your kitchen. The purpose is to select optimal tools that will help your work, making it more efficient and effective. In the case of LMS, the goal is the same. You need to compare and contrast the LMSs available in the market before making a decision. Usually, people assess the LMS based on its features, flexibility, cost, and other important LMS functions. One way to start this process is by analyzing the main types of LMS before deciding the type that will meet your needs. For example, when selecting a proprietary LMS, customers might select this option because this type of LMS usually provides high support; however, the cost associated with this option might be a downside. A better comparison and contrast of each option can be found in the table below:

Table 4

Comparison of the Types of LMSs

Compents/Apps that Enhance LMS

Most LMSs include user management features such as user account and profiles, authentication as well as roles and permissions (Foreman, 2018). In addition to user management features, LMSs also include some general features that assist the operation of the platform such as: (a) content, in which instructional materials are upload or displayed for learners, (b) communication, in which instructors and learners interact via email, discussion, announcements, etc., (c) assessment, in which instructors can create assessment materials to learners such assignments or tests, and (d) administrative, in which instructors and students can manage the courses and even customize individual courses. Although those features are common in the LMSs, customers might want to add extra components and apps to enhance the online environment.

Adding a little extra seasoning to your LMS never hurts. Thus, there are a few free cloud tools that can be used to create a kind of personalized LMS. These tools work well with open-source and cloud-based LMS.

1. Facebook: a popular social media tool that could be integrated with the LMS for personalization such as common interests, hobbies, etc.
2. Google Drive: a cloud-based storage that could allow instructors and students to store and share large documents/files online.
3. Dropbox: another cloud-based storage that could allow instructors and students to store and share large documents/files online.
4. Skype: a video conferencing system that allows instructors and students to meet synchronously.
5. Flickr: an online photo management that allows instructors and students to use and share photos.
6. YouTube: a video streaming platform that allows instructors and students to share videos.
7. Camtasia: a video editing and production tool that can be used in video creation and sharing.

References