Software Engineering Quiz & Flashcards

Requirements analysis is the phase where the needs of stakeholders are gathered and documented.

Agile methodology is known for its iterative development, allowing for changes throughout the project.

A software architect is responsible for making high-level design choices and technical standards.

Unit testing focuses on the smallest testable parts of an application, like functions or classes, in isolation.

A feasibility study assesses whether a project is viable and worth pursuing.

Continuous integration involves frequent integration of code into a shared repository to detect errors early.

User stories are simple descriptions of a feature from the user's perspective, often used in agile methodologies.

The spiral model combines iterative development with the systematic aspects of the waterfall model and emphasizes risk assessment.

Regression testing ensures that new code changes do not adversely affect the existing functionality of the software.

Risk management involves a comprehensive approach to identifying, assessing, and prioritizing risks to mitigate them effectively.

In the waterfall model, the implementation phase follows the design phase.

Refactoring improves code readability and maintainability without altering its external behavior.

White box testing involves examining the internal structure or workings of a program.

An MVP is the simplest version of a product that can be released to test a new business idea and gather feedback.

A business analyst identifies business needs and determines solutions, often involving software systems development.

Pair programming involves one developer writing code while the other reviews each line, fostering collaboration and quality.

Software maintenance encompasses bug correction, performance improvement, and adaptation to new environments.

Technical debt is the implied cost of additional rework caused by choosing a quick solution now instead of a better one that would take longer.

Beta testing involves real users testing the software in a real environment before the final release.

Mock testing uses simulated objects to mimic real objects' behavior in a controlled way.

Regression testing involves automatically re-running tests after changes to ensure existing functionality isn't broken.

Software prototyping involves creating incomplete versions of the software program to understand requirements better.

Agile methodology uses short, iterative cycles called 'sprints' to manage work and deliver increments of the product.

The SRS document provides a detailed description of the software system's functional and non-functional requirements.

Continuous deployment is a process where code changes are automatically deployed to production after passing automated tests.

Integration testing involves testing combined units or components to detect interface defects between integrated units.

Load testing evaluates how a system performs under expected or high load conditions, ensuring it can handle the required amount of work.

UAT is the final phase of testing where actual users ensure that the software can handle required tasks in real-world scenarios.

Backlog grooming involves reviewing and prioritizing the product backlog items to ensure they are ready for delivery.

Object-oriented design is based on the concept of objects, which are instances of classes that encapsulate data and behavior.

A DevOps engineer works with developers and IT staff to oversee code releases and ensure smooth deployment.

Scalability refers to a system's capability to handle a growing amount of work or its potential to accommodate growth.

Code review is the process of systematically examining source code to find bugs and improve overall software quality.

The V-Model emphasizes verification and validation at each phase of the development process.

Risk mitigation involves implementing strategies to reduce the impact or likelihood of risks during a project.

Incremental development is a process where the software is developed and tested incrementally until completion.

Project scope involves determining and documenting a list of specific project goals, deliverables, features, and tasks.

Alpha testing is the initial phase of testing performed by developers to identify bugs before releasing to real users.

Regression testing ensures that changes or additions have not adversely affected existing functionality.

Load testing assesses how a system behaves under a specific expected load, ensuring it can handle the load.

Software configuration management involves tracking and controlling changes in the software.

Documentation is crucial as it provides detailed guidance on software architecture, functionality, and usage.

TDD is a process where tests are written before code, ensuring that the code meets its requirements.

Non-functional requirements focus on criteria like performance and usability, rather than specific behaviors.

Acceptance criteria are conditions that a software product must satisfy for a user story to be considered complete.