Software Engineering Models Quiz

A planned approach to releasing software updates and features to users. This can involve multiple steps and environments

A phase in the software development lifecycle that has specific tasks and deliverables. Phases like Requirements, Design, and Testing are common in the Waterfall Model; Training is not part of the core model stages.

Flexibility in adapting to changing requirements during the software development process, providing better options than pure waterfall.

A framework for managing software development projects using iterative and incremental development.

Well-defined deliverables in distinct stages, improving efficiency and project management.

The process of gathering information about user needs to design a software solution.

Inheritance is an "is-a" relationship, while composition is a "has-a" relationship.

A diagram that doesn't explicitly show the time sequence of events, although it can be implied.

The spiral model involves iterative cycles focused on risk management, while the waterfall model follows a linear, sequential approach.

The prototype model helps clarify client expectations, assess technical feasibility, and provide early user feedback.

Scrum is a framework for managing Agile projects, focusing on sprints and collaboration. XP emphasizes coding practices like pair programming and test-driven development.

The waterfall model is a software development process where phases are executed sequentially, with each phase depending on the previous one.

TDD encourages adaptable code, early problem detection, code simplification, and straightforward integration.

Method overloading occurs within a class, allowing different methods with the same name but different parameters. Method overriding happens in classes with inheritance, where a subclass provides its own version of a parent class method.

Method overloading is an example of compile-time polymorphism because method resolution happens during compilation based on the number and type of arguments.

Method overriding is an example of runtime polymorphism because the specific method to be executed is determined at runtime based on the object type.

A technique where a subclass provides its own implementation for a method already defined in its superclass. The method signature (name and parameters) must be identical.

A technique where multiple methods within the same class have the same name but different parameters (number, type, or order).

A software development methodology that prioritizes flexibility, customer collaboration, and continuous improvement. It emphasizes frequent releases, short iterations, and a focus on code quality.

A design principle stating that each module, class, or function should have a single, well-defined responsibility.

A set of principles and practices that emphasizes iterative, incremental development and continuous feedback. It encourages collaboration, customer involvement, and adaptability.

Allows for flexibility in responding to changing requirements during development, making adjustments easier.

The iterative model produces a runnable software system earlier than the waterfall model, allowing for faster feedback and adjustments.

The pure waterfall model does not actively deal with risks as effectively as iterative models, as it focuses on sequential steps.

A software sizing technique that measures the functional complexity of a software system based on user input, output, inquiries, files, and interfaces.

A risk-driven software development model that iteratively cycles through planning, risk analysis, development, and evaluation phases.

A software architecture where different components of a system are spread across multiple physical locations, often communicating through networks.

A software development approach that breaks down a project into smaller, incremental phases, applying the waterfall model to each phase.

The entire process of creating, deploying, and maintaining software, encompassing phases like planning, analysis, design, development, testing, deployment, and maintenance.

A structured set of steps, guidelines, and methodologies used to create and maintain software applications.

A programming paradigm that uses objects and classes to encapsulate data and behavior.

The Rapid Application Development (RAD) method allows for quick software development due to its reliance on proven technologies, computer-assisted software engineering tools, and a focus on iterative development cycles.

The Unified Process Model combines elements of both iterative and incremental development methodologies. It emphasizes continuous iteration, user feedback, and a flexible approach to software creation.

Gantt charts are visual representations of project schedules, displaying tasks and their durations. PERT charts showcase task dependencies. They differ in how they visualize time and relationships between tasks.

Test-Driven Development (TDD) is a software development approach where tests are written before the actual code. This helps ensure quality and provides a framework for guiding development.

Software development process models offer several benefits, including standardization, enhanced communication, clear documentation, and a shared understanding of the development process.

The iterative model in software engineering focuses on developing a simplified version of the software initially, then gradually adding features and complexity in subsequent iterations.

A Gantt chart is a bar chart that shows the duration of tasks over time. A PERT chart is a network diagram that shows the dependencies between tasks.

The iterative model breaks down software development into smaller, manageable cycles, which allows for early testing and debugging, making the process more flexible and allowing for user feedback to be incorporated throughout development.

A deployment strategy where the old system is completely replaced by the new system at a specific point in time. All users transition to the new system simultaneously.

Coding standards help ensure code consistency, readability, and maintainability, making it easier for developers to collaborate, understand the code, and perform code reviews.

A document that clearly defines the essential requirements of a software system, including the functionalities it should provide, the data it will handle, and its interactions with other systems.

A deployment strategy where new features or modules of a software system are released gradually to users, allowing for testing and feedback in smaller iterations.

The process of understanding the specific industry or domain of a software system. It involves gathering information about the business processes, terminology, and requirements specific to that domain.

Evolutionary prototyping is a process model that focuses on initial, simplified implementation, then progressively gains more complexity and a broader feature set until the final system is completed. It involves building and refining a working prototype iteratively.