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

RAD - Rapid Application Development is an adaptive software development model based on prototyping and quick feedback with less emphasis on specific planning.

• In general, the RAD approach prioritizes development and building a prototype, rather than planning.
• With rapid application development, developers can quickly make multiple iterations and updates to the software without starting from scratch.
• It also helps in ensuring that the final outcome is more quality-focused and aligns with the end users’ requirements.

Size Oriented Metrics - It has been derived by normalising quality and productivity Point Metrics measures by considering size of the software that has been produced. The organization builds a simple record of size measure for the software projects.

Function-Oriented Metrics - They are also known as Function Point Model. This model generally focuses on the functionality of the software application being delivered. These methods are actually independent of the programming language that is being used in software applications and based on calculating the Function Point (FP). A function point is a unit of measurement that measures the business functionality provided by the business product.

Verifiable - an SRS is verifiable only if every stated requirement can be verified cost effectively. A requirement is verifiable if there is some method to quantifiably measure whether the final software meets that requirement. 

Traceable - an SRS is traceable if the origin of each of its requirements is clear and if it makes it easy to reference each requirement in future development.

Modifiable - an SRS must clearly identify each and every requirement in a systematic manner. If there are any changes, the specific requirements and the dependent ones can be modified accordingly without impact the others.

Complete - an SRS should contain all the features requested by a client.

Software measurement is considered as a management tool which if conducted in an effective manner, helps the project manager and the entire software team to take decisions that lead to successful completion of the project.

Direct measures - It includes software processes like cost and effort applied and products like lines of code produced, execution speed, and other defects that have been reported.

Indirect measures - It include products like functionality, quality, complexity, reliability, maintainability, and many more. - 

Correct answer is Option 4Explanation:

• Fault-based testing aims to detect certain classes of known faults.
• Example: security testing for buffer overflows
• Mutation Testing Fault-based testing strategy
• It is used to evaluate test suite adequacy
• Measures the effectiveness of test cases
• Leads to creation of more effective tests
• Mutation Testing Faults are introduced into the program by creating versions of the program called mutants.

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:

• Six Sigma is a statistical term used to measure the number of defects that processes create.
• The term implies high-quality performance because a process performing at a Six Sigma level allows only 3.4 defects per one million opportunities.

Different sigma levels of quality would lead to the following number of defects.

1. Three Sigma quality – This level of performance produces a defect-free product 93.32% of the time. 770 applications would be processed incorrectly and would require rework every day.
2. Four Sigma quality – This level of performance yields a defect-free product 99.349% of the time. With four sigma quality, 73 applications would need to be corrected every day.
3. Five Sigma quality – Five Sigma performance produces defect-free products and services 99.977% of the time. Every week the bank would need to correct 13 application errors.
4. Six Sigma quality – Six Sigma performance produces a defect-free product 99.99966% of the time; allowing only 3.4 errors per one million opportunities. 10 applications would need to be corrected during the entire year.

Important Points:

Four sigma and six sigma levels of performance both have an error free rate over 99% of the time. However, the large volume of applications in this example makes all of the difference. With numbers this big, it turned out that the four-sigma process made 18,710 more errors than the six sigma process.

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

Therefore, all options are correct

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:

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

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.

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.

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