Software Engineering MCQ Quiz - Objective Question with Answer for Software Engineering - Download Free PDF

During the software requirements gathering phase, it is important to gather information from various sources to ensure that the software product meets the needs of the stakeholders. The following are common methods for gathering information during this phase:

• Conducting interviews with stakeholders: This involves talking to stakeholders such as customers, users, and subject matter experts to get an understanding of their needs and requirements.
• Creating use cases to describe system functionality: This involves creating detailed descriptions of how the system will be used and the various scenarios that it will be used in.
• Analyzing existing documentation and systems: This involves reviewing existing documentation, such as specifications and user manuals, as well as any existing software systems to understand their strengths and weaknesses.
• Designing the user interface for the software: This is not a common method for gathering information during the software requirements gathering phase. While the user interface is an important aspect of software design, it is typically developed after the requirements have been gathered and analyzed.

Therefore, the correct answer is option 4.

A software analyst normally acts as a liaison between the team responsible for development as well as the client. Analyst is accountable for working along with the client for eliciting or refining the requirements. Although, such requirements are made by the client side, the software analyst remains completely equipped with all the knowledge to document those requirements after they have been properly defined.

Black-box testing is a method of software testing that examines the functionality of an application without peering into its internal structures or workings. This method of test can be applied virtually to every level of software testing: unit, integration, system and acceptance. White-box testing (also known as clear box testing, glass box testing, and transparent box testing, and structural testing) is a method of testing software that tests internal structures or workings of an application, as opposed to its functionality. Unit Testing is a level of software testing where individual units/components of software are tested.

Just-in-time (JIT) compilation

• Also, dynamic translation or run-time compilations is a method of executing computer code that involves compilation during program execution (at run time) as opposed to before execution. 
• This may involve the translation of source code, but it is more commonly the translation of bytecode to machine code, which is then executed directly.

Hence the correct answer is option 3.

Boundary Value Analysis is a testing technique that focuses on testing the values at the boundaries of input domains, where the behaviour of the system may change. The technique involves selecting input values that are at the upper and lower boundaries of the input domain, as well as values that are just inside the boundaries.

For computing the square root of an integer value from 1 to 4000, the lower boundary value is 1, and the upper boundary value is 4000. The values just inside the boundaries are 2 and 3999.

Therefore, the correct set of test cases for this scenario would be - [1, 2, 3999, 4000]

The correct answer is Application software

Important Points

• MS Office, Photoshop, and Animagic are examples of Application software
• MS Office is a software bundle provided by Microsoft.
• It includes software like MS Word, MS Excel, MS Powerpoint, MS Outlook, MS Access, MS One Note, and others.

Additional Information

• Photoshop is a powerful photo editing tool by Adobe.
• An Operating System (OS) is an interface between a computer user and computer hardware.
• An operating system is software that performs all the basic tasks like file management, memory management, process management, handling input and output, and controlling peripheral devices such as disk drives and printers.

Concept:

Software development life cycle is the logical process of developing a system that satisfies customer needs and can be developed within the predefined schedule and cost.

Explanation:

Various phases of the software development life cycle are : 

1) Analysis: First thing is to gather and analyze the requirements of the system. The information domain, function, behavioral requirements of the system are understood. These requirements are then well documented.

2) Design: After collecting and analyzing all necessary requirements, design architecture is prepared.

3) Coding: After the design, one can develop the code for the system using some programming language. During this, design is translated into a machine-readable form.

4) Testing: It is done to uncover the errors and fix the bugs.

5) Maintenance: Sometimes errors may get produced after system installation and sometimes the requirements get changed. At that time, the maintenance of the system is needed.

Concept:

System development life cycle (SDLC) is a process followed for a software project, within a software organization. It consists of a detailed plan describing how to develop, maintain, replace and alter or enhance specific software.

The life cycle defines a methodology for improving the quality of software and the overall development process.

Phases of SDLC

Feasibility study

↓

Requirements analysis and specification

↓

Design

↓

Coding and unit testing

↓

Integration and system testing

↓

Maintenance

Therefore, all options are correct

Concept:

Mutlimedia means combination of text, audio, video, graphics, and animation. Mutlimedia project are the multimedia materials which are presented on computer screen.

Explanation:

Phases of a multimedia project are : planning, designing , testing and delivering. 

Some points about multimedia project : 

• Interactive mutlimedia gives the navigational controls to the user. It control what elements are to be delivered.
• It requires creative skills, tools and organization talent to create mutlimedia projects.
• There are two categories in multimedia : linear and non - linear.
• Linear multimedia is without any navigational control example cinema.
• Non - linear provides user interactivity to control progress. Example : computer game.
• Mutlimedia system must be integrated, handled digitally and usually interactive.
• Mutlimedia can be delivered using optical disk, web or distributed network.

Explanation:

• Mean time between failures is the average time between failures and not the average time something works then fails.
  • Mean time between failure (MTBF) = \(\frac{{total\;uptime}}{{number\;of\;breakdowns}}\)
• Mean time to repair is the average time taken to repair something.
  • Mean time to repair (MTTR) = \(\frac{{total\;downtime}}{{number\;of\;breakdowns}}\)

Availability = \(\frac{{total\;uptime}}{{\left( {total\;uptime + total\;downtime} \right)}}\)

       = \(\frac{{MTBF}}{{\left( {MTBF + MTTR} \right)}} \times 100\;\;\;\;\;\;\;\;\;\;\backslash \backslash percentage\;\)

                       = \(\frac{{20*24}}{{\left( {20*24 + 20} \right)}} \times 100\)

       = 0.96 × 100 = 96%

Important Point:

In MTBF, we converted 20 days into hours = 20 × 24 hours.

Explanation:

• The purpose of regression testing is to confirm that a recent program or code change has not adversely affected existing features.
• Regression testing is nothing but a full or partial selection of already executed test cases that are re-executed to ensure existing functionalities work fine.
• This testing is done to make sure that new code changes should not have side effects on the existing functionalities. It ensures that the old code still works once the new code changes are done.

The purpose of regression testing is to select test cases partially or fully to ensure existing functionalities work fine. Thus, regression testing is primarily related to functional testing

Need of Regression Testing

• Regression Testing is required when there is a change in requirements and code is modified according to the requirement or when one of the following has been done.
  • New feature is added to the software
  • Defect fixing
  • Performance issue fix

The correct answer is option 3

Formula:

The total cost of the project = Total development cost + Total maintenance cost

Calculation:

Let p1 be the LOC using L1 and p2 be the LOC using L2.

Total cost of the project using L1 = (p1/1000) x 70,000 + (10 x 1,00,000) = 70p1 + 10,00,000

Total cost of the project using L2 = (p2/1000) x 90,000 + (10 x 40,000) = 90p2 + 4,00,000

Given that p2 = 3xp1

=>70p1 + 10,00,000 = 90p2 + 4,00,000

=>70p1 + 10,00,000 = 270p1 + 4,00,000

=> 200p1 = 6,00,000

=> p1 = 3000

Software requirement specification (SRS) is a description of a software system to be developed.  Specification types that are included are functional, non- functional, interfaces, performance, maintainability etc.

But design specification is not included in software requirement specification.  Design is something related to implementation.

The correct answer is "option 2".

CONCEPT:

CMM which stands for Capability Maturity Model is a benchmark to measure the maturity of an organization's software development process.

EXPLANATION:

The Capability Maturity Model is used to analyze techniques used in developing software products in any organization.

CMM has 5 different levels:

1.Initial: At this level, processes for developing software are Adhoc & not well defined.

2.Repeatable: This level focuses on project management policies establishment.

3.Define: Documentation of procedures & standard guidelines are the major focus of this level.

4.Managed: This level sets quantitative goals for software products as well as for software processes.

5.Optimizing: Using quantitative feedback, this level focuses on continuous process improvement.

Hence, Measurable is not a maturity level as per the Capability Maturity Model.

Additional Information

Levels	Quality/Risk
Initial	Lowest quality/highest risk
Repeatable	Low quality/high risk
Defined	Medium quality/medium risk
Managed	Higher quality/lower risk
Optimizing	Highest quality/lowest risk

Cohesion is like a type of ranking which is used to measure the degree of modules are functionally related

The degree of Cohesion can be defined as

Important Information

• Coincidental cohesion is when parts of a module are grouped arbitrarily
• Logical cohesion is when parts of a module are grouped because they are logically categorized 
• Temporal cohesion is when parts of a module are grouped by when they are processed
• Procedural cohesion is when parts of a module are grouped because they always follow a certain sequence of execution 
• Communicational cohesion if all functions of the module refer to or update the same data structure.
• Sequential cohesion is when parts of a module are grouped because the output from one part is the input to another part like an assembly line 
• Functional cohesion is when parts of a module are grouped because they all contribute to a single well-defined task of the module