Module 3 Lesson 2-6 GE 4 Living in The IT Era

You might also like

Download as docx, pdf, or txt
Download as docx, pdf, or txt
You are on page 1of 7

Republic of the Philippines

NORTHERN ILOILO POLYTECHNIC STATE COLLEGE


AJUY CAMPUS
Ajuy, Iloilo

1|Page GE 4 – LIVING IN THE INFORMATION


TECHNOLOGY ERA
Republic of the Philippines
NORTHERN ILOILO POLYTECHNIC STATE COLLEGE
AJUY CAMPUS
Ajuy, Iloilo

Course Title: LIVING IN


THE IT ERA
Course Description: This course takes one aspect of the debate concerning
the new Economic-innovation in the form of the
introduction of information and communication
technologies and places it in the historical context of
industrial revolutions. 

Credit hours: 3 hours


Pre-Requisite: NONE
Program Objectives: The BSEd graduates are expected to become globally
Competent, innovative and socially and ethically
responsible computing professionals engaged in life-long
learning endeavors. They are capable of contributing to
the country’s national development goals.

Dear Learners,
 
Our courseware is specially designed to equip you with the necessary
knowledge and skills so you can navigate the terrain of present technology. Consider
this module as a guide to strengthening human productivity and a tool for exploring
the twenty-first century.
 
This will be use throughout the semester. This will serve your medium in
teaching-learning process wherein you will be assessed each lesson how much you
have learned from the subject matter. You are required to submit this module at the
end of this semester or else you are mark incomplete.

MODULE 5 SOCIAL, ETHICAL, LEGAL &


PROFESSIONAL ISSUES IN COMPUTING
LESSON 1 Different licenses
LESSON 2 Intellectual property code of the Philippines
LESSON 3 Data privacy act of 2012
LESSON 4 Cyber bullying
LESSON 5 Fake news

2|Page GE 4 – LIVING IN THE INFORMATION


TECHNOLOGY ERA
Republic of the Philippines
NORTHERN ILOILO POLYTECHNIC STATE COLLEGE
AJUY CAMPUS
Ajuy, Iloilo

Lesson 1: Different Licenses


There are many different types of software licenses, and the penalties for license
noncompliance can be harsh. If you reuse a component without following the obligations
of its license, the licensor might sue, and you might be forced to publish your own
source code. To protect your code and your organization, you need to understand these
software licenses before using any code, including libraries and frameworks, you didn’t
write yourself. See our list of the top open source licenses and their potential legal risks.

What are the different types of software licenses?


Here are five types of common software license models you should know about. Four
are examples of open source licenses (which allow you to reuse code to some extent),
and one disallows any reuse whatsoever.

1. Public domain. This is the most permissive type of software license. When
software is in the public domain, anyone can modify and use the software without
any restrictions. But you should always make sure it’s secure before adding it to
your own codebase. Warning: Code that doesn’t have an explicit license is NOT
automatically in the public domain. This includes code snippets you find on the
internet.

2. Permissive. Permissive licenses are also known as “Apache style” or “BSD


style.” They contain minimal requirements about how the software can be
modified or redistributed. This type of software license is perhaps the most
popular license used with free and open source software. Aside from the Apache
License and the BSD License, another common variant is the MIT License.

3. LGPL. The GNU Lesser General Public License allows you to link to open
source libraries in your software. If you simply compile or link an LGPL-licensed
library with your own code, you can release your application under any license
you want, even a proprietary license. But if you modify the library or copy parts of
it into your code, you’ll have to release your application under similar terms as
the LGPL.

4. Copyleft. Copyleft licenses are also known as reciprocal licenses or restrictive


licenses. The most well-known example of a copyleft or reciprocal license is the
GPL. These licenses allow you to modify the licensed code and distribute new
3|Page GE 4 – LIVING IN THE INFORMATION
TECHNOLOGY ERA
Republic of the Philippines
NORTHERN ILOILO POLYTECHNIC STATE COLLEGE
AJUY CAMPUS
Ajuy, Iloilo

works based on it,


as long as you distribute any new works or adaptations under the same software
license. For example, a component’s license might say the work is free to use
and distribute for personal use only. So any derivative you create would also be
limited to personal use only. (A derivative is any new software you develop that
contains the component.)

The catch here is that the users of your software would also have the right to
modify the code. Therefore, you’d have to make your own source code available.
But of course, exposing your source code may not be in your best interests.

5. Proprietary. Of all types of software licenses, this is the most restrictive. The
idea behind it is that all rights are reserved. It’s generally used for proprietary
software where the work may not be modified or redistributed.

Online Source: https://www.synopsys.com/blogs/software-security/5-types-of-


software-licenses-you-need-to-understand/

Common Software License Types and Terms


Common License Types
Appliance: A license covering use of a specific piece of hardware, such as a hub,
router, or PBX. Terms and conditions vary between vendors.
User: A license that provides access to the software to a specific number of users. All
installations of the software will be counted but installations across multiple devices for
the same user will be counted as one license consumption.
Concurrent User: A license which provides wider access to the software but limits the
number of simultaneous users using the software. It may or may not include compliance
enforcement capabilities. Typically, a concurrent license is “checked out” from the
license server when the software is run, assuming a license is available. If no license is
available, the requester experiences a denial of service.
Named User: A license that allows access to the software by a specific number of
named users. In some cases, these licenses can be transferred from one user to
another. When you create the license, you should allocate the license to specific users.
Only installations associated with allocated users are counted. For example, if the
license is allocated to users Sam and Jan, the maximum installation count is two. Any
other installations of the licensed application are treated as unassigned installations. For
example, if May has also installed the licensed application but has not been allocated to
the license, her installation will not be shown against installations of this license.
4|Page GE 4 – LIVING IN THE INFORMATION
TECHNOLOGY ERA
Republic of the Philippines
NORTHERN ILOILO POLYTECHNIC STATE COLLEGE
AJUY CAMPUS
Ajuy, Iloilo

Enterprise: A license to
install software an unlimited number of times within the enterprise. An Enterprise
Agreement, such as the Microsoft EA, is defined separately to this in FlexNet Manager
Suite (FNMS). An Enterprise Agreement is structured as ‘all you can eat’ but the
organization must be licensed for a specific quantity of licenses so this is not strictly an
‘Enterprise License’ model in its pure form.

Evaluation: A license that allows one or more users to install and use software for trial
purposes. Evaluation licenses may be time limited, may offer limited functionality, or
may restrict or mark output (for example, some PDF writing software includes the name
of the software on every PDF document produced from a trial version). After evaluation,
a user may purchase a full license, uninstall the software, or (for time-limited trials) the
software will simply no longer work.
Node Locked: A license that allows access to the software on a specific number of
named computers. These licenses are usually for server applications such as database
or VMware products. In some cases, these licenses can be transferred from one
computer to another, usually by requesting a new license key.
OEM: A license for software that is delivered with the hardware and is only for use on
that piece of hardware. These licenses are tied to the lifecycle of the hardware and
typically cannot be transferred to other hardware.
Processor (per Processor/CPU): A license based on the number of CPU/Processor
sockets on which the software will run, and NOT the logical processors aka cores.
Client Server: A server license that is based on a device metric. In many cases this
type of license may also have a Client Access License (or CAL) aspect. In a Server/CAL
model a license must be purchased for the physical server (or virtual server – there are
varying rules around virtualisation) and also additional ‘access’ licenses must be
purchased for any users/devices that may access the server for that application.
Run-Time: A license that provides access rights to third party software embedded in
an application. The use of the runtime license is limited to the application through which
it has been acquired.
Site: A license to install software on an unlimited number of computers at one physical
location.
Device (most common metric): A license for a defined number of software
installations. The software may be uninstalled on one computer and installed on any
other computer within the same enterprise, so long as the total number of installations
does not exceed the number of purchased licenses.

5|Page GE 4 – LIVING IN THE INFORMATION


TECHNOLOGY ERA
Republic of the Philippines
NORTHERN ILOILO POLYTECHNIC STATE COLLEGE
AJUY CAMPUS
Ajuy, Iloilo

Core/Processor points: A
license based on points applied as a multiplier to the number of Cores/Processors in the
physical server, or in some cases, the virtual machine. Some vendors count Processor
sockets and others count logical processors, or cores, but the license model is similar.
For example an application installed on a 4 processor server with 100 points per
processor would require a purchase of 400 processor points to cover the license
liability. These licenses are mainly used for Datacenter software licensing such as IBM.

Common Software Asset Management (SAM) Terms


Installations: The number of raw software installations without product use rights or
license metrics applied.
Entitlement: The number of purchased licenses available combined with any
contractual or product use rights.

Consumed: The actual license liability (not to be confused with ‘Installs’), consumption
is the install count applied against the entitlement.
Compliant: If the number of licenses consumed is less than or equal to the number of
licenses purchased.
Breach: If the number of licenses consumed is more than the number of licenses
purchased.
Delta: The difference between the number of licenses consumed and the number
purchased (for example 10 licenses purchased and 14 consumed would mean a delta
of 4).

Common Software Licensing Questions


How many types of software licenses are there?
There are many types of software licenses, with each creating a different
relationship between the software supplier and end user. For example, while a
Concurrent License provides wider access to a software but limits the number of
simultaneous users using the software, a Node-locked License allows access to a
software on a specific number of named computers. For a full list, visit our post on
Software License Types.
How do you control software licenses?

6|Page GE 4 – LIVING IN THE INFORMATION


TECHNOLOGY ERA
Republic of the Philippines
NORTHERN ILOILO POLYTECHNIC STATE COLLEGE
AJUY CAMPUS
Ajuy, Iloilo

Within a strong
software licensing framework, suppliers can add tamper-resistance to code, install
safeguards against unauthorized access to software, use secure activation
mechanisms, and react accordingly to any detected hacking or overuse. In this way,
those administering the licenses are able to monitor customer compliance and ensure
that the software is being used properly and in a manner which benefits both parties.
What is software license key?
A software license key is a combination of numbers and/or letters that authorizes
the use of software. This unique code is used to verify a purchaser’s right to install a
software and makes it available for use, if that license key has not already been used.

Online Source: https://www.revenera.com/blog/software-monetization/common-


software-license-types-and-terms/

7|Page GE 4 – LIVING IN THE INFORMATION


TECHNOLOGY ERA

You might also like