Term
|
Definition
| A system requirement validation method that shows that a system performance metric, which is impractical to test, is met through calculations |
|
|
Term
|
Definition
| The chance that a voice or data call cannot be initiated due to lack of network resources. |
|
|
Term
|
Definition
| The average time of voice calls. Example: 12 minutes/call, or 0.2 hours/call. |
|
|
Term
|
Definition
| The average number of voice calls per unit time. Example: 50 calls/hour |
|
|
Term
|
Definition
| A type of user requirement that defines function and performance needed by a user or systems/network administrator to do their job |
|
|
Term
|
Definition
| A lifecycle phase go/no-go decision point, usually accompanied with a review of phase objectives and documentation. |
|
|
Term
|
Definition
| The person or organization who acts as the agent for users, and who typically funds a project |
|
|
Term
|
Definition
| The number of information bits in a data transaction |
|
|
Term
|
Definition
| A system requirement validation method which shows the presence of a required system function |
|
|
Term
|
Definition
| A user requirements collection method that consists of discovering, reading, and analyzing existing written information for relevant needs |
|
|
Term
|
Definition
| The acronym identifying the validation methods for system requirements, which are demonstration, test, analysis, and inspection |
|
|
Term
|
Definition
| A dimensionless measure of voice traffic intensity which is the product of Call Volume and Call Duration. |
|
|
Term
|
Definition
| A type user responsible for a business or organization being effective in meeting its overall mission |
|
|
Term
|
Definition
| The expected number of failures per unit time, which is the reciprocal of MTTF. |
|
|
Term
|
Definition
| A user requirements method that consists of eliciting requirements from a small group of representative users at meetings with project staff acting as a facilitator and transcriber |
|
|
Term
|
Definition
| A system requirement validation method that shows by visual examination that a system requirement is met |
|
|
Term
|
Definition
| A user requirements collection method that consists of first hand discussions with users and stakeholders |
|
|
Term
| Mean Time Between Failure |
|
Definition
| it is apparent that the times between failure is equal to the time to failure and the time to repair/restore |
|
|
Term
|
Definition
| The arithmetic average of a set of different times it takes for an equipment system, network, or service to cease successful operation. Also, the expected lifetime of an equipment, network, system, or service (expressed in hours, days, months, years). Services, systems, equipment and power have MTTFs, which means that MTTFs are either system requirements or component specifications. |
|
|
Term
|
Definition
| The arithmetic average of a set of different times required to reestablish an equipment, network, system, or service which includes diagnosis, travel, troubleshooting, replacement, repair, and testing time. Also, the expected time required to reestablish equipment, network, system or service (expressed in seconds, minutes, hours, days). Services, systems, equipment and power have MTTRs, which means that MTTRs are either system requirements or component specifications. |
|
|
Term
|
Definition
|
|
Term
|
Definition
| An individual who likes to operate and/or maintain a system, and who is best suited for the Operations Stage of a project/lifecycle. |
|
|
Term
|
Definition
| The portion of definition stage where the best architectural approach to meeting requirements is selected, identifying major components and estimating lifecycle costs. |
|
|
Term
| Network Definition Stage* |
|
Definition
| The first stage of a project, consisting of four sequential phases: requirements, concept, specification, and planning phases |
|
|
Term
| Network Enhancement Project* |
|
Definition
| A network project to significantly upgrade an existing operational network, with nontrivial disruption risk. Often offers users and administrators additional capabilities, introduces new technologies, and requires significant systems engineering effort, engineering expertise, and transition planning |
|
|
Term
| Network Infrastructure Project |
|
Definition
| A network/communication utilities or infrastructure within a new or existing building. Documentation should focus on facility “as-built” specifications to allow for a well-defined, low risk effort |
|
|
Term
| Network Integration Project* |
|
Definition
| One of the sequential phases of the implementation stage which assembles, configures, integrates, tests, and stages network equipment in preparation for network deployment/rollout, including the development of Network Operations and Maintenance manuals, and test reports |
|
|
Term
|
Definition
| A sequential portion of a lifecycle stage. For instance, the operations phase consists of the deployment phase, followed by the operations and maintenance phase |
|
|
Term
|
Definition
| A sequential period during the lifecycle that consists of phases. The three stages are definition, implementation, and operations. |
|
|
Term
|
Definition
| The logical sequence of incremental activities necessary to define, implement and operate a network over its lifetime. |
|
|
Term
| Network Operations Project* |
|
Definition
| A network project of small scope to upgrade an existing operational network with incremental refinements, using ample in-house technical expertise and having little risk of disruption |
|
|
Term
|
Definition
| The portion of the definition stage where the network project tasks, schedules, resources and responsibilities are identified and documented |
|
|
Term
| Network Project Archetype* |
|
Definition
| A categorical network project representative of those with similar purpose, characteristics and risks |
|
|
Term
| Network Project Complexity Factor |
|
Definition
• Range of network geographic dispersion, and number of user sites
• Sophistication or obsolescence of IT/Network staff, systems, equipment and applications
• Business process efficiency
• Continuity of leased (versus owned) network services
• Variability of network service characteristics not within direct control (such as Internet traffic)
• Rapidity of network technology evolution
• Evolving network security risks |
|
|
Term
|
Definition
| The probability a network service will operate continuously for a specific period of time. Alternately, the probability a network service will not fail over a specific period of time |
|
|
Term
| Network Requirements Phase* |
|
Definition
| The portion of a project where user and system requirements are identified, documented, and approved |
|
|
Term
| Network Service Availability* |
|
Definition
| The actual or expected fraction of time a network service is UP over a time interval of interest, also called “interval availability”. Alternately, the probability a network service is available at an instant |
|
|
Term
| Network Service Maintainability* |
|
Definition
| Maintainability is the chance a failed service will be restored by a specified period of time |
|
|
Term
| Network Service Unavailability* |
|
Definition
| The actual or expected fraction of time a network service is DOWN over a time interval of interest, also called “interval unavailability”). Alternately, the probability a network service is unavailable at an instant |
|
|
Term
| Network Specification Phase* |
|
Definition
| The portion of the definition stage where the necessary attributes of each major component are identified and documented. All major component attributes must collectively satisfy system requirements. |
|
|
Term
|
Definition
| A group of hierarchical elements and people that interact to provide voice, data, and/or image transfers with user acceptable performance and function |
|
|
Term
|
Definition
| A collection of nodes and links that cooperate to allow successful telecommunication functions such as voice, data, and/or image transfers. |
|
|
Term
| New Network Initiative Project* |
|
Definition
| A network project that provides a network where one did not exist before. Often introduces the latest technology to provide telecommunication functions and performance to users |
|
|
Term
|
Definition
By applying a proven methodology, success cannot be guaranteed, however the probability of success is significantly increased. The network project management methodology (Figure 6) has four elements:
• The Network Project Cycle
• Network Project Management Tools and Techniques
• Teamwork, and
• Project Communication |
|
|
Term
|
Definition
must be applied throughout the life of a network project to support the project management methodology. The project manager selects what tools and techniques will be used on a network project, and the experts on the team decide how to implement the selections.
• Leadership – leading the team
• Project Management Skills – training the project team
• Project Visibility – knowing what is going on
• Project Requirements Traceability – managing project requirements
• Project Planning – planning the work
• Project Risk Management – identifying and managing risk
• Project Organization – organizing the team
• Project Control – controlling deviations from plan
• Project Status – measuring progress
• Project Corrective Action – implementing effective corrective actions |
|
|
Term
|
Definition
| A continuous effort with a goal, a resource budget, and no scheduled end |
|
|
Term
|
Definition
| The means by which project members effectively share information among themselves, the users, and stakeholders |
|
|
Term
|
Definition
| The methods, tools and techniques used to shepherd a project from inception to completion. This process must balance the technical, cost, and schedule objectives of a project |
|
|
Term
|
Definition
| The one person with the responsibility and authority to meet project goals on time and on budget |
|
|
Term
|
Definition
| Project members commitment to work together cooperatively to achieve project goals |
|
|
Term
|
Definition
| A planned temporary effort with a goal, a scheduled beginning and end, and a resource budget. |
|
|
Term
|
Definition
| The expected time it takes to restore, which is the reciprocal of MTTR |
|
|
Term
|
Definition
Understanding the volume of data between sources and sinks is essential to determine aggregate flow requirements between locations. This is accomplished by combining the latency requirement and the data volume requirement for each source-sink pair to determine the communications capacity, expressed as Information Transfer Rate (ITR) as follows:
ITR = V (information bits) / L (seconds) |
|
|
Term
|
Definition
| Any individual, group or organization other than users who are affected by a requirement, concept, specification, design, installation, operation, or maintenance of a network system |
|
|
Term
|
Definition
| A user requirements method that consists of eliciting needs from users based on a questionnaire. |
|
|
Term
|
Definition
| The translation of user needs into the system attributes, architectural concept, and major component specifications necessary to either buy or build a system. Also includes the necessary methods to validate the delivered system meets need and is ready to turn the system over to system operators and administrators |
|
|
Term
| Systems Requirement Document* |
|
Definition
| A manuscript consisting of enumerated systems attributes necessary to meet each user requirement, tracing to user requirements from which they are derived, and identifying the system requirement validation method |
|
|
Term
|
Definition
| See Network System Requirement |
|
|
Term
|
Definition
| A function allowing sharing, or transfer, of information from a distance. Information can be voice, data or images. Sharing is from source to sink. A source or a sink can be people, computers, sensors, or other machines. |
|
|
Term
|
Definition
| A system requirement validation method, which shows that a measurable system performance metric is met |
|
|
Term
|
Definition
| The information transfer rate and/or Erlangs required between users at different locations |
|
|
Term
|
Definition
| An array reflecting the amounts of traffic flow between multiple locations |
|
|
Term
|
Definition
| The collection of people and organizations that have the need for capabilities to be addressed by a project, including executives, system administrators, and users. |
|
|
Term
| User Requirement Document* |
|
Definition
| A manuscript consisting of enumerated user needs/capabilities, interface requirements, and schedule requirements for capabilities |
|
|
Term
|
Definition
| A capability needed by users to solve a problem, achieve an objective, or support a business process. Alternately, the capabilities needed by those using an unspecified system to accomplish operational or organizational goals. The three types of user requirements are (1) capabilities, (2) interface requirements, and (3) schedule by which capabilities are required |
|
|
Term
|
Definition
| Those individuals (1) requiring a capability to meet a business/organizational goal, (2) requiring a capability to operate and maintain an IT/network system in an efficient manner, or (3) responsible for a business or organization being effective in meeting its mission |
|
|
Term
|
Definition
| A desired capability or solution not based on need |
|
|
