iTeh StandardsiTeh Standards
EURUSD
Your shopping cart is empty.
ISO

ISO/IEC 19513:2017

(Main)

Information technology — Object Management Group Unified Profile for DoDAF and MODAF (UPDM), 2.1.1

Information technology — Object Management Group Unified Profile for DoDAF and MODAF (UPDM), 2.1.1

This International Standard provides a specification language, UPDM, that is readily understandable not only by the community of architects of information technology systems but also by a wide range of end users including executives and enterprise management that sponsor such systems, program managers that oversee their development, developers of supporting hardware and software (design, implementation, and testing), subject matter experts, and end users. UPDM bridges the gap from setting of requirements to high level system design and to visualization for practitioners. While designed in the context of military organizations and their procurement processes, UPDM can also be applied in entirely civilian industrial and service organization contexts. UPDM 2.1.1 supports the capability to: ? model architectures for a broad range of complex systems, which may include hardware, software, data, personnel, and facility elements; ? model consistent architectures for system-of-systems down to lower levels of design and implementation; ? model service oriented architectures; ? support the analysis, specification, design, and verification of complex systems; and ? improve the ability to exchange architecture information among related tools that are UML based and tools that are based on other standards. The profile provides the modeling of operational capabilities, services, system activities, nodes, system functions, ports, protocols, interfaces, performance, and physical properties and units of measure. In addition, the profile enables the modeling of related architecture concepts such as DoD's doctrine, organization, training material, leadership & education, personnel, and facilities (DOTMLPF) and the equivalent UK Ministry of Defence Lines of Development (DLOD) elements. UPDM 2.1.1, as illustrated in Figure 1.1, addresses DoDAF and MODAF Viewpoints as well as enabling extensions to new architecture perspectives (e.g., Services views, Custom views, Logistics views cost views, etc.). MODAF terminology has been used for simplicity.

Technologies de l'information — Profil unifié pour DoDAF et MODAF (UPDM) de l'OMG, 2.1.1

General Information

Status
Published
Publication Date
09-Nov-2017
ICS
35.080 - Software
Technical Committee
ISO/IEC JTC 1 - Information technology
Drafting Committee
ISO/IEC JTC 1 - Information technology
Current Stage
9060 - Close of review
Start Date
03-Jun-2028
Ref Project

Buy Standard

ISO/IEC 19513:2017 - Information technology -- Object Management Group Unified Profile for DoDAF and MODAF (UPDM), 2.1.1ISO/IEC 19513:2017 - Information technology -- Object Management Group Unified Profile for DoDAF and MODAF (UPDM), 2.1.1
PreviousNext
Standard
ISO/IEC 19513:2017 - Information technology -- Object Management Group Unified Profile for DoDAF and MODAF (UPDM), 2.1.1
English language
415 pages
sale 15% off
Preview
sale 15% off
Preview

Standards Content (Sample)

INTERNATIONAL ISO/IEC
STANDARD 19513
First edition
2017-10
Information technology — Object
Management Group Unified Profile for
DoDAF and MODAF (UPDM), 2.1.1
Technologies de l'information — Profil unifié pour DoDAF et MODAF
(UPDM) de l'OMG, 2.1.1
Reference number
ISO/IEC 19513:2017(E)
©
ISO/IEC 2017

---------------------- Page: 1 ----------------------
ISO/IEC 19513:2017(E)

COPYRIGHT PROTECTED DOCUMENT
© ISO/IEC 2017, Published in Switzerland
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized otherwise in any form
or by any means, electronic or mechanical, including photocopying, or posting on the internet or an intranet, without prior
written permission. Permission can be requested from either ISO at the address below or ISO’s member body in the country of
the requester.
ISO copyright office
Ch. de Blandonnet 8 • CP 401
CH-1214 Vernier, Geneva, Switzerland
Tel. +41 22 749 01 11
Fax +41 22 749 09 47
copyright@iso.org
www.iso.org
ii © ISO/IEC 2017 – All rights reserved

---------------------- Page: 2 ----------------------
ISO/IEC 19513:2017(E)
Table of Contents
Foreword . x
Introduction .xi
1 Scope . 3
2 Compliance . 4
2.1 Compliance Levels .4
2.1.1 Level 0 : Based on UML 2 and Partial SoaML Import . 6
2.1.2 Level 1 : Based on UML 2 and Full SysML Import . 7
2.2 Compliance to DoDAF 2.0.2 .7
3 Normative References . 7
3.1 Overview .7
3.2 References .7
4 Terms and Definitions . 8
5 Symbols and Acronyms . 8
6 Additional Information . 9
6.1 Additional Materials .9
6.2 Overview of this International Standard .10
6.2.1 Intended Audience . 10
6.2.2 Organization . 10
7 Language Architecture . 13
7.1 Introduction .13
7.2 Philosophy .13
7.3 Core Principles .13
7.4 Representing Stereotype Constraints .14
7.5 UML Constraint Representation .18
7.6 Important Areas of the Architecture .18
7.6.1 Aliases .18
7.6.2 SoaML Reuse in L0 . 19
7.6.3 SysML Reuse in L1 . 19
7.6.4 SOPES Reuse in L1 . 19
8 UPDM Profile . 21
8.1 Introduction .21
8.2 DoDAF Class Library .21
iii
© ISO/IEC 2017 – All rights reserved

---------------------- Page: 3 ----------------------
ISO/IEC 19513:2017(E)
8.2.1 ClassificationType . 22
8.2.2 CommunicationsLinkProperties . 22
8.2.3 DataElementProperties . 22
8.2.4 ExchangeProperties . 22
8.2.5 InformationAssuranceProperties . 22
8.2.6 InformationElementProperties . 22
8.2.7 OperationalActivityProperties . 23
8.2.8 SecurityAttributes . 23
8.3 UPDM L1 .23
8.3.1 UPDM L1::UPDM L0 . 28
8.3.1.1 UPDM L1::UPDM L0::Core . 28
8.3.1.1.1 UPDM L1::UPDM L0::Core::AcquisitionElements .28
8.3.1.1.1.1 UPDM L1::UPDM L0::Core::AcquisitionElements::Milestone .28
8.3.1.1.1.1.1 ActualProject .28
8.3.1.1.1.1.2 ActualProjectMilestoneRole .30
8.3.1.1.1.1.3 OrganizationalProjectRelationship .30
8.3.1.1.1.1.4 ProjectMilestoneRole .31
8.3.1.1.1.1.5 ProjectType .32
8.3.1.1.2 UPDM L1::UPDM L0::Core::AllElements .33
8.3.1.1.2.1 Exchange .34
8.3.1.1.2.2 UPDMElement .34
8.3.1.1.2.3 UPDM L1::UPDM L0::Core::AllElements::Behavior .35
8.3.1.1.2.3.1 Activity .35
8.3.1.1.2.3.2 CapableElement .36
8.3.1.1.2.3.3 Implements .37
8.3.1.1.2.3.4 IsCapableOfPerforming .38
8.3.1.1.2.4 UPDM L1::UPDM L0::Core::AllElements::Environment .39
8.3.1.1.2.4.1 ActualLocation .39
8.3.1.1.2.4.2 ConditionType .41
8.3.1.1.2.4.3 Environment .41
8.3.1.1.2.4.4 EnvironmentProperty .42
8.3.1.1.2.4.5 LocationHolder .43
8.3.1.1.2.4.6 LocationKind .44
8.3.1.1.2.4.7 LocationType .45
8.3.1.1.2.4.8 LocationTypeKind .46
8.3.1.1.2.5 UPDM L1::UPDM L0::Core::AllElements::Measurements .46
8.3.1.1.2.5.1 ActualMeasurement .46
8.3.1.1.2.5.2 ActualProperty .47
8.3.1.1.2.5.3 ActualPropertySet .49
8.3.1.1.2.5.4 ActualPropertySetKind .50
8.3.1.1.2.5.5 Measurement .50
8.3.1.1.2.5.6 MeasurementSet .51
8.3.1.1.2.5.7 Property .52
8.3.1.1.2.5.8 PropertySet .52
8.3.1.1.2.6 UPDM L1::UPDM L0::Core::AllElements::Structure .53
8.3.1.1.2.6.1 ExchangeElement .53
8.3.1.1.2.6.2 ExchangeElementKind .55
8.3.1.1.2.6.3 Participant .55
8.3.1.1.2.6.4 Resource .56
8.3.1.1.2.6.5 Rule .56
8.3.1.1.2.6.6 RuleKind .57
8.3.1.1.2.7 UPDM L1::UPDM L0::Core::AllElements::Views .58
8.3.1.1.2.7.1 ArchitecturalDescription .58
8.3.1.1.2.7.2 ArchitecturalReference .60
iv
© ISO/IEC 2017 – All rights reserved

---------------------- Page: 4 ----------------------
ISO/IEC 19513:2017(E)
8.3.1.1.2.7.3 ArchitectureFrameworkKind .60
8.3.1.1.2.7.4 ArchitectureMetadata .61
8.3.1.1.2.7.5 Metadata .61
8.3.1.1.2.7.6 View .62
8.3.1.1.2.7.7 Viewpoint .63
8.3.1.1.3 UPDM L1::UPDM L0::Core::ExternalTypes .64
8.3.1.1.3.1 ISO8601DateTime .64
8.3.1.1.4 UPDM L1::UPDM L0::Core::OperationalElements .65
8.3.1.1.4.1 UPDM L1::UPDM L0::Core::OperationalElements::Behavior .65
8.3.1.1.4.1.1 NodeOperation .65
8.3.1.1.4.1.2 OperationalActivity .66
8.3.1.1.4.1.3 OperationalActivityAction .68
8.3.1.1.4.1.4 OperationalActivityEdge .69
8.3.1.1.4.1.5 OperationalEventTrace .70
8.3.1.1.4.1.6 OperationalMessage .71
8.3.1.1.4.1.7 OperationalParameter .72
8.3.1.1.4.1.8 OperationalState .72
8.3.1.1.4.1.9 OperationalStateDescription .73
8.3.1.1.4.1.10 SubjectOfOperationalStateMachine .74
8.3.1.1.4.2 UPDM L1::UPDM L0::Core::OperationalElements::Data .75
8.3.1.1.4.2.1 LogicalDataModel .75
8.3.1.1.4.3 UPDM L1::UPDM L0::Core::OperationalElements::Flows .75
8.3.1.1.4.3.1 Command .75
8.3.1.1.4.3.2 OperationalExchange .76
8.3.1.1.4.3.3 OperationalExchangeItem .78
8.3.1.1.4.3.4 OperationalExchangeKind .79
8.3.1.1.4.4 UPDM L1::UPDM L0::Core::OperationalElements::Structure .80
8.3.1.1.4.4.1 ArbitraryConnector .80
8.3.1.1.4.4.2 Competence .81
8.3.1.1.4.4.3 ConceptItem .81
8.3.1.1.4.4.4 ConceptRole .82
8.3.1.1.4.4.5 HighLevelOperationalConcept .83
8.3.1.1.4.4.6 KnownResource .84
8.3.1.1.4.4.7 LogicalArchitecture .85
8.3.1.1.4.4.8 Specializations .86
8.3.1.1.4.4.9 Mission .86
8.3.1.1.4.4.10 Needline .87
8.3.1.1.4.4.11 Node . 88
8.3.1.1.4.4.12 NodeParent .89
8.3.1.1.4.4.13 NodePort .90
8.3.1.1.4.4.14 NodeRole .91
8.3.1.1.4.4.15 OperationalConstraint .92
8.3.1.1.4.4.16 SecurityDomain .93
8.3.1.1.4.4.17 SubjectOfOperationalConstraint .93
8.3.1.1.4.4.18 UPDM L1::UPDM L0::Core::OperationalElements::
 Structure::Organizational .94
8.3.1.1.5 UPDM L1::UPDM L0::Core::ServiceElements .110
8.3.1.1.5.1 UPDM L1::UPDM L0::Core::ServiceElements::Behavior .110
8.3.1.1.5.1.1  ServiceFeature .110
8.3.1.1.5.1.2  ServiceFunction .111
8.3.1.1.5.1.3  ServiceFunctionAction .112
8.3.1.1.5.1.4  ServiceFunctionEdge .112
8.3.1.1.5.1.5  ServiceInteraction .113
8.3.1.1.5.1.6  ServiceMessage .114
8.3.1.1.5.1.7  ServiceMessageHandler .115
v
© ISO/IEC 2017 – All rights reserved

---------------------- Page: 5 ----------------------
ISO/IEC 19513:2017(E)
8.3.1.1.5.1.8  ServiceOperation .116
8.3.1.1.5.1.9  ServiceParameter . 117
8.3.1.1.5.1.10 ServiceStateMachine .118
8.3.1.1.5.2  UPDM L1::UPDM L0::Core::ServiceElements::Structure .119
8.3.1.1.5.2.1  AsynchronousMessage .119
8.3.1.1.5.2.2  Request .120
8.3.1.1.5.2.3  Service .121
8.3.1.1.5.2.4  ServiceAttribute .121
8.3.1.1.5.2.5  ServiceInterface .122
8.3.1.1.5.2.6  ServiceLevelValue .124
8.3.1.1.5.2.7  ServiceLevelValueSet .125
8.3.1.1.5.2.8  ServicePolicy .125
8.3.1.1.5.2.9  ServicePort .126
8.3.1.1.6  UPDM L1::UPDM L0::Core::StrategicElements .128
8.3.1.1.6.1  UPDM L1::UPDM L0::Core::StrategicElements::Structure .128
8.3.1.1.6.1.1  Capability .128
8.3.1.1.6.1.2  CapabilityProperty .129
8.3.1.1.6.1.3  DesiredState .130
8.3.1.1.6.1.4  Desirer .130
8.3.1.1.6.1.5  EnterpriseGoal .131
8.3.1.1.6.1.6  EnterprisePhase .132
8.3.1.1.6.1.7  EnterpriseVision .133
8.3.1.1.6.1.8  Exhibits .134
8.3.1.1.6.1.9  MapsToCapability .135
8.3.1.1.6.1.10  StructuralPart .136
8.3.1.1.6.1.11  TemporalPart .137
8.3.1.1.6.1.12  VisionStatement .137
8.3.1.1.7  UPDM L1::UPDM L0::Core::SystemsElements .138
8.3.1.1.7.1  UPDM L1::UPDM L0::Core::SystemsElements::Behavior .138
8.3.1.1.7.1.1  Function .138
8.3.1.1.7.1.2  FunctionAction .140
8.3.1.1.7.1.3  FunctionEdge .140
8.3.1.1.7.1.4  ResourceEventTrace .141
8.3.1.1.7.1.5  ResourceMessage .142
8.3.1.1.7.1.6  ResourceOperation .143
8.3.1.1.7.1.7  ResourceParameter .144
8.3.1.1.7.1.8  ResourceState .145
8.3.1.1.7.1.9  ResourceStateMachine .146
8.3.1.1.7.2  UPDM L1::UPDM L0::Core::SystemsElements::Data .147
8.3.1.1.7.2.1  DataModel .147
8.3.1.1.7.2.2  PhysicalDataModel .148
8.3.1.1.7.3  UPDM L1::UPDM L0::Core::SystemsElements::Flows .148
8.3.1.1.7.3.1  ResourceInteraction .148
8.3.1.1.7.3.2  ResourceInteractionItem .150
8.3.1.1.7.4  UPDM L1::UPDM L0::Core::SystemsElements::Structure .151
8.3.1.1.7.4.1  CapabilityConfiguration .151
8.3.1.1.7.4.2  FieldedCapability .151
8.3.1.1.7.4.3  Forecast .152
8.3.1.1.7.4.4  Materiel .153
8.3.1.1.7.4.5  PhysicalArchitecture .154
8.3.1.1.7.4.6  PhysicalResource .154
8.3.1.1.7.4.7  ResourceArtifact .155
8.3.1.1.7.4.8  ResourceConnector .156
8.3.1.1.7.4.9  ResourceConstraint .158
8.3.1.1.7.4.10  ResourceInterface .158
vi
© ISO/IEC 2017 – All rights reserved

---------------------- Page: 6 ----------------------
ISO/IEC 19513:2017(E)
8.3.1.1.7.4.11  ResourcePort .159
8.3.1.1.7.4.12  ResourceRole .160
8.3.1.1.7.4.13  RoleKind .162
8.3.1.1.7.4.14  Software .162
8.3.1.1.7.4.15  SubjectOfForecast .163
8.3.1.1.7.4.16  SubjectOfResourceConstraint .164
8.3.1.1.7.4.17  SystemResource .164
8.3.1.1.7.4.18  VersionOfConfiguration .166
8.3.1.1.7.4.19  WholeLifeConfiguration .167
8.3.1.1.8  UPDM L1::UPDM L0::Core::TechnicalStandardsElements .167
8.3.1.1.8.1  Protocol .168
8.3.1.1.8.2  ProtocolImplementation .168
8.3.1.1.8.3  Standard .169
8.3.1.1.8.4  StandardConfiguration .171
8.3.1.1.8.5  UPDM L1::UPDM L0::Core::TechnicalStandardsElements::Data .171
8.3.1.1.8.5.1  Details .171
8.3.1.1.8.5.2  EntityAttribute .172
8.3.1.1.8.5.3  EntityItem .173
8.3.1.1.8.5.4  EntityRelationship .174
8.3.1.2 UPDM L1::UPDM L0::DoDAF . 175
8.3.1.2.1  UPDM L1::UPDM L0::DoDAF::AcquisitionElements .175
8.3.1.2.1.1  ActivityPartOfProject .175
8.3.1.2.1.2  Project .176
8.3.1.2.1.3  ProjectActivity .177
8.3.1.2.1.4  ProjectActivityAction .178
8.3.1.2.1.5  ProjectActivityEdge .178
8.3.1.2.2  UPDM L1::UPDM L0::DoDAF::AllElements . 179
8.3.1.2.2.1  Information .179
8.3.1.2.2.2  InformationKind .180
8.3.1.2.2.3  UPDM L1::UPDM L0::DoDAF::AllElements::Behavior .181
8.3.1.2.2.3.1  ActivityPerformedByPerformer .181
8.3.1.2.2.4  UPDM L1::UPDM L0::DoDAF::AllElements::Environment .181
8.3.1.2.2.4.1  Condition .182
8.3.1.2.2.4.2  ConditionProperty .182
8.3.1.2.2.4.3  GeoPoliticalExtent .183
8.3.1.2.2.4.4  GeoPoliticalExtentKind .185
8.3.1.2.2.4.5  GeoPoliticalExtentType .185
8.3.1.2.2.4.6  GeoPoliticalExtentTypeKind .187
8.3.1.2.2.4.7  Location .187
8.3.1.2.2.5  UPDM L1::UPDM L0::DoDAF::AllElements::Measurements .187
8.3.1.2.2.5.1  Measure .188
8.3.1.2.2.5.2  MeasureType .188
8.3.1.2.3  UPDM L1::UPDM L0::DoDAF::OperationalElements .189
8.3.1.2.3.1  UPDM L1::UPDM L0::DoDAF::OperationalElements::Structure .189
8.3.1.2.3.1.1  Performer .189
8.3.1.2.3.1.2  UPDM L1::UPDM L0::DoDAF::OperationalElements::
Structure::Organizational .189
8.3.1.2.4  UPDM L1::UPDM L0::DoDAF::ServiceElements .192
8.3.1.2.4.1  ServiceAccess .192
8.3.1.2.4.2  ServiceDescription .193
8.3.1.2.5  UPDM L1::UPDM L0::DoDAF::StrategicElements .194
8.3.1.2.5.1  ActivityPartOfCapability .194
8.3.1.2.5.2  CapabilityOfPerformer .194
8.3.1.2.5.3  DesiredEffect .195
8.3.1.2.5.4  Vision .196
vii
© ISO/IEC 2017 – All rights reserved

---------------------- Page: 7 ----------------------
ISO/IEC 19513:2017(E)
8.3.1.2.6  UPDM L1::UPDM L0::DoDAF::SystemElements .196
8.3.1.2.6.1  UPDM L1::UPDM L0::DoDAF::SystemElements::Structure .197
8.3.1.2.6.1.1  System .197
8.3.1.2.7  UPDM L1::UPDM L0::DoDAF::TechnicalStandardsElements .197
8.3.1.2.7.1  FunctionalStandard .197
8.3.1.2.7.2  TechnicalStandard .198
8.3.1.2.7.3  UPDM L1::UPDM L0::DoDAF::TechnicalStandardsElements::Data .198
8.3.1.2.7.3.1  AssociationOfInformation .198
8.3.1.2.7.3.2  SecurityAttributesGroup .199
8.3.1.3 UPDM L1::UPDM L0::MODAF . 200
8.3.1.3.1  UPDM L1::UPDM L0::MODAF::AcquisitionElements .200
8.3.1.3.1.1  UPDM L1::UPDM L0::MODAF::AcquisitionElements::Milestones .200
8.3.1.3.1.1.1  ActualProjectMilestone .2
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.

This May Also Interest You

ISO
ISO/IEC 5962:2021(Main)
Information technology — SPDX® Specification V2.2.1

This Software Package Data Exchange® (SPDX®) specification defines a standard data format for communicating the component and metadata information associated with software packages. An SPDX document can be associated with a set of software packages, files or snippets and contains information about the software in the SPDX format described in this specification.

  • Standard
    145 pages
    English language
    sale 15% off
  • Draft
    145 pages
    English language
    sale 15% off
ISO
ISO/IEC 5055:2021(Main)
Information technology — Software measurement — Software quality measurement — Automated source code quality measures

The measures in this standard were calculated from detecting and counting violations of good architectural and coding practices in the source code that could result in unacceptable operational risks or excessive costs. Establishing standards for these measures at the source code level is important because they have been used in outsourcing and system development contracts without having international standards to reference. For instance, the ISO/IEC 25000 series of standards that govern software product quality provide only a small set of measures at the source code level. A primary objective of updating these measures was to extend their applicability to embedded software, which is especially important for the growing implementation of embedded devices and the Internet of Things. Functionality that has traditionally been implemented in IT applications is now being moved to embedded chips. Since the weaknesses included in the measures specified in this document have been found to be applicable to all forms of software, embedded software is not treated separately in this specification.

  • Standard
    235 pages
    English language
    sale 15% off
  • Draft
    235 pages
    English language
    sale 15% off
ISO
ISO/IEC 19515:2019(Main)
Information technology — Object Management Group Automated Function Points (AFP), 1.0

1.1 Purpose This International Standard defines a method for automating the counting of Function Points that is generally consistent with the Function Point Counting Practices Manual, Release 4.3.1 (IFPUG CPM) produced by the International Function Point Users Group (IFPUG). Guidelines in this International Standard may differ from those in the IFPUG CPM at points where subjective judgments have to be replaced by the rules needed for automation. The IFPUG CPM was selected as the anchor for this International Standard because it is the most widely used functional measurement specification with a large supporting infrastructure maintained by a professional organization. 1.2 Applicability This International Standard is applicable to the functional sizing of transaction-oriented software applications, and in particular those with data persistency. To be consistent with the IFPUG CPM, the International Standard provides details on the support of applications using relational databases. However, the International Standard can be used and extended for any type of transactional application with data persistency. 1.3 Limitations This International Standard does not address the sizing of enhancements to an application or maintained functionality (often called Enhancement Function Points). Extensions of the automated counting methods described in this International Standard such as Automated Enhancement Function Points will be addressed in future addendums to this International Standard. This International Standard does not address sizing for the non-functional components of a software application. Non-functional components (as defined by IFPUG) include: — Structural Quality Constraints Reliability, Security, Performance Efficiency, Maintainability, etc. — Organizational Constraints locations for operations, target hardware, compliance to standards, etc. — Environmental Constraints interoperability, security, privacy, safety, etc. — Implementation Constraints development language, delivery schedule, etc.

  • Standard
    28 pages
    English language
    sale 15% off
ISO
ISO/IEC 24570:2018(Main)
Software engineering — NESMA functional size measurement method — Definitions and counting guidelines for the application of function point analysis

ISO/IEC 24570:2018 specifies the set of definitions, rules and guidelines for applying the Nesma Function Point Analysis (FPA) method.

  • Standard
    70 pages
    English language
    sale 15% off
ISO
ISO/IEC 19678:2015(Main)
Information Technology — BIOS Protection Guidelines

ISO 19678:2015 provides requirements and guidelines for preventing the unauthorized modification of Basic Input/Output System (BIOS) firmware on PC client systems. Unauthorized modification of BIOS firmware by malicious software constitutes a significant threat because of the BIOS's unique and privileged position within the PC architecture. A malicious BIOS modification could be part of a sophisticated, targeted attack on an organization ?either a permanent denial of service (if the BIOS is corrupted) or a persistent malware presence (if the BIOS is implanted with malware). As used in this publication, the term BIOS refers to conventional BIOS, Extensible Firmware Interface (EFI) BIOS, and Unified Extensible Firmware Interface (UEFI) BIOS. This International Standard applies to system BIOS firmware (e.g., conventional BIOS or UEFI BIOS) stored in the system flash memory of computer systems, including portions that may be formatted as Option ROMs. However, it does not apply to Option ROMs, UEFI drivers, and firmware stored elsewhere in a computer system. Subclause 7.2 provides platform vendors with requirements for a secure BIOS update process. Additionally, subclause 7.3 provides guidelines for managing the BIOS in an operational environment. While this International Standard focuses on current and future x86 and x64 client platforms, the controls and procedures are independent of any particular system design.

  • Standard
    15 pages
    English language
    sale 15% off
ISO
ISO/IEC 40500:2012(Main)
Information technology — W3C Web Content Accessibility Guidelines (WCAG) 2.0

ISO/IEC 40500:2012 [Web Content Accessibility Guidelines (WCAG) 2.0] covers a wide range of recommendations for making Web content more accessible. Following these guidelines will make content accessible to a wider range of people with disabilities, including blindness and low vision, deafness and hearing loss, learning disabilities, cognitive limitations, limited movement, speech disabilities, photo-sensitivity and combinations of these. Following these guidelines will also often make your Web content more usable to users in general. WCAG 2.0 success criteria are written as testable statements that are not technology-specific. Guidance about satisfying the success criteria in specific technologies, as well as general information about interpreting the success criteria, is provided in separate documents. An overview of WCAG 2.0, the WCAG 2.0 standard, technical and education material supporting implementation of WCAG 2.0, and information on translating WCAG 2.0, are freely available from Web Content Accessibility Guidelines (WCAG) Overview.

  • Standard
    2 pages
    English language
    sale 15% off
ISO
ISO/IEC 17998:2012(Main)
Information technology — SOA Governance Framework

ISO/IEC 17998:2012 describes a framework that provides context and definitions to enable organizations to understand and deploy service-oriented architecture (SOA) governance. ISO/IEC 17998:2012 defines: SOA Governance, including its relationship between Business, IT, and EA governance; this assists organizations in understanding the impact that the introduction of SOA into an organization has on governance; an SOA Governance Reference Model (SGRM) and its constituent parts, which assists organizations in specifying their appropriate governance regimes; and capturing best practice as a basis for a common approach; the SOA Governance Vitality Method (SGVM) which assists organizations in customizing the SGRM and realizing their SOA Governance Regimen. ISO/IEC 17998:2012 is not intended to be used as provided; it is intended to be customized to create appropriate SOA governance for the organization. Many of the lists are non-normative and exemplary and intended to be filtered and as input to the customization process. ISO/IEC 17998:2012 does not include an explanation of the fundamentals and value of SOA, which is important for being able to understand and apply SOA governance. It lists some of the many other specifications and books that are available on SOA basics.

  • Standard
    87 pages
    English language
    sale 15% off
ISO
ISO/IEC 19500-3:2012(Main)
Information technology — Object Management Group — Common Object Request Broker Architecture (CORBA) — Part 3: Components

ISO/IEC 19500-3:2012 defines the syntax and semantics of a component model, based on CORBA IDL, and a corresponding meta-model, a language to describe the structure and state of component implementations, and a corresponding meta-model, a programming model for constructing component implementations, a runtime environment for component implementations, interaction between components and Enterprise Java Beans, meta-data for describing component-based applications, and interfaces for their deployment, and a lightweight subset of the component model, programming model and runtime environment.

  • Standard
    339 pages
    English language
    sale 15% off
ISO
ISO/IEC 19500-1:2012(Main)
Information technology — Object Management Group — Common Object Request Broker Architecture (CORBA) — Part 1: Interfaces

ISO/IEC 19500-1:2012 specifies the CORBA Object Model and uses concepts from that model to define the operation of the Object Request Broker (ORB). The ORB is the basic mechanism by which objects transparently make requests to, and receive responses from, each other on the same machine or across a network. A client need not be aware of the mechanisms used to communicate with or activate an object, how the object is implemented, or where the object is located.

  • Standard
    509 pages
    English language
    sale 15% off
  • Standard
    509 pages
    English language
    sale 15% off
ISO
ISO/IEC 19500-2:2012(Main)
Information technology — Object Management Group — Common Object Request Broker Architecture (CORBA) — Part 2: Interoperability

ISO/IEC 19500-2:2012 specifies a comprehensive, flexible approach to supporting networks of objects that are distributed across and managed by multiple, heterogeneous CORBA-compliant Object Request Brokers (ORBs). The approach to inter-ORB operation is universal, because elements can be combined in many ways to satisfy a very broad range of needs. ISO/IEC 19500-2:2012 specifies ORB interoperability architecture Inter-ORB bridge support General Inter-ORB Protocol (GIOP) for object request broker (ORB) interoperability. GIOP can be mapped onto any connection-oriented transport protocol that meets a minimal set of assumptions defined by this International Standard Internet Inter-ORB Protocol (IIOP), a specific mapping of the GIOP which runs directly over connections that use the Internet Protocol and the Transmission Control Protocol (TCP/IP connections) CORBA Security Attribute Service (SAS) protocol and its use within the CSIv2 architecture to address the requirements of CORBA security for interoperable authentication, delegation, and privileges ISO/IEC 19500-2:2012 provides a widely implemented and used particularization of ITU-T Rec. X.931 | ISO/IEC 14752. It supports interoperability and location transparency in ODP systems.

  • Standard
    226 pages
    English language
    sale 15% off