ログイン

(Pre-finals) Application Development Mocktest BSIT 505
41問 • 2ヶ月前
  • Xai Alexandrei Delos Reyes
  • 通報

    問題一覧

  • 1

    is the degree to which a software product meets the gathered requirements.

    Software quality

  • 2

    Which statement BEST DESCRIBES Software Quality Assurance?

    it is a set of activities that define and assess the adequacy of software process to provide evidence which establishes confidence that the software processes are appropriate for and produce software products of suitable quality for their intended processes.

  • 3

    Software developers and their organizations rely on this. Software bugs can have immediate impacts on clients or customers.

    Reputation

  • 4

    Poor quality software tends to be expensive to develop and maintain, which can negatively affect organizations or end up maintaining the software in the longer term. These costs are often referred to as “technical debt.”

    Limiting Technical Debt

  • 5

    The development and use of the software might require some form of certification, which can often require evidence of the application of various quality control and assessment measures.

    Software Certification

  • 6

    There may be overriding legal obligations that apply to organizations that use the software. As such, every practicable measure must be taken to demonstrate that the software system does not pose a risk to its users.

    Legality

  • 7

    In cases where a software system is not covered by software certification and legislation, and where its failure is not necessarily business or safety-critical, there can remain moral obligation to the users. This implies that software engineers should do whatever is possible to maximize the quality of their software and to prevent it from containing potentially harmful bugs.

    Ethical Codes of Practice

  • 8

    It displays the functionality of the product under development, but may not actually hold the exact logic of the original software

    Software prototyping

  • 9

    Prototyping software is used to achieve which of the following?

    Allow users to evaluate the software system design and how the software actually works, Clarify the functionalities of the software to both users and developers., Reduce cost and time relative to building software product and iterating the process., Reduce the need to recreate the software system due to some gaps on the implementation.

  • 10

    Which statement is NOT TRUE about Throwaway Prototyping

    The prototypes on this paradigm are reused after the testing in a way that they are altered according to the test results and then reused in a new test cycle

  • 11

    Which statement is NOT TRUE about Evolutionary Prototyping

    This is used in early design stages where the gathered requirements are still unclear

  • 12

    It pertains to how it conveys the look and feel of the final product

    Prototype Fidelity

  • 13

    Its role is to check and test the visual appearance and user flows of a software.

    Low-Fidelity Prototyping

  • 14

    This prototyping technique is used to create a prototype based on hand drawings that represent user interfaces of the software. This allows developers to explore ideas and refine designs quickly.

    Paper-Based Prototyping

  • 15

    It is a visual representation of a product page that developers can use to arrange pages of user interfaces. These are used to create interactive prototypes by linking them together.

    Wireframing

  • 16

    Which statement is NOT TRUE about High-Fidelity Prototyping

    Its role is to check and test the visual appearance and user flows of a software.

  • 17

    It is a formalized peer review process for detecting and correcting defects or bugs in software artifacts.

    Software inspection or software review

  • 18

    Which statement is NOT TRUE about Fagan inspection methodology?

    It is a structured approach to improve software quality.

  • 19

    Who developed the Fagan inspection methodology

    Michael Fagan

  • 20

    S/He leads the inspection team and takes care of logistics.

    Moderator

  • 21

    In Fagan inspection methodology, S/He is the creator of the software artifacts under inspection. S/He will actively answer all the questions regarding the artifacts during the inspection meeting. S/He is responsible for fixing identified defects and bugs in the artifacts.

    Author

  • 22

    In Fagan inspection methodology, S/He is an experienced peer who can be a subject matter expert on the software artifacts under inspection.

    Reader

  • 23

    In Fagan inspection methodology, S/He is responsible for writing and executing test cases for the software module or product. This role is focused on how the product would be tested.

    Tester

  • 24

    What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of requirements and raise questions or concerns. The moderator records identified defects

    Requirements

  • 25

    What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of design, compare it to requirements, and raise questions or concerns.

    Design Inspection

  • 26

    What is the Inspection Type, Based on the Procedure stated? Inspectors review the code, compare it to requirements and/or design, and raise questions or concerns. The moderator records identified defects.

    Code Inspection

  • 27

    What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of test plan or specification, compare it to requirements and/or design, and raise questions or concerns. The moderator records identified defects.

    Test Plan Inspection

  • 28

    Which statement is NOT TRUE about Structured Walkthrough?

    it is the act of systematically convening with fellow programmers to check each other’s code for faultsto ensure the code meets quality standards.

  • 29

    Which statement is NOT TRUE About Code Reviewing or Inspection?

    It is the degree to which a software product meets the gathered requirements

  • 30

    This approach uses automated code analysis techniquesthat can pick out problematic patterns within the source code.

    Tool-Driven Code Review

  • 31

    Which statement BEST DESCRIBES Developer-Driven Code Review?

    The developers In this approach, the developers themselves reviews the code to pick out problems. Reviews the code to pick out problems.

  • 32

    a lightweight variant of the code inspections because it does not rely on face-to-face meetings. This operates on tools and development processes.

    Modern Code Review

  • 33

    In Modern Code Review, it integrates reviewing tools such as Google’s Gerrit and Microsoft’s CodeFlow with version repositories to act as gatekeepers to commits.

    Tool-Driven Code Review

  • 34

    In Modern Code Review, This development approach enforces modern code review and does not use code reviewing tools. This revolves around a mechanism known as a “pull request.”

    Pull-Based Development

  • 35

    in Tool-Driven Code Review, What is the first Step?

    The developer checks out a version from the repository and makes changes.

  • 36

    in Tool-Driven Code Review, What is the second Step?

    This change is then submitted for review. This is often automatically initiated when the developer tries to push his/her change to the central version repository

  • 37

    in Tool-Driven Code Review, What is the third Step?

    Before the commit can be finalized, the patch submitted by the developer is subject to review by a pool of reviewers.

  • 38

    in Tool-Driven Code Review, What is the fourth Step?

    If the reviewers accept the patch, it is then passed to someone who verifies it by testing it, and finally commits the reviewed, verified code fragment to the version repository.

  • 39

    in Pull-Based Development, What is the first Step?

    A developer who does not have the privileges to push his/her changes directly to the central repository takes a clone of the code from the repository then makes changes.

  • 40

    in Pull-Based Development, What is the second Step?

    The developer then submits his/her proposed changes to the repository as a pull request.

  • 41

    in Pull-Based Development, What is the third Step?

    A developer with appropriate privileges (referred to as “integrator”) examines the proposed changes, integrates them with their own clone of source code, and makes the commit

  • 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

    is the degree to which a software product meets the gathered requirements.

    Software quality

  • 2

    Which statement BEST DESCRIBES Software Quality Assurance?

    it is a set of activities that define and assess the adequacy of software process to provide evidence which establishes confidence that the software processes are appropriate for and produce software products of suitable quality for their intended processes.

  • 3

    Software developers and their organizations rely on this. Software bugs can have immediate impacts on clients or customers.

    Reputation

  • 4

    Poor quality software tends to be expensive to develop and maintain, which can negatively affect organizations or end up maintaining the software in the longer term. These costs are often referred to as “technical debt.”

    Limiting Technical Debt

  • 5

    The development and use of the software might require some form of certification, which can often require evidence of the application of various quality control and assessment measures.

    Software Certification

  • 6

    There may be overriding legal obligations that apply to organizations that use the software. As such, every practicable measure must be taken to demonstrate that the software system does not pose a risk to its users.

    Legality

  • 7

    In cases where a software system is not covered by software certification and legislation, and where its failure is not necessarily business or safety-critical, there can remain moral obligation to the users. This implies that software engineers should do whatever is possible to maximize the quality of their software and to prevent it from containing potentially harmful bugs.

    Ethical Codes of Practice

  • 8

    It displays the functionality of the product under development, but may not actually hold the exact logic of the original software

    Software prototyping

  • 9

    Prototyping software is used to achieve which of the following?

    Allow users to evaluate the software system design and how the software actually works, Clarify the functionalities of the software to both users and developers., Reduce cost and time relative to building software product and iterating the process., Reduce the need to recreate the software system due to some gaps on the implementation.

  • 10

    Which statement is NOT TRUE about Throwaway Prototyping

    The prototypes on this paradigm are reused after the testing in a way that they are altered according to the test results and then reused in a new test cycle

  • 11

    Which statement is NOT TRUE about Evolutionary Prototyping

    This is used in early design stages where the gathered requirements are still unclear

  • 12

    It pertains to how it conveys the look and feel of the final product

    Prototype Fidelity

  • 13

    Its role is to check and test the visual appearance and user flows of a software.

    Low-Fidelity Prototyping

  • 14

    This prototyping technique is used to create a prototype based on hand drawings that represent user interfaces of the software. This allows developers to explore ideas and refine designs quickly.

    Paper-Based Prototyping

  • 15

    It is a visual representation of a product page that developers can use to arrange pages of user interfaces. These are used to create interactive prototypes by linking them together.

    Wireframing

  • 16

    Which statement is NOT TRUE about High-Fidelity Prototyping

    Its role is to check and test the visual appearance and user flows of a software.

  • 17

    It is a formalized peer review process for detecting and correcting defects or bugs in software artifacts.

    Software inspection or software review

  • 18

    Which statement is NOT TRUE about Fagan inspection methodology?

    It is a structured approach to improve software quality.

  • 19

    Who developed the Fagan inspection methodology

    Michael Fagan

  • 20

    S/He leads the inspection team and takes care of logistics.

    Moderator

  • 21

    In Fagan inspection methodology, S/He is the creator of the software artifacts under inspection. S/He will actively answer all the questions regarding the artifacts during the inspection meeting. S/He is responsible for fixing identified defects and bugs in the artifacts.

    Author

  • 22

    In Fagan inspection methodology, S/He is an experienced peer who can be a subject matter expert on the software artifacts under inspection.

    Reader

  • 23

    In Fagan inspection methodology, S/He is responsible for writing and executing test cases for the software module or product. This role is focused on how the product would be tested.

    Tester

  • 24

    What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of requirements and raise questions or concerns. The moderator records identified defects

    Requirements

  • 25

    What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of design, compare it to requirements, and raise questions or concerns.

    Design Inspection

  • 26

    What is the Inspection Type, Based on the Procedure stated? Inspectors review the code, compare it to requirements and/or design, and raise questions or concerns. The moderator records identified defects.

    Code Inspection

  • 27

    What is the Inspection Type, Based on the Procedure stated? Inspectors review each page of test plan or specification, compare it to requirements and/or design, and raise questions or concerns. The moderator records identified defects.

    Test Plan Inspection

  • 28

    Which statement is NOT TRUE about Structured Walkthrough?

    it is the act of systematically convening with fellow programmers to check each other’s code for faultsto ensure the code meets quality standards.

  • 29

    Which statement is NOT TRUE About Code Reviewing or Inspection?

    It is the degree to which a software product meets the gathered requirements

  • 30

    This approach uses automated code analysis techniquesthat can pick out problematic patterns within the source code.

    Tool-Driven Code Review

  • 31

    Which statement BEST DESCRIBES Developer-Driven Code Review?

    The developers In this approach, the developers themselves reviews the code to pick out problems. Reviews the code to pick out problems.

  • 32

    a lightweight variant of the code inspections because it does not rely on face-to-face meetings. This operates on tools and development processes.

    Modern Code Review

  • 33

    In Modern Code Review, it integrates reviewing tools such as Google’s Gerrit and Microsoft’s CodeFlow with version repositories to act as gatekeepers to commits.

    Tool-Driven Code Review

  • 34

    In Modern Code Review, This development approach enforces modern code review and does not use code reviewing tools. This revolves around a mechanism known as a “pull request.”

    Pull-Based Development

  • 35

    in Tool-Driven Code Review, What is the first Step?

    The developer checks out a version from the repository and makes changes.

  • 36

    in Tool-Driven Code Review, What is the second Step?

    This change is then submitted for review. This is often automatically initiated when the developer tries to push his/her change to the central version repository

  • 37

    in Tool-Driven Code Review, What is the third Step?

    Before the commit can be finalized, the patch submitted by the developer is subject to review by a pool of reviewers.

  • 38

    in Tool-Driven Code Review, What is the fourth Step?

    If the reviewers accept the patch, it is then passed to someone who verifies it by testing it, and finally commits the reviewed, verified code fragment to the version repository.

  • 39

    in Pull-Based Development, What is the first Step?

    A developer who does not have the privileges to push his/her changes directly to the central repository takes a clone of the code from the repository then makes changes.

  • 40

    in Pull-Based Development, What is the second Step?

    The developer then submits his/her proposed changes to the repository as a pull request.

  • 41

    in Pull-Based Development, What is the third Step?

    A developer with appropriate privileges (referred to as “integrator”) examines the proposed changes, integrates them with their own clone of source code, and makes the commit