|
|
| Scalability - The ability to use the same applications and systems on all classes of computers from personal computers to supercomputers and for those applications to continue to function well as it (or its context) is changed. |
| Schedule - Time-sequenced plan of activities or tasks used to direct and control project execution. Usually shown as a milestone chart, Gantt or other bar chart, or tabular listing of dates. |
| Schedule Baseline - Approved project schedule that serves as the basis for measuring and reporting schedule performance.
|
| Schedule Control - Management of project schedule changes. |
| Schedule Management Plan - This document describes the process and how the defined tool (e.g. MS Project) is used to implement the methodology for establishing, managing, and modifying the Master Project Schedule and Schedule Baseline, and coordinating inputs from the contractor and county/local office work plans and schedules. |
| Schedule Performance Index (SPI) - Analysis of activity sequences, activity durations, and resource requirements to prepare the project schedule. |
| Schedule Revision - Changes to the scheduled start and finish dates in the approved project schedule. |
| Schedule Risk - Risk that jeopardizes completing the project according to the approved schedule |
| Schedule Update - Schedule revision to reflect the most current status of the project. |
| Schedule Variance (SV) - (1) Difference between the scheduled completion of an activity and its actual completion. (2) In earned value, BCWP less BCWS; an SV of less than zero shows that project activity is behind schedule. |
| Scope - The sum of the products and services to be provided as a project. |
| Scope Change - Modification to the agreed-upon project scope as defined by the approved WBS. |
| Scope Change Control - Process of:
(1) influencing the factors that cause scope changes to help ensure that the changes are beneficial,
(2) determining that a scope change has occurred, and
(3) managing the changes if and when they occur.
|
| Scope Creep - Gradual progressive increase of the project's scope such that it is not noticed by the project management team or the customer. Occurs when the customer identifies additional, sometimes minor, requirements that, when added together, may collectively result in a significant scope change and cause cost and schedule overruns. |
| Scope Definition - Division of the major deliverables into smaller, more manageable components to:
(1) improve the accuracy of cost, time, and resource estimates;
(2) define a baseline for performance measurement and control; and
(3) facilitate clear responsibility assignments.
|
| Scope Of Work - Description of the totality of work to be accomplished or resources to be supplied under a contract. |
| Service Area - is a technical tier that supports the secure construction, exchange, and delivery of business or service components. Each Service Area groups the requirements of component based architectures within the Government into functional areas. |
| Service Category - is a sub-tier of the Service Area to classify lower levels of technologies, standards, and specifications in respect to the business or technology function they serve. |
| Service Level Agreement (SLA) - This document describes the system performance and service level expectations and requirements for the prime contractor during the Implementation and M&O phases. The SLA includes target performance measures, unacceptable measures and penalties for not meeting required service levels. Usually included or referenced in a SOW and contract. |
| Service Oriented Architecture (SOA) - An architecture that provides for reuse of existing business services and rapid deployment of new business capabilities based on existing capital assets. Major components include an Enterprise Service Bus, Service Registry, SOA Governance, Federated Identity Management, which interoperate via standard interfaces and protocols. |
| Service Reference Model - is a framework classifying Service Components according to the capabilities they provide to business functions. |
| Significant Variance - Difference between the plan and actual performance that jeopardizes the project objectives. |
| Sister Project - A sister project is an OSI project that is at a point in its life cycle where it can accept the additional workload to support a new project. The objective of Establish a Sister Project is to setup a working relationship with an existing OSI project that will allow the new project to leverage existing location, staff, infrastructure and, if possible, understanding of the customer. A sister project is an OSI project that is at a point in its life cycle where it can accept the additional workload to support a new project. The objective of Establish a Sister Project is to setup a working relationship with an existing OSI project that will allow the new project to leverage existing location, staff, infrastructure and, if possible, understanding of the customer. |
| SLA for the Data Center - If a data center will be hosting or providing services for the system, a Service Level Agreement with the Data Center is needed. The SLA describes the system performance and service level expectations and requirements for the data center during the Development, Implementation and M&O phases. The SLA includes target performance measures, unacceptable measures and penalties for not meeting required service levels. Usually referenced as part of a SOW and contract. |
| SMART - The five elements for a well-worded objective, namely Specific, Measurable, Achievable, Realistic, Time Bound. |
| Software Component - An object, or collection of objects offering a predefined service's or event's, possessing the ability to communicate with or be used by other components. A component is a piece of a solution that can be isolated as a set of functions and features that relates to other components within the same solution. |
| Software Engineering Institute (SEI) - U.S. government Federally Funded Research and Development Center (FFRDC), operated by Carnegie-Mellon University in Pittsburgh, Pennsylvania, under contract to the U.S. Department of Defense (DOD). SEI's mission is to improve software engineering processes for the DOD. Has become well-known worldwide for its software Capability Maturity Model (CMM), used by software development professionals to improve the processes by which they develop application programs. |
| Solution - Determining what should be done to best support your current and future business strategy and needs. The deliverables clearly describe the solutions goals and scope, the capabilities to be implemented, and the risks associated with the program of work that must be carried out. |
| Solution Architect - An individual responsible for developing solution architecture frameworks and solution set designs. The Solution Architect’s primary role is to translate what is required to run the business (from the Business and Information Architecture gaps and migration strategies) into actual design specifications and models that can be supported and fulfilled by components within the Technology Architecture. |
Solution Architecture - An architecture within Enterprise Architecture that guides the solution architect in the design of a particulate solution set. For each solution set, Solution Architecture assists in:- The identification of business requirements
- The determination of the design specifications necessary to deliver the business requirements
- The development of the solution set design. Integrating designs based on details with the Business, Information and Technology blueprints
|
| Solution Architecture Model - The graphical representation of concepts to portray a desired future state of a business solution, as well as an undesirable current state, which is used for communicating, analyzing, testing, simulating, or exploring options. |
| SOW for the Data Center - If a data center will be hosting or providing services for the system, a Statement of Work (SOW) with the data center is needed. The SOW describes the specific tasks, activities and deliverables that the data center will provide to support the system. The SOW is used with some type of contract vehicle to establish binding responsibility for the work to be performed. An SLA is usually included or referenced by the SOW. |
| Span Of Control - Number of individuals (direct reports) that a manager or project manager can effectively manage. The number will vary, but generally, a manager should have no more than ten direct reports. Once that number is exceeded, the organizational structure needs to be reviewed and changed. |
| Specification - Description of the technical requirements for a material, product, or service, including the criteria for determining that the requirements have been met. Generally, three types of specifications are used in projects: performance, functional, and design. |
| Sponsor - The individual or group who champions the project and provides the resources, in cash or in kind. Provides the executive leadership, priority and commitment to the project, its goals and objectives. This is the manager representing the organizational unit most affected by the business change. If several organizational units will be heavily impacted by the business change, this is an executive manager with authority over the majority of the organizational units. |
| Stakeholders - (1) Individuals and/or groups who are involved in or may be affected by project activities. (2) The people who have a vested interest in the outcome of the project. |
| Standard - (1) Basis for uniformly measuring or specifying performance. (2) Document used to prescribe a specific consensus solution to a repetitive design, operations, or maintenance situation. (3) Document approved by a recognized body that provides for common and repeated use, rules, guidelines, or characteristics for products, processes, or services; however, compliance is not mandatory. (4) Documentation that establishes engineering and technical limitations and applications of items, materials, processes, methods, designs, and engineering practices. |
| Statement Of Work (SOW) - The SOW describes the specific tasks, activities and deliverables the contractor will provide to the project. The SOW is used with some type of contract vehicle to establish binding responsibility for the work to be performed. An SLA may be included or referenced by the SOW, if appropriate. |
| Status Report - (1) Description of where the project currently stands; part of the performance reporting process. (2) Formal report on the input, issues, and actions resulting from a status meeting. |
| Strategic Plan - A plan that is tightly tied to the organization's mission, vision, values and objectives, and depends heavily on high-level coordination and influences management to achieve their goals. |
| Strategy - Action plan to set the direction for the coordinated use of resources through programs, projects, policies, procedures, and organizational design and establishment of performance standards. |
| Strengths- Weaknesses-Opportunities-Threats (SWOT) Analysis - Analysis used to determine where to apply special efforts to achieve desired outcomes. Entails listing: (1) strengths and how best to take advantage of them;
(2) weaknesses and how to minimize their impacts;
(3) opportunities presented by the project and how best to take advantage of them; and
(4) threats and how to deal with them.
|
| Structured Walkthrough - Systematic, comprehensive review of the requirements, design, or implementation of a system by a group of qualified experts. |
| Sub-process - A set of related activities and tasks within a process. |
| System Architecture - Manner in which hardware or software is structured, that is, how the system or program is constructed, how its components fit together, and what protocols and interfaces are used for communication and cooperation among the components, including human interaction. |
| System Design - Translation of customer requirements into comprehensive, detailed functional, performance, or design specifications, which are then used to construct the specific solution. |
| System Environment - The hardware and software platforms including development tools and databases, as well as the shop standards and styles, in which the system exists. |
| System Interface - The services, system, or mechanisms that a business system uses to gather or provide information. The source varies from external systems services or information repositories, or the internal data source which is managed by the business system. Physical interfaces among connecting parts of a system, or performance interfaces among various functional or product subsystems. |
| System Requirement - A condition or capability that must be met or possessed by a system to satisfy a condition or capability needed by a user(s). |
| System Requirements Specification (SyRS) - Developed by the project to describe the business and system requirements based on the user/sponsor needs. The SyRS is included or referenced in the RFP and forms the basis for the system. The prime contractor further refines the requirements in their Software Requirements Specification and resulting design documents. |
| System Testing - When a new or modified object is processed in combination with other objects to insure it works as part of the complete system. |
| System Test Summary Report - This report describes how test activities were performed and a summary of the results of the test. The report should provide a clear picture of what tests were performed, what types of problems were found, the severity of problems found, how the problems were resolved (or what is currently being done to resolve them), and if the system was sufficiently tested to provide confidence that the system is ready for the next phase. |
