暗記メーカー

暗記メーカー

​
ログイン
Application Development Mocktest (Midterm) BSIT 505
42問 • 4ヶ月前
  • Xai Alexandrei Delos Reyes
    • 通報

    問題一覧

  • 1

    The software is hard to change because every applied change will affect many parts of the software.

    Rigidity

  • 2

    When applying changes, unexpected parts of the software breaks

    Fragility

  • 3

    The modules of the software are hard to reuse ins another software because these cannot be extracted from the current software.

    Immobility

  • 4

    It is a object-oriented design are applied to software development projects to make software easier to change when requirements changes.

    SOLID principles

  • 5

    This is one of the basic principles most developers apply to build robust and maintainable software. This suggests that each software module, class, or interface should have only one (1) reason to change

    S: Single Responsibility Principle (SRP)

  • 6

    This states that for a software to be easy to change, the software classes must be designed to allow the behavior of those classes to be changed by adding new code rather than changing existing code.

    O: Open-Closed Principle (OCP)

  • 7

    Barbara Liskov introduced this principle which states that the derived classes should be substitutable for their base classes to build a software from interchangeable modules or classes.

    L: Liskov Substitution Principle (LSP)

  • 8

    This principle advises software designers to avoid depending on things that they don’t use.

    I: Interface Segregation Principle (ISP)

  • 9

    This principle suggests that flexible software are those with classes that depend on abstract classes or interfaces.

    D: Dependency Inversion Principle (DIP)

  • 10

    Which of the following is TRUE about the help the developers will achieve using SOLID Principle

    Reduce the complexity of source codes, Increase readability, extensibility, and maintenance, Reduce accidental errors and implement reusability easily, Achieve easier and better software testing

  • 11

    Which of the Following is NOT TRUE about Single Responsibility Principle (SRP) ?

    states that software modules, interfaces, or classes should be open for extension but closed for modification. This means that when there are new requirements for the software, the new behavior must be added by deriving a new class without modifying the existing class.

  • 12

    Which Statement is NOT TRUE About Open-Closed Principle (OCP)

    suggests that when creating a new derived class of an existing class, make sure that the derived class can be a substitute for its base class.

  • 13

    Which statement is NOT TRUE about Liskov Substitution Principle (LSP)

    suggests avoiding depending on things that are not used. This means that clients should not be forced to implement interfaces they don’t use.

  • 14

    Which statement is NOT TRUE about Interface Segregation Principle (ISP)

    suggests that the most flexible software systems are those in which source code dependencies refer only to abstractions, not to concretions.

  • 15

    Which statement is NOT TRUE about Dependency Inversion Principle (DIP)

    suggests that when creating a new derived class of an existing class, make sure that the derived class can be a substitute for its base class.

  • 16

    These are the reusable solutions to commonly occurring problems in software design.

    Design Patterns

  • 17

    Which statement is FALSE about design patterns?

    This is the name of a pattern that can be used to describe a design problem, its solution, and consequences.

  • 18

    This is the name of a pattern that can be used to describe a design problem, its solution, and consequences.

    Pattern Name

  • 19

    This describes when to use the pattern. It explains the problem and its context.

    Problem

  • 20

    This describes the elements that make up the design, their relationships, responsibilities, and collaborations. The pattern provides an abstract description of a design problem and how a general arrangement of element solves it.

    Solution

  • 21

    These are the results and interchanges of applying the pattern to the problem. They include time and space tradeoffs, but also flexibility, extensibility, and portability, among others.

    Consequences

  • 22

    These patterns deal with when and how objects are created. These provide object creation mechanisms that increase flexibility and reuse of existing codes

    Creational Patterns

  • 23

    These describe how objects are composed into larger groups and explain how to assemble objects and classes into larger structures while keeping their structures flexible and efficient.

    Structural Patterns

  • 24

    These describe how responsibilities are distributed between objects in the design and how communication happens between objects.

    Behavioral Patterns

  • 25

    This design pattern lets developers ensure that a class has only one (1) instance while providing a global access point to the instance.

    Singleton Pattern

  • 26

    This provides an interface for creating objects in a superclass but allows subclasses to alter the type of object that will be created.

    Factory Method Pattern

  • 27

    This creational design pattern lets a developer copy existing objects without making his code dependent on their classes.

    Prototype Pattern

  • 28

    - This allows developers to produce families of related objects without specifying their concrete classes. - A family of objects that are usually used together or a set of objects that are dependent on each other in some way.

    Abstract Factory Pattern

  • 29

    This creational design pattern allows developers to construct complex objects step by step. The pattern allows developers to produce different types and representations of an object using the same construction code.

    Builder Pattern

  • 30

    Which statement is NOT TRUE about Creational Patterns?

    These patterns deal with the arrangement and relationship between the classes in the software system.

  • 31

    Which statement is NOT TRUE about Structural patterns

    These patterns are concerned with how classes and objects behave in a system software and how objects communicate with each other.

  • 32

    This structural design pattern allows objects with incompatible interfaces to collaborate. This pattern converts the interface of a class into another interface as expected by the client application.

    Adapter Pattern

  • 33

    This allows the developers to split a large class or a set of closely related classes into two (2) separate hierarchies, which are abstraction and implementation, that can be developed independently of each other.

    Bridge Pattern

  • 34

    This design pattern allows developers to compose objects into tree structures and then work with these structures treating them as individual objects.

    Composite Pattern

  • 35

    This allows developers to attach new behaviors to objects by placing these objects inside special wrapper objects that contain the behaviors.

    Decorator Pattern

  • 36

    This allows developers to fit more objects into the available amount of RAM by sharing common parts of state between multiple objects instead of keeping all of the data in each other.

    Flyweight Pattern

  • 37

    This design pattern allows developers to provide a substitute or placeholder for another object. This controls access to the original object, allowing developers to perform something before or after the requests gets through to the original object.

    Proxy Pattern

  • 38

    Which statement is NOT TRUE about Behavioral Patterns

    These patterns deal with the arrangement and relationship between the classes in the software system

  • 39

    This design pattern allows developers to traverse elements of a collection without exposing its underlying representation, such as list, stack, and tree. This pattern is used for sequentially iterating and accessing items from a collection of items.

    Iterator Pattern

  • 40

    This design pattern allows developers to define a subscription mechanism to notify multiple objects about any events that happen to the object they are observing. This means that when an object changes state, all of its dependents are notified and updated automatically.

    Observer Pattern

  • 41

    This allows developers to define a family of algorithms, put each of them into a separate class, and make their objects interchangeable.

    Strategy Pattern

  • 42

    These are a set of guidelines to be followed that helps developers arrange methods and data structures into classes, and how those classes should be interconnected, which can adapt to the changes in requirements without major code rewrites.

    Design principles

    • The Contemporary World Mock test (Prelims)

    The Contemporary World Mock test (Prelims)

    Xai Alexandrei Delos Reyes · 58問 · 2年前

    The Contemporary World Mock test (Prelims)

    The Contemporary World Mock test (Prelims)

    58問 • 2年前
    Xai Alexandrei Delos Reyes

    Computing Mock test (Prelims)

    Computing Mock test (Prelims)

    Xai Alexandrei Delos Reyes · 67問 · 2年前

    Computing Mock test (Prelims)

    Computing Mock test (Prelims)

    67問 • 2年前
    Xai Alexandrei Delos Reyes

    Programming Mock Test (Prelims)

    Programming Mock Test (Prelims)

    Xai Alexandrei Delos Reyes · 64問 · 2年前

    Programming Mock Test (Prelims)

    Programming Mock Test (Prelims)

    64問 • 2年前
    Xai Alexandrei Delos Reyes

    Entrepreneurship Mock Test (Prelims)

    Entrepreneurship Mock Test (Prelims)

    Xai Alexandrei Delos Reyes · 23問 · 2年前

    Entrepreneurship Mock Test (Prelims)

    Entrepreneurship Mock Test (Prelims)

    23問 • 2年前
    Xai Alexandrei Delos Reyes

    Computing Mock Test (Midterms) BSIT 107

    Computing Mock Test (Midterms) BSIT 107

    Xai Alexandrei Delos Reyes · 76問 · 2年前

    Computing Mock Test (Midterms) BSIT 107

    Computing Mock Test (Midterms) BSIT 107

    76問 • 2年前
    Xai Alexandrei Delos Reyes

    Math Mock Test (Prelims)

    Math Mock Test (Prelims)

    Xai Alexandrei Delos Reyes · 48問 · 2年前

    Math Mock Test (Prelims)

    Math Mock Test (Prelims)

    48問 • 2年前
    Xai Alexandrei Delos Reyes

    Programming Mock Test (Midterms) BSIT 107

    Programming Mock Test (Midterms) BSIT 107

    Xai Alexandrei Delos Reyes · 52問 · 2年前

    Programming Mock Test (Midterms) BSIT 107

    Programming Mock Test (Midterms) BSIT 107

    52問 • 2年前
    Xai Alexandrei Delos Reyes

    UTS Mock Test (Midterms) BSIT107

    UTS Mock Test (Midterms) BSIT107

    Xai Alexandrei Delos Reyes · 40問 · 2年前

    UTS Mock Test (Midterms) BSIT107

    UTS Mock Test (Midterms) BSIT107

    40問 • 2年前
    Xai Alexandrei Delos Reyes

    Entrepreneurship Mock Test (Midterms) BSIT 107

    Entrepreneurship Mock Test (Midterms) BSIT 107

    Xai Alexandrei Delos Reyes · 38問 · 2年前

    Entrepreneurship Mock Test (Midterms) BSIT 107

    Entrepreneurship Mock Test (Midterms) BSIT 107

    38問 • 2年前
    Xai Alexandrei Delos Reyes

    Contemporary World Mock Test (Midterms) BSIT 107

    Contemporary World Mock Test (Midterms) BSIT 107

    Xai Alexandrei Delos Reyes · 28問 · 2年前

    Contemporary World Mock Test (Midterms) BSIT 107

    Contemporary World Mock Test (Midterms) BSIT 107

    28問 • 2年前
    Xai Alexandrei Delos Reyes

    Math Mocktest (Midterms) BSIT 107

    Math Mocktest (Midterms) BSIT 107

    Xai Alexandrei Delos Reyes · 24問 · 2年前

    Math Mocktest (Midterms) BSIT 107

    Math Mocktest (Midterms) BSIT 107

    24問 • 2年前
    Xai Alexandrei Delos Reyes

    Computer Programming Mocktest (Pre-finals)

    Computer Programming Mocktest (Pre-finals)

    Xai Alexandrei Delos Reyes · 26問 · 2年前

    Computer Programming Mocktest (Pre-finals)

    Computer Programming Mocktest (Pre-finals)

    26問 • 2年前
    Xai Alexandrei Delos Reyes

    Math Mocktest (Pre-Finals)

    Math Mocktest (Pre-Finals)

    Xai Alexandrei Delos Reyes · 19問 · 2年前

    Math Mocktest (Pre-Finals)

    Math Mocktest (Pre-Finals)

    19問 • 2年前
    Xai Alexandrei Delos Reyes

    Computing Mock Test (Pre-finals)

    Computing Mock Test (Pre-finals)

    Xai Alexandrei Delos Reyes · 36問 · 2年前

    Computing Mock Test (Pre-finals)

    Computing Mock Test (Pre-finals)

    36問 • 2年前
    Xai Alexandrei Delos Reyes

    Computing Mock Test Finals

    Computing Mock Test Finals

    Xai Alexandrei Delos Reyes · 26問 · 2年前

    Computing Mock Test Finals

    Computing Mock Test Finals

    26問 • 2年前
    Xai Alexandrei Delos Reyes

    Comprog 2nd sem (prelims) BSIT 205

    Comprog 2nd sem (prelims) BSIT 205

    Xai Alexandrei Delos Reyes · 63問 · 1年前

    Comprog 2nd sem (prelims) BSIT 205

    Comprog 2nd sem (prelims) BSIT 205

    63問 • 1年前
    Xai Alexandrei Delos Reyes

    Discrete Math 2nd sem (prelims) BSIT 205

    Discrete Math 2nd sem (prelims) BSIT 205

    Xai Alexandrei Delos Reyes · 36問 · 1年前

    Discrete Math 2nd sem (prelims) BSIT 205

    Discrete Math 2nd sem (prelims) BSIT 205

    36問 • 1年前
    Xai Alexandrei Delos Reyes

    Art Appreciation (Prelim) BSIT 205

    Art Appreciation (Prelim) BSIT 205

    Xai Alexandrei Delos Reyes · 56問 · 1年前

    Art Appreciation (Prelim) BSIT 205

    Art Appreciation (Prelim) BSIT 205

    56問 • 1年前
    Xai Alexandrei Delos Reyes

    Ethics 2nd sem (Prelims) BSIT 205

    Ethics 2nd sem (Prelims) BSIT 205

    Xai Alexandrei Delos Reyes · 45問 · 1年前

    Ethics 2nd sem (Prelims) BSIT 205

    Ethics 2nd sem (Prelims) BSIT 205

    45問 • 1年前
    Xai Alexandrei Delos Reyes

    STS 2nd Sem (Prelim) BSIT 205

    STS 2nd Sem (Prelim) BSIT 205

    Xai Alexandrei Delos Reyes · 40問 · 1年前

    STS 2nd Sem (Prelim) BSIT 205

    STS 2nd Sem (Prelim) BSIT 205

    40問 • 1年前
    Xai Alexandrei Delos Reyes

    問題一覧

  • 1

    The software is hard to change because every applied change will affect many parts of the software.

    Rigidity

  • 2

    When applying changes, unexpected parts of the software breaks

    Fragility

  • 3

    The modules of the software are hard to reuse ins another software because these cannot be extracted from the current software.

    Immobility

  • 4

    It is a object-oriented design are applied to software development projects to make software easier to change when requirements changes.

    SOLID principles

  • 5

    This is one of the basic principles most developers apply to build robust and maintainable software. This suggests that each software module, class, or interface should have only one (1) reason to change

    S: Single Responsibility Principle (SRP)

  • 6

    This states that for a software to be easy to change, the software classes must be designed to allow the behavior of those classes to be changed by adding new code rather than changing existing code.

    O: Open-Closed Principle (OCP)

  • 7

    Barbara Liskov introduced this principle which states that the derived classes should be substitutable for their base classes to build a software from interchangeable modules or classes.

    L: Liskov Substitution Principle (LSP)

  • 8

    This principle advises software designers to avoid depending on things that they don’t use.

    I: Interface Segregation Principle (ISP)

  • 9

    This principle suggests that flexible software are those with classes that depend on abstract classes or interfaces.

    D: Dependency Inversion Principle (DIP)

  • 10

    Which of the following is TRUE about the help the developers will achieve using SOLID Principle

    Reduce the complexity of source codes, Increase readability, extensibility, and maintenance, Reduce accidental errors and implement reusability easily, Achieve easier and better software testing

  • 11

    Which of the Following is NOT TRUE about Single Responsibility Principle (SRP) ?

    states that software modules, interfaces, or classes should be open for extension but closed for modification. This means that when there are new requirements for the software, the new behavior must be added by deriving a new class without modifying the existing class.

  • 12

    Which Statement is NOT TRUE About Open-Closed Principle (OCP)

    suggests that when creating a new derived class of an existing class, make sure that the derived class can be a substitute for its base class.

  • 13

    Which statement is NOT TRUE about Liskov Substitution Principle (LSP)

    suggests avoiding depending on things that are not used. This means that clients should not be forced to implement interfaces they don’t use.

  • 14

    Which statement is NOT TRUE about Interface Segregation Principle (ISP)

    suggests that the most flexible software systems are those in which source code dependencies refer only to abstractions, not to concretions.

  • 15

    Which statement is NOT TRUE about Dependency Inversion Principle (DIP)

    suggests that when creating a new derived class of an existing class, make sure that the derived class can be a substitute for its base class.

  • 16

    These are the reusable solutions to commonly occurring problems in software design.

    Design Patterns

  • 17

    Which statement is FALSE about design patterns?

    This is the name of a pattern that can be used to describe a design problem, its solution, and consequences.

  • 18

    This is the name of a pattern that can be used to describe a design problem, its solution, and consequences.

    Pattern Name

  • 19

    This describes when to use the pattern. It explains the problem and its context.

    Problem

  • 20

    This describes the elements that make up the design, their relationships, responsibilities, and collaborations. The pattern provides an abstract description of a design problem and how a general arrangement of element solves it.

    Solution

  • 21

    These are the results and interchanges of applying the pattern to the problem. They include time and space tradeoffs, but also flexibility, extensibility, and portability, among others.

    Consequences

  • 22

    These patterns deal with when and how objects are created. These provide object creation mechanisms that increase flexibility and reuse of existing codes

    Creational Patterns

  • 23

    These describe how objects are composed into larger groups and explain how to assemble objects and classes into larger structures while keeping their structures flexible and efficient.

    Structural Patterns

  • 24

    These describe how responsibilities are distributed between objects in the design and how communication happens between objects.

    Behavioral Patterns

  • 25

    This design pattern lets developers ensure that a class has only one (1) instance while providing a global access point to the instance.

    Singleton Pattern

  • 26

    This provides an interface for creating objects in a superclass but allows subclasses to alter the type of object that will be created.

    Factory Method Pattern

  • 27

    This creational design pattern lets a developer copy existing objects without making his code dependent on their classes.

    Prototype Pattern

  • 28

    - This allows developers to produce families of related objects without specifying their concrete classes. - A family of objects that are usually used together or a set of objects that are dependent on each other in some way.

    Abstract Factory Pattern

  • 29

    This creational design pattern allows developers to construct complex objects step by step. The pattern allows developers to produce different types and representations of an object using the same construction code.

    Builder Pattern

  • 30

    Which statement is NOT TRUE about Creational Patterns?

    These patterns deal with the arrangement and relationship between the classes in the software system.

  • 31

    Which statement is NOT TRUE about Structural patterns

    These patterns are concerned with how classes and objects behave in a system software and how objects communicate with each other.

  • 32

    This structural design pattern allows objects with incompatible interfaces to collaborate. This pattern converts the interface of a class into another interface as expected by the client application.

    Adapter Pattern

  • 33

    This allows the developers to split a large class or a set of closely related classes into two (2) separate hierarchies, which are abstraction and implementation, that can be developed independently of each other.

    Bridge Pattern

  • 34

    This design pattern allows developers to compose objects into tree structures and then work with these structures treating them as individual objects.

    Composite Pattern

  • 35

    This allows developers to attach new behaviors to objects by placing these objects inside special wrapper objects that contain the behaviors.

    Decorator Pattern

  • 36

    This allows developers to fit more objects into the available amount of RAM by sharing common parts of state between multiple objects instead of keeping all of the data in each other.

    Flyweight Pattern

  • 37

    This design pattern allows developers to provide a substitute or placeholder for another object. This controls access to the original object, allowing developers to perform something before or after the requests gets through to the original object.

    Proxy Pattern

  • 38

    Which statement is NOT TRUE about Behavioral Patterns

    These patterns deal with the arrangement and relationship between the classes in the software system

  • 39

    This design pattern allows developers to traverse elements of a collection without exposing its underlying representation, such as list, stack, and tree. This pattern is used for sequentially iterating and accessing items from a collection of items.

    Iterator Pattern

  • 40

    This design pattern allows developers to define a subscription mechanism to notify multiple objects about any events that happen to the object they are observing. This means that when an object changes state, all of its dependents are notified and updated automatically.

    Observer Pattern

  • 41

    This allows developers to define a family of algorithms, put each of them into a separate class, and make their objects interchangeable.

    Strategy Pattern

  • 42

    These are a set of guidelines to be followed that helps developers arrange methods and data structures into classes, and how those classes should be interconnected, which can adapt to the changes in requirements without major code rewrites.

    Design principles