Software Testing and PHP Fundamentals Quiz

User Privacy and Data Protection = Informed Consent: Software engineers should ensure that users are informed about the data being collected, how it will be used, and obtain their consent before collecting any personal information. Data Security = Developers must implement robust security measures to protect user data from unauthorized access, breaches, and other security threats. Transparency and Accountability = Transparent Communication: Software engineers should communicate openly and honestly about the capabilities and limitations of their systems to users, clients, and other stakeholders. Fairness and Non-discrimination = Algorithmic Fairness: Developers should be mindful of potential biases in algorithms and strive to create systems that are fair and unbiased, avoiding discrimination based on race, gender, age, or other factors.

User Privacy and Data Protection = Ensuring users are informed about data collection and obtaining consent before collecting personal information. Data Security = Implementing robust security measures to protect user data from unauthorized access and breaches. Transparency and Accountability = Communicating openly and honestly about system capabilities and limitations to users, clients, and stakeholders. Fairness and Non-discrimination = Being mindful of biases in algorithms and creating fair and unbiased systems to avoid discrimination based on various factors.

Informed Consent = Ensuring users are informed about the data being collected, how it will be used, and obtaining their consent before collecting any personal information. Transparent Communication = Communicating openly and honestly about the capabilities and limitations of their systems to users, clients, and other stakeholders. Accountability for Errors = Taking responsibility for the consequences of errors in the software developed and working towards resolving issues promptly. Algorithmic Fairness = Being mindful of potential biases in algorithms and striving to create fair and unbiased systems, avoiding discrimination based on various factors.

Inclusive design = Emphasizes accessibility and usability for diverse users, including those with disabilities. Intellectual property and open source practices = Include respecting IP rights, avoiding unauthorized use, and encouraging open source contributions for collaboration and knowledge sharing. Professional competence = Involves continuous learning to stay updated with the latest technologies and honest representation of skills and experience. Social responsibility = Includes considering the environmental impact, contributing positively to society, and promoting a culture of ethical conduct through whistleblowing.

Monolithic architecture = Involves developing the entire application as a single, tightly-coupled unit, which can become challenging to scale and maintain. Microservices architecture = Breaks down an application into small, independent services for flexibility, scalability, and the use of different technologies for different services. Service-oriented architecture (SOA) = Comprises loosely coupled, reusable services designed to provide specific business functionalities. Client-server architecture = Divides the application into client and server components communicating over a network, implemented in various ways such as two-tier or three-tier architectures.

Legal compliance = Requires adherence to laws and regulations related to software development, including privacy laws and intellectual property laws. Ethical considerations = Are dynamic and may evolve with changing technology and societal norms, necessitating ongoing discussions and education. Application architecture = Refers to the high-level structuring of software systems, impacting scalability, maintainability, and performance. Event-driven architecture = Focuses on the production, detection, consumption, and reaction to events, often used for real-time processing and responsiveness.

Client-server architecture = Divides the system into client and server components, enabling the client to send requests and the server to process them independently. Microservices architecture = Decomposes the system into small, independent services that can be developed, deployed, and scaled independently. Structural design patterns = Facilitate the creation of flexible and reusable software components, including patterns like Adapter, Bridge, Composite, and Decorator. Object-oriented analysis and design (OOAD) = A methodology for analyzing and designing a system by visualizing it as a group of interacting objects, each defined by their roles, behaviors, and attributes.

UML's class diagrams = Represent the static structure of a system, illustrating classes, their attributes, methods, and relationships. Entity-Relationship Diagrams (ERD) = Model the relationships between entities (tables) in a database, while database schema describes the structure of a database, including tables, fields, relationships, and constraints. Use case diagrams = Visualize the various ways a system can be used and the interactions between actors and the system. Sequence diagrams = Show how objects interact in a particular scenario of a use case or a part of a system's functionality.

Logical view = Describes the functionality from an end-user perspective, focusing on the logical organization of the system components. Development view = Describes the software development structure, including modules, packages, classes, interfaces, and their relationships. Process view = Describes the system's runtime behavior, including the interactions between various components and their behavior during execution. Architecture documentation = Provides a comprehensive understanding of the overall architecture and key components, typically including architecture documentation and readme files.

Automated testing = Involves using testing tools, scripts, and software for testing Test case design techniques = Involve equivalence partitioning, boundary value analysis, decision table testing, and state transition testing Performance testing = Includes load testing, stress testing, and performance monitoring to assess system behavior and optimize performance Regression testing = Ensures that changes or enhancements to the software do not negatively impact existing functionality

Variables in PHP = Start with the $ symbol and are case-sensitive PHP syntax = Is embedded within HTML or can be used as a standalone script and utilizes tags PHP usage = Commonly used for forms handling, error handling, file handling, database connectivity, sessions, cookies, and including external files Data types, operators, and control structures in PHP = Supported by PHP

Test planning = Is a stage in the testing life cycle Test execution = Is a stage in the testing life cycle Defect reporting = Is a stage in the testing life cycle Test closure = Is a stage in the testing life cycle

Faster execution, repeatability, better coverage, and early bug detection = Advantages of test automation Tools like Selenium, JUnit, TestNG, Appium, and JIRA = Utilized in test automation

Identifying vulnerabilities = Involves in security testing Authentication and authorization testing = Involves in security testing Data security testing = Involves in security testing

Forms handling, error handling, file handling, database connectivity, sessions, cookies, and including external files = Commonly used PHP areas Server-side scripting language for web development = PHP usage