Chapter 3-4
Cards (71)
- a software platform that helps users solve their problems through a single (or multiple) point of contact.
- allow employees and IT team members to troubleshoot problems, track their issues, and get assistance regarding products, services, or processes
- help teams proactively maintain services, manage incidents, and enable communication with end users and customers.
- customercentric communication centerpoint where users, employees, and stakeholders can solicit help from their IT service providers
- typically used to provide reactive, rather than proactive, assistance via basic ticketing
- used when changing hardware, installing or upgrading to new releases of off-the-shelf applications, installing a software patch and configuring various network devices
- an area of systems management that involves acquiring, testing and installing multiple patches (code changes) to an administered computer system in order to maintain up-to-date software and often to address security risk
- tool that automates the patch management process of an enterprise starting from scanning and detection of missing patches to testing, deploying and installing them on the required endpoints
- is the process of identifying, testing, deploying, and installing software patches (or updates) to computers.
- piece of code, tailored to fix existing bugs/vulnerabilities in the software, add new features, or enhance its security.
- ( also referred to as the patch management system) includes scanning computers in the network for missing patches, testing them in a test group of machines, and deploying them manually or automatically via patch management tools.
- Security patch management, i.e. the process of deploying security patches to address security vulnerabilities in the software, drivers, and other related components helps secure it from being exploited by vulnerabilities and other threat actors.
- ensure that the software is up to date with the latest, bug-free version
- introduce newer features and functions to software. In addition, they also enhance performance, making software faster and more efficient.
- process of detecting, testing and deploying security patches or updates to the systems to address the security vulnerabilities and issues. Security patches ensure that the known security vulnerabilities in the systems and the network are promptly mitigated
- the process of detecting, testing, and deploying the missing patches to prevent the servers from being exploited by vulnerabilities and external threat actors.
- explained on the Google Testing Blog, as “the continuous and consistent improvement and maintenance of process that… gives us confidence the product will meet the need of customers.”
- a part of quality management that verifies the product’s compliance with standards set by QA.
- the primary activity of detecting and solving technical issues in the software source code and assessing the overall product usability, performance, security, and compatibility.
- Representing a traditional software development life cycle, the Waterfall model includes six consecutive phases: requirements gathering and analysis, system design, development, testing, deployment, and maintenance
- breaks the development process into smaller parts called iterations or sprints
- an evolution of Agile that bridges the gap between development along with QA and operations. I
- a series of activities conducted within the software development life cycle or alongside the SDLC stages. It
- the most common type based on the requirements or additional risk analysis. In the latter case, a testing team collaborates with stakeholders to prioritize areas that are most critical for end users
- follows a prebuilt model of how a program must work. This model typically comes as a diagram visualizing various aspects of expected software behavior — a customer journey through a website, data flows, interactions between components, etc. It helps better understand system functionality, improves communication with stakeholders, and reduces the time and effort required for test automation.
- employs predefined quality checklists and procedures сreated inhouse or adopted across the industry. It’s often used for standard apps or particular types of checks — for example, security testing.
- adheres to specific regulations, guidelines, and industry standards.
- apply informal techniques that don’t require pre-planning (such as ad hoc and exploratory testing.) It belongs to a reactive category and comes into play when bumping into defects in the running software.
- relies on the expertise and recommendations of stakeholders or end-user feedback when deciding on testing scope, methods, etc.
- revolves around reducing risks of regressions — or situations when an app stops working correctly after updates. Typically, it’s a highly automated approach
- has a more hands-on approach, describing in detail what to test, how to test, when to test, and who will do the test.
- initially examines the source code and software project documents to catch and prevent defects early in the software testing life cycle. Also called a non-execution technique or verification testing.
- systematic peer inspections of the source code;
- informal meetings when a developer explains a program to peers, receives comments and makes modifications to the code;
- formal procedures carried out by experts from several departments to validate product compliance with requirements and standards
- The objective of this level is to verify that units work well together as a group and also smoothly interact with other system elements —
- At this level, a complete software system is tested as a whole. The stage verifies the product’s compliance with the functional and non-functional requirements.
- This is where the product is validated against the end-user requirements and for accuracy.
- aids in organizing, controlling and using the data needed by application programs.
- provides the facility to create and maintain a well-organized database