Software Engineering MCQs

 What is the first step in the software development lifecycle?

  1. System Design
  2. Coding
  3. System Testing
  4. Preliminary Investigation and Analysis

What does the study of an existing system refer to?

  1. Details of DFD
  2. Feasibility Study
  3. System Analysis
  4. System Planning

Which of the following is involved in the system planning and designing phase of the Software Development Life Cycle (SDLC)?

  1. Sizing
  2. Parallel run
  3. Specification freeze
  4. All of the above

What does RAD stand for?

  1. Rapid Application Document
  2. Rapid Application Development
  3. Relative Application Development
  4. None of the above

      RAD  is categorized as an agile development method, which is meant to accomplish a quick turnaround and high-end outcomes.

Which of the following prototypes does not associated with Prototyping Model?

  1. Domain Prototype
  2. Vertical Prototype
  3. Horizontal Prototype
  4. Diagonal Prototype

The major drawback of RAD model is __________.

  1. It requires highly skilled developers/designers.
  2. It necessitates customer feedbacks.
  3. It increases the component reusability.
  4. Both (a) & (c)

Which of the following does not relate to Evolutionary Process Model?

  1. Incremental Model
  2. Concurrent Development Model
  3. WINWIN Spiral Model
  4. All of the above

What is the major drawback of the Spiral Model?

  1. Higher amount of risk analysis
  2. Doesn't work well for smaller projects
  3. Additional functionalities are added later on
  4. Strong approval and documentation control
      • Expensive
      • Doesn't work well for smaller projects
      • Risk analysis requires highly skilled experts.

Model selection is based on __________.

  1. Requirements
  2. Development team & users
  3. Project type & associated risk
  4. All of the above






  • What is software management and what are the responsibilities of a software manager?

    It is the process of managing the activities like time, cost and quality while developing the software. The software manager is engaged with managing the activities like planning project, monitoring the progress, communication among the stakeholders, and managing the risks and resources for the smooth execution of development within the constraints.

     
     
  • Q13.

    Mentions some software management tools?

    The tools are used as per the requirement, the few popular and widely used software management tools are Gantt chart, PERT chart, Resource histogram, Critical path analysis, Status reports etc.

     
     
  • Q14.

    What do you mean by feasibility study?

    It gauges how beneficial and practical the project development will be for the organization. The feasibility study encompasses economic, technical and operational feasibility of the project.

     
     
  • Q15.

    Explain software metric?

    It provides measures of various aspects of software process and product. They are divided into requirement metrics, process metrics, and product metrics.

     
     
  • Q16.

    What is the difference between structured English and pseudocode?

    Structured English is the native one and is used to write the structure of the program module using programming language, and the pseudocode is the programming language that uses the native English words to write the bits of code.

     
     
  • Q17.

    Do you know black-box and White-box testing?

    Black Box testing – It checks if the desired outputs are produced when the valid inputs are given.

    White Box testing – It checks the valid output and input and also if the code is implemented correctly.

     
     
  • Q18.

    Explain the difference between validation and verification?

    Validation – It checks if the product is made as per the user requirements.

    Verification – It checks if the proper steps are followed to produce the product.

    Validation confirms the right product and the verification ensures the product is built in the right way.
     
     
  • Q19.

    Explain various types of software maintenance?

    The various types of software maintenance are:

    • Corrective – removing the errors found.
    • Adaptive – tackling changes in hardware and software environments.
    • Perfective Maintenance – implementing changes in existing or new requirements.
    • Preventive Maintenance – appropriate measures to avoid future problems.
     
     
  • Q20.

    What is agile software philosophy?

    It is a philosophy for managing software projects and teams. It has the similarities to lean manufacturing principles for "eliminating wastes", or say "abstraction".

     
     
  • Q21.

    Differentiate between mutex and semaphore?

    Both of them are used as synchronization primitives. But have a big difference.

    • Mutex – the Only thread that locked or acquired can be unlocked.
    • Semaphore – A different thread can signal of the thread waiting on a semaphore.




  •  act consistently with the public interest.”
  •  act in a manner that is in the best interests of his expertise and favour.”
  •  ensure that their products only meet the SRS.” d) all of the mentioned
  •  all of the mentioned

  •  Unauthorized modification of computer material
  •  Unauthorized access to computer material
  •  Dissemination of viruses or other malware
  •  All of the above
  •  Software is documentation and configuration of data
  •  Software is set of programs
  •  Software is set of programs, documentation & configuration of data
  •  None of the mentioned

  •  Software development
  •  Software dependence
  •  Software validation
  •  Software specification
  •  Software Security
  •  Software reuse
  •  Software processes
  •  Software Validation

  •  Prototyping Model
  •  RAD Model
  •  Build & Fix Model
  •  Waterfall Model
  •  System Development Life cycle
  •  Software Design Life Cycle
  •  Software Development Life Cycle
  •  System Design Life Cycle
  •  Barry Boehm
  •  Pressman
  •  Royce
  •  Pressman
  •  Concurrent Model
  •  Spiral Model
  •  WINWIN Spiral Model
  •  Incremental Model
  •  Customised Products
  •  Generic and Customised Products
  •  Generic Products
  •  None of the above
  •  1 Phases
  •  2 Phases
  •  3 Phases
  •  4 Phases
  •  Graph Testing
  •  Basic path
  •  Glass box testing
  •  Dataflow
  •  alteration & iteration
  •  multiple exit from loops
  •  sequencing
  •  only 1 and 3
  •  Organizing manual
  •  Personal poling bank
  •  Administration policy manual
  •  Procedure log
  •  Non-Functional Requirements
  •  Goals of Implementation
  •  Functional Requirements
  •  Algorithms for Software Implementation

  •  constructive cost Model
  •  common control Model
  •  composition cost Model
  •  consumed cost Model

  •  Errors per KLOC
  •  Defects per KLOC
  •  $ per KLOC
  •  Pages of documentation per KLOC
  •  Direct measures
  •  Coding
  •  Indirect measures
  •  None of the above
  •  track potential risk
  •  help in assessment of status of ongoing project.
  •  both 1 and 2
  •  none of the mentioned
  •  Effort Applied
  •  Efficiency
  •  Effort Applied
  •  All of the mentioned

  •  number of user inputs
  •  number of lines of code
  •  number of Functions
  •  amount of memory usage
  •  Time required to become moderately efficient in system usage
  •  Net increase in productivity
  •  Intellectual skill to learn the system
  •  All of the mentioned

  •  Software functionality
  •  Software maintainability
  •  Software development
  •  Both Software functionality & maintainability

  •  Actively involve system users in the analysis, design, and development phases
  •  Focus initially on creating a prototype that looks and acts like the desired system
  •  Accelerate collecting the business requirements through an interactive and iterative construction approach
  •  All of the above

  •  The importance of self-organizing teams as well as communication and collaboration between team members and customers.
  •  Recognition that change represents opportunity.
  •  Emphasis on rapid delivery of software that satisfies the customer.
  •  Having a separate testing phase after a build phase.
  •  Unambiguous
  •  Distinctly specified
  •  Functional
  •  All of these

  •  Management Myths
  •  Customer Myths
  •  Practitioner Myths
  •  All of the above

  •  Customer involvement
  •  Embrace change
  •  Incremental delivery
  •  Following the plan

  •  Prototyping
  •  Iterative
  •  Timeboxing
  •  Glassboxing

  •  Pareto analysis is a statistical method used for analyzing causes, and is one of the primary tools for quality management.
  •  Reliability of a software specifies the probability of failure-free operation of that software for a given time duration.
  •  The reliability of a system can also be specified as the Mean Time To Failure (MTTF).
  •  In white-box testing, the test cases are decided from the specifications or the requirements.
  •  Stereotype is used for extending the UML language
  •  Stereotyped class must be abstract
  •  The stereotype indicates that the UML element cannot be changed
  •  UML profiles can be stereotyped for backward compatibility
  •  Ability to undergo change
  •  Adaptability to new environments
  •  Operational characteristics
  •  Production costs and scheduling














Comments

Popular posts from this blog