The file's text, extracted by GovTribe without its formatting.
TSO IT Services Contract – Appendix B Glossary of Terms
| Agile Software Development |
| A set of principles and values followed to implement an iterative methodology and incremental (evolutionary) approach to software development. It is performed in a highly collaborative manner by self- organizing teams within an effective governance framework with "just enough" ceremony that produces high quality solutions in a cost effective and timely manner, thus meeting the changing needs of its stakeholders. |
| Artifact |
| In the software project development cycle, an artifact is any of the part of the plans used to create and develop the software. Artifacts communicate project information to software developers to ensure each person works individually or in unison. |
| Authoritative Data Source (ADS) |
| A recognized or official data production source with a designated mission statement or source/product to publish reliable and accurate data for subsequent use by customers. An authoritative data source may be the functional combination of multiple, or separate data sources. |
| Authority-to-Connect (ATC) |
| Grant approval to connect the system to a Network. |
| Authority-to-Operate (ATO) |
| The official management decision issued by a DAA or PAA to authorize operation of an information system and to explicitly accept the residual risk to agency operations (including mission, functions, image, or reputation), agency assets, or individuals. |
| Automated Information Systems (AIS) |
| A combination of computer hardware and computer software, data and/or telecommunications that performs functions such as collecting, processing, transmitting, and displaying information. MCTFS and OWS are examples of AISs maintained by TSO. |
| Balanced Score Card |
| A method and tool used by TSO for measuring a Division’s activities in terms of its vision and strategies, to give managers a comprehensive view of the performance within the organization. |
| Business Enterprise System (BES) |
| A term used to identify all the internal enterprise systems utilized by the TSO to perform a variety of business functions. The term encompasses the following systems as a group: DLT, JIRA, SQMS, SharePoint, and EMS. |
| Capability Maturity Model Integrated (CMMI) |
| Developed by the Software Engineering Institute (SEI) at Carnegie Mellon University, the CMMI is a framework that describes the key elements of an effective software process. The CMMI covers practices for planning, engineering, and managing software development and maintenance. |
| Change Management Plan |
| A process for managing changes to the TSO’s technology, systems or applications, hardware, tools, documentation, processes, as well as roles and responsibilities. |
| Change Request |
| Generically describes all changes including, but not limited to: System Change Requests (SCRs), both user identified and customer identified Production Trouble Reports (PTRs), TSO identified Internally Identified PTRs (IIPs), Test Discrepancy Reports (TDRs), Standalones, and Engineering Change Requests (ECRs). |
| Commercial-off-the-Shelf (COTS) |
| Hardware or software purchased from a vendor and adapted to a desired purpose. |
| Common Access Card (CAC) |
| A smart card about the size of a credit card that is the standard identification for active-duty military personnel, Selected Reserve, United States Department of Defense (DoD) civilian employees, and eligible contractor personnel. It is also the principal card used to enable physical access to buildings and controlled spaces, and it provides access to defense computer networks and systems. |
| Configuration Control Board (CCB) |
| The formal process where the System Change Requests (SCRs) submitted by the customer and estimated by the TSO are negotiated to determine which SCRs will be contained in the software release. |
| Contract Officer Representative (COR) |
| The TSO Government employee assigned to manage the daily operations of the contract. |
| Critical Computer Resource (CCR) |
| Consumable computer resources that must exist in sufficient quantity for an |
Information System to perform at an acceptable level. The most common, but not limited to, examples are storage, CPU and memory.
| Cybersecurity (CY) |
| Prevention of damage to, protection of, and restoration of computers, electronic communications systems, electronic communications services, wire communication, and electronic communication, including information contained therein, to ensure its availability, integrity, authentication, confidentiality, and nonrepudiation. |
| Data Call |
| When information is requested by higher authorities/headquarters or outside agencies, and a limited time is given to provide this information. |
| Data Marts |
| The access layer of the data warehouse environment that is used to get data out to the users. The data mart is a subset of the data warehouse that is usually oriented to a specific business line or team. Data marts are small slices of the data warehouse. Whereas data warehouses have an enterprise-wide depth, the information in data marts pertains to a single department. |
| Data Stores |
| A data repository of a set of integrated objects. These objects are modeled using classes defined in database schemas. Data store includes not only data repositories like data bases, it is a more general concept that includes also flat files that can store data. |
| Data Warehouse |
| A system used for reporting and data analysis. Integrating data from one or more disparate sources creates a central repository of data, a Data Warehouse (DW). Data warehouses store both current and historical data and are used for creating trending reports for senior management reporting such as annual and quarterly comparisons. |
| Decision Logic Table (DLT) |
| Used within TSO MCTFS and ODSE for managing design documents in the form of Decision Logic Tables (DLTs). The TSO has an organizational support tool called DLT-Web. |
| Defense Finance and Accounting Service (DFAS) |
| An agency of the United States Department of Defense under the direction of the Under Secretary of Defense (Comptroller). DFAS provides finance and accounting services for the civil and military members of the Department. |
| Defense Information Systems Agency (DISA) |
| A United States Department of Defense (DoD) combat support agency composed of military, federal civilians, and contractors. DISA provides information technology (IT) and communications support to the President, Vice President, Secretary of Defense, the military services, the combatant commands, and any individual or system contributing to the defense of the United States. |
| Defense Travel System (DTS) |
| A fully integrated, electronic, end-to-end travel management system that automates temporary duty travel (TDY) for the Department of Defense. It allows travelers to create authorizations (TDY travel orders), prepare reservations, receive approvals, generate travel vouchers, and direct deposit payment to themselves and the government charge card vendor, all via a single web portal available 24 hours a day, seven days a week. |
| Department of Defense (DoD) |
| An executive branch department of the federal government of the United States, charged with coordinating and supervising all agencies and functions of the government concerned directly with national security and the United States Armed Forces. |
| Department of Defense Architecture Framework (DoDAF) |
| 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. |
| Department of the Navy (DON) |
| Established by an Act of Congress on 30 April 1798 to provide a government organizational structure to the United States Navy and, from 1834 onwards, for the United States Marine Corps. |
| Design Peer Review (DPR) |
| Evaluation of the accuracy and completeness of design deliverables by Designers and their peers. |
| Estimating and Management System (EMS) |
| A GOTS application that was created to automate and support the business functions related to change requests received by the customer. EMS tracks system change requests and the attributes related to system change request estimates and releases. |
| Facilities Systems Branch (FSB) |
| Provides software development, maintenance, and system support for installations, facilities, and environment information technology systems used within the Marine Corps Installations Command. |
| Function Points |
| A measure of software size. A product of 5 defined data components (inputs, outputs, inquiries, files, external interfaces) and 14 weighted environment characteristics (data comm., performance, reusability, etc.). |
| Functional Area |
| Also known as a business area. A Functional Area (e.g., personnel) is composed of one or more functional activities (e.g., recruiting), each of which consists of one or more functional processes (e.g., interviews). |
| Functional Area Manager (FAM) |
| Organizations or person(s) responsible for the development and management of system, application, and database portfolios used to support the processes within that functional area. |
| Functional Data Manager (FDM) |
| Organization or person(s) designated by the respective FAM to produce and control structuring of data and metadata within functional activities, information systems, and computing and communications infrastructures. |
| Government-off-the-Shelf (GOTS) |
| Hardware or software purchased from the Government and adapted to a desired purpose. |
| Help Desk |
| Provides Marine Corps-wide support to travelers & system users of DTS, MROWS, and MOL. Performs such activities as curriculum development and sustainment, training, Post Payment Reviews, Debt Management, staff assistance visits, and administers the travel card compliance tool. |
| Information Assurance Vulnerability Alerts (IAVA) |
| An announcement of a computer application software or operating system vulnerability notification in the form of alerts, bulletins, and technical advisories identified by DoD-CERT, a division of the United States Cyber Command. |
| Integrated Product Team (IPT) |
| A multidisciplinary group of people who are collectively responsible for delivering a defined product or process. |
| JIRA |
| A commercial-off-the-shelf issues management tool that the government has tailored to support the formal assignment of specific tasks to the Contractor and receipt of task deliverables/completion. |
| Joint Application Development (JAD) |
| A methodology used to help users accurately define the requirements of a system. Guided by a session leader, users and technical personnel design systems together in structured group sessions. The end product from a JAD is a SCR. |
| Labor Reporting System Tool (LRS Web) |
| LRS Web is used to track all the time and effort expended on any TSO project for project management and performance management purposes. |
| Life Cycle Methodology (LCM) |
| Software engineering methodologies, e.g., waterfall, spiral, iterative. |
| Local Hours |
| Hours local to the time zone the employee and/or hardware resources are currently located. |
| Management Reviews (MR) |
| A review that provides a forum for the Contract Program Manager, COR and key government staff to discuss contractor performance, resources and workload assignments, process improvement opportunities, personnel issues, and other topics of the Contractor’s or Government’s choosing. |
| Manpower Information Systems Support Activity (MISSA) |
| Located in Kansas City, Missouri and is the HQMC (MI-Manpower Management Information Systems Support Division) liaison to the MCPSD and TSO. The MISSA assists reporting unit commanders in timely and accurate reporting, problem resolution, quality control, and retrieval of MCTFS manpower, personnel, and pay information while deployed and or in garrison. |
| Marine Corps Information Technology Center (MCITC) |
| An approved DON centralized data center for the Marine Corps located in Kansas City, Missouri. |
| Marine Corps Enterprise Information Technology Services (MCEITS) |
| Provides enterprise IT services and a data hosting environment with supporting communications, computing network information assurance, and enterprise services infrastructure for the USMC. |
| Marine Corps Network Operations and Security Center (MCNOSC) |
| Provides global network operations and computer network defense of the Marine Corps Enterprise Network (MCEN) in order to facilitate seamless information exchange in support of Marine and Joint Forces operating worldwide. |
Marine Corps Pay Requirements Directorate (MCPRD)
The Marine Corps Pay Requirements Directorate facilitates and generates system changes for the Marine Corps Total Force Family of Systems to provide timely and accurate pay services to the service member, continuing government activities to retirees, and to fully support payroll accounting requirements.
| Marine Corps Publication Distribution System (MCPDS) |
| Used to manage initial distribution of publications, as well as reprints for stock replenishments and filling publication backorders. The MCPDS is also used by publication clerks throughout the operating forces worldwide to order publications, check status on outstanding orders, report receipts and manage local unit libraries. |
| Meta-Data Repository (MDR) |
| A tool utilizing a COTS product user interface with a DB2 database to centrally locate information that defines a description of stored data for systems and applications sustained and maintained by the TSO. |
| Mid-Tier Application |
| The Application layer, or middle tier, of a three-tier architecture web-based application that is modeled following the N-Tier application architecture. They are deployed on commodity x86 chipset hardware. |
| Mid-Tier Environment |
| The collection of all of the mid-tier applications and the overarching ecosystem of servers, network infrastructure, and storage devices that those applications are deployed on. |
| Organizational Support Tools |
| TSO customized tools used to support the organizational mission and its customers. These tools include: DLT, JIRA, SQMS, SharePoint, SETT, and EMS. |
| Post Implementation Review (PIR) |
| A formal review conducted after the implementation of a software release. A PIR is intended to determine the original and final objectives of the release, in terms of performance (end product), cost and schedule and to determine whether these objectives were met. The PIR also determines what factors contributed to the success of the release and, where things went wrong, determine the basic causes. The outcome of the PIR could include policy and procedure changes to eliminate causes of missed objectives or other problems. |
| Program Manager |
| The Program Manager is the organization or person(s) responsible for the acquisition, development, and execution of a solution to a validated operational requirement. |
| Program Management Plan |
| The documented approach of the Program Manager to support successful execution of a validated operational requirement. |
| Programming Peer Review |
| A programming (or code) peer review is a review that systematically examines computer source code intended to find and fix errors overlooked in the initial development phase, improving overall code quality. |
| Quality Assurance Plan |
| The SQA Plan describes the quality assurance activities that will be performed by the system including the audits and reviews that will be performed on the processes used by the system and the work products developed by the system. |
| Release Management Plan |
| The Release Implementation Plan describes the release implementation activities that will be performed by the system. Each system develops a release implementation plan that addresses the establishment of baselines, release environments, release instructions, and release certification. |
| Remark & Table Spreadsheet |
| Maintained by MCTFS Design and documents the addition, deletion or a change of name to a MCTFS remark or to a MCTFS Table. |
| Scrum |
| An iterative and incremental agile software development framework for managing software projects and product or application development. Its focus is on "a flexible, holistic product development strategy where a development team works as a unit to reach a common goal" as opposed to a "traditional, sequential approach". |
| SharePoint |
| A web application framework and platform developed by Microsoft that integrates intranet, content management, and document management. |
| SIT/SAT Readiness Review |
| System Integration Test (SIT) verifies that the combined previously tested software units produced a fully operational product, and through the use of test conditions, verifies the operational product, changed by the SCR, provides the desired outcome. System Acceptance Test (SAT) is the user testing of user manual and implementation procedures. Approval of this stage of the testing will result in distribution of the final product to the end users and/or turn on the application for mass use. |
| Software Development Lifecycle (SDLC) |
| The period that starts when a software product is conceived and ends when the product is no longer available for use |
| Software Engineering Institute (SEI) |
| A member of Carnegie Mellon University that sets the standards for CMMI. |
| Software Implementation |
| The migration of software changes to the production environment, typically in conjunction with a Software Release. |
| Software Release (SR) |
| All SCRs and PTRs that are packaged into a common schedule for a given software implementation date. All changes are intended to implement into the production environment, as a whole, during a single release window. |
| Standalone |
| SCRs received during the actual development phases. These SCRs may implement before, with or after the Software Release. The number and size of the standalones can have significant impact on the Software Release. |
| Subject Matter Expert (SME) |
| An individual well versed in a particular discipline or subject area that is called upon to provide expert knowledge and experience to working groups or assessment interviews. |
| System Change Request (SCR) |
| The mechanism that the functional manager or TSO Customer uses to request a change to TSO supported systems applications. It serves as the identifier that is used for all changes to systems modules and for tracking status through the life-cycle. Also referred to as projects, changes and modifications, customer generated requests for systems alterations. |
| System Owner |
| The organization responsible for the business functions that the AIS system supports. |
| Technical Solution Walkthrough |
| A MCTFS internal meeting to review, understand the requirements, and develop a solution for a CCB or Standalone SCR. The attendees are practitioners from |
MCTFS Design, Programming, and Test. Technical Solution Walkthrough is used for specific SCRs which contain new or complex processing.
| Technology Services Organization (TSO) |
| Provides development, design, production, and maintenance support of information technology systems, particularly pay, personnel and accounting systems, for the Marine Corps as well as DoD components, services, and agencies. |
| Temporary Duty Travel (TDY) |
| Also known as "temporary additional duty" (TAD), "temporary duty travel" (TDT) or "temporary duty" (TDY) refers to a United States Government employee travel assignment at a location other than the employee's permanent duty station. |
| Test Peer Review |
| A quality and procedural review that is held to determine proposed testing and scenario details and to ensure complete and quality coverage of the software being tested. |
| TSO Customers |
| TSO customers typically are the functional managers for TSO supported systems. Principal customers include MISSA and MCPRD for the MCTFS FoS; and all P&R Branches and DFAS for the SABRS FoS. |
| Web Services |
| A standardized way of integrating web-based applications using open standards over an Internet Protocol backbone. Web services allow applications developed in various programming languages and running on various platforms to exchange data without intimate knowledge of each application's underlying IT systems. |
| Work Breakdown Structure (WBS) |
| A deliverable-oriented decomposition of a project into smaller components. It provides the necessary framework for detailed cost estimating and control, along with providing guidance for schedule development and control. |
United States Marine Corps