|
|
| Table - set of data elements (values) that is organized using a model of vertical columns (which are identified by their field name) and horizontal rows (records). |
| Target Date - (1) Date an activity is planned to start or end. (2) Date generated by the initial CPM schedule operation and resource allocation process. |
| Tasks - The smallest unit of work performed by an organization, which is limited in duration and scope. |
| Technical Complexity - This represents the technical difficulty or risk associated with a particular business issue or opportunity that is driving a need for change. |
| Technical Reference Model - is a framework to describe how standards and technologies support the secure delivery, exchange, and construction of Service Components. |
| Technical Requirements - Description of the features of the deliverable in detailed technical terms to provide project team members with crucial guidance on what needs to be done on the project. |
| Technical Walkthrough - A thorough review of the object, using the detail specifications, test plan, test results, and shop standards, to ensure that the object construction is sound and meets the design. |
| Technology Trends - Widely recognized forces or patterns of change that can be used to infer or predict the future of technology. |
| Template - A guideline for a document outline and its contents. A template is used to record the work activities, discussions, findings, and specification to help achieve a common understanding. In addition it is used to provide a consistent look and feel to the project documentation. |
| Templates - Set of guidelines that provide sample outlines, forms, checklists, and other documents. |
| Test Plan - Defining responsibilities, identifying test methodologies and phases, identifying the test environment throughout the project lifecycle. |
| Test Scripts - A record of actions to be performed, expected results, and actual results used to test the effect of the modifications. |
| Test Strategy - The Test Strategy is used to help the project office clarify expectations with the user and sponsor (and contractor) regarding their obligations in the testing and acceptance of the new system in the user environment. The prime contractor may also prepare a Master Test Plan (as part of the contract) that describes their approach to all testing phases and the activities for which they are responsible. |
| Threshold - Time, monetary unit, or resource level, placed on something, which is used as a guideline that, if exceeded, causes some type of management review to occur. |
| Timeline - A schedule showing a planned order or sequence of events and procedures. |
| Traceable - The origin of each requirement is clear and can be traced backward to the stakeholder need forward to other products. |
| Traceability - 1) Ability to trace the history, application, or location of an item or activity by means of recorded identification. (2) Ease with which a project can be traced forward from specifications to the final deliverable or backward from the deliverable to the original specifications in a systematic way. |
| Trade-Off - Giving up or accepting one advantage, or disadvantage, to gain another that has more value to the decision maker. For example, accepting the higher cost (a disadvantage) of a project because there will be more functionality (an advantage) in the delivered product. |
| Transition Support Plan - This plan essentially serves as a final review prior to operations and maintenance and details the service/performance level agreement that all stakeholders share. |
| Travel Budget - The Travel budget is established to allocate funds for travel on behalf of the project. Typically travel includes site visits to the counties/local offices to prepare for implementation, attendance at federal or national conferences and select training symposiums. The travel budget is submitted annually in accordance with the DOF process. |
