﻿<?xml version="1.0" encoding="utf-8"?>
<etgov:EmergingTechnology xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:etgov="www.cio.gov/AIC/ETgov/">
  <etgov:ComponentDetails>
    <etgov:ComponentName>Business Process Modeling Notation</etgov:ComponentName>
    <etgov:XMLGenerationDate>2006-08-10</etgov:XMLGenerationDate>
    <etgov:ComponentType>Data</etgov:ComponentType>
    <etgov:ComponentDescription>Business Process Modeling Notation (BPMN) is a graphical notation that depicts the steps in a business process. BPMN depicts the end to end flow of a business process. The notation has been specifically designed to coordinate the sequence of processes and the messages that flow between different process participants in a related set of activities.</etgov:ComponentDescription>
    <etgov:GovernmentBenefits>The primary goal of BPMN is to provide a notation that is readily understandable by all business users, from the business analysts that create the initial drafts of the processes, to the technical developers responsible for implementing the technology that will perform those processes, and finally, to the business people who will manage and monitor those processes. Thus, BPMN creates a standardized bridge for the gap between the business process design and process implementation. Currently, there are scores of process modeling tools and methodologies. BPMN will also advance the capabilities of traditional business process notations by inherently handling B2B business process concepts, such as public and private processes and choreographies, as well as advanced modeling concepts, such as exception handling and transaction compensation.</etgov:GovernmentBenefits>
    <etgov:Categorizations>
      <etgov:Categorization etgov:categorizationScheme="FEA">
        <etgov:ServiceReferenceModelInformation>
          <etgov:ServiceType>Visualization</etgov:ServiceType>
        </etgov:ServiceReferenceModelInformation>
        <etgov:TechnicalReferenceModelInformation>
          <etgov:ServiceArea>Service Platform and Infrastructure</etgov:ServiceArea>
          <etgov:ServiceCategory>Software Engineering</etgov:ServiceCategory>
          <etgov:ServiceStandard>Modeling</etgov:ServiceStandard>
          <etgov:ProposedSpecification>BPMN</etgov:ProposedSpecification>
        </etgov:TechnicalReferenceModelInformation>
        <etgov:TechnicalReferenceModelInformation>
          <etgov:ServiceArea>Service Interface and Integration</etgov:ServiceArea>
          <etgov:ServiceCategory>Interoperability</etgov:ServiceCategory>
          <etgov:ServiceStandard>Data Format / Classification</etgov:ServiceStandard>
          <etgov:ServiceSpecification>eXtensible Markup Language (XML)</etgov:ServiceSpecification>
        </etgov:TechnicalReferenceModelInformation>
      </etgov:Categorization>
    </etgov:Categorizations>
  </etgov:ComponentDetails>
  <etgov:OrganizationAndRepresentativeDetails>
    <etgov:OrganizationDetails>
      <etgov:OrganizationName>Interior Enterprise Architecture</etgov:OrganizationName>
      <etgov:WebAddress>http://www.doi.gov/ocio/architecture/index.html</etgov:WebAddress>
      <etgov:OfficeDetails>
        <etgov:TelephoneNumber etgov:telephoneNumberType="Phone" />
        <etgov:OfficeAddressDetails>
          <etgov:StreetName />
          <etgov:City />
          <etgov:PostalCode />
        </etgov:OfficeAddressDetails>
      </etgov:OfficeDetails>
    </etgov:OrganizationDetails>
    <etgov:RepresentativeDetails>
      <etgov:FirstName>Diane</etgov:FirstName>
      <etgov:MiddleInitial />
      <etgov:LastName>Reeves</etgov:LastName>
      <etgov:ElectronicMailAddress />
      <etgov:RepresentativeAddressDetails>
        <etgov:StreetName />
        <etgov:City />
        <etgov:PostalCode />
      </etgov:RepresentativeAddressDetails>
    </etgov:RepresentativeDetails>
  </etgov:OrganizationAndRepresentativeDetails>
</etgov:EmergingTechnology>