Context ICT System
Identifying Physical Environment
Political Environment Cultural Environment
Social Norms In Scope

 

An information and communication technology system used to process and communicate information. The circumstances or setting in which an ICT system operates.
The physical surroundings, including natural elements such as landforms, water bodies, and climate. The process of recognizing or determining the characteristics or nature of something.
The collective beliefs, customs, values, behaviors of a particular group of people. The social, economic, and legal factors that impact the governance, policies, and decision-making within a society or country.
The activities, deliverables, and requirements that are included as part of a project. The accepted standards of behavior and beliefs established by a particular society or community.

 

Out Of Scope Scope Creep
Scope Statement Change Request
Project Constraints Project Objectives
Users Stakeholders

 

The uncontrolled expansion or addition of project scope , leading to potential delays and cost overruns. The activities, deliverables, and requirements that are explicitly not included as part of a project.
A document that identifies a change to the project scope and describes the impact on project cost, schedule, quality, or resources. A document that outlines the project objectives, deliverables, and boundaries, including what is in-scope and out-of-scope.
The SMART goals that a project aims to achieve within the defined scope. The limitations, restrictions, or boundaries within which a project must be executed, including factors like time, cost, resources, quality, and scope.
Individuals or groups who have an interest or investment in a project or organization. Individuals who interact with a system or software application.

 

End Users Customers
Clients Managers
Shareholders Developers
Designers Investors

 

People who purchase goods or services from a business. The final consumers or users of a product or service.
Individuals who oversee the operations and activities of a team or organization. Individuals or organizations that receive professional services from another.
Individuals or teams responsible for creating software or applications. Owners or holders of shares in a company.
Individuals or organizations that provide funds or resources for a project or venture. People who plan and create the visual and functional aspects of a product or system.

 

Existing System Legacy System
Paper Based System Migration
Digital Transformation Reliability
Accessibility Analog System

 

An outdated and often unsupported software or hardware system, still in use by an organization. An already implemented system that is currently in use.
The process of transferring data and functionality from one system to another. A system that relies on physical paper documents for storing and processing information.
The ability of a system to perform consistently and accurately over a period of time. The integration of digital technology into all areas of a business to fundamentally change how it operates.
A system that uses continuous signals or physical quantities to represent and process data, as opposed to digital systems that use discrete values. The ease with which a system can be accessed, understood, and used by people with disabilities.

 

Obsolete System Internal Constraints
External Constraints Resource Constraints
Legal Constraints Market Constraints
Technological Constraints Environmental Constraints

 

Factors within an organization that limit its operations or activities. A system that is no longer in use or considered relevant, usually due to advancements in technology.
Limitations in terms of time, money, personnel, or equipment available to an organization. Factors outside an organization that restrict its operations or activities.
Limits imposed by the characteristics and dynamics of the market in which an organization operates. Laws and regulations that impose restrictions on an organization's behavior or operations.
Restrictions imposed by the natural or physical environment in which an organization operates. Restrictions arising from the level of technology available or the ability to adopt new technologies.

 

Social Constraints Political Constraints
Economic Constraints Change Management
Change Agent Change Readiness
Change Control Change Resistance

 

Limitations imposed by political systems, governments, or political factors on an organization. Restrictions resulting from social norms, values, or cultural factors that affect an organization.
The process of planning, implementing, and monitoring changes in an organization in order to ensure successful adoption. Restrictions arising from economic conditions, such as inflation, recession, or currency fluctuations.
The state of preparedness and willingness among individuals and teams to embrace and support change. An individual or group responsible for driving and managing change within an organization.
The opposition or reluctance to change by individuals or groups within an organization. A systematic process for managing changes to a project, system, or organization, including assessing, approving, and implementing change requests.

 

Kotter Model Urgency
Guiding Coalition Vision
Communication Empowerment
Short-Term Wins Consolidation

 

The first step in the Kotter Model, creating a sense of urgency is about convincing people that change is necessary and must happen now. A change management model developed by John Kotter that provides a step-by-step approach for leading organizational change.
The desired future state or outcome that the organization aims to achieve through the change effort. A group of influential individuals formed to lead and support the change initiative throughout an organization.
Giving employees the necessary authority, autonomy, and resources to take ownership and make decisions. Open, honest, and continuous exchange of information between leaders and employees to keep everyone informed during the change process.
Embedding the changes into the organization's culture and ensuring they become the new way of doing things. Celebrating and communicating small victories and quick wins to maintain momentum and increase morale.

 

Institutionalization Resistance
Compatibility Issues ICT Systems
New ICT Systems Compatibility
Integration Conflicts

 

Opposition, reluctance, or refusal to accept and support the change effort by individuals or groups within the organization. Sustaining the changes over time by integrating them into the organization's systems, processes, and behaviors.
Information and Communication Technology systems, which encompass hardware, software, and networks. Problems that arise when trying to integrate new ICT systems with existing technologies or software.
The ability of different systems or components to work together without conflicts or issues. Recently implemented or upgraded Information and Communication Technology systems.
Incompatibilities or clashes between different software, hardware, or data formats. The process of combining and interconnecting new ICT systems with existing technology infrastructure.

 

Software Hardware
Networks Upgrades
Interoperability Legacy Systems
Integration Problems Software Incompatibility

 

Physical components of ICT systems, including computers, servers, routers, and other devices. Programs and applications that run on ICT systems, such as operating systems, databases, or productivity tools.
Updates or enhancements to existing ICT systems, often introducing new features or capabilities. The infrastructure and connections that allow ICT systems to communicate and share data.
Refers to outdated or older ICT systems or software that may not be fully compatible with new or modern ICT systems, resulting in compatibility issues. The ability of different ICT systems or software to seamlessly communicate, exchange data, and work together without any compatibility issues.
The inability of software applications or programs to function properly or work together due to differences in programming languages, versions, or dependencies. Difficulties faced when trying to combine or merge different ICT systems or software into a unified and functional system, leading to compatibility issues.

 

Hardware Incompatibility Data Migration Challenges
Upgrading Problems Testing And Quality Assurance
Middleware Compatibility Layer
Mitigate API Gateway

 

Problems or complications faced when transferring data from old or existing systems to new ICT systems, often resulting in data corruption or compatibility issues. Refers to conflicts or issues that arise when hardware components, devices, or peripherals are not compatible or able to effectively work together with new ICT systems.
The process of evaluating, validating, and ensuring that new ICT systems are compatible, functional, and meet the required quality standards before deployment or implementation. Difficulties or obstacles encountered when upgrading or transitioning from older ICT systems to newer ones, often leading to compatibility issues.
A module or component within a program that enables it to function on different platforms or with different software versions without modification. A software component that acts as an intermediary between two or more applications or services to facilitate communication and data exchange.
A server that acts as an entry point for APIs to manage, route, and secure incoming and outgoing API traffic. To reduce or lessen the severity or impact of something, often in reference to risks, problems, or threats.

 

Backward Compatibility Technical Debt
Limited Scalability Obsolete Hardware
Lack Of Support Compliance Risks
Unit Testing Integration Testing

 

The cost of maintaining and supporting legacy systems over time The ability of a system or software to work with older versions or systems while still supporting newer functionalities.
Old and outdated physical equipment that legacy systems run on The inability of legacy systems to grow or adapt to changing business needs
The potential for legacy systems to fail to meet modern regulatory requirements Difficulty in finding resources or expertise to maintain legacy systems
The process of combining software modules or components and testing them as a group to verify their interactions and functionality. The practice of testing individual software components, such as functions or methods, to ensure their correctness.

 

System Testing Acceptance Testing
Regression Testing Black Box Testing
White Box Testing Test Case
Dry Run Testing Walkthrough Testing

 

The final phase of software testing where a system is evaluated for its acceptance by the end users or stakeholders. The process of testing an integrated software system to evaluate its compliance with the specified system requirements.
A testing technique that focuses on the functionality and behavior of a software system without examining its internal code structure. The practice of retesting previously tested software to ensure that changes or fixes have not introduced new defects or regression bugs.
A specific set of inputs, conditions, and expected results used to determine whether a software system is functioning correctly. A testing technique that examines the internal code structure of a software system to identify any defects or vulnerabilities.
A type of software testing where the tester goes through the entire software application, step by step, to ensure that there are no defects or issues. A test where the program is run with sample data to verify the correctness of its logic.

 

Alpha Testing Beta Testing
Stub Testing Local System
Remote System System Access
Latency Bandwidth

 

A type of software testing performed by end-users before the final release of the software to ensure its reliability and usability. A type of software testing performed to identify and eliminate all possible issues before releasing the software to the end-users.
A computer system that is physically located nearby and operates independently from other systems. A testing technique where specific code segments or modules are replaced with placeholder code to simulate the behavior of dependent components.
The ability to connect to and interact with a computer system. A computer system that is located elsewhere and can be accessed over a network or the internet.
The maximum amount of data that can be transmitted over a network connection in a given amount of time. The amount of time it takes for data to travel from one system to another.

 

Data Security Data Privacy
Network Infrastructure Scalability
Security Compliance
Data Sovereignty Confidentiality

 

The right to control how personal information is collected, used, and shared. Measures taken to protect data from unauthorized access, use, disclosure, disruption, modification, or destruction.
The ability of a system to handle increased workload or accommodate growth without sacrificing performance. The hardware, software, and protocols used to connect devices and systems in a network.
The adherence to laws, regulations, guidelines, and standards relevant to an organization's business and industry. The protection of computer systems and data against unauthorized access, use, disclosure, disruption, modification, or destruction.
The protection of information from unauthorized access or disclosure, ensuring it is only accessible to authorized individuals. The concept that data is subject to the laws and regulations of the country in which it is located.

 

Availability Risk Management
Audit Trail Upfront Cost
Operating Cost Capital Expenditure
Operating Expenditure Total Cost Of Ownership

 

The process of identifying, assessing, and prioritizing potential risks to minimize their impact on an organization's objectives. The assurance that information and resources are accessible and usable when needed, without downtime or interruptions.
The initial cost or investment required to acquire or set up a product or service. A record of events and activities that provides documentary evidence of the sequence of activities that have affected a specific operation, procedure, or event.
An expense incurred to acquire an asset like equipment or infrastructure, which is recorded on the balance sheet. The ongoing cost incurred to operate or maintain a product or service.
The complete cost associated with owning and using a product or service over its lifetime, including both upfront and operating costs. An expense incurred to maintain day-to-day business activities, which is recorded on the income statement.

 

Return On Investment Cost-Benefit Analysis
Depreciation Lifecycle Cost
Sunk Cost Business Continuity
Disaster Recovery Risk Assessment

 

A systematic approach to comparing the costs and benefits of different options to determine the most favorable course of action. A measure of the profitability of an investment, calculated by dividing the net profit by the initial investment.
The total cost of a product or service over its entire lifecycle, including acquisition, operation, maintenance, and disposal costs. The decrease in value or usefulness of an asset over time, typically recorded as an expense on the income statement.
The ability of a business to continue its operations in the event of a disruption or disaster. A cost that has already been incurred and cannot be recovered, regardless of future actions or decisions.
The process of identifying and evaluating potential risks that could impact business continuity. The process of restoring and recovering systems, data, and infrastructure after a disaster or disruption.

 

Business Impact Analysis Emergency Response Plan
Incident Management Crisis Communication
Business Resilience Software As A Service
Cloud Computing Subscription-Based Model

 

A plan outlining the immediate actions and procedures to be followed during an emergency situation. The process of identifying the potential impact of disruptions on business operations and their financial consequences.
The process of delivering timely and accurate information during a crisis to internal and external stakeholders. The process of responding to and managing incidents to minimize their impact on business operations.
A software distribution model in which applications are hosted by a third-party provider and made available to customers over the internet. The ability of a business to adapt, recover, and grow despite disruptions or crises.
A pricing model where customers pay a recurring fee at regular intervals for access to a product or service. The delivery of computing services over the internet, including storage, servers, databases, networking, software, analytics, and more.

 

On-Demand Software Virtualization
Vendor Lock-In Random Sampling
Real-World Data Negative Testing
Positive Testing Data Completeness

 

The process of creating a virtual version of a resource, such as a server, storage device, network, or operating system. Software that is delivered over the internet and is available to users whenever they need it.
A technique used to select test data by randomly choosing data points from a larger set. Where a customer is dependent on a particular vendor for products and services, making it difficult or costly to switch to another vendor.
A type of testing where test data is intentionally selected to trigger error conditions or invalid inputs. Data that represents the actual usage scenarios, conditions, and environments in which the software will operate.
Ensuring that all relevant and necessary data scenarios are covered during the testing process. A type of testing where test data is selected to validate the expected behavior or correct execution of the software.

 

Test Data Boundary Values
Code Coverage Ad-Hoc Testing
Pairwise Testing Usability Testing
Test Coverage Rolling Release

 

Test data chosen at the lower and upper limits of input ranges to evaluate system behavior at edge cases Data used in testing to execute test cases and evaluate the behavior of a system
Testing performed without any formal test plan or pre-defined steps The extent to which the source code is executed by a test suite
Testing done to evaluate the ease of use and user-friendliness of a system A test design technique that focuses on testing all possible combinations of input parameters
A software development model where new features and updates are continuously released to users as soon as they are ready. The measurement of the extent to which testing has covered a system

 

Nightly Build Stable Build
Hard Release Soft Release
Incremental Release Continuous Deployment
Alpha Release Beta Release

 

A version of software that has been thoroughly tested and is considered reliable and free from major bugs or issues. A software build that is automatically created every night, usually to test the latest changes made to the codebase.
A controlled release of software to a limited audience or group of users for testing or evaluation purposes. A software release that introduces significant changes or new features, often requiring user adaptation or migration.
A software development practice where code changes are automatically released to production as soon as they pass automated tests and quality checks. A software release that adds new features or improvements to an existing version without requiring a major update.
A pre-release version of software that is made available to a limited number of users or testers for feedback and bug reporting. An early version of software that is typically released for internal testing or evaluation purposes.

 

Patch Release Build
Software Release Update
Source Code Maintenance Update
Bug Performance Improvement

 

A compiled version of software that can be installed or run by users. A software release that provides updates or fixes for specific issues or vulnerabilities in an existing version.
A piece of software that replaces an existing version with a newer one, often addressing issues or adding new features. The distribution of a new version or update of a software product to users.
An update to software or hardware that is designed to fix bugs, improve performance, or add new features. The human-readable version of a computer program that can be used to create executable software.
A change made to software or hardware that increases its speed, efficiency, or overall performance. A flaw or error in software or hardware that causes it to behave unexpectedly or not as intended.

 

New Feature Patch
Release Notes Rollback
System Downtime Software Update
Security Patch Vulnerability

 

A small update or fix applied to software to address specific issues or vulnerabilities. A functionality or capability added to software or hardware that was not previously available.
The process of reverting to a previous version of software or hardware after an update has caused issues or problems. Documentation that provides information about the changes, improvements, and known issues in a software update.
An action that installs the latest version of software, often including bug fixes, security patches, and new features. The period of time during which a system or service is not available or accessible due to maintenance or updates.
A weakness in a computer system or software application that can be exploited by malicious actors to gain unauthorized access. A software update designed to fix vulnerabilities or weaknesses in a computer system or software application.

 

Zero-Day Vulnerability Exploit
Mitigation Parallel Running
Pilot Running Direct Changeover
Phased Conversion System Implementation

 

Malicious code or technique that takes advantage of a vulnerability in a computer system or software application to gain unauthorized access. A previously unknown software vulnerability that is exploited by cybercriminals before the software developer releases a patch or fix for it.
Where new and old systems run simultaneously for a period of time to ensure smooth transition and mitigate risks. Reducing the severity, impact, or likelihood of a security vulnerability or potential attack through proactive measures such as applying patches.
Where the old system is replaced abruptly with the new system, often with minimal or no overlap in operation. Where a small group or subset of users operate the new system before full implementation, allowing for evaluation and refinements.
The process of putting a new computerized system into use, involving installation, configuration, and testing to ensure its functionality and efficiency. An approach to system implementation where different modules or components are introduced gradually until the entire system is fully operational.

 

Transition Period Risk Mitigation
Operational Overlap User Evaluation
Module-Based Implementation

 

The actions taken to reduce or eliminate risks and their impact during the implementation or execution of a project or system. The time frame during which a changeover or conversion occurs, allowing for adaptation, training, and adjustment to the new system.
Gathering feedback from users or stakeholders to evaluate the effectiveness, usability, and satisfaction with a system. The time where both the old and new systems are active, allowing for parallel running or testing before a complete changeover takes place.
An approach where a system is divided into distinct modules or components, allowing for separate implementation, testing, and integration.