EtGov

Process for Identifying Emerging Technology Components    (53B)

See http://xml.gov/draft/etLifeCycle.htm    (53C)

Stage 1.Identification    (53D)

Stage 2.Subscription    (53E)

Stage 3.Stewardship    (53F)

Stage 4.Graduation    (53G)

Stage 5.Budgeting    (53H)

Stage 6.Acquisition    (53I)

Stage 7.Maintenance    (53J)

Stage 8.Retirement/Replacement    (53K)

Stage 1.Identification    (53L)

• (1) ComponentNameType    (53M)
  • What is the short name of the proposed component? One of the challenges is to translate between the traditional focus on projects, products, and systems versus the new emphasis on components. Presumably, at some point in the ET process a successfully proposed component will become a 'project' in the context of Exhibit 300 and the A-11 budget process. This element would be indexed on the et.gov site and displayed in the first column of the default view, in alphabetical order. Its length should be constrained to provide for reasonable display on the et.gov site.    (53N)

• (2) WebAddressType    (53O)
  • Where on the Web can the XML instance document for this proposed component be accessed for indexing? In the first stage of the process, all the 'contact' information that may needed is the URL for the XML instance document to be validated against this schema. Other contact information would be optional in Stage 1 but would be specified in Stage 2 - to facilitate the formation of communities of interest through Subscription. The URL would be implicitly indexed on the et.gov site as a link on ComponentNameType.    (53P)

• (3) ComponentDescriptionType    (53Q)
  • How will this component improve efficiency or effectiveness in relation to other technical alternatives? In the first stage of the process, this element would be used to indicate what is new and better about the proposed ET component - technically speaking - in relation to alternatives. Economic analyses would occur later in the process. This data would not be indexed on the et.gov site but would be required to be available in the XML instance document at the specified URL. (Invalid documents would not be indexed.).    (53R)

• (4) ComponentBenefitType    (53S)
  • How will this component improve efficiency or effectiveness in relation to other technical alternatives? In the first stage of the process, this element would be used to indicate what is new and better about the proposed ET component - technically speaking - in relation to alternatives. Economic analyses would occur later in the process. This data would not be indexed on the et.gov site but would be required to be available in the XML instance document at the specified URL. (Invalid documents would not be indexed.).    (53T)

• (5) TechnicalStandardType    (53U)
  • Select the appropriate standard or standards that are implemented in this component. This element would reference the the FEA TRM for a controlled vocabulary of technical standards. It would not be displayed in the listing of proposed components on the et.gov site but would be used to enable selective listings of the names and brief descriptions of the components. Since more than one element of the TRM may be applicable to any proposed component, this element of the schema should be repeatable. Since ET may not yet implement any recognized standard, an 'Other' or 'To Be Determined' option should also be provided, along with an enumerated listing of the standards identified in the TRM. Conformance with any standard would not be a requirement during the early stages of the process but probably will be required in subsequent stages, prior to Acquisition, in order to facilitate interoperability.    (53V)

• (6) ServiceTypeType    (53W)
  • Select the type of service identified in the Service Component Reference Model that best categorizes the function served by this component. This element would reference the FEA SRM for a controlled vocabulary of service types. Like the TechnicalStandards element, it would be also be used to enable selective listings of the proposed ET components but would not be displayed in the listing of those components. It may be appropriate to limit each proposal to a single reference to an element of the SRM, on the theory that a single 'component' cannot perform more than one 'service'.    (53X)

• (7) DataDomainType    (53Y)
  • If this proposed component uses a particular type of data or a particular data model, please cite it. This element will eventually reference the FEA DRM as a controlled vocabulary. However, since the DRM has not been specified yet, it may be appropriate to enable reference to any data model or data type that may be applicable. Initially, this element would not be indexed or displayed on the et.gov site. However, as soon as the DRM is specified, it should be used to enable selective listings of the proposed components. In addition, steps should be taken to consider data models that may be identified in the ET process but not already included in the DRM.    (53Z)

• (8) ComponentTypeType    (540)
  • Select the type of component being proposed. The controlled vocabulary for this element would be: hardware, software, or data. It would not be displayed in the component listing but would be used to provide selective listings of the proposed components. The assumption is that a component can be composed of only one 'type' and that any proposal encompassing more than one type comprises multiple logically separable components, each of which should be registered separately.    (541)