GEIA EIA-836A-2007 Configuration Management Data Exchange and Interoperability For GEIA Subscription Customers Only To Obtain your Complimentary Copy Contact IHS at 1-800-854-7179.pdf

1、 GEIA STANDARD EIA-836A Configuration Management Data Exchange and Interoperability EIA-836A March 2007 GOVERNMENT ELECTRONICS AND INFORMATION TECHNOLOGY ASSOCIATION A Sector of the Electronic Industries Alliance Copyright Government Electronics Version 1.2 has the changes accepted. Unlike Version 1

2、.0, where the Business Objects were located within the reference schema, the Business Objects in the interim versions 1.1 and 1.2 consist of individual schemas that relate to a Program or Project, a Product or an Instance of a Product. The elements used in the Business Objects are defined in the Ref

3、erence Schema, whis is linked to and accessible from each of the business objects. An XML schema language conversion of the Reference Schema DTD is included and is an exact equivalent. Jan 2004 A This revision provides significant technical changes: the data model was restructured using a discipline

4、d modeling language; the data model/data dictionary is now independent of implementation conventions; as opposed to separate Business Objects in the prior releases, CM objects that may be the subject of data exchange are now an integral part of the model; a method of constructing exchange messages i

5、ncorporating any model object is provided. Mar 2007 Copyright Government Electronics a complete vehicle;or a software program.InstanceA language that is used to systematically structure the Data Dictionary. (See Annex)Modeling LanguageA correlation of a specific XML vocabulary with a uniform resourc

6、e identifier (URI).NamespaceA class of things that exist in the real world such as: Engineering Drawing, Standard or Person.Real ObjectAn XML Schema representation of the Data Dictionary. (See Reference Schema 359)Reference SchemaAn item that is named and defined in the Data Dictionary.TermAn organi

7、zation (external or internal) with whom business is conducted and with whom config-uration management or other related data may be exchanged. Aliases: Acquirer, Supplier, Oper-ator, Maintainer, Customer, Buyer, End-User.Trading Partner5EIA-836Copyright Government Electronics a unique ten digit numbe

8、rISBNInformation Security MarkingISMInternational Organization for StandardizationISOInternational Organization for Standardization Request for CommentsISO RFCMilitary HandbookMIL-HDBKMilitary StandardMIL-STDMultipurpose Internet Mail ExtensionMIMENetBios Extended User InterfaceNetBEUI9EIA-836Copyri

9、ght Government Electronics e.g. documents, facilities, firmware, hardware, materials, processes, services, software, systems.” For the purposes ofthis standard, products are the things that are being configuration managed. This standard is written generically tocover all products, but this revision

10、primarily covers hardware and software. Information for firmware and systemsare included in the hardware area. Facilities are addressed, but only in the most basic way and only in support ofhardware and software for operational purposes. It is expected that future revisions of this standard will exp

11、and on thedetailed elements and properties needed to fully support the exchange of configuration management data about facilities,publications, and other products.Products (both hardware and software) exist first as a design, then as actual instances of the ProductDesign .5.1.1.1.1. HardwareIn Hardw

12、are, the design is called HardwareDesign and covers all information necessary to describe the design of ahardware product (assemblies, subassemblies, and piece parts) and its properties. It also includes the requirements forand results of testing, qualification, and certification, and information ne

13、cessary for the operation, maintenance,modification, and disposal of hardware instances. The hardware design provides for the identification of embeddedsoftware. It provides the current design information for the developer, acquirer, and user. It is the baseline for productionand procurement, and th

14、e basis for all proposed design changes.A Hardware instance is called a HardwareUnit . The HardwareUnit is uniquely identified to differentiate it fromall other like pieces of that product. The information captured about the HardwareUnit begins with the “as-built”configuration describing the actual

15、configuration as manufactured, into what higher assembly it was placed, and changesthat were authorized to the design as it was being built. Information captured about the HardwareUnit and changesto its configuration continues throughout its lifecycle, including maintenance, modifications, and dispo

16、sal.5.1.1.1.2. SoftwareIn Software, the design of an executable program that satisfies a requirement is called a SoftwareItem and coversall information necessary to describe the actual design of the software and its properties. It also includes its developmentand target environments, requirements fo

17、r and results of testing, qualification, and certification and information necessaryfor operation and support.The structure of a SoftwareItem includes SoftwareComponents and SoftwareUnits . The structure of Software-Components include other SoftwareComponents and SoftwareUnits . A SoftwareUnit is th

18、e lowest level ofsoftware that is a separately compilable piece of code.In general, a Software Design is compiled as a master (otherwise known as a Build) from which replicas are made anddistributed. The information captured about the SoftwareItemBuild includes requirements for and results of compil

19、ing11EIA-836Copyright Government Electronics but are terms not dir-ectly related to Configuration Management, butare necessary for data exchange. No suitablenamespace XML schema for these terms wasfound when this standard was published.Otherother13EIA-836Copyright Government Electronics 0/&RUH&RPSRQ

20、HQWV7HFKQLFDO6SHFLILFDWLRQ&XUUHQF WSH FRGHXVH RSWLRQDOGHIDXOW 86FRGHOLVWQDPH SUP,62&XUUHQF HILQLWLRQ7HW $QRSWLRQDOYDOXHIURPDFDWHJRULDWLRQRIZRUOGZLGHPRQHWDUVVWHPV,IQR&XUUHQFLVJLYHQ 86 LVDVVXPHGWREHWKH&XUUHQF.HILQLWLRQ6RXUFH (,$5HIHUHQFHV,627(VWLPDWLRQ WSH ERROHDQXVH RSWLRQDOGHIDXOW IDOVH HILQLWLRQ7HW

21、 $QRSWLRQDOLQGLFDWLRQRIZKHWKHUWKHDPRXQWLVDQHVWLPDWHRUQRW,IQRLQGLFDWLRQLVJLYHQLWLVDVVXPHGWKDWWKHDPRXQWLVQRWDQHVWLPDWHHILQLWLRQ6RXUFH (,$LQGHILQLQJDWDWSH3DUWRU2EMHFW1DPHFP5HTXHVW)RU&KDQJH&RVW6DYLQJ,PSDFW DWDWSH FP5HTXHVW)RU9DULDQFH&RVW6DYLQJV,PSDFW DWDWSH &RVW6DYLQJ&RVW6DYLQJVFigure 5.8. Primary Datat

22、ype Example in the Data Dictionary19EIA-836Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-20EIA-836Copyright Government Electronics & Information Technology Association Provided by IHS under license with GEIA Not for ResaleNo reproduction or networking permitted without license from IHS-,-,-