{"component": "definition", "props": {"groups": [{"size": 6, "snippet": "means the capability of the software to be understood, learned, used, and be attractive to the user.", "snippet_links": [{"key": "the-software", "type": "definition", "offset": [24, 36]}, {"key": "the-user", "type": "definition", "offset": [91, 99]}], "samples": [{"hash": "8mg2MXfPSvg", "uri": "https://legacy.winnipeg.ca/finance/findata/matmgt/documents/2020/628-2020/628-2020_Request_for_Proposal.pdf", "label": "legacy.winnipeg.ca", "score": 10.7467488022, "published": false}, {"hash": "c7ET9e8QRRu", "uri": "https://www.winnipeg.ca/finance/findata/matmgt/documents/2019/769-2019/769-2019_Request_for_Proposal.pdf", "label": "www.winnipeg.ca", "score": 8.0828199863, "published": false}], "hash": "c4e0846fdf8c82e3e675224532d61edb", "id": 1}, {"size": 5, "snippet": "means a change in the use of a property which would:", "snippet_links": [{"key": "a-change-in", "type": "definition", "offset": [6, 17]}], "samples": [{"hash": "elxNz54xrUB", "uri": "http://www.zorra.ca/Portals/8/Documents/ByLaws/FULL%20-%2054-20%20Adopt%20Site%20Plan%20By-law.pdf", "label": "www.zorra.ca", "score": 10.7823408624, "published": false}, {"hash": "6D93ljMT9bD", "uri": "http://www.zorra.ca/Portals/8/Documents/ByLaws/54-20%20Adopt%20Site%20Plan%20Control%20Guidelines.pdf", "label": "www.zorra.ca", "score": 10.325119781, "published": false}, {"hash": "7wDeXH85xpR", "uri": "https://www.norwich.ca/Portals/Norwich/Documents/By-law%2015-2012%20-%20revised-A.pdf?ver=2021-03-04-124602-637", "label": "www.norwich.ca", "score": 6.1170431211, "published": false}], "hash": "c124f92e77d2826b6ccbd837040113ed", "id": 2}, {"size": 3, "snippet": "means the degree to which software can be used by specified consumers to achieve quantified objectives with effectiveness, efficiency, and satisfaction in a quantified context of use;", "snippet_links": [{"key": "specified-consumers", "type": "definition", "offset": [50, 69]}], "samples": [{"hash": "JGXqj4bej2", "uri": "https://legacy.winnipeg.ca/finance/findata/matmgt/documents/2016/859-2016/859-2016_Request_for_Qualification.pdf", "label": "legacy.winnipeg.ca", "score": 11.7980835044, "published": false}, {"hash": "k1DVmNPCUcV", "uri": "https://winnipeg.ca/finance/findata/matmgt/documents/2016/205-2016/205-2016_Request_for_Qualification.pdf", "label": "winnipeg.ca", "score": 10.8959616701, "published": false}, {"hash": "4bMhqwAhfH1", "uri": "https://winnipeg.ca/finance/findata/matmgt/documents/2018/820-2018/820-2018_Request_for_Proposal.pdf", "label": "winnipeg.ca", "score": 9.3696098563, "published": false}], "hash": "d29054b9eb683e7a93d4b46f800c5c3f", "id": 3}, {"size": 1, "snippet": "the ability to navigate and use content in an intuitive way, as content architectures are standardized through industry- or community-based metadata models and taxonomies; \u2022 Reusability: the flexibility to reuse content objects for multiple purposes, in different applications, in different products, via varying access devices, for numerous markets; \u2022 ?Durability: the ability to transcend technology (platforms, tools, access devices, products, vendors) changes or evolution without costly redesign, reconfiguration, redevelopment or recoding. \u2022 ?Information currency: the possibility for customers to get the latest, most up to date information, since the use of standard makes it easier and more economical to revise and update content in real-time (without having to republish the entire collection). From this point of view it\u2019s almost impossible, and actually a non sense, to talk about best practices in dealing with learning objects without taking into account the standard issue and in particular LOM and SCORM. This issue, as a matter of fact, seems to be crucial from a double perspective: \u2022 In the eLearning environment nowadays a best practice can\u2019t avoid facing with standards which grants interoperability and scalability of LOs, therefore, being LOM and SCORM the most updated and internationally widespread standards, we could mean as best practices in dealing with LOs experiences that are LOM or SCORM compliant. \u2022 LOM and SCORM (that is LOM based as far as metadata are concerned) allow to highlight the core features of a learning object being it a real learning object (and not just a piece of digital educational content), as the metadata they require focus on pedagogical, structural, technical but also legal (copyright) and economical aspects of a LOs based eLearning system.", "snippet_links": [{"key": "ability-to", "type": "clause", "offset": [4, 14]}, {"key": "multiple-purposes", "type": "definition", "offset": [232, 249]}, {"key": "access-devices", "type": "definition", "offset": [313, 327]}, {"key": "for-customers", "type": "clause", "offset": [587, 600]}, {"key": "up-to-date", "type": "definition", "offset": [625, 635]}, {"key": "a-non", "type": "clause", "offset": [867, 872]}, {"key": "best-practices", "type": "definition", "offset": [894, 908]}, {"key": "dealing-with", "type": "clause", "offset": [912, 924]}, {"key": "standard-issue", "type": "clause", "offset": [974, 988]}, {"key": "in-particular", "type": "clause", "offset": [993, 1006]}, {"key": "core-features", "type": "definition", "offset": [1525, 1538]}, {"key": "learning-object", "type": "definition", "offset": [1544, 1559]}, {"key": "educational-content", "type": "definition", "offset": [1625, 1644]}], "samples": [{"hash": "gQnxvkMw91q", "uri": "http://www.esode.com/downloadable%20files/ORMEE%20Project/best_practices_in%20learning%20objects.pdf", "label": "www.esode.com", "score": 4.0, "published": false}], "hash": "4c0a6aa66671f9774e3b0ad987716f0f", "id": 4}, {"size": 1, "snippet": "is the extent to which specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use [ISO/IEC 1998] can use a product", "snippet_links": [], "samples": [{"hash": "4h5OzlSpo0V", "uri": "/contracts/4h5OzlSpo0V#usability", "label": "Grant Agreement", "score": 29.3626232622, "published": true}], "hash": "18b50920e916f3f6c6268c28d4d68e68", "id": 5}, {"size": 1, "snippet": "means the extent to which a business record can be located, retrieved, presented and interpreted.", "snippet_links": [{"key": "business-record", "type": "definition", "offset": [28, 43]}], "samples": [{"hash": "8rj74wQ5pFR", "uri": "http://healthcareathome.ca/central/en/who/Documents/BOD%20LHIN%202016%2003%2029%20Package.pdf", "label": "healthcareathome.ca", "score": 5.1006160164, "published": false}], "hash": "76fe2d8f7986ab967236e074df9417f4", "id": 6}, {"size": 1, "snippet": "means the availability of the service in the production environment at the access point of the public data network and as agreed in this Agreement.", "snippet_links": [{"key": "availability-of-the-service", "type": "clause", "offset": [10, 37]}, {"key": "production-environment", "type": "definition", "offset": [45, 67]}, {"key": "access-point", "type": "clause", "offset": [75, 87]}, {"key": "data-network", "type": "definition", "offset": [102, 114]}, {"key": "as-agreed", "type": "clause", "offset": [119, 128]}, {"key": "in-this-agreement", "type": "definition", "offset": [129, 146]}], "samples": [{"hash": "ciEkLdKIR8K", "uri": "/contracts/ciEkLdKIR8K#usability", "label": "Terms and Conditions", "score": 31.0778982585, "published": true}], "hash": "bbdc5bdb4ca45119c8fd40cfd0c762c9", "id": 7}, {"size": 1, "snippet": "easy to use both for the information provider and the receiver, high flexibility of design and content structure.", "snippet_links": [{"key": "information-provider", "type": "definition", "offset": [25, 45]}], "samples": [{"hash": "lLBvn44UGjL", "uri": "/contracts/lLBvn44UGjL#usability", "label": "Grant Agreement", "score": 29.7251799509, "published": true}], "hash": "fd4106410d7b10634727e28a97595528", "id": 8}, {"size": 1, "snippet": "refers to the quality of the user\u2019s experience when interacting with the Audio Newspaper Program, including the user\u2019s ability to navigate the program and all its features.", "snippet_links": [{"key": "the-user", "type": "definition", "offset": [25, 33]}, {"key": "ability-to", "type": "clause", "offset": [119, 129]}, {"key": "the-program", "type": "clause", "offset": [139, 150]}], "samples": [{"hash": "8KsxJynVr3C", "uri": "/contracts/8KsxJynVr3C#usability", "label": "Contract", "score": 27.3312799452, "published": true}], "hash": "84e55f1bc4c79c6be1408602da34e000", "id": 9}, {"size": 1, "snippet": "characteristic related with user experience and easiness for a worker to access the dataspace through different tools. \uf0b7 New data space: improvement of the traditional personal dataspace, moving towards a complete dematerialization on centralized cloud services. \uf0b7 Communication service provider: availability of large and long bandwidth. Within this environment, sensing the context of a user becomes important in order to adapt the enabling technologies\u2019 usability [72]. The Context helps to define which data of the personal dataspace a user can access, in a specific place: to protect identity, privacy or to respect some security policies. Nowadays, in order to verify users\u2019 identity (and decide whether to grant access or not) machines collect personal data from users accessing to services. Users want to use those services and therefore are willing to reveal personal data, following a data-for-(free) services logic. At the same time, humans\u2019 identity, trust and privacy constraints are not the same for every environment (business identity, cultural identity, administrative identity etc.). From a technological point of view, it is a digital ecosystem: a community of people who interact, exchange information, combine, evolve in terms of knowledge, skills and contacts, in order to improve their lives and meet their needs. Among cloud services the concept of federated cloud is emerging, where there are common standards for both hardware and software companies. An important issue emerging from this scenario is the change in trust chains that are growing in number and are influenced by logical and physical contexts. In this kind of environment, the essence of cybercrime is to abuse the trust chains to steal assets. Hence, changes in trust models and importance of assets implies changes in cybercrime. Starting from assertions made so far, going further into detail and based on different studies on the topic, it is easy to speculate on the trend of workforces\u2019 evolution in terms of cybersecurity. According to a McAfee Labs' five-year look ahead [95], the predictions on how the types of threat actors will change and how the industry will meet these challenges over the next five years could be briefly summarized as follows: \uf0b7 Below-the-OS attacks: applications and operating systems are hardened against conventional attacks so attackers could look for weaknesses in firmware and hardware. The consequence could be a broad control performed by the attackers.", "snippet_links": [{"key": "user-experience", "type": "clause", "offset": [28, 43]}, {"key": "new-data", "type": "definition", "offset": [121, 129]}, {"key": "cloud-services", "type": "clause", "offset": [247, 261]}, {"key": "communication-service-provider", "type": "definition", "offset": [265, 295]}, {"key": "availability-of", "type": "clause", "offset": [297, 312]}, {"key": "the-context", "type": "clause", "offset": [372, 383]}, {"key": "in-order-to", "type": "clause", "offset": [412, 423]}, {"key": "enabling-technologies", "type": "clause", "offset": [434, 455]}, {"key": "the-personal", "type": "clause", "offset": [515, 527]}, {"key": "security-policies", "type": "definition", "offset": [626, 643]}, {"key": "to-verify", "type": "definition", "offset": [664, 673]}, {"key": "to-grant-access", "type": "clause", "offset": [710, 725]}, {"key": "personal-data", "type": "definition", "offset": [751, 764]}, {"key": "to-services", "type": "clause", "offset": [786, 797]}, {"key": "services-and", "type": "clause", "offset": [823, 835]}, {"key": "cultural-identity", "type": "definition", "offset": [1052, 1069]}, {"key": "a-community", "type": "clause", "offset": [1165, 1176]}, {"key": "exchange-information", "type": "definition", "offset": [1201, 1221]}, {"key": "terms-of", "type": "clause", "offset": [1242, 1250]}, {"key": "the-concept", "type": "clause", "offset": [1358, 1369]}, {"key": "hardware-and-software", "type": "clause", "offset": [1444, 1465]}, {"key": "in-trust", "type": "definition", "offset": [1538, 1546]}, {"key": "the-trust", "type": "clause", "offset": [1701, 1710]}, {"key": "changes-in", "type": "definition", "offset": [1742, 1752]}, {"key": "based-on", "type": "clause", "offset": [1890, 1898]}, {"key": "according-to", "type": "definition", "offset": [2020, 2032]}, {"key": "types-of", "type": "clause", "offset": [2102, 2110]}, {"key": "five-years", "type": "definition", "offset": [2199, 2209]}, {"key": "operating-systems", "type": "clause", "offset": [2291, 2308]}, {"key": "performed-by", "type": "clause", "offset": [2457, 2469]}], "samples": [{"hash": "b9HCC1euWZm", "uri": "/contracts/b9HCC1euWZm#usability", "label": "Work Package", "score": 23.0417522245, "published": true}], "hash": "5bce97407c53f8e06cea3c256703899f", "id": 10}], "next_curs": "ClYSUGoVc35sYXdpbnNpZGVyY29udHJhY3RzcjILEhpEZWZpbml0aW9uU25pcHBldEdyb3VwX3Y1NiISdXNhYmlsaXR5IzAwMDAwMDBhDKIBAmVuGAAgAA==", "definition": {"size": 25, "title": "Usability", "snippet": "means the capability of the software to be understood, learned, used, and be attractive to the user.", "id": "usability", "examples": ["<strong>Usability</strong> data includes information such as dashboard items clicked in the Tower Software, amount of time spent on individual pages and paths taken throughout the Tower Software.", "<strong>Usability</strong> data is collected and transmitted to Red Hat via a javascript file that is downloaded to a customer\u2019s web-browser.", "The purpose of a <strong>Usability</strong> Study is to test and study the <strong>usability</strong> of one or more pre-release products being developed by Qubit which Qubit may agree to make available to Customer for such purposes (together the \u201cTest Products\u201d).", "<strong>Usability</strong> data is collected and transmitted to Red Hat via a javascript file that is downloaded to a customer\u2019s web- browser.", "Creates such artifacts as <strong>Usability</strong> Testing Plan, Testing Scripts, and <strong>Usability</strong> Testing Report.", "In compliance with Texas Administrative Code, Title 1, Part 10, Chapters 206 and 213 (related to Accessibility and <strong>Usability</strong> of State Web Sites), the digital copy of the FINAL REPORT must comply with the requirements and standards specified in statute.", "<strong>Usability</strong> shall be specifically addressed for the two small open spaces in the town home area (550 sf and 700 sf), one small open space in the cottage area (1,300 sf) and the one small open space adjacent to the alley 1,310 sf).", "<strong>Usability</strong> testing to evaluate the man-machine interface and the web browser interface.", "Der im Rahmen des <strong>Usability</strong> Improvement Program generierte Bericht enth\u00e4lt im Allgemeinen Informationen \u00fcber: die Konfiguration, beispielsweise die Anzahl der Prozessoren in Ihrem Computer, die Anzahl der von Ihnen genutzten Netzwerkanschl\u00fcsse, das derzeit auf Ihrem Computer installierte Betriebssystem und die Bildschirmaufl\u00f6sung Ihrer Anzeigeger\u00e4te.", "This privacy statement explains the data collection and use practices for the ABB <strong>Usability</strong> Improvement Program that will be sent to ABB if you participate in the program."], "related": [["permeability", "Permeability", "Permeability"], ["durability", "durability", "durability"], ["repeatability", "Repeatability", "Repeatability"], ["interoperability", "Interoperability", "Interoperability"], ["compatibility", "Compatibility", "Compatibility"]], "related_snippets": [], "updated": "2025-07-06T21:58:36+00:00"}, "json": true, "cursor": ""}}