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> | + | <tr valign="top"><td>acceptable</td><td>Meeting stakeholder expectations that can be shown to be reasonable or merited (Source: ISO/IEC Std. 38500:2008, Corporate governance of information technology, ISO/IEC, 2008)</td></tr> |
| − | <tr valign="top"><td>BCA</td><td> | + | <tr valign="top"><td>acceptance criteria</td><td>(1) The criteria that a system or component must satisfy in order to be accepted by a user, customer, or other authorized entity (Source: ISO/IEC/IEEE Std. 24765:2010, Systems and software engineering—Vocabulary, ISO/IEC/IEEE, 2010) <br />(2) Those criteria, including performance requirements and essential conditions, which must be met before project deliverables are accepted. (Source: A Guide to the Project Management Body of Knowledge [PMBOK[R] Guide]—Fourth Edition)</td></tr> |
| − | <tr valign="top"><td>CBA</td><td> | + | <tr valign="top"><td>acquisition</td><td>(1) The process of obtaining a system, product, or service and ensuring its successful implementation. Acquisition also includes ensuring that proper mechanisms are in place to monitor the supplier’s/vendors’ performance in providing support and fulfilling other contractual obligations. Original to ITBOK.<br />(2) The process of obtaining a system or software product (Source: IEEE Std. 1062-1998, IEEE Recommended Practice for Software Acquisition, IEEE, 1998)<br />(3) The process of obtaining a system, software product or software service (Source: ISO/IEC 12207:2008, Systems and software engineering—Software life cycle processes, 4.2)<br />(4) The process of obtaining a system product or service (Source: ISO/IEC 15288:2008, Systems and software engineering—System life cycle processes, 4.2)</td></tr> |
| + | <tr valign="top"><td>acquisition strategy</td><td>Specific approach to acquiring products and services that is based on considerations of supply sources, acquisition methods, requirements specification types, contract or agreement types, and related acquisition risks (Source: ISO/IEC 24765:2009, Systems and software engineering vocabulary)</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>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>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> | + | <tr valign="top"><td>constraint</td><td>(1) An externally imposed limitation on system requirements, design, or implementation or on the process used to develop or modify a system (IEEE Std. 29148-2011, Systems and software engineering—Life cycle processes—Requirements engineering, IEEE, 2011) <br />(2) A statement that expresses measurable bounds for an element or function of the system (IEEE Std. 29148-2011, Systems and software engineering—Life cycle processes—Requirements engineering, IEEE, 2011)</td></tr> |
| + | <tr valign="top"><td>contract</td><td>Binding agreement between two parties, especially enforceable by law, or a similar internal agreement wholly within an organization (Source: ISO/IEC 12207:2008, Systems and software engineering—Software life cycle processes, ISO/IEC, 2008)</td></tr> | ||
| + | <tr valign="top"><td>CSP</td><td>Cost schedule performance</td></tr> | ||
| + | <tr valign="top"><td>DoDAF</td><td>Department of Defense Architecture Framework, an architecture framework for the United States Department of Defense (DoD) that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views</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> | + | <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>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>ICT</td><td>Information and communications technology</td></tr> | ||
| Line 17: | Line 24: | ||
<tr valign="top"><td>ISO</td><td>International Organization for Standardization</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>ITIL</td><td>IT infrastructure library </td></tr> | ||
| − | <tr valign="top"><td>ITSC</td><td> | + | <tr valign="top"><td>ITSC</td><td>Information technology support center</td></tr> |
| − | <tr valign="top"><td>LCCE</td><td> | + | <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> | + | <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>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> | + | <tr valign="top"><td>resource management</td><td>The identification, estimation, allocation, and monitoring of the means used to develop a product or perform a service (Source: ISO/IEC/IEEE Std. 24765:2010, Systems and software engineering—Vocabulary, ISO/IEC/IEEE, 2010)</td></tr> |
| − | <tr valign="top"><td>RFP </td><td> | + | <tr valign="top"><td>RFI </td><td>Request for information </td></tr> |
| − | <tr valign="top"><td>RFQ</td><td> | + | <tr valign="top"><td>RFP </td><td>Request for proposal</td></tr> |
| − | <tr valign="top"><td>RFT</td><td> | + | <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>risk</td><td>A function of the probability of occurrence of a given threat and the potential adverse consequences of that threat's occurrence (Source: ISO/IEC Std. 15026-3:2011, Systems and software engineering—Systems and software assurance—Part 3: System integrity levels, ISO/IEC, 2011)</td></tr> | ||
| + | <tr valign="top"><td>SaaS</td><td>Software as a Service</td></tr> | ||
<tr valign="top"><td>SFIA</td><td>Skills Framework for the Information Age</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 (Source: A Guide to the Project Management Body of Knowledge [PMBOK[R] Guide], Fourth Edition)</td></tr> |
<tr valign="top"><td>TOGAF</td><td>The Open Group Architecture Framework </td></tr> | <tr valign="top"><td>TOGAF</td><td>The Open Group Architecture Framework </td></tr> | ||
| − | |||
</table> | </table> | ||
Revision as of 22:28, 28 August 2015
| Term | Meaning |
| acceptable | Meeting stakeholder expectations that can be shown to be reasonable or merited (Source: ISO/IEC Std. 38500:2008, Corporate governance of information technology, ISO/IEC, 2008) |
| acceptance criteria | (1) The criteria that a system or component must satisfy in order to be accepted by a user, customer, or other authorized entity (Source: ISO/IEC/IEEE Std. 24765:2010, Systems and software engineering—Vocabulary, ISO/IEC/IEEE, 2010) (2) Those criteria, including performance requirements and essential conditions, which must be met before project deliverables are accepted. (Source: A Guide to the Project Management Body of Knowledge [PMBOK[R] Guide]—Fourth Edition) |
| acquisition | (1) The process of obtaining a system, product, or service and ensuring its successful implementation. Acquisition also includes ensuring that proper mechanisms are in place to monitor the supplier’s/vendors’ performance in providing support and fulfilling other contractual obligations. Original to ITBOK. (2) The process of obtaining a system or software product (Source: IEEE Std. 1062-1998, IEEE Recommended Practice for Software Acquisition, IEEE, 1998) (3) The process of obtaining a system, software product or software service (Source: ISO/IEC 12207:2008, Systems and software engineering—Software life cycle processes, 4.2) (4) The process of obtaining a system product or service (Source: ISO/IEC 15288:2008, Systems and software engineering—System life cycle processes, 4.2) |
| acquisition strategy | Specific approach to acquiring products and services that is based on considerations of supply sources, acquisition methods, requirements specification types, contract or agreement types, and related acquisition risks (Source: ISO/IEC 24765:2009, Systems and software engineering vocabulary) |
| 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 |
| constraint | (1) An externally imposed limitation on system requirements, design, or implementation or on the process used to develop or modify a system (IEEE Std. 29148-2011, Systems and software engineering—Life cycle processes—Requirements engineering, IEEE, 2011) (2) A statement that expresses measurable bounds for an element or function of the system (IEEE Std. 29148-2011, Systems and software engineering—Life cycle processes—Requirements engineering, IEEE, 2011) |
| contract | Binding agreement between two parties, especially enforceable by law, or a similar internal agreement wholly within an organization (Source: ISO/IEC 12207:2008, Systems and software engineering—Software life cycle processes, ISO/IEC, 2008) |
| CSP | Cost schedule performance |
| DoDAF | Department of Defense Architecture Framework, an architecture framework for the United States Department of Defense (DoD) that provides visualization infrastructure for specific stakeholders concerns through viewpoints organized by various views |
| 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. |
| resource management | The identification, estimation, allocation, and monitoring of the means used to develop a product or perform a service (Source: ISO/IEC/IEEE Std. 24765:2010, Systems and software engineering—Vocabulary, ISO/IEC/IEEE, 2010) |
| RFI | Request for information |
| RFP | Request for proposal |
| RFQ | Request for quotation |
| RFT | Request for tender |
| risk | A function of the probability of occurrence of a given threat and the potential adverse consequences of that threat's occurrence (Source: ISO/IEC Std. 15026-3:2011, Systems and software engineering—Systems and software assurance—Part 3: System integrity levels, ISO/IEC, 2011) |
| SaaS | Software as a Service |
| 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 (Source: A Guide to the Project Management Body of Knowledge [PMBOK[R] Guide], Fourth Edition) |
| TOGAF | The Open Group Architecture Framework |
