System Integration Architecture Reviewer

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/41

flashcard set

Earn XP

Description and Tags

Flashcards generated from system integration architecture, quality assurance, and evaluation lecture notes.

42 Terms

1
New cards

What is System Integration Testing (SIT)?

A QA process performed after separate testing where combined modules are tested as a group to ensure they work together as a whole.

2
New cards

What is System Testing?

The final stage and third level of testing (performed after integration and before acceptance) that provides an end-to-end, black box evaluation against customer requirements for both functional and non-functional aspects.

3
New cards

What is Black Box Testing?

A testing approach focusing on functionality where the tester sees an outside view only and is unaware of inner workings.

4
New cards

What is White Box Testing?

A testing approach where source code and code structure are known, allowing design of test cases based on that knowledge.

5
New cards

What is Gray Box Testing?

A testing approach based on partial code knowledge, where some internal workings are known and some are not.

6
New cards

What is Unit Testing?

Testing applied to the smallest piece of code, such as a function, method, or property.

7
New cards

What is User Acceptance Testing?

A development phase testing conducted in the real world environment.

8
New cards

What is Integration Testing?

Testing a collection of modules and interfaces between components like a building plan for early bug detection, requiring programming knowledge from the integrator.

9
New cards

Why is Integration Testing important?

It checks that modules work together, addresses compatibility and communication issues early, and enhances reliability, performance, and quality.

10
New cards

What is Big-Bang Integration Testing?

The simplest approach where all modules are combined at once; suitable for small systems only and makes errors hard to localize.

11
New cards

What is Bottom-Up Integration Testing?

An integration strategy testing lower levels first and moving upward, using test drivers and testing subsystem interfaces.

12
New cards

What is Top-Down Integration Testing?

An integration strategy testing high-level components first and moving downward, simulating lower modules that are not yet integrated.

13
New cards

What is Mixed Integration Testing?

A sandwiched hybrid approach combining top-down plus bottom-up methods using stubs and drivers to overcome shortcomings.

14
New cards

What are Test Drivers?

Tools or scripts used to drive and pass data to lower-level modules during testing.

15
New cards

What is the purpose of Software Testing?

To ensure the end product meets standards, evaluate functionality, find bugs and defects, and find gaps.

16
New cards

What is Postman?

An API testing tool used to send requests and validate responses for RESTful services, covering functional, load, and security testing.

17
New cards

What is SoapUI?

A tool used for testing web services and APIs (SOAP and REST), SOA, SLAs, message queues, and business logic.

18
New cards

What is Jenkins?

An open-source automation server for CI/CD that builds, tests, and deploys software by auto-triggering frequent test runs on code push.

19
New cards

What is Automation Testing?

Testing executed via software tools running predefined test cases without human intervention.

20
New cards

What is Manual Testing?

Testing conducted by human testers without automation tools.

21
New cards

What is Incremental Testing?

Testing components one at a time, using either top-down or bottom-up strategies.

22
New cards

What is Automated Regression Testing?

Re-running previous test cases after new changes to ensure no new defects are introduced in existing functionality.

23
New cards

What is Architecture Quality Assurance?

Assessing software architecture quality before the coding phase to ensure it is robust, scalable, secure, and maintainable, enabling early error detection.

24
New cards

What is MuleSoft?

An integration platform offering API-led connectivity and reusable assets across on-premises and cloud environments.

25
New cards

What is Apache Camel?

An open-source framework using enterprise integration patterns (EIPs) with a rich library of connectors.

26
New cards

What are Microservices?

Independent, modular services focused on specific functionality that can be deployed separately, interact through APIs, and increase agility.

27
New cards

What is Service-Oriented Architecture (SOA)?

An architecture centered around centralized systems, common messaging protocols, enterprise service buses (ESB), reusability, and standardization.

28
New cards

What is Contract Testing?

Testing that verifies API agreements between independent services.

29
New cards

What is Service Virtualization?

A technique that simulates service interactions during testing.

30
New cards

What is Requirement Traceability?

Linking requirements to functional and non-functional test cases to ensure accountability and track changes.

31
New cards

What is JMeter?

Apache JMeter is a tool used for load and performance testing to analyze data flows across components.

32
New cards

What tools are used for Log Management in integration QA?

ELK Stack and Splunk, which track integration issues in real time.

33
New cards

What tools are used for Monitoring Services?

New Relic and Prometheus, which provide real-time visibility into system health and performance.

34
New cards

What is Software Evaluation?

Running software under known conditions with defined inputs and documented outcomes, then comparing the results to predefined expectations.

35
New cards

What is Verification?

Ensuring the system is built correctly without technical errors, requirements are reviewed, syntactically and logically correct code is written, and the right problem is solved.

36
New cards

What is Validation?

Determining the meaning and content of rules, criteria of adequacy, and overall acceptability of the system.

37
New cards

What are System Requirements?

The foundation of a new system, specifying a condition or capability needed by a user, including environment description, list to fulfill, and verification criteria.

38
New cards

What is Intensional Correctness?

Validating semantic features, domains, keys, and dependencies to avoid data errors and inconsistencies.

39
New cards

What is Normalization in database verification?

Verifying database design, normal forms, table keys, and dependencies to remove redundant data and avoid update anomalies.

40
New cards

What are Update Anomalies?

Issues where performing an update creates inconsistent data or inadvertently removes data.

41
New cards

What is Robustness testing?

Testing rules and control strategies under extreme conditions using the least and most significant input parameters.

42
New cards

What is Accuracy in system evaluation?

Evaluating correct predictions against known data and comparing conclusions with historic data to reflect reality.