ISO19770-2 (ISO/IEC 19770-2) Software Asset Management Part 2: Software Identification Tag

ISO19770-2 (ISO/IEC 19770-2) Software Asset Management Part 2: Software Identification Tag

ISO/IEC 19770-2:2009 establishes specifications for tagging software to optimise its identification and management.

It will help you to manage your software assets more effectively, saving money through having defined asset management processes in place.


Quantity:  
Price: R 3 297,96 (ZAR) 
Ready to order
Sub Total: R 0,00 (ZAR)
CHECKOUT
 

Other payment options available

 

Order ISO/IEC 19770-2:2009, the second part to this essential standard for managing software as an asset - buy now!

ISO/IEC 19770-2:2009 establishes specifications for tagging software to optimise its identification and management. The software identification tag is an XML file containing authoritative identification and management information about a software product.

ISO/IEC 19770-2 supports software asset management processes as defined in ISO/IEC 19770-1. It is also designed to work together with the future ISO/IEC 19770-3 that will provide a standard for software entitlement tags.

Software identification tags will benefit all stakeholders involved in the creation, licensing, distribution, releasing, installation, and on-going management of software. Key benefits associated with software identification tags include:

  • The ability to consistently and authoritatively identify software products that need to be managed for any purpose. Such as for licensing, upgrading, packaging or for the specification of dependencies. Software identification tags provide the meta-data necessary to support more accurate identification which differentiates this approach from traditional file-oriented identification techniques.
  • The ability to identify groups or suites of software products in the same way as for individual software products. Enabling entire groups or suites of software products to be managed with the same flexibility as for individual products.
  • Facilitation of de-facto standardisation between different software creators, and within software creator organisations, of how different versions of software are identified. Allowing for better identification and management by software consumers of those different versions. For example, being able to distinguish between free-standing versions and versions which are components of suites, upgrade paths, etc.
  • Facilitation of automated approaches to licence compliance.
  • The ability to provide comprehensive information about the structural footprint of packages, i.e. the list of components such as files and system settings associated with that package. This is in order to link package-level management with file-level management.
  • The ability to provide information about how to identify if a particular software package is being actively used or not.
  • The ability to deal with the complexities of software installed on removable or shared storage, or in virtual environments (subject to the evolving ability of platforms and installers to identify devices and environments).
  • The ability to reflect within the software identification tag the identities and requirements of different entities, including:
    • Software creators,
    • Software licensors,
    • Packagers,
    • Distributors external to the software consumer,
    • Release managers within the software consumer,
    • And those responsible for installing and managing software on an on-going basis.
  • The ability to allow for the validation of any of this information. This is through the optional use of digital signatures by anyone creating or modifying information in the software identification tag.
  • The ability for entities besides the software creators (e.g. independent providers, or in-house personnel) to create software identification tags for legacy software. And also for software from software creators who do not provide software identification tags themselves.
  • The ability of this International Standard to evolve in informal and formal ways. As common approaches become accepted throughout industry for dealing with additional types of information not currently covered by this part of ISO/IEC 19770, such as for product activation.

Key Features and Benefits

  • Establishes specifications for tagging software to optimise its identification and management. Helping you to manage your software assets more effectively, saving money through having defined asset management processes in place.
  • Written in a generic manner, making the advice and guidance within the standard applicable no matter the size, type or location of your organisation.
  • Aids with the facilitation of automated approaches to licence compliance. The information in the tag will be able to be read by network auditing tools, allowing you to monitor where licences are being utilised. Saving you time over having to manually compile software asset logs.

Pages: 99
Format: Hardcopy
Availability: In Stock

Ensure your organisation's software assets are working as hard as possible, uitilise the advice and guidance in this standard - buy today!

Product Rating: (0.00)   # of Ratings: 0   (Only registered customers can rate)

There are no comments for this product.