Enterprise Architecture Executive Handbook - U.S. Coast Guard
Enterprise Architecture Executive Handbook - U.S. Coast Guard
Enterprise Architecture Executive Handbook - U.S. Coast Guard
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Measurement Indicator: The specific measures,<br />
(e.g., number and/or percentage of customers<br />
satisfied) tailored for a specific Business<br />
Reference Model (BRM) LOB or subfunction,<br />
agency, program, or IT initiative<br />
(OMB, 2007). An example of a measurement<br />
indicator for the USCG mission area of<br />
“Safety” is the “Percent of all mariners in<br />
imminent danger rescued.”<br />
Model: Mid-level information products that<br />
graphically map the connections between<br />
elements in the CGEA to show relationships<br />
between processes, entities, and the<br />
information they exchange.<br />
Operational Controls: The security controls<br />
(i.e., safeguards or countermeasures) for an<br />
information system that primarily are<br />
implemented and executed by people (as<br />
opposed to systems) (NIST, 2006).<br />
Performance Perspective: Provides information<br />
about the measurement of USCG strategic<br />
and business outcomes. This includes<br />
information from the U.S. USCG Posture<br />
Statement (2009 Budget in Brief) and the<br />
OMB Performance Assessment Rating Tool<br />
(PART).<br />
Performance Targets: Performance measures<br />
with targets and time frames. For example, in<br />
FY 2007 the performance target for the<br />
“Ports, waterways, and coastal security”<br />
mission area was to reduce maritime<br />
terrorism risk by 15 percent.<br />
Product Manager (PM): The Product Manager<br />
is responsible for updating the CGEA with<br />
revisions resulting from DRs.<br />
Product: Includes hardware, the physical part of<br />
a computer system, and software, the<br />
programs or other instructions that computer<br />
needs to perform specific tasks (Harvard<br />
University, 2002).<br />
Profile: High-level, strategic view of CGEA<br />
information for the executive decisionmaker.<br />
As the satellite view of CGEA,<br />
profiles use graphic visualization to show<br />
complex information in a condensed format.<br />
117<br />
PSB: The PSB supports the EAB by reviewing<br />
DRs for C4&IT products and standards.<br />
After reviewing each DR for potential<br />
impact on <strong>Coast</strong> <strong>Guard</strong> mission execution<br />
and the CGEA, the PSB provides their<br />
findings and recommendations to the EAB.<br />
Program: An organizational unit within an<br />
agency with responsibility for delivering on<br />
a clearly defined mission or service area.<br />
Scope of a program may be determined by<br />
legislation, executive order, or by<br />
organizational structure of the agency to<br />
achieve its mission (OMB, 2005). Major<br />
programs at the USCG include Rescue 21,<br />
Command 21, Deepwater and NAIS.<br />
Security Perspective: Describes how the USCG<br />
assures the confidentiality, integrity,<br />
availability, and privacy of USCG<br />
information. NIST standards are an example<br />
of the type of information managed in this<br />
perspective.<br />
Segment <strong>Architecture</strong>: Focuses on business<br />
outcomes of an individual LOB and defines a<br />
simple roadmap for a core mission area,<br />
business service, or enterprise service.<br />
Sensors: Systems that sense, detect, and collect<br />
data.<br />
Service Access and Delivery: The collection of<br />
Access and Delivery Channels used to<br />
leverage the Service Component, and the<br />
legislative requirements governing its use<br />
and interaction.<br />
Service Interface and Integration: The<br />
discovery, interaction, and communication<br />
technologies joining disparate systems and<br />
information providers. SOAs leverage and<br />
incorporate Service Interface and Integration<br />
standards to provide interoperability and<br />
scalability.<br />
Service Oriented <strong>Architecture</strong>: A paradigm<br />
for organizing and utilizing distributed<br />
capabilities that may be under the control of<br />
different ownership domains. It provides a<br />
uniform means to offer, discover, interact<br />
with and use capabilities to produce desired<br />
effects consistent with measurable<br />
preconditions and expectations (OASIS,<br />
2005).