<html xmlns:xlink="http://www.w3.org/1999/xlink"> <head> <META http-equiv="Content-Type" content="text/html; charset=UTF-16"> <link rel="stylesheet" type="text/css" href="../../reports/css/panel.css"> <title>DOI Glossary - Objects/Attributes - Linked</title><SCRIPT language="JavaScript"> window.onerror = handleError; function word() { var oWSHShell = new ActiveXObject("WScript.Shell"); oWSHShell.Run("winword " + window.location.href); } function excel() { var oWSHShell = new ActiveXObject("WScript.Shell"); oWSHShell.Run("excel " + window.location.href); } function save() { document.execCommand('SaveAs',true, 'report.htm'); } function printme() { window.print(); } function handleError() { alert ("DEAR BROWSER SECURITY SETTING (One-time change). \n\n You will need to change a setting on the client computer to accept the Active X Script. \n\n1, In your IE browser, go to Tools | Internet Options | Security | Custom Level. \n2, Scroll down until you see Initalizing and Scripting ActiveX controls that are not marked safe is disabled. \n3, Changed it from disabled to prompt. This will ask you page if you would like to run the script (that opens in word or excel)."); return true; } function comment() { document.location.href="mailto:NBCDEN_DEAR_DOI@ios.doi.gov\?subject\=DEAR Report:" + escape(document.title) + "&body\=Report: " + escape(window.location.href) + "%0D%0A(Comments on format, data, values, fields missing, etc. are all welcome)."; } function email() { document.location.href="mailto:\?subject\=DEAR Report:" + escape(document.title) +"&body\=" + "Link: " + escape(window.location.href) + " %0D%0A- Got DEAR Login? http://dear.nbc.gov/reports . %0D%0A---NOTE: To add report to email, Ctrl-V to paste.---"; bodyrange=document.body.createTextRange().execCommand('Copy'); } </SCRIPT></head> <body class="Main"> <P><P> <table border="0" width="100%" cellspacing="0" cellpadding="0"> <tr align="middle"> <td width="250" valign="bottom" height="40" rowspan="2" STYLE="COLOR: #003399; FONT-SIZE: 8pt; font-family: Tahoma, Verdana, Arial; padding: 4px; background-image: url(logosmall.gif); background-repeat: no-repeat; background-position: bottom left; margin: 0px; line-height: 30px; margin-bottom: 0pt; position: bottom;"> <a href="" onclick="history.go(-1); return false;">Go Back</a> | <a href="javascript:show(true);">Show</a> | <a href="javascript:show(false);">Hide</a> | <a href="javascript:CleanUp();">Reset</a> </td> <td colspan="4" align="right" height="15"> <font size="1"> Information is for official use only - <I>Last update&nbsp;<SCRIPT language=JavaScript> <!-- document.write(document.lastModified); // --> </SCRIPT></FONT></I></td> </tr> <tr valign="middle" align="right" height="23"> <td valign="top" align="left" class="header1" width="400" height="23"> <table cellpadding="0" cellspacing="0" border="0" valign="bottom" width="100%"> <tr class="header1"> <td valign="middle" align="left" class="header1" width="400" height="23"> &nbsp; DOI Glossary - Objects/Attributes - Linked</td> </tr> </table> </td> <td valign="top" align="right" class="header2" width="335" height="23"> <table cellpadding="0" cellspacing="0" border="0" align="right" valign="top"> <tr class="header2" valign="bottom"> <td height="23" align="left" valign="bottom"> &nbsp;<B>Export :</B>&nbsp;&nbsp;&nbsp; </td> <td class="xword" width="24" height="23" onclick='javascript:word();' alt="Word (DOC)"></td> <td class="xexcel" width="24" height="23" onclick='javascript:excel();' alt="Excel (XLS)"></td> <td class="xsep" width="9" height="23"></td> <td class="xprinter" width="28" height="23" onclick='javascript:printme();' alt="Print Friendly View"></td> <td class="xsave" width="24" height="23" onclick='javascript:save();' alt="Save Report"></td> <td class="xemail" width="24" height="23" onclick='javascript:email();' alt="Email Report"></td> <td class="xfeedback" width="75" height="23" onclick='javascript:comment();' alt="Send Comments"></td> <td class="xsep" width="9" height="23"></td> <td class="tab_rg" width="28" height="23"></td> <tr> </table> </td> </tr> </table> <table border="0" width="100%" cellpadding="0" cellspacing="0"> <tr width="100%" height="23"> <td width="66%" height="23" class="header1" align="left"> &nbsp; DOI Glossary - Objects/Attributes - Linked</td> <td width="34%" height="23" class="header2" align="right"> <table class="header2" cellpadding=0 cellspacing=0 border=0 width="100%"> <tr> <td align="left" valign="middle" class="header2" width="50%" height="23"> &nbsp;Count: 1456 </td> <td align="right" valign="middle" class="header2" width="50%" height="23"> <table class="header2" cellpadding=0 cellspacing=0 border=0 width="100%"> <tr> <td align="center" valign="middle" class="xsep" width="16" height="23"></td> <td align="center" valign="middle" class="chart" width="50" height="23" onclick="LoadGraph();" onMouseOver="this.className = 'show';showMessage('click to show<BR> or hide charts');" onMouseOut="this.className = 'chart'; hideMessage('');"></td> <td align="center" valign="middle" class="xsep" width="16" height="23"></td> <td align="center" valign="middle" class="matrix" width="50" height="23" title="click to show or hide matrix" onclick="GenerateForm('maindata');" onMouseOver="showMessage('click to show<BR> Matrix Report Creator');" onBlur="window.status='';return true"></td> <td align="center" valign="middle" class="xsep" width="16" height="23"></td> <td align="center" valign="middle" class="color" width="50" height="23" title="click to show row colors" onclick="alternate('maindata', true)" onMouseOver="window.status='click to turn on alternating color.';return true" onFocus="window.status='click to turn on alternating color.';return true" onMouseOut="window.status='';return true" onBlur="window.status='';return true"></td> <td align="left" valign="bottom" class="header2" width="20" height="23"><a href="javascript:void(0);" onclick="alternate('maindata', false)" onMouseOver="window.status='click to turn off alternating color.';return true" onFocus="window.status='click to turn off alternating color.';return true" onMouseOut="window.status='';return true" onBlur="window.status='';return true">Off</a></td> </tr> </table> </td> </tr> </table> </td> </tr> </table> <div id="DEARCharts"></div> <div id="matrix"></div> <div id="trace"></div> <font face="Arial" size="2"> <p> <h3><a name="##"></a></h3> <table border="1" cellpadding="0" cellspacing="0"> <tr> <th>Glossary Entity</th> <th>Description</th> <th>IsCoreData</th> <th>IsSecurityData</th> <th>IsSensitive</th> <th>Glossary Model Object Properties</th> </tr> <tr> <td><a href="#176631#">ABC-WORK-ACTIVITY</a></td> <td>The Activity-Based Costing Item that describes an activity that can have work tied to it to measure effort against. Short name to describe the activity usually containing 3-10 words Needs to be renamed to ABC Work Activity per change by the DOI ABC Team.</td> <td>T</td> <td>F</td> <td>F</td> <td>"cost drivers" description "doi program area contact(s)" "doi program area contacts" "doi sub process code" "doi sub process name" "example notes" "full name" "function activities" inputs name organization outcomes output "program area" "system interfaces" "unit of measure" </td> </tr> <tr> <td><a href="#176658#">AGREEMENT</a></td> <td>AN ARRANGEMENT BETWEEN PARTIES.</td> <td>T</td> <td>F</td> <td>F</td> <td>"AGREEMENT ABBREVIATED NAME" "AGREEMENT CATEGORY CODE" "AGREEMENT DESCRIPTION TEXT" "AGREEMENT DURATION TYPE CODE" "AGREEMENT EFFECTIVE CALENDAR DATE" "AGREEMENT EXPIRATION CALENDAR DATE" "AGREEMENT IDENTIFIER" "AGREEMENT NAME" "AGREEMENT TEXT" "AGREEMENT TYPE CODE" "AGREEMENT USE CATEGORY CODE" "AGREEMENT VERSION IDENTIFIER" </td> </tr> <tr> <td><a href="#176659#">AGREEMENT-ASSOCIATION</a></td> <td>AN ASSOCIATION BETWEEN AN AGREEMENT AND ANOTHER AGREEMENT.</td> <td>T</td> <td>F</td> <td>F</td> <td>"AGREEMENT-ASSOCIATION IDENTIFIER" "AGREEMENT-ASSOCIATION REASON CODE" </td> </tr> <tr> <td><a href="#176757#">ARCHITECTURAL-PATTERN</a></td> <td>Symbol used on the System Interface decomposition to represent a pattern overlay for networks.</td> <td>T</td> <td>F</td> <td>F</td> <td>"anti pattern" "child patterns" name </td> </tr> <tr> <td><a href="#176661#">ARCHITECTURE-PROJECT-ANALYSIS-RESULT</a></td> <td>THE ASSOCIATION BETWEEN A SPECIFIC ARCHITECTURE-PROJECT AND A SPECIFIC ARCHITECTURE-ANALYSIS-PROCESS-RESULT.</td> <td>T</td> <td>F</td> <td>F</td> <td>"ACTION-DOCUMENT IDENTIFIER" "Analysis Process ACTION IDENTIFIER" "ARCHITECTURE IDENTIFIER" "ARCHITECTURE-ANALYSIS-PROCESS-RESULT IDENTIFIER" "ARCHITECTURE-PROJECT IDENTIFIER" "Project ACTION IDENTIFIER" "Project DOCUMENT IDENTIFIER" </td> </tr> <tr> <td><a href="#176863#">BEST-PRACTICE</a></td> <td>To be defined by ITA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>description name </td> </tr> <tr> <td><a href="#176632#">BFA-INTEGRATION</a></td> <td> </td> <td>T</td> <td>F</td> <td>F</td> <td>name "touch point" </td> </tr> <tr> <td><a href="#176739#">BUSINESS-AREA</a></td> <td>An FEA BRM Business Area as defined by OMB.</td> <td>T</td> <td>F</td> <td>F</td> <td>"child lines of business" "fea code" name "parent business reference model" </td> </tr> <tr> <td><a href="#176864#">BUSINESS-DRIVER</a></td> <td>To be defined by ITA Team</td> <td>F</td> <td>F</td> <td>F</td> <td>"business driver type" "business focus areas" citation "citation initial date" "citation last changed" "end outcomes" "in effect" "intermediate outcomes" level "mandate final date" name organizations persons </td> </tr> <tr> <td><a href="#176786#">BUSINESS-DRIVER/ORGANIZATION</a></td> <td>Updated by complex Matrix Business Driver to Organization.</td> <td>T</td> <td>F</td> <td>F</td> <td>"architectural status" columndefinition comment "comment date" name rowdefinition </td> </tr> <tr> <td><a href="#176801#">BUSINESS-DRIVER/PERSON</a></td> <td>Updated by complex Matrix Business Driver to Person.</td> <td>F</td> <td>F</td> <td>F</td> <td>columndefinition comment "comment date" name rowdefinition </td> </tr> <tr> <td><a href="#176759#">BUSINESS-FOCUS-AREA</a></td> <td>A BFA is a logical grouping of business areas and/or sets of interrelated business functions that are currently serving the business. For example, within the DOI OCIO office, the CPIC Planning, Policy Development and Enterprise Architecture (EA) are three of its major functions. The establishment of a BFA for the OCIO, might only include EA and CPIC given their strong demand for common information and possibilities to improve business processes.</td> <td>F</td> <td>F</td> <td>F</td> <td>"blueprint scope" "business focus area type" "Data Quality Attributes" "Default Authorization Group" "main point of contact" "managing partner" name </td> </tr> <tr> <td><a href="#176760#">BUSINESS-FOCUS-AREA (ANALYSIS)</a></td> <td>Sub-Attributes for the Business Focus Area; Captures the Analysis Summary and Supporting artifacts links delivered as part of this blueprint</td> <td>T</td> <td>F</td> <td>F</td> <td>"business results score" "citizen and market score" "executive summary" "funding strategy" "highlevel findings summary" "human resource score" "impact statement" "implementation plan" "knowledge management score" "leadership score" "mbt criterion scoring" "mbt findings" "process management score" "risk management plan" "sequencing plan" "strategic planning score" "total score" </td> </tr> <tr> <td><a href="#176761#">BUSINESS-FOCUS-AREA (BLUEPRINT STATUS)</a></td> <td>Sub-Attributes for the Business Focus Area; Captures metadata related to the transformation and modernization status of this blueprint</td> <td>T</td> <td>F</td> <td>F</td> <td>accomplishments "blueprint status" "irb priority" "issues/challlenges" "mbt status" "milestones / budgeted or required funds" overview "quantitative data sources" "quantitative data sources text" "record of decision" </td> </tr> <tr> <td><a href="#176762#">BUSINESS-FOCUS-AREA (BUSINESS PROCESS RE-ENGINEERING)</a></td> <td>Sub-Attributes for the Business Focus Area; Captures links to the BPR efforts related to this blueprints</td> <td>T</td> <td>F</td> <td>F</td> <td>"bprt background" "bprt charter" "bprt meeting minutes" "bprt meeting presentations" "bprt mission" "bprt next meeting" "bprt organization" "bprt scope" </td> </tr> <tr> <td><a href="#176763#">BUSINESS-FOCUS-AREA (BUSINESS VISION AND MISSION)</a></td> <td>Sub-Attributes for the Business Focus Area; Captures vision and mission blurbs and links</td> <td>T</td> <td>F</td> <td>F</td> <td>"business focus area description" "business mission" "business vision" "candidate ideas" challenges "due dilligence" "top priority ideas" "values and benefits" </td> </tr> <tr> <td><a href="#176764#">BUSINESS-FOCUS-AREA (LINE OF SIGHT)</a></td> <td>Sub-Attributes for the Business Focus Area; Identifies the objectives, products, services, functions, data, and technologies involved in this blueprint</td> <td>T</td> <td>F</td> <td>F</td> <td>business-drivers "end outcomes" "function activities" "information classes" "lines of business" products "service components" "technical service categories" </td> </tr> <tr> <td><a href="#176765#">BUSINESS-FOCUS-AREA (PROTFOLIO)</a></td> <td>Sub-Attributes for the Business Focus Area; Systems and Investments that are part of this blueprint</td> <td>T</td> <td>F</td> <td>F</td> <td>enterprise "enterprise components" "investment projects" organizations persons "system inventories" "system inventory roles" </td> </tr> <tr> <td><a href="#176805#">BUSINESS-FOCUS-AREA (TEAM INFORMATION)</a></td> <td>Sub-Attributes for the Business Focus Area; Persons and Organizations involved with the blueprints</td> <td>T</td> <td>F</td> <td>F</td> <td>background charter "communications plan" "meeting minutes" "meeting presentations" mission "next meeting" organization "organization roles" "person roles" scope "web site" </td> </tr> <tr> <td><a href="#176787#">BUSINESS-FOCUS/BUSINESS-DRIVER</a></td> <td>Updated through Complex Matrix Business Focus Area to Business Driver.</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" "business driver category" columndefinition "description swot assessment" "mbt findings" name "rollout phase" rowdefinition stakeholders </td> </tr> <tr> <td><a href="#176652#">BUSINESS-FOCUS/DATA-SUB-AREA</a></td> <td>Associative between these two objects</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" "data subject area" name </td> </tr> <tr> <td><a href="#176633#">BUSINESS-FOCUS/FUNCT-ACTIVITY</a></td> <td>This associative entity BUSINESS-FOCUS/FUNCT-ACTIVITY will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" "business focus area" "function activity" "modes of delivery" name "rollout phase" </td> </tr> <tr> <td><a href="#176653#">BUSINESS-FOCUS/INFO-CLASS</a></td> <td>Associative between these two objects</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" columndefinition columndefinitionkey1 name "rollout phase" rowdefinition </td> </tr> <tr> <td><a href="#176788#">BUSINESS-FOCUS/INTEGRATION</a></td> <td>Should only be created through the business focus area which is to be the primary business focus area.</td> <td>F</td> <td>F</td> <td>F</td> <td>columndefinition name rowdefinition "touch point" </td> </tr> <tr> <td><a href="#176744#">BUSINESS-FOCUS/INVESTMENT</a></td> <td>This associative entity BUSINESS-FOCUS/INVESTMENT will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" "business focus area" "investment project" name "rollout phase" </td> </tr> <tr> <td><a href="#176758#">BUSINESS-FOCUS/MBT-STATUS</a></td> <td>Look up table for MBT Status where Business Focus area is NULL. Should be set list of status choices when added to BFA become unique to that BFA.</td> <td>F</td> <td>F</td> <td>F</td> <td>business-focus-area name "status begin date" "status comment" "status end date" </td> </tr> <tr> <td><a href="#176802#">BUSINESS-FOCUS/ORGANIZATION-ROLE</a></td> <td>This associative entity BUSINESS-FOCUS/ORGANIZATION will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" "business focus area" name organizations </td> </tr> <tr> <td><a href="#176789#">BUSINESS-FOCUS/OUTCOME</a></td> <td>This associative entity BUSINESS-FOCUS/END-OUTCOME will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" "business focus area" "end outcome" "end outcome name" name "rollout phase" </td> </tr> <tr> <td><a href="#176803#">BUSINESS-FOCUS/PERSON-ROLE</a></td> <td>This associative entity BUSINESS-FOCUS/PERSON will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" "business focus area" name persons </td> </tr> <tr> <td><a href="#176790#">BUSINESS-FOCUS/PRODUCT</a></td> <td>Updated via Business Focus Area to Product Matrix.</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" columndefinition "level business objectives" "level description" "level target" name "rollout phase" rowdefinition </td> </tr> <tr> <td><a href="#176820#">BUSINESS-FOCUS/SERVICE-COMP</a></td> <td>Associative between these two objects</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" columndefinition "level business objectives" "level description" "level target" name "rollout phase" rowdefinition </td> </tr> <tr> <td><a href="#176804#">BUSINESS-FOCUS/SYSTEM-INV-ROLE</a></td> <td>Look up table for roles System Invemtories can play with in a BFA. Possible values: Pending, Retire, Target, Target-Integrate, Target-Consolidate.</td> <td>F</td> <td>F</td> <td>F</td> <td>"business focus area" name "system inventories" </td> </tr> <tr> <td><a href="#176865#">BUSINESS-INFORMATION-REQUIREMENT</a></td> <td>To be defined by ITA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>BIR_description BIR_ID </td> </tr> <tr> <td><a href="#176740#">BUSINESS-REFERENCE-MODEL</a></td> <td>A way to relate a certain Line of Business to the other EA Domains The term Business Focus Area (BFA) was chosen as the BRM uses the term Line of Business slightly differently than the DOI does. BFA serves multiple purposes across domains Without this, a</td> <td>T</td> <td>F</td> <td>F</td> <td>"child business areas" </td> </tr> <tr> <td><a href="#176815#">C-&amp;-A-BOUNDARY</a></td> <td>All components of an information system to be accredited by an authorizing official and excludes separately accredited systems, to which the information system is connected. Synonymous with the term security perimeter defined in Committee on National Security Systems (CNSS) Instruction 4009 and Director of Central Intelligence Directive 6/3. (Source: NIST Special Publication 800-37)</td> <td>F</td> <td>T</td> <td>F</td> <td>"Accreditation Status" acronym "additional names" bureau ca300andl id "member system inventories" name outsourced production stype system_category </td> </tr> <tr> <td><a href="#176816#">C-&amp;-A-BOUNDARY (CATEGORIZATION)</a></td> <td>Sub-Attributes of the C-&amp;-A-BOUNDARY object; FIPS-199 Categorization status</td> <td>T</td> <td>F</td> <td>T</td> <td>availability confidentiality integrity securitycategorization </td> </tr> <tr> <td><a href="#176817#">C-&amp;-A-BOUNDARY (CONTACTS)</a></td> <td>Sub-Attributes of the C-&amp;-A-BOUNDARY object; Contact information related to this boundary</td> <td>T</td> <td>F</td> <td>T</td> <td>daa daa_email daa_phone owner owner_email owner_phone pia_completed_by pia_completed_by_email pia_completed_by_phone sso sso_email sso_phone system_mgr system_mgr_email system_mgr_phone </td> </tr> <tr> <td><a href="#176818#">C-&amp;-A-BOUNDARY (DATES)</a></td> <td>Sub-Attributes of the C-&amp;-A-BOUNDARY object; dates related to each document within the C&amp;A Package for this boundary</td> <td>T</td> <td>F</td> <td>T</td> <td>acc asc_test avg ca800_26 cert cp cp_test fips-199 ra ssp st_e </td> </tr> <tr> <td><a href="#176785#">C-&amp;-A-BOUNDARY (PRIVACY)</a></td> <td>Sub-Attributes of the C-&amp;-A-BOUNDARY object; Privacy fields abstracted from a Privacy Impact Assessmen Document used in FISMA and Enterprise Reporting on Privacy Status</td> <td>T</td> <td>F</td> <td>T</td> <td>"completed privacy impact assessment" fed_owned_info fed_owned_info_a fed_owned_info_b fed_owned_info_c fed_owned_info_d "individuals doing business" "personnel privacy concerns" "pia comment" "pia completed" "pia required" pia_fed_owned_info_id pia_online_form pia_online_form_omb_number pia_online_form_omb_number_name pia_online_form_privacy_notice pia_records_name pia_records_notice prelim_pia "privacy act system of record" "public information individuals" </td> </tr> <tr> <td><a href="#176819#">C-&amp;-A-BOUNDARY (other FISMA)</a></td> <td>Sub-Attributes of the C-&amp;-A-BOUNDARY object; Additional FISMA fields as requested for reporting purposes</td> <td>T</td> <td>F</td> <td>T</td> <td>"c and a comments" "e-authentication eligible" "level of assurance required" "provider of services" "system criticality" "system internet need" </td> </tr> <tr> <td><a href="#176866#">CAP-IMPLICATION</a></td> <td>To be defined by ITA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>cap_implication_description cap_implication_id </td> </tr> <tr> <td><a href="#176867#">CAP-RATIONALE</a></td> <td>To be defined by ITA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>cap_rationale_description cap_rationale_id </td> </tr> <tr> <td><a href="#176662#">CATEGORY-RELATIONSHIP</a></td> <td>A SPECIFIC TYPE OF DATA MODEL RELATIONSHIP USED TO SPECIFY A CATEGORY TYPE ARRANGEMENT BETWEEN PARENT AND CHILD ENTITIES.</td> <td>T</td> <td>F</td> <td>F</td> <td>"CATEGORY-RELATIONSHIP COMPLETENESS CODE" </td> </tr> <tr> <td><a href="#176868#">COMMON-REQUIREMENTS-VISION</a></td> <td>To be defined by ITA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>crv_author crv_background crv_ID crv_introduction crv_version "External File 1" "External File 2" "External File 3" </td> </tr> <tr> <td><a href="#176843#">COMP-INST-INTERFACE</a></td> <td>This associative entity will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>bi-directional Delete description "from sub system" "from sub system version" "from system" "from system version" "from system-component-instance" initiator Initiator "joint it security requirements" "moa or mou complete" "operational frequency" "operational mode" "system interface capability" "to sub system" "to sub system version" "to system" "to system version" "to system-component-instance" type "written approval for esbablishing connection" </td> </tr> <tr> <td><a href="#176849#">COMPONENT-ARCHITECTURE</a></td> <td>Look table for valules.</td> <td>T</td> <td>F</td> <td>F</td> <td>name </td> </tr> <tr> <td><a href="#176845#">COMPONENT-INSTANCE</a></td> <td>A system component instance actually does (at least part of) what the system is made to do. A system component instance is physical--you actually deploy it on a processing node. In a car, the system component instance for the passenger-holding subsystem w</td> <td>F</td> <td>F</td> <td>T</td> <td>Acronym "data storage comment" "deployment mode" "deployment scope inter enterprise" "deployment scope outer enterprise" "deployment tiers" "execution environment comment" "future plans comment" "interface comment" name "operational month" "operational status" "operational year" "platform comment" "processing nodes" quantity "replaces system component instsances" "sub system" "sub system version" system "system component" "system component version" "system version" </td> </tr> <tr> <td><a href="#176844#">COMPONENT_</a></td> <td>Independently deployable unit of software that exposes its functionality through a set of services accessed via well-defined interfaces. A component is based on a component standard, is described by a specification, and has an implementation. Components can be assembled to create applications or larger-grained components.</td> <td>F</td> <td>F</td> <td>F</td> <td>acronym "availability requirement" "component architecture design model" "component framework design model" "configuration management flag" "construction comment" "construction modification level" "cpic phase" "data exchange technique" "data interchange design model" "data storage comment" "data transformation design model" "database architecture design model" "delivery channel types" enterprise "enterprise architecture component state" "enterprise architecture component state rationale" "execution environment comment" "external system component" functionality "future plans comment" "government approved encryption algorithm usage" "managing partner" "message exchange protocol design model" "message format design model" "middleware architecture design model" "modification eligibility" name "organization roles" "ownership model" "performance requirement" "person roles" "platform comment" "replaces system components" "re-use design" "scalability requirement" scope "security authentication model" "security authorization model" "security comment" "service delivery model" "service discovery" "service interface design model" "software development lifecycle stage" "throughput requirement" "transport protocol design model" version </td> </tr> <tr> <td><a href="#176806#">COMPONENT_/ORGANIZATION-ROLE</a></td> <td>This associative entity will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>Delete Name organization "role remarks" "system component" version </td> </tr> <tr> <td><a href="#176807#">COMPONENT_/PERSON-ROLE</a></td> <td>This associative entity SYSTEM-COMPONENT/PERSON-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>Delete Name Person "Role Remarks" "System Component" Version </td> </tr> <tr> <td><a href="#176869#">CONCEPTUAL-ARCHITECTURE-PRINCIPLE</a></td> <td>To be defined by ITA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>cap_author cap_background cap_ID cap_introduction cap_version </td> </tr> <tr> <td><a href="#176663#">CONCEPTUAL-DATA-MODEL</a></td> <td>A STRUCTURED GRAPHICAL AND TEXTUAL REPRESENTATION OF CONCEPTS AND KNOWLEDGE WITHIN AN ACTIVITY.</td> <td>T</td> <td>F</td> <td>F</td> <td>"CONCEPTUAL-DATA-MODEL CREATOR IDENTIFIER" "CONCEPTUAL-DATA-MODEL DEVELOPMENT METHODOLOGY NAME" "CONCEPTUAL-DATA-MODEL DEVELOPMENT STATUS IDENTIFIER" "CONCEPTUAL-DATA-MODEL DEVELOPMENT TOOL NAME" "CONCEPTUAL-DATA-MODEL NOTATION STYLE NAME" "CONCEPTUAL-DATA-MODEL PURPOSE TEXT" "CONCEPTUAL-DATA-MODEL REFINEMENT LEVEL CODE" "CONCEPTUAL-DATA-MODEL REVISION EFFECTIVE CALENDAR DATE" "CONCEPTUAL-DATA-MODEL SCOPE TEXT" "CONCEPTUAL-DATA-MODEL STATUS EFFECTIVE CALENDAR DATE" "CONCEPTUAL-DATA-MODEL TENSE CODE" "CONCEPTUAL-DATA-MODEL TENSE EFFECTIVE CALENDAR DATE" </td> </tr> <tr> <td><a href="#176664#">CONCEPTUAL-DATA-MODEL-VIEW</a></td> <td>A COLLECTION OF ENTITIES, ATTRIBUTES, AND RELATIONSHIPS THAT REPRESENT A SPECIFIC PART OF A DATA MODEL.</td> <td>T</td> <td>F</td> <td>F</td> <td>"CONCEPTUAL-DATA-MODEL-VIEW CREATOR IDENTIFIER" "CONCEPTUAL-DATA-MODEL-VIEW DATA STANDARDIZATION IDENTIFIER" "CONCEPTUAL-DATA-MODEL-VIEW SCOPE TEXT" </td> </tr> <tr> <td><a href="#176665#">CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION</a></td> <td>THE ASSOCIATION BETWEEN ONE CONCEPTUAL-DATA-MODEL-VIEW AND ANOTHER.</td> <td>T</td> <td>F</td> <td>F</td> <td>"CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION CREATION CALENDAR DATE" "CONCEPTUAL-DATA-MODEL-VIEW-ASSOCIATION DEPENDENCY DESCRIPTION TEXT" </td> </tr> <tr> <td><a href="#176667#">CONCEPTUAL-DATA-MODEL-VIEW-DATA-ENTITY-RELATIONSHIP</a></td> <td>AN ASSOCIATIVE ENTITY THAT IDENTIFIES A DATA-ENTITY-RELATIONSHIP WITH A CON CEPTUAL-DATA-MODEL-VIEW.</td> <td>T</td> <td>F</td> <td>F</td> <td>"CONCEPTUAL-DATA-MODEL-VIEW-DATA-ENTITY-RELATIONSHIP COMMENT TEXT" </td> </tr> <tr> <td><a href="#176870#">CRV-STRATEGY</a></td> <td>To be defined by ITA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>strategy_description strategy_ID </td> </tr> <tr> <td><a href="#176668#">DATA-ATTRIBUTE</a></td> <td>A PROPERTY OR CHARACTERISTIC OF A DATA-ENTITY THAT IS COMMON TO INSTANCES OF AN ENTITY AND REPRESENTS THE ASSOCIATION OF A DATA-DOMAIN WITH A DATA-ENTITY.</td> <td>T</td> <td>F</td> <td>F</td> <td>"attribute composition type name" "authoritative source" "derivation procedure" derived "domain description" "domain values" "entity name" "full name" "indian trus data" model name notes precision "reference source" "security classification code" "units of measure" "xml tag name" </td> </tr> <tr> <td><a href="#176669#">DATA-ATTRIBUTE-ALIAS</a></td> <td>AN ASSOCIATIVE ENTITY THAT IDENTIFIES AN ALTERNATE LABEL USED TO REFER TO A DATA-ATTRIBUTE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"ALIAS IDENTIFIER" "DATA-ATTRIBUTE-ALIAS CREATION CALENDAR DATE" </td> </tr> <tr> <td><a href="#176670#">DATA-ATTRIBUTE-ASSOCIATION</a></td> <td>THE ASSOCIATION AMONG DATA ATTRIBUTES WHICH INDICATES HOW A NON-ATOMIC DATA ATTRIBUTE IS CONSTRUCTED.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ATTRIBUTE-ASSOCIATION TYPE CODE" </td> </tr> <tr> <td><a href="#176671#">DATA-ATTRIBUTE-CHAIN</a></td> <td>(4227/1) (A) A SUBTYPE OF DATA ATTRIBUTE ASSOCIATION WHICH INDICATES A DATA ATTRIBUTE DE RIVED THROUGH PARTICIPATION IN A CHAIN.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ATTRIBUTE-CHAIN PARTICIPANT TYPE CODE" </td> </tr> <tr> <td><a href="#176673#">DATA-ATTRIBUTE-CHAIN-MEMBER-ATTRIBUTE</a></td> <td>To be defined by IDA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ATTRIBUTE-CHAIN DATA ATTRIBUTE POSITION IDENTIFIER" </td> </tr> <tr> <td><a href="#176674#">DATA-ATTRIBUTE-DATA-TYPE</a></td> <td>THE SPECIFICATION OF A DATA CLASS OF A DATABASE QUERY LANGUAGE FOR A SPECIFIC DATA-ATTRIBUTE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ATTRIBUTE-DATA-TYPE NAME" "DATA-ATTRIBUTE-DATA-TYPE TARGET ENVIRONMENT NAME" </td> </tr> <tr> <td><a href="#176675#">DATA-ATTRIBUTE-DERIVED</a></td> <td>A SUBTYPE OF A DATA ATTRIBUTE ASSOCIATION WHICH INDICATES A DERIVED DATA AT TRIBUTE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ATTRIBUTE-DERIVED ALGORITHM TEXT" </td> </tr> <tr> <td><a href="#176676#">DATA-ATTRIBUTE-USER-PRESENTATION-VIEW-FIELD</a></td> <td>AN ASSOCIATIVE ENTITY THAT IDENTIFIES A DATA-ATTRIBUTE WITH A USER-PRESENTATION-VIEW-FIELD.</td> <td>T</td> <td>F</td> <td>F</td> <td>"User Presentation View INFORMATION-ASSET IDENTIFIER" "USER-PRESENTATION-VIEW-FIELD IDENTIFIER" </td> </tr> <tr> <td><a href="#176677#">DATA-CLASS</a></td> <td>THE CLASSIFICATION OF DATA TO WHICH A DATA ATTRIBUTE BELONGS.</td> <td>T</td> <td>F</td> <td>F</td> <td>"Data Class INFORMATION-ASSET IDENTIFIER" "DATA-CLASS CATEGORY NAME" "DATA-CLASS TYPE CODE" </td> </tr> <tr> <td><a href="#176678#">DATA-DICTIONARY</a></td> <td>A LISTING OF DATA-ELEMENTS AND THEIR CHARACTERISTICS.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DICTIONARY TYPE CODE" </td> </tr> <tr> <td><a href="#176679#">DATA-DICTIONARY-ELEMENT</a></td> <td>AN INFORMATION CONCEPT DEFINED IN A SPECIFIC DATA-DICTIONARY.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DICTIONARY-ELEMENT APPROVAL STATUS CALENDAR DATE" "DATA-DICTIONARY-ELEMENT APPROVAL STATUS CODE" "DATA-DICTIONARY-ELEMENT DEFINITION TEXT" "DATA-DICTIONARY-ELEMENT FORMAT DESCRIPTION TEXT" "DATA-DICTIONARY-ELEMENT IDENTIFIER" "DATA-DICTIONARY-ELEMENT NAME" "DATA-DICTIONARY-ELEMENT SOURCE NAME" "DATA-DICTIONARY-ELEMENT USAGE DESCRIPTION TEXT" "INFORMATION-ELEMENT IDENTIFIER" </td> </tr> <tr> <td><a href="#176680#">DATA-DICTIONARY-ELEMENT-ASSOCIATION</a></td> <td>THE RELATIONSHIP OF ONE DATA-DICTIONARY-ELEMENT TO ANOTHER DATA-DICTIONARY-ELEMENT.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DICTIONARY-ELEMENT-ASSOCIATION IDENTIFIER" "DATA-DICTIONARY-ELEMENT-ASSOCIATION TYPE CODE" </td> </tr> <tr> <td><a href="#176681#">DATA-DICTIONARY-SPECIFICATION</a></td> <td>A DOCUMENT THAT CONTAINS METADATA FOR INFORMATION CONCEPTS.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DOCUMENT IDENTIFIER" </td> </tr> <tr> <td><a href="#176682#">DATA-DOMAIN</a></td> <td>A SET OF PERMISSIBLE DATA VALUES FROM WHICH ACTUAL VALUES ARE TAKEN.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DOMAIN CONSTRUCTION TYPE CODE" "DATA-DOMAIN FORMAT CODE" "DATA-DOMAIN MAXIMUM CHARACTER QUANTITY" "DATA-DOMAIN TYPE CODE" "DATA-DOMAIN VALUE TYPE CODE" </td> </tr> <tr> <td><a href="#176683#">DATA-DOMAIN-BASE</a></td> <td>A DATA DOMAIN, ASSIGNED A CERTAIN DATA TYPE, UPON WHICH OTHER DOMAINS MAY BE BASED.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DOMAIN-BASE DATA TYPE NAME" </td> </tr> <tr> <td><a href="#176684#">DATA-DOMAIN-LIST</a></td> <td>AN ENUMERATED SET OF VALUES ALLOWED IN DATA REPRESENTATION OF A DATA-ATTRIBUTE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DOMAIN-LIST SOURCE LIST TEXT" </td> </tr> <tr> <td><a href="#176685#">DATA-DOMAIN-LIST-VALUE</a></td> <td>A SPECIFIC ACCEPTABLE INSTANCE VALUE THAT IS PART OF A DATA-DOMAIN-LIST.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DOMAIN-LIST-VALUE DEFINITION TEXT" "DATA-DOMAIN-LIST-VALUE IDENTIFIER" "DATA-DOMAIN-LIST-VALUE SOURCE NAME" </td> </tr> <tr> <td><a href="#176686#">DATA-DOMAIN-LIST-VALUE-ASSOCIATION</a></td> <td>THE RELATIONSHIP OF ONE SPECIFIC DATA-DOMAIN-LIST-VALUE WITH ANOTHER DATA-DOMAIN-LIST-VALUE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DOMAIN-LIST-VALUE-ASSOCIATION ALGORITHM TEXT" </td> </tr> <tr> <td><a href="#176687#">DATA-DOMAIN-RANGE</a></td> <td>THE SET OF ALL ACCEPTABLE INSTANCE VALUES OF A DATA DOMAIN WHERE THE INSTANCE VALUES ARE CONSTRAINED BY LOWER AND/OR UPPER BOUNDARIES.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DOMAIN-RANGE HIGH VALUE TEXT" "DATA-DOMAIN-RANGE INCREMENT MEASUREMENT QUANTITY" "DATA-DOMAIN-RANGE LOW VALUE TEXT" </td> </tr> <tr> <td><a href="#176688#">DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION</a></td> <td>THE COMBINATION OF RULES BY WHICH A DATA DOMAIN IS CONSTRUCTED.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION ALGORITHM TEXT" "DATA-DOMAIN-STRUCTURE-RULE-ASSOCIATION NAME" </td> </tr> <tr> <td><a href="#176689#">DATA-DOMAIN-TYPED</a></td> <td>A DATA DOMAIN WHOSE ALLOWABLE VALUES ARE CONSTRAINED BY A DATA DOMAIN STRUC TURE RULE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-DOMAIN-TYPED NAME" </td> </tr> <tr> <td><a href="#176690#">DATA-ENTITY</a></td> <td>THE REPRESENTATION OF A SET OF PEOPLE, OBJECTS, PLACES, EVENTS OR IDEAS, THAT SHARE THE SAME CHARACTERISTICS.</td> <td>T</td> <td>F</td> <td>F</td> <td>"entity mappable indicator" "full name" "function activities" "information classes" name "sub systems" version "xml tag name" </td> </tr> <tr> <td><a href="#176691#">DATA-ENTITY-ALTERNATE-KEY-GROUP</a></td> <td>To be defined by IDA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ENTITY-ALTERNATE-KEY-GROUP IDENTIFIER" "DATA-ENTITY-DATA-ATTRIBUTE ALTERNATE KEY IDENTIFIER" </td> </tr> <tr> <td><a href="#176694#">DATA-ENTITY-KEY-GROUP</a></td> <td>To be defined by IDA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ENTITY-KEY-GROUP Identifier" </td> </tr> <tr> <td><a href="#176697#">DATA-ENTITY-RELATIONSHIP</a></td> <td>THE ASSOCIATION OF ONE SPECIFIC DATA-ENTITY WITH ANOTHER DATA-ENTITY.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ENTITY-RELATIONSHIP CARDINALITY TYPE CODE" "DATA-ENTITY-RELATIONSHIP CATEGORY CODE" "DATA-ENTITY-RELATIONSHIP CHILD DELETE RULE TEXT" "DATA-ENTITY-RELATIONSHIP CHILD INSERT RULE TEXT" "DATA-ENTITY-RELATIONSHIP CHILD UPDATE RULE TEXT" "DATA-ENTITY-RELATIONSHIP DEPENDENCY CODE" "DATA-ENTITY-RELATIONSHIP DESCRIPTION TEXT" "DATA-ENTITY-RELATIONSHIP GLOBALLY-UNIQUE PHYSICAL NAME" "DATA-ENTITY-RELATIONSHIP IDENTIFIER" "DATA-ENTITY-RELATIONSHIP NAME" "DATA-ENTITY-RELATIONSHIP NULL RULE TEXT" "DATA-ENTITY-RELATIONSHIP PARENT DELETE RULE TEXT" "DATA-ENTITY-RELATIONSHIP PARENT INSERT RULE TEXT" "DATA-ENTITY-RELATIONSHIP PARENT UPDATE RULE TEXT" "DATA-ENTITY-RELATIONSHIP TYPE CODE" "DATA-ENTITY-RELATIONSHIP VERSION IDENTIFIER" </td> </tr> <tr> <td><a href="#176698#">DATA-ENTITY-RELATIONSHIP-ROLE-NAME</a></td> <td>To be defined by IDA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>"DATA-ENTITY-RELATIONSHIP ROLE NAME IDENTIFIER" </td> </tr> <tr> <td><a href="#176700#">DATA-FLOW</a></td> <td>To be defined by IDA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>Delete "information classes" name </td> </tr> <tr> <td><a href="#176701#">DATA-FORMAT</a></td> <td>Look up table for system interface capability data formats.</td> <td>T</td> <td>F</td> <td>F</td> <td>Name </td> </tr> <tr> <td><a href="#176836#">DATA-QUALITY</a></td> <td> </td> <td>T</td> <td>F</td> <td>F</td> <td>"data quality comments" "data quality description" "data quality status" "integrating rating score" "inventory rating score" "modeling rating score" "next steps" priority "ref model mapping rating score" </td> </tr> <tr> <td><a href="#176702#">DATA-SET</a></td> <td>In an EA sense, a geospatial data set can be viewed in a similarfashion as a system and may be viewed as a type of simplified system in the EA:they have a defined structure, a set of data elements, a theme or subject area,and are created and maintained by owners. They also have a set of standardized ?system?metadata, such as creator, creation date, description, status, currentness , purpose etc. The FGDC metadata standard for spatialdata sets is a good way to consistently describe them across the department. In fact, if a data set is fully described using this metadata, they should already contain much of the information to populate DEAR</td> <td>T</td> <td>F</td> <td>F</td> <td>"creation date" creator currentness Entities name "owning organization" purpose status "subject area diagram" </td> </tr> <tr> <td><a href="#176703#">DATA-STORE</a></td> <td>A PROCESS-ACTIVITY THAT PERSISTENTLY HOLDS INFORMATION.</td> <td>T</td> <td>F</td> <td>F</td> <td>"information classes" name "processing nodes" "system component instances" "technical service specifications" </td> </tr> <tr> <td><a href="#176736#">DATA-STORE/SYSTEM-COMP-INST</a></td> <td>This associative entity DATA-STORE/SYSTEM-COMP-INST will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>"data store" name "sub system" "sub system version" system "system component instance" "system component instance version" "system version" </td> </tr> <tr> <td><a href="#176704#">DATA-SUBJECT-AREA</a></td> <td>A BROAD CLASSIFICATION OF INFORMATION or a grouping of related entities (those in which data are closely related and describe a general business idea or object) are called Data Subject Areas (DSA). A DSA is a grouping of entities based on a commonality of the data, and NOT how it is used by any given business process or application. This will be a definition object as well as a diagram object. The DATA-SUBJECT-AREA entity should be able to support both the DOI data management program and BEA. Source:IT Pioneers, Jim Cox, &amp; BLM EA Team of Bob Perkins &amp; Barb Kett</td> <td>T</td> <td>F</td> <td>F</td> <td>"information classes" name status </td> </tr> <tr> <td><a href="#176846#">DEPLOYMENT-TIER</a></td> <td>None</td> <td>T</td> <td>F</td> <td>F</td> <td>Name </td> </tr> <tr> <td><a href="#176706#">DOCUMENT</a></td> <td>RECORDED INFORMATION REGARDLESS OF PHYSICAL FORM.</td> <td>T</td> <td>F</td> <td>F</td> <td>"CAVEATED-SECURITY-CLASSIFICATION IDENTIFIER" "DOCUMENT ABBREVIATED NAME" "DOCUMENT APPROVAL CALENDAR DATE" "DOCUMENT ARCHITECTURE PRODUCT TYPE CODE" "DOCUMENT CATEGORY CODE" "DOCUMENT CREATION CALENDAR DATE" "DOCUMENT DESCRIPTION TEXT" "DOCUMENT IDENTIFIER" "DOCUMENT NAME" "DOCUMENT NOTATION TEXT" "DOCUMENT ORIGINATOR NAME" "DOCUMENT PUBLICATION CALENDAR DATE" "DOCUMENT REMARK TEXT" "DOCUMENT ROUTING CODE" "DOCUMENT TEMPORAL SCOPE CODE" "DOCUMENT TYPE CODE" "DOCUMENT UNIVERSAL RESOURCE LOCATOR TEXT" "DOCUMENT VERSION IDENTIFIER" "SECURITY-CLASSIFICATION CODE" "Time Frame PERIOD IDENTIFIER" </td> </tr> <tr> <td><a href="#176707#">DOCUMENT-ASSOCIATION</a></td> <td>AN ASSOCIATION BETWEEN A DOCUMENT AND ANOTHER DOCUMENT.</td> <td>T</td> <td>F</td> <td>F</td> <td>"DOCUMENT-ASSOCIATION BEGIN CALENDAR DATE-TIME" "DOCUMENT-ASSOCIATION END CALENDAR DATE-TIME" "DOCUMENT-ASSOCIATION IDENTIFIER" "DOCUMENT-ASSOCIATION REASON CODE" </td> </tr> <tr> <td><a href="#176754#">DOCUMENT-INSTANCE</a></td> <td>This Entity is utilized internall by System Architect to aid Report generation. It is not part of the DOI Enterprise Architecture Definition.</td> <td>T</td> <td>F</td> <td>F</td> <td>"Creating Office" Custodian "Cutoff Date" Disposition document-instance-name "Electronic Location" "File Scheme" GRS "HTML Link" "Media Type" "Paper Location" "Record Indicator" Status Vital </td> </tr> <tr> <td><a href="#176755#">DOCUMENT-TYPE</a></td> <td>This Entity is utilized internall by System Architect to aid Report generation. It is not part of the DOI Enterprise Architecture Definition.</td> <td>T</td> <td>F</td> <td>F</td> <td>Author Category "Document Status" document-type-name "File Name" ID Keywords Links "Report or Binder" "Revision Date" Synopsis Type "Version nbr" </td> </tr> <tr> <td><a href="#176872#">DOMAIN-ARCH-PRINCIPLE</a></td> <td>To be defined by ITA Team</td> <td>T</td> <td>F</td> <td>F</td> <td>"dap implications" "dap rationales" name "service components" "technology domain team" </td> </tr> <tr> <td><a href="#176708#">DOMAIN-VALUE</a></td> <td>Meant to represent the list of valid values for a given attribute.</td> <td>T</td> <td>F</td> <td>F</td> <td>name </td> </tr> <tr> <td><a href="#176709#">ENTITY/ORGANIZATION-ROLE</a></td> <td>Associative between these two objects</td> <td>T</td> <td>F</td> <td>F</td> <td>description entity model name organizations </td> </tr> <tr> <td><a href="#176737#">ENTITY/SUB-SYSTEM</a></td> <td>This associative entity will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name. This relatioinship has been taken to the lowest level (rather than sub-system) since if it is not known at the system component, then it is likely not known at the sub-system level.</td> <td>F</td> <td>F</td> <td>F</td> <td>columndefinition columndefinitionkey1 columndefinitionkey2 columndefinitionkey3 "crud info" "data store form of sharing" description intersection? name rowdefinition rowdefinitionkey1 </td> </tr> <tr> <td><a href="#176873#">ENVIRONMENTAL-TREND</a></td> <td>None</td> <td>T</td> <td>F</td> <td>F</td> <td>env_trend_description env_trend_ID </td> </tr> <tr> <td><a href="#176745#">EXHIBIT-53</a></td> <td>A data container for miscellaneous information required by the Exhibit 53. At this time, it only contains the exhibit53-name. If this is the same as the Exhibit 53 Investment Title, that information is already captured in INVESTMENT(PROJECT) investment-title. I believe this is a hold over from some earlier modeling when we were representing reports as objects.</td> <td>T</td> <td>F</td> <td>F</td> <td>exhibit53-name </td> </tr> <tr> <td><a href="#176874#">FOCUS</a></td> <td>None</td> <td>T</td> <td>F</td> <td>F</td> <td>focus_idenifier </td> </tr> <tr> <td><a href="#176655#">FUNCTION-ACTIVITY</a></td> <td>BRM-TIER represents an entity in the FEA BRM. A BRM-TIER can be a Business area, Line of Businbess, or Business Sub Funciton or a further Agency specific decomposition. It is the super entity for BUSINESS-AREA, LINE-OF-BUSINESS, SUB-FUNCTION, LEVEL-2-SUB-FUNCTION, WORK-ACTIVITY, and PROCESS-STEP. The OMB has incorporated Mode of Delivery into the categorization of a Business Area. It is also considered to be its own entity at its level of Business Area with its own two lines of businesses. This later part is not modeled with the expectation that OMB will provide further guidance.</td> <td>T</td> <td>F</td> <td>F</td> <td>"abc work activities" "child function activities" "full name" "functin activity type" "leaf node flag" level "modes of delivery" name organizations "parent function activity" "secondary parent function activities" "service components" "sub function flag" "sub systems" </td> </tr> <tr> <td><a href="#176741#">FUNCTION-ACTIVITY (SECURITY)</a></td> <td>NIST attributes from the NIST 800-60 used in FIPS-199 Security Categorization based on Information types used by a system. NIST adopted the FEA BRM as the standard. NIST Information Types is equal to FEA BRM Sub-functions</td> <td>T</td> <td>F</td> <td>F</td> <td>"availability impact description" "availability impact recommended level" "availability impact special factors" "avaliability impact rationale" "confidentiality impact description" "confidentiality impact rationale" "confidentiality impact recommended level" "confidentiality impact special factors" "integrity impact description" "integrity impact rationale" "integrity impact recommended level" "integrity impact special factors" </td> </tr> <tr> <td><a href="#176738#">FUNCTION-ACTIVITY/ENTITY</a></td> <td>This associative entity FUNCTION-ACTIVITY/DATA-ENTITY will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>T</td> <td>F</td> <td>F</td> <td>columndefinition columndefinitionkey1 "crud info" name "rollout/phase" rowdefinition </td> </tr> <tr> <td><a href="#176832#">FUNCTION-ACTIVITY/SUB-SYSTEM</a></td> <td>How the system component is utilized by business processes. Taken to the lowest level (rather than sub-system) since if it is not known at the system component, then it is likely not known at the sub-system level.</td> <td>F</td> <td>F</td> <td>F</td> <td>columndefinitionkey columndefinitionkey1 "data qualification" description intersection? name "process automation qualification" "rollout/phase" rowdefinition </td> </tr> <tr> <td><a href="#176791#">GENERIC-INDICATOR/MEASURE</a></td> <td>Operationalized Measurement Indicators agencies use in the PRM will be informed and determined by the GPRA and budget planning process, PART assessments, and other drivers. This is the intersection between the OMB PRM and the DOI PRM. It is implemented as a complex matrix.</td> <td>T</td> <td>F</td> <td>F</td> <td>"generic measurement indicator" "intermediate outcome measure" "measurement area" "measurement category" name </td> </tr> <tr> <td><a href="#176792#">GENERIC-MEASUREMENT-INDICATOR</a></td> <td>Generic Measurement Indicators  The generic indicators, for example delivery time, that agencies then "operationalize" for their specific environment. Importantly, the Generic Measurement Indicators included in the PRM are merely starting points for agencies. In their FY 2005 Exhibit 300s, agencies "operationalize" the four Generic Measurement Indicators they propose to use for each major IT initiative classified as DME. Agencies are free to tailor these operationalized Measurement Indicators so that they fit the agency s specific environment and the IT initiative s specific goals. As agencies use the PRM over time, these Operationalized Measurement Indicators will evolve and comprise the actual and most useful contents of the PRM. The development of these will be more difficult in some cases than in others and the links between inputs and outcomes will not always be easy to define. For IT initiatives that support programs that have been subject to the PART, a useful starting point would be to use the PART key performance measures.</td> <td>T</td> <td>F</td> <td>F</td> <td>"end outcome measures" "intermediate outcome measures" "measurement area" "measurement category" name </td> </tr> <tr> <td><a href="#176826#">GOAL</a></td> <td> </td> <td>T</td> <td>F</td> <td>F</td> <td>name </td> </tr> <tr> <td><a href="#176710#">GUIDANCE</a></td> <td>(336/3) (A) A STATEMENT OF DIRECTION RECEIVED FROM A HIGHER ECHELON.</td> <td>T</td> <td>F</td> <td>F</td> <td>"GUIDANCE AUTHORITY TEXT" "GUIDANCE BEGIN CALENDAR DATE-TIME" "GUIDANCE CATEGORY CODE" "GUIDANCE END CALENDAR DATE-TIME" "GUIDANCE FUNCTIONAL TYPE CODE" "GUIDANCE IDENTIFIER" "GUIDANCE NAME" "GUIDANCE SUBJECT TEXT" "GUIDANCE SYNOPSIS TEXT" "GUIDANCE TEXT" "POINT-OF-CONTACT IDENTIFIER" </td> </tr> <tr> <td><a href="#176711#">GUIDANCE-ASSOCIATION</a></td> <td>AN ASSOCIATION OF A SPECIFIC GUIDANCE WITH ANOTHER SPECIFIC GUIDANCE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"GUIDANCE-ASSOCIATION BEGIN CALENDAR DATE-TIME" "GUIDANCE-ASSOCIATION END CALENDAR DATE-TIME" "GUIDANCE-ASSOCIATION IDENTIFIER" "GUIDANCE-ASSOCIATION ROLE CODE" </td> </tr> <tr> <td><a href="#176656#">ICOM-ARROW</a></td> <td>None</td> <td>T</td> <td>F</td> <td>F</td> <td>"business drivers" "data entities" delete name </td> </tr> <tr> <td><a href="#176712#">INFORMATION-ASSET</a></td> <td>AN INFORMATION RESOURCE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"INFORMATION-ASSET ACRONYM TEXT" "INFORMATION-ASSET COMMENT TEXT" "INFORMATION-ASSET DEFINITION TEXT" "INFORMATION-ASSET IDENTIFIER" "INFORMATION-ASSET NAME" "INFORMATION-ASSET REUSABLE CODE" "INFORMATION-ASSET SHORT NAME" "INFORMATION-ASSET STANDARDIZATION AUTHORITY CODE" "INFORMATION-ASSET STANDARDIZATION STATUS CALENDAR DATE" "INFORMATION-ASSET STANDARDIZATION STATUS CODE" "INFORMATION-ASSET TYPE CODE" "INFORMATION-ASSET VERSION IDENTIFIER" </td> </tr> <tr> <td><a href="#176713#">INFORMATION-ASSET-AGREEMENT</a></td> <td>THE ASSOCIATION OF A SPECIFIC INFORMATION-ASSET TO A SPECIFIC AGREEMENT.</td> <td>T</td> <td>F</td> <td>F</td> <td>"INFORMATION-ASSET-AGREEMENT IDENTIFIER" "INFORMATION-ASSET-AGREEMENT ROLE CODE" </td> </tr> <tr> <td><a href="#176714#">INFORMATION-ASSET-DOCUMENT</a></td> <td>THE ASSOCIATION OF A SPECIFIC INFORMATION-ASSET TO A SPECIFIC DOCUMENT.</td> <td>T</td> <td>F</td> <td>F</td> <td>"INFORMATION-ASSET-DOCUMENT IDENTIFIER" "INFORMATION-ASSET-DOCUMENT ROLE CODE" </td> </tr> <tr> <td><a href="#176715#">INFORMATION-ASSET-GUIDANCE</a></td> <td>THE ASSOCIATION OF A SPECIFIC INFORMATION-ASSET WITH A SPECIFIC INSTANCE OF GUIDANCE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"INFORMATION-ASSET-GUIDANCE DESCRIPTION TEXT" </td> </tr> <tr> <td><a href="#176716#">INFORMATION-ASSET-RELATION</a></td> <td>THE ASSOCIATION BETWEEN INFORMATION-ASSETS.</td> <td>T</td> <td>F</td> <td>F</td> <td>"INFORMATION-ASSET-RELATION REASON TEXT" "INFORMATION-ASSET-RELATION ROLE CODE" "INFORMATION-ASSET-RELATION TRACE GENERATED RELATIONSHIP INDICATOR CODE" "INFORMATION-ASSET-RELATION TYPE CODE" </td> </tr> <tr> <td><a href="#176718#">INFORMATION-CLASS</a></td> <td>To be defined by IDA Team Was named super type.</td> <td>T</td> <td>F</td> <td>F</td> <td>"business focus areas" "data entities" "data subject area" name status "sub systems" </td> </tr> <tr> <td><a href="#176719#">INFORMATION-CLASS/SUB-SYSTEM</a></td> <td>This associative entity SUPER-TYPE/SUB-SYSTEM will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>columndefinition columndefinitionkey1 columndefinitionkey2 columndefinitionkey3 "curd info" "data store form of sharing" "data subject area" name rowdefinition rowdefinitionkey1 </td> </tr> <tr> <td><a href="#176720#">INFORMATION-SYSTEM</a></td> <td>A COLLECTION OF INFORMATION-ASSETS COMBINED TO ACHIEVE A DIRECTED PURPOSE.</td> <td>T</td> <td>F</td> <td>F</td> <td>"FUNCTIONAL-AREA IDENTIFIER" "INFORMATION-SYSTEM ENVIRONMENT TEXT" "INFORMATION-SYSTEM INTERFACE TRANSACTION PREDOMINANT METHOD CODE" "INFORMATION-SYSTEM SITE QUANTITY" "INFORMATION-SYSTEM TYPE CODE" "INFORMATION-SYSTEM USER QUANTITY" </td> </tr> <tr> <td><a href="#176721#">INFORMATION-TECHNOLOGY-REQUIREMENT</a></td> <td>GUIDANCE THAT SPECIFIES A NEED OR DEMAND FOR THE ACQUISITION, STORAGE, MANIPULATION, MANAGEMENT, MOVEMENT, CONTROL, SWITCHING, INTERCHANGE, TRANSMISSION, OR RECEPTION OF DATA.</td> <td>T</td> <td>F</td> <td>F</td> <td>"FUNCTIONAL-AREA IDENTIFIER" "INFORMATION-TECHNOLOGY-REQUIREMENT ALTERNATE IDENTIFIER" "INFORMATION-TECHNOLOGY-REQUIREMENT ALTERNATE IDENTIFIER SOURCE NAME" "INFORMATION-TECHNOLOGY-REQUIREMENT CATEGORY CODE" "INFORMATION-TECHNOLOGY-REQUIREMENT DESCRIPTION TEXT" "INFORMATION-TECHNOLOGY-REQUIREMENT USE CLASS CODE" </td> </tr> <tr> <td><a href="#176722#">INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET</a></td> <td>THE ASSOCIATION OF A SPECIFIC INFORMATION-TECHNOLOGY-REQUIREMENT WITH A SPECIFIC INFORMATION-ASSET.</td> <td>T</td> <td>F</td> <td>F</td> <td>"INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET IDENTIFIER" "INFORMATION-TECHNOLOGY-REQUIREMENT-INFORMATION-ASSET ROLE CODE" </td> </tr> <tr> <td><a href="#176837#">INTERFACE_</a></td> <td>Generic Interface used in the SYSTEM-INTERFACE-DECOMPOSITION Diagram. Not keyed by to and from objects.</td> <td>F</td> <td>F</td> <td>F</td> <td>bi-directional "data entities" description initiator "joint it security requirements" "moa or mou complete" name "operational frequency" "operational mode" type "written approval for esbablishing connection" </td> </tr> <tr> <td><a href="#176747#">INVESTMENT-PHASE</a></td> <td>Will either be Exhibit 300 or 300-1.</td> <td>T</td> <td>F</td> <td>F</td> <td>actual-exit-date name target-exit-date </td> </tr> <tr> <td><a href="#176748#">INVESTMENT-PROJECT</a></td> <td>An acquisition activity associated with the procuring and management of an asset or service throughout the asset's or service's life-cycle. Capital projects represent investments associated with the acquisition of capital assets and the management of that asset through its life-cycle after the initial acquisition. An IT Investment represents a special type of capital project (or investment). An Investment for an IT project has a corresponding Exhibit 300 and is represented by a summary line on an Exhibit 53. A Program may sponsor many Investments, but an Investment may only have one sponsoring Program. Many Programs, however, may support an Investment by contributing funds, and a Program may support many Investments.</td> <td>F</td> <td>F</td> <td>F</td> <td>"budget year" "curernt upi code" egov gpea "home land security" "investment load comment" "investment phase" "investment title" "investment type" name "omb investment type" "percent financial" "percent security" "planned completion date" "previous investment title" "previous upi code" </td> </tr> <tr> <td><a href="#176749#">INVESTMENT-PROJECT (OTHER RELATIONS)</a></td> <td>Sub-Attributes of INVESTMENT-PROJECT; Relationships to Organizations, People, or Programs</td> <td>F</td> <td>F</td> <td>F</td> <td>"business focus areas" "contributing organizations" "contributing programs" "mbt recommendations" "organization roles" "project investment roles" "sponsoring program" </td> </tr> <tr> <td><a href="#176750#">INVESTMENT-PROJECT (REFERENCE MODEL INFORMATION)</a></td> <td>Sub-Attributes of INVESTMENT-PROJECT; Relationships to FEA Reference Models</td> <td>F</td> <td>F</td> <td>F</td> <td>"associated brm sub-functions" "associated prm - end outcomes" "associated prm - intermediate outcomes" "associated srm - components" "associated trm - standards" "primary brm sub-function" </td> </tr> <tr> <td><a href="#176751#">INVESTMENT-PROJECT (SOA)</a></td> <td>Sub-Attributes of INVESTMENT-PROJECT; Relationships to SOA Artifacts produced</td> <td>F</td> <td>F</td> <td>F</td> <td>"enterprise level solutions presentation" "final solution requirements document" "findings and recommendations presentation" "implemented solution" "ooa application security group requirements" "ooa architectural decisions" "ooa glossary" "ooa non functional requirements" "ooa requirements matrix" "ooa test strategy" "ooa user requirements" "ooc backup and recovery plan" "ooc build procedures" "ooc deployable components" "ooc help manual" "ooc operations guide" "ooc source code" "ooc test results" "ooc test specification" "ood acceptance test plan" "ood application resource descriptions" "ood deployment plan" "ood detailed test plan" "ood enterprise information and data stores definition" "ood persistence design specifications" "ood service descriptions" "ood ui specification and navigation detail" "policy memo(s)" "proposal evaluation criteria" "soa team" "systems development compliance document" "training strategy/curriculum" </td> </tr> <tr> <td><a href="#176808#">INVESTMENT-PROJECT/ORG-ROLE</a></td> <td>This associative entity INVESTMENT-PROJECT/PERSON-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>Delete "investment project" name organizations </td> </tr> <tr> <td><a href="#176809#">INVESTMENT-PROJECT/PERSON-ROLE</a></td> <td>This associative entity INVESTMENT-PROJECT/PERSON-ROLE will be implemented as a matrix (or other means to be determined) in system architect to resolve the many to many relationship that is on either side of the / of the entity name.</td> <td>F</td> <td>F</td> <td>F</td> <td>Delete "investment project" name person </td> </tr> <tr> <td><a href="#176746#">INVESTMENT/MBT-RECOMMENDATION</a></td> <td>Updated via Matrix Investment Project to MBT Recommendation Cell property is Investment Status.</td> <td>F</td> <td>F</td> <td>F</td> <td>"architectural status" columndefinition "investment status" name "roll out phase" rowdefinition </td> </tr> <tr> <td><a href="#176766#">ISSUE</a></td> <td>None</td> <td>T</td> <td>F</td> <td>F</td> <td>"issue status" name </td> </tr> <tr> <td><a href="#176742#">LINE-OF-BUSINESS</a></td> <td>An FEA BRM Line of business. The LINE-OF-BUSINESS inherits attributes from BRM-TIER. The complete As-Is DOI Business Architecture for the following business areas: Fire Management - DOI will extend the FEA BRM Line of Business to include Fire Management. Law Enforcement Indian Trust - DOI will extend the FEA BRM Line of Business to include Indian Trust (To Be Decided by Trust TEA team). Financial Management Recreation</td> <td>T</td> <td>F</td> <td>F</td> <td>"child sub functions" "fea code" "parent business area" </td> </tr> <tr> <td><a href="#176648#">LOCATION-NODE</a></td> <td>A Location Node could be a building, city, center, room, or other designation of a physical place.</td> <td>F</td> <td>F</td> <td>T</td> <td>"address 1" "address 2" city Delete Name "node type" "participating organizations" state "sub location noes" </td> </tr> <tr> <td><a href="#176767#">MBT-CATEGORY</a></td> <td>See MBT Blueprint Step 5 for Categorization of Findings and Recommendations</td> <td>T</td> <td>F</td> <td>F</td> <td>"child mbt categories" name "parent mbt category" </td> </tr> <tr> <td><a href="#176768#">MBT-CRITERIA</a></td> <td>See MBT Blueprint Step 5 for Criteria guidance of Findings and Recommendations</td> <td>T</td> <td>F</td> <td>F</td> <td>name type </td> </tr> <tr> <td><a href="#176769#">MBT-CRITERIA/BUSINESS-FOCUS</a></td> <td>Associative between these two objects</td> <td>F</td> <td>F</td> <td>F</td> <td>"business focus area" "mbt criteria" "mbt issues" name rationale score </td> </tr> <tr> <td><a href="#176770#">MBT-CRITERIA/SYSTEM</a></td> <td>Associative between these two objects</td> <td>F</td> <td>F</td> <td>F</td> <td>"mbt criteria" "mbt issues" name rationale score system "system version" </td> </tr> <tr> <td><a href="#176771#">MBT-FINDING</a></td> <td>See MBT Blueprint Step 5 for Criteria on Blueprint Findings</td> <td>F</td> <td>F</td> <td>F</td> <td>"business drivers" "mbt categories" "mbt recomendations" name "stakeholder categories" </td> </tr> <tr> <td><a href="#176772#">MBT-RECOMENDATION-CATEGORY</a></td> <td>See MBT Blueprint Step 5 for Categorization of Recommendations</td> <td>T</td> <td>F</td> <td>F</td> <td>"child mbt recomendation categories" name "parent mbt recomendation category" </td> </tr> <tr> <td><a href="#176773#">MBT-RECOMMENDATION</a></td> <td>See MBT Blueprint Step 5 for Criteria on Blueprint Recommendations</td> <td>F</td> <td>F</td> <td>F</td> <td>"best practice classification" "business case" "child recommendations" "dependant recommendations" "end outcomes" "fy(04) o&amp;m funding" "intermediate outcomes" "mbt recomendation category" "mbt tactical areas" name "planning period" priority "protfolio manager prioritization" "recomendation type" "tactical solution - cost estimate" "tactical solution - level of effort" </td> </tr> <tr> <td><a href="#176774#">MBT-RECOMMENDATION/MBT-STATUS</a></td> <td>Look up table for MBT Status where MBT Recommendation is NULL. Should be set list of status choices when added to BFA become unique to that Recommendation.</td> <td>F</td> <td>F</td> <td>F</td> <td>name recommendation "status begin date" "status comment" "status end date" </td> </tr> <tr> <td><a href="#176775#">MBT-STATUS</a></td> <td>Captures the Status of what MBT Step this blueprint or business focus area is in</td> <td>T</td> <td>F</td> <td>F</td> <td>name </td> </tr> <tr> <td><a href="#176776#">MBT-TACTICAL-AREA</a></td> <td> </td> <td>T</td> <td>F</td> <td>F</td> <td>name </td> </tr> <tr> <td><a href="#176793#">MEASURE</a></td> <td>A measurable indicator of the Intermediate Outcome that can be systematically tracked to assess progress made in achieving predetermined End Outcome goals