Difference between revisions of "Glossary"
From EITBOK
| Line 1: | Line 1: | ||
<table> | <table> | ||
<tr valign="top"><td width="15%">'''Term'''</td><td>'''Meaning'''</td></tr> | <tr valign="top"><td width="15%">'''Term'''</td><td>'''Meaning'''</td></tr> | ||
| + | <tr valign="top"><td>AOA</td><td>analysis of alternatives</td></tr> | ||
| + | <tr valign="top"><td>BCA</td><td>business case analysis</td></tr> | ||
| + | <tr valign="top"><td>CBA</td><td>cost benefit analysis</td></tr> | ||
| + | <tr valign="top"><td>CMMI</td><td>Capability Maturity Model Integration</td></tr> | ||
| + | <tr valign="top"><td>COBIT</td><td>Control Objectives for Information and Related Technology</td></tr> | ||
<tr valign="top"><td>conceptual design</td><td>Describes the proposed solution in a functional manner that could be easily understood by a future user, including what the solution will look like and how it will behave</td></tr> | <tr valign="top"><td>conceptual design</td><td>Describes the proposed solution in a functional manner that could be easily understood by a future user, including what the solution will look like and how it will behave</td></tr> | ||
| + | <tr valign="top"><td>CSP</td><td>cost schedule performance</td></tr> | ||
<tr valign="top"><td>domain</td><td>A specific sphere of activity or knowledge. A domain can correspond to the boundaries of an organization, a job function, or even a particular task.</td></tr> | <tr valign="top"><td>domain</td><td>A specific sphere of activity or knowledge. A domain can correspond to the boundaries of an organization, a job function, or even a particular task.</td></tr> | ||
<tr valign="top"><td>domain elicitation</td><td>Collecting the right information from SMEs, stakeholders, or consumers about how the solution should function</td></tr> | <tr valign="top"><td>domain elicitation</td><td>Collecting the right information from SMEs, stakeholders, or consumers about how the solution should function</td></tr> | ||
| + | <tr valign="top"><td>GSC</td><td>global standards collaboration</td></tr> | ||
| + | <tr valign="top"><td>HITSR</td><td>Healthcare Information Technology Standards Panel</td></tr> | ||
| + | <tr valign="top"><td>ICT</td><td>Information and communications technology</td></tr> | ||
| + | <tr valign="top"><td>IEEE</td><td>Institute of Electrical and Electronics Engineers</td></tr> | ||
| + | <tr valign="top"><td>INCITS</td><td>International Committee for Information Technology Standards</td></tr> | ||
| + | <tr valign="top"><td>ISO</td><td>International Organization for Standardization</td></tr> | ||
| + | <tr valign="top"><td>ITIL</td><td>IT infrastructure library </td></tr> | ||
| + | <tr valign="top"><td>ITSC</td><td>information technology support center</td></tr> | ||
| + | <tr valign="top"><td>LCCE</td><td>life cycle cost estimate</td></tr> | ||
<tr valign="top"><td>logical design</td><td>Defines objects, entities, their attributes, and their relationships. It also describes the business rules associated with these entities</td></tr> | <tr valign="top"><td>logical design</td><td>Defines objects, entities, their attributes, and their relationships. It also describes the business rules associated with these entities</td></tr> | ||
| + | <tr valign="top"><td>MOE</td><td>measures of effectiveness </td></tr> | ||
| + | <tr valign="top"><td>NIST</td><td>National Institute of Standards and Technology</td></tr> | ||
<tr valign="top"><td>physical design</td><td>Also called the technical design. Where the conceptual and logic designs are converted to a definition of how the solution will be implemented in hardware, software, and potentially other media. The physical design is developed by the construction team not by the requirements team.</td></tr> | <tr valign="top"><td>physical design</td><td>Also called the technical design. Where the conceptual and logic designs are converted to a definition of how the solution will be implemented in hardware, software, and potentially other media. The physical design is developed by the construction team not by the requirements team.</td></tr> | ||
| + | <tr valign="top"><td>RFI </td><td>request for information </td></tr> | ||
| + | <tr valign="top"><td>RFP </td><td>request for proposal</td></tr> | ||
| + | <tr valign="top"><td>RFQ</td><td>request for quotation</td></tr> | ||
| + | <tr valign="top"><td>RFT</td><td>request for tender</td></tr> | ||
| + | <tr valign="top"><td>SFIA</td><td>Skills Framework for the Information Age</td></tr> | ||
<tr valign="top"><td>SME</td><td>Subject matter expert</td></tr> | <tr valign="top"><td>SME</td><td>Subject matter expert</td></tr> | ||
<tr valign="top"><td>solution</td><td>A set of changes to the current state of an enterprise that will enable the enterprise to meet a need, solve a problem, or take advantage of an opportunity</td></tr> | <tr valign="top"><td>solution</td><td>A set of changes to the current state of an enterprise that will enable the enterprise to meet a need, solve a problem, or take advantage of an opportunity</td></tr> | ||
<tr valign="top"><td>SWOT</td><td>Strengths, weaknesses, opportunities. and threats involved in a project or in a business venture</td></tr> | <tr valign="top"><td>SWOT</td><td>Strengths, weaknesses, opportunities. and threats involved in a project or in a business venture</td></tr> | ||
| − | <tr valign="top"><td> | + | <tr valign="top"><td>TOGAF</td><td>The Open Group Architecture Framework </td></tr> |
| − | + | ||
<tr valign="top"><td> </td><td> </td></tr> | <tr valign="top"><td> </td><td> </td></tr> | ||
</table> | </table> | ||
Revision as of 23:32, 27 August 2015
| Term | Meaning |
| AOA | analysis of alternatives |
| BCA | business case analysis |
| CBA | cost benefit analysis |
| CMMI | Capability Maturity Model Integration |
| COBIT | Control Objectives for Information and Related Technology |
| conceptual design | Describes the proposed solution in a functional manner that could be easily understood by a future user, including what the solution will look like and how it will behave |
| CSP | cost schedule performance |
| domain | A specific sphere of activity or knowledge. A domain can correspond to the boundaries of an organization, a job function, or even a particular task. |
| domain elicitation | Collecting the right information from SMEs, stakeholders, or consumers about how the solution should function |
| GSC | global standards collaboration |
| HITSR | Healthcare Information Technology Standards Panel |
| ICT | Information and communications technology |
| IEEE | Institute of Electrical and Electronics Engineers |
| INCITS | International Committee for Information Technology Standards |
| ISO | International Organization for Standardization |
| ITIL | IT infrastructure library |
| ITSC | information technology support center |
| LCCE | life cycle cost estimate |
| logical design | Defines objects, entities, their attributes, and their relationships. It also describes the business rules associated with these entities |
| MOE | measures of effectiveness |
| NIST | National Institute of Standards and Technology |
| physical design | Also called the technical design. Where the conceptual and logic designs are converted to a definition of how the solution will be implemented in hardware, software, and potentially other media. The physical design is developed by the construction team not by the requirements team. |
| RFI | request for information |
| RFP | request for proposal |
| RFQ | request for quotation |
| RFT | request for tender |
| SFIA | Skills Framework for the Information Age |
| SME | Subject matter expert |
| solution | A set of changes to the current state of an enterprise that will enable the enterprise to meet a need, solve a problem, or take advantage of an opportunity |
| SWOT | Strengths, weaknesses, opportunities. and threats involved in a project or in a business venture |
| TOGAF | The Open Group Architecture Framework |
