Software licensing security is a two-pronged approach – to firstly, ensuring
that users remain in compliance with developer license agreements and
secondly, to implementing anti-piracy measures. The common goal, is to
maximize profits and minimize losses from the sale of developed
application/s.
Draw a UML class diagram that models the aspects of software licensing
security solutions which are described below:
_________________________________________________________
1http://sourceforge.net/projects/pdfcreator
(a) Every development using software licensing security begins with the
purchase of a licensing development kit.
(b) With each purchase, the developer is handed over a unique Qual Code
(Batch Qualification Code) and a corresponding hashed vendor key.
(c) The Qual code is used to authenticate with different protection keys (of
different applications from the same developer) and differentiate vendor
keys from those of other software developers.
(d) The Qual Code contains five alphanumeric characters that represent the
developer’s unique vendor code.
(e) A feature is an identifiable functionality of a developed application.
(f) Features can offer implicit (e.g. identify .exe files, software modules,
extension and plug-ins, etc.) or explicit (e.g. file format conversion, print,
save, etc.) functionalities.
(g) Individual features can be locked and / or unlocked using generated
protection keys from both Qual code and vendor key.
(h) Each protected software product has some features and is associated
with a Qual Code.
(i) The protection key is generated from a unique feature id and name
combination.
(j) Each software product can be further categorized according to the level
of entitlement/s it gives to its user through a specific locking type
mechanism (using a combination of protection keys).
(k) For example, a software base product can contain all the product
attributes such as features, licensing data and memory, and can be used
as a product offered for sale.
(l) A provisional product can be