Explore topic-wise InterviewSolutions in .

This section includes InterviewSolutions, each offering curated multiple-choice questions to sharpen your knowledge and support exam preparation. Choose a topic below to get started.

1.

According to a statistical report: “over 30% of all software projects are cancelled before completion and over 70% of the remainder fail to deliver expected features”. What must be the reason for such a situation ?(a) Poor change management(b) Poor requirements management(c) Poor quality control(d) All of the mentionedI got this question in a national level competition.I would like to ask this question from Requirement Management topic in section Requirement Engineering of Software Engineering

Answer»

Right OPTION is (b) Poor requirements management

Easy explanation: Fundamental to the problem MENTIONED in the STATISTICAL REPORT is poor requirements management. Option a and c are its SUB parts.

2.

What functionality of Requirement Management Tool (RMT) is depicted by the statement: “the tool should be able to automatically detect relations between artifacts. For example information retrieval techniques, monitoring of change history, naming schemas or model transformations.”(a) Automatic Link Detection(b) Documentation Support(c) Graphical Representation(d) Automatic Link Creation and ChangeThe question was posed to me in semester exam.This intriguing question comes from Requirement Management topic in chapter Requirement Engineering of Software Engineering

Answer»

The CORRECT OPTION is (a) Automatic LINK DETECTION

Easy explanation: DOORS is one such tool that SUPPORTS Automatic Link Detection.

3.

Which of the following is a requirement management activity ?(a) Investigation(b) Design(c) Construction and Test(d) All of the mentionedThis question was addressed to me during an online interview.This interesting question is from Requirement Management topic in portion Requirement Engineering of Software Engineering

Answer»

Right OPTION is (d) All of the mentioned

Explanation: All the OPTIONS are the activities of requirement MANAGEMENT.

4.

Which of the following is not a Requirement Management workbench tool ?(a) RTM(b) DOORS(c) Rational Suite(d) RDD 100I got this question during a job interview.My doubt stems from Requirement Management topic in portion Requirement Engineering of Software Engineering

Answer» RIGHT OPTION is (c) RATIONAL Suite

Explanation: Rational Suite is an environment tool for REQUIREMENT management.
5.

Requirements Management has a high initial start-up cost but does not need ongoing funding throughout a project.(a) True(b) FalseThis question was posed to me in semester exam.This interesting question is from Requirement Management topic in division Requirement Engineering of Software Engineering

Answer»

Correct answer is (b) False

The best explanation: Requirements Management NEEDS CONTINUED funding throughout a PROJECT.Project funding is often limited at the onset of a project, restricted to those aspects of the project which are tangible and VISIBLE, and subsequently allocated in a phase-by-phase manner.

6.

Requirements Management is a prerequisite for Quality-Oriented Development.(a) True(b) FalseThe question was asked during an internship interview.I would like to ask this question from Requirement Management topic in chapter Requirement Engineering of Software Engineering

Answer»

The correct ANSWER is (a) True

The best I can EXPLAIN: Quality makes no sense without reference to requirements, which means quality-oriented DEVELOPMENT is requirements-driven development, thus requirements management is a prerequisite for quality-oriented development.

7.

Requirements traceability is one of the most important part requirement management. It may also be referred to as the heart of requirement management.(a) True(b) FalseI got this question in exam.The question is from Requirement Management in division Requirement Engineering of Software Engineering

Answer»

The CORRECT answer is (a) True

Explanation: Requirements traceability refers to the ability to describe and follow the life of a requirement in both forwards and BACKWARDS direction. Requirements can be traced from its origins, through its development and specification, to its subsequent DEPLOYMENT and use, and through periods of ongoing refinement and iteration in any of these phases.

8.

Why is Requirements Management Important ? It is due to the changes(a) to the environment(b) in technology(c) in customer’s expectations(d) in all of the mentioned.I got this question during an interview for a job.Question is taken from Requirement Management in chapter Requirement Engineering of Software Engineering

Answer»

Right choice is (d) in all of the mentioned.

To elaborate: Systems continue to be built as the advancement of NEW PRODUCTS being LAUNCHED in the market and so does the market CHANGES, the technology and in turn customer’s expectation.

9.

Considering the example of issue/return of a book, cataloging etc. in a library management.What type of management requirement is being depicted here?(a) Enduring(b) Volatile(c) Both Enduring & Volatile(d) All of the mentionedThe question was posed to me in an interview for job.The doubt is from Requirement Management topic in chapter Requirement Engineering of Software Engineering

Answer»

Correct option is (a) Enduring

The best EXPLANATION: For library MANAGEMENT system issue/return of a book, CATALOGING etc. are core ACTIVITIES and are stable for any system.

10.

Which two requirements are given priority during Requirement Management of a product ?(a) User and Developer(b) Functional and Non-functional(c) Enduring and Volatile(d) All of the mentionedThe question was posed to me during an interview.I would like to ask this question from Requirement Management topic in division Requirement Engineering of Software Engineering

Answer»

Right OPTION is (C) Enduring and Volatile

Easy explanation: Enduring requirements are core requirements & are related to main ACTIVITY of the organization while volatile requirements are likely to change during software development life cycle or after delivery of the PRODUCT.

11.

Narrative essay is one of the best types of specification document ?(a) True(b) FalseThe question was asked in class test.The query is from Requirement Documentation in section Requirement Engineering of Software Engineering

Answer»

Correct option is (b) False

For EXPLANATION I would say: Narrative essay is ONE of the worst types of SPECIFICATION DOCUMENT as it is difficult to change, difficult to be precise, has scope for contradictions, etc.

12.

Consider the following Statement: “The product should have a good human interface.”What characteristic of SRS is being depicted here ?(a) Consistent(b) Non-Verifiable(c) Correct(d) AmbiguousThis question was posed to me in an internship interview.Question is from Requirement Documentation in chapter Requirement Engineering of Software Engineering

Answer»

The correct option is (B) Non-Verifiable

To elaborate: An SRS is verifiable, if and only if, every REQUIREMENT STATED THEREIN is verifiable. The statement can only be answered on completion of the software and customer evaluation but still human interface will vary from person to person.

13.

Consider the following Statement: “The data set will contain an end of file character.”What characteristic of SRS is being depicted here ?(a) Consistent(b) Non-verifiable(c) Correct(d) AmbiguousThe question was asked during a job interview.This intriguing question comes from Requirement Documentation topic in chapter Requirement Engineering of Software Engineering

Answer» CORRECT answer is (b) Non-verifiable

Explanation: An SRS is UNAMBIGUOUS if and only if, EVERY requirement stated therein has only one unique interpretation. The given statement does not answer the question: “which DATA set will have an end of file character ?”.
14.

Consider the following Statement: “The output of a program shall be given within 10 secs of event X 10% of the time.”What characteristic of SRS is being depicted here ?(a) Consistent(b) Verifiable(c) Non-verifiable(d) CorrectThe question was posed to me by my college director while I was bunking the class.The origin of the question is Requirement Documentation in portion Requirement Engineering of Software Engineering

Answer»

Right option is (b) Verifiable

The best explanation: An SRS is verifiable, if and only if, EVERY requirement stated THEREIN is verifiable.Here the GIVEN condition can be VERIFIED during testing phase.

15.

Which of the following is not included in SRS ?(a) Performance(b) Functionality(c) Design solutions(d) External InterfacesThis question was addressed to me in homework.My enquiry is from Requirement Documentation in portion Requirement Engineering of Software Engineering

Answer» RIGHT CHOICE is (c) Design solutions

The explanation: The SRS DOCUMENT concentrates on:”what needs to be done” and carefully avoids the solution (“how to do”) aspects.
16.

Which of the following is included in SRS ?(a) Cost(b) Design Constraints(c) Staffing(d) Delivery ScheduleI have been asked this question by my school teacher while I was bunking the class.I need to ask this question from Requirement Documentation in section Requirement Engineering of Software Engineering

Answer»

Correct option is (b) Design CONSTRAINTS

Easiest explanation: Design constraints include standards to be incorporated in the software, implementation LANGUAGE, resource limits, operating environment ETC.

17.

The SRS document is also known as _____________ specification.(a) black-box(b) white-box(c) grey-box(d) none of the mentionedI have been asked this question during an online interview.The above asked question is from Requirement Documentation in division Requirement Engineering of Software Engineering

Answer» RIGHT answer is (a) black-BOX

Best explanation: The system is considered as a black box whose INTERNAL DETAILS are not known that is, only its VISIBLE external (input/output) behavior is documented.
18.

The SRS is said to be consistent if and only if(a) its structure and style are such that any changes to the requirements can be made easily while retaining the style and structure(b) every requirement stated therein is one that the software shall meet(c) every requirement stated therein is verifiable(d) no subset of individual requirements described in it conflict with each otherI got this question in final exam.I want to ask this question from Requirement Documentation in portion Requirement Engineering of Software Engineering

Answer»

The correct OPTION is (d) no subset of individual requirements described in it conflict with each other

The explanation: Real WORLD object MAY conflict with each other for example one requirement says that all lights should be RED while the other states that all lights should GREEN.

19.

Which of the following property of SRS is depicted by the statement : “Conformity to a standard is maintained” ?(a) Correct(b) Complete(c) Consistent(d) ModifiableI had been asked this question by my college professor while I was bunking the class.This key question is from Requirement Documentation in section Requirement Engineering of Software Engineering

Answer»

Correct answer is (B) Complete

The best explanation: The SRS is complete full LABELING and referencing of all figures, tables etc. and definition of all TERMS and units of measure is DEFINED.

20.

Which of the following property does not correspond to a good Software Requirements Specification (SRS) ?(a) Verifiable(b) Ambiguous(c) Complete(d) TraceableThis question was addressed to me in exam.This interesting question is from Requirement Documentation topic in section Requirement Engineering of Software Engineering

Answer»

The CORRECT answer is (b) Ambiguous

For explanation I would SAY: The SRS should be unambiguous in nature which means each SENTENCE in SRS should have a UNIQUE INTERPRETATION.

21.

Coad and Yourdon suggested _______ selection characteristics that should be used as an analyst considers each potential object for inclusion in the requirement analysis model.(a) Three(b) Four(c) Five(d) SixThis question was addressed to me during an online exam.Enquiry is from Requirement Analysis topic in division Requirement Engineering of Software Engineering

Answer»

Correct CHOICE is (d) Six

Explanation: Retained information, Needed SERVICES, MULTIPLE attributes, Common attributes, Common operations and Essential REQUIREMENTS are the six criterion mentioned by Coad and Yourdon.

22.

Requirements should specify ‘what’ but not ‘how’.(a) True(b) FalseThis question was posed to me in an online quiz.Asked question is from Requirement Analysis in division Requirement Engineering of Software Engineering

Answer»

The CORRECT CHOICE is (a) True

To explain I WOULD SAY: ‘What’ refers to a system’s purpose, while ‘How’ refers to a system’s structure and BEHAVIOR.

23.

Requirements Analysis is an Iterative Process.(a) True(b) FalseI had been asked this question during an interview.I would like to ask this question from Requirement Analysis topic in division Requirement Engineering of Software Engineering

Answer»

Correct ANSWER is (a) True

Explanation: Requirements analysis is CONDUCTED ITERATIVELY with functional analysis to optimize PERFORMANCE requirements for identified functions, and to VERIFY that synthesized solutions can satisfy customer requirements.

24.

The requirements that result from requirements analysis are typically expressed from one of three perspectives or views.WhaT is that perspective or view ?(a) Developer(b) User(c) Non-Functional(d) PhysicalI got this question in a national level competition.The doubt is from Requirement Analysis in section Requirement Engineering of Software Engineering

Answer»

Correct CHOICE is (d) Physical

To elaborate: The perspectives or views have been DESCRIBED as the Operational, Functional, and Physical views.All THREE are necessary and MUST be coordinated to fully UNDERSTAND the customers’ needs and objectives.

25.

_________ and _________ are the two issues of Requirement Analysis.(a) Performance, Design(b) Stakeholder, Developer(c) Functional, Non-Functional(d) None of the mentionedThis question was posed to me during an interview for a job.The doubt is from Requirement Analysis in division Requirement Engineering of Software Engineering

Answer» RIGHT option is (b) Stakeholder, Developer

Easy EXPLANATION: Option a and c are the TYPES of requirements and not the ISSUES of requirement ANALYSIS..
26.

Requirements analysis is critical to the success of a development project.(a) True(b) False(c) Depends upon the size of project(d) None of the mentionedThis question was addressed to me by my college director while I was bunking the class.My question is based upon Requirement Analysis in portion Requirement Engineering of Software Engineering

Answer»

The correct answer is (a) True

Explanation: REQUIREMENTS must be ACTIONABLE, measurable, testable, RELATED to identified business needs or opportunities, and defined to a level of DETAIL sufficient for SYSTEM design.

27.

Traceability is not considered in Requirement Analysis.(a) True(b) FalseThe question was posed to me at a job interview.The query is from Requirement Analysis in section Requirement Engineering of Software Engineering

Answer»

Correct option is (b) False

Best explanation: Requirements TRACEABILITY is concerned with documenting the life of a requirement and PROVIDING bi-directional traceability between various ASSOCIATED requirements, hence requirements must be traceable.

28.

How many phases are there in Requirement Analysis ?(a) Three(b) Four(c) Five(d) SixI have been asked this question in an international level competition.I'm obligated to ask this question of Requirement Analysis topic in division Requirement Engineering of Software Engineering

Answer»

The correct CHOICE is (c) Five

The EXPLANATION is: PROBLEM RECOGNITION, Evaluation and SYNTHESIS (focus is on what not how), Modeling, Specification and Review are thefive phases.

29.

How many feasibility studies is conducted in Requirement Analysis ?(a) Two(b) Three(c) Four(d) None of the mentionedThis question was posed to me in class test.This interesting question is from Requirement Analysis topic in chapter Requirement Engineering of Software Engineering

Answer»

The correct answer is (B) Three

To explain: Economic FEASIBILITY (cost/benefit ANALYSIS), Technical feasibility (hardware/software/people, etc.) and Legal feasibility STUDIES are DONE in Requirement Analysis.

30.

Which of the following is not a diagram studied in Requirement Analysis ?(a) Use Cases(b) Entity Relationship Diagram(c) State Transition Diagram(d) Activity DiagramI had been asked this question during an interview.Query is from Requirement Analysis topic in chapter Requirement Engineering of Software Engineering

Answer»

Correct CHOICE is (d) Activity DIAGRAM

Easiest EXPLANATION: Activity Diagram comes under the DESIGN phase of SDLC.

31.

Who controls the FAST (Facilitated Application Specification Techniques) meeting ?(a) System Analyst(b) Scribe(c) Facilitator(d) ManagerI had been asked this question in quiz.I'd like to ask this question from Requirement Elicitation Techniques topic in division Requirement Engineering of Software Engineering

Answer»

The correct choice is (c) FACILITATOR

The explanation is: A Facilitator (a customer/developer/an outsider) CONTROLS the FAST meeting.His ROLE is to ensure that the meeting is productive.

32.

How many phases are there in Brainstorming ?(a) Two(b) Three(c) Four(d) All of the mentionedI had been asked this question during a job interview.This interesting question is from Requirement Elicitation Techniques in section Requirement Engineering of Software Engineering

Answer»

Right choice is (B) Three

For explanation: Preparation, Execution and Follow up are the three phases to be ACHIEVED for a successful BRAINSTORMING session.

33.

Choose the disadvantage of using SSM as an elicitation technique.(a) It incorporates human element into design(b) SSM is in its infant stage(c) SSM is suitable for new systems(d) Standard methodologies like Role Exploration, Issue Resolution and Reorganization support SSMThe question was posed to me during a job interview.Question is taken from Requirement Elicitation Techniques topic in section Requirement Engineering of Software Engineering

Answer»

Correct OPTION is (b) SSM is in its INFANT stage

Explanation: SSM is still in its infancy.It is EVOLVING and its industrial usage is low.

34.

To ensure that a given root definition is rigorous and comprehensive, The Lancaster team proposed several criteria that are summarized in the mnemonic CATWOE in Soft Systems Methodology (SSM).Which of the following alphabet is representing an entirely different meaning to SSM ?(a) C – Customer(b) A – Actor(c) T – Transformation(d) E – ER ModelThis question was posed to me in an international level competition.This is a very interesting question from Requirement Elicitation Techniques in chapter Requirement Engineering of Software Engineering

Answer» CORRECT OPTION is (d) E – ER Model

Easiest EXPLANATION: ‘E’ in CATWOE stands for Environmental constraints.
35.

Which of the following Requirement Elicitation Techniques is applicable to messy, changing and ill-defined problem situations ?(a) Quality Function Deployment (QFD)(b) Prototyping(c) Soft Systems Methodology (SSM)(d) Controlled Requirements Expression (CORE)I got this question by my school principal while I was bunking the class.The question is from Requirement Elicitation Techniques topic in division Requirement Engineering of Software Engineering

Answer»

Correct option is (c) Soft SYSTEMS Methodology (SSM)

The explanation: Soft systems methodology (SSM) is a systemic approach for tackling real-world PROBLEMATIC situations.It is a COMMON misunderstanding that SSM is a methodology for dealing solely with ‘soft problems’ (problems which INVOLVE psychological, social, and cultural elements). SSM does not differentiate between ‘soft’ and ‘hard’ problems, it merely provides a different way of dealing with situations PERCEIVED as problematic.

36.

QFD works best if it has management commitment.(a) True(b) FalseI had been asked this question in examination.Asked question is from Requirement Elicitation Techniques topic in division Requirement Engineering of Software Engineering

Answer»

Correct ANSWER is (a) True

The explanation: QFD involves heavy investment in INITIAL stages, thus bounding the management to provide APPROPRIATE FUNDING for the development process .

37.

Keeping the requirements of QFD in mind which of the following is not an example of an Expected Requirement ?(a) Ease of software installation(b) Overall operational correctness and reliability(c) Specific system functions(d) Quality graphical displayThe question was asked in final exam.Question is taken from Requirement Elicitation Techniques in section Requirement Engineering of Software Engineering

Answer»

Correct choice is (c) Specific system functions

Explanation: Expected requirements are so FUNDAMENTAL that a CUSTOMER does not explicitly STATE them.System functions comes under the CATEGORY of Normal requirements in QFD which is COMPULSORY to be defined,hence is not an expected requirement.

38.

How is throwaway prototype different from evolutionary prototype ?(a) It involves successive steps(b) It involves just one task(c) The prototype is built with the idea that it will eventually be converted into final system(d) It has a shorter development timeThis question was posed to me in homework.This interesting question is from Requirement Elicitation Techniques topic in chapter Requirement Engineering of Software Engineering

Answer» RIGHT option is (b) It involves just one task

The BEST I can explain: Except option b all other options represent the CHARACTERISTICS of an evolutionary PROTOTYPE.
39.

How is brainstorming different from JAD ? Brainstorming sessions(a) last for about 2-3 hours(b) last for about 2-3 days(c) cover the technology used for the development(d) all of the mentionedI had been asked this question in semester exam.My question is based upon Requirement Elicitation Techniques topic in chapter Requirement Engineering of Software Engineering

Answer»

The correct choice is (a) LAST for about 2-3 hours

To ELABORATE: Brainstorming is a group or individual creativity TECHNIQUE by which efforts are made to find a conclusion for a specific problem by gathering a list of ideas SPONTANEOUSLY contributed by its member(s).The IDEA is to quickly reach to an approved solution ASAP.

40.

Which one of the following is not an actor in JAD sessions ?(a) User(b) Tester(c) Scribe(d) SponsorI have been asked this question by my school principal while I was bunking the class.Origin of the question is Requirement Elicitation Techniques -1 topic in division Requirement Engineering of Software Engineering

Answer»

Correct OPTION is (B) TESTER

The explanation is: A Tester’s role is SEEN in after coding phase rather than in elicitation phase.

41.

What of the following is not an output of a JAD session ?(a) Context Diagrams(b) DFDs(c) ER model(d) UML diagramsI have been asked this question in semester exam.I'd like to ask this question from Requirement Elicitation Techniques -1 in chapter Requirement Engineering of Software Engineering

Answer»

The correct CHOICE is (d) UML DIAGRAMS

Easy explanation: Unified MODELING Language (UML) diagrams are constructed during the design phase of the SDLC.

42.

IBIS is a more structured approach than CORE.(a) True(b) FalseI got this question in unit test.This interesting question is from Requirement Elicitation Techniques -1 in portion Requirement Engineering of Software Engineering

Answer»

The correct answer is (a) True

The explanation: IBIS is a more STRUCTURED approach as it captures information which is consistent and important.On the other hand CORE gives IMPORTANCE to every view POINT even if it is OBSOLETE.

43.

How many steps are involved in Feature Oriented Domain Analysis (FODA) ?(a) Two(b) Three(c) Four(d) FiveI had been asked this question in an international level competition.My question is based upon Requirement Elicitation Techniques -1 in chapter Requirement Engineering of Software Engineering

Answer»

The CORRECT option is (b) Three

For EXPLANATION I would SAY: Context Analysis, Domain Modeling and Architecture Modeling are the three steps involved in Feature ORIENTED Domain Analysis (FODA).

44.

Which of the following Requirement Elicitation Techniques removes the poor understanding of application domain and lack of common terminology between the users and the analysts ?(a) FODA(b) CORE(c) IBIS(d) PrototypingI got this question during an online exam.Question is from Requirement Elicitation Techniques -1 topic in portion Requirement Engineering of Software Engineering

Answer»

Right choice is (a) FODA

For explanation: Feature ORIENTED DOMAIN Analysis (FODA) is defined as the PROCESS of identifying, COLLECTING, organizing and representing relevant INFORMATION in a domain .

45.

How is CORE different from IBIS ?(a) Iterative in nature(b) Redundancies are removed(c) It is simple and an easier method to use(d) Consistency problems are addressed in COREI have been asked this question by my school teacher while I was bunking the class.Question is from Requirement Elicitation Techniques -1 in section Requirement Engineering of Software Engineering

Answer»

Correct OPTION is (d) Consistency problems are ADDRESSED in CORE

For explanation: Preliminary data COLLECTION is DONE in CORE to get some broad level data on each view point to structure the view point and to CHECK consistency from within and outside the viewpoints.

46.

Choose a framework that corresponds to Issue Based Information System (IBIS).(a) Idea -> Question -> Argument(b) Question -> Idea -> Argument(c) Issue -> Position -> Justification(d) Both Question -> Idea -> Argument and Issue -> Position -> JustificationI had been asked this question in my homework.This interesting question is from Requirement Elicitation Techniques -1 in portion Requirement Engineering of Software Engineering

Answer»

Right answer is (d) Both QUESTION -> Idea -> Argument and ISSUE -> POSITION -> Justification

To explain: IBIS is a simple and non-intrusive METHOD that provides a framework forresolving ISSUES and gathering requirements.

47.

___________ and ____________ are the two view points discussed in Controlled Requirements Expression (CORE).(a) Functional, Non-Functional(b) User, Developer(c) Known, Unknown(d) All of the mentionedI have been asked this question during an interview.My question is based upon Requirement Elicitation Techniques -1 topic in chapter Requirement Engineering of Software Engineering

Answer»

The correct OPTION is (a) Functional, Non-Functional

For explanation: The CORE sessions includes the DISCUSSION of functional and non-functional requirements.

48.

What is the major drawback of CORE ?(a) Requirements are comprehensive(b) NFRs are not given enough importance(c) Role of analyst is passive(d) All of the mentionedThe question was asked during an interview.I'd like to ask this question from Requirement Elicitation Techniques -1 in section Requirement Engineering of Software Engineering

Answer» CORRECT answer is (c) Role of ANALYST is passive

For EXPLANATION: In CORE the requirement specification are put TOGETHER by all users, customers and analysts, so a passive analyst will not GET the requirements properly.
49.

Which of the following elicitation techniques is a viewpoint based method?(a) FODA(b) QFD(c) CORE(d) IBISI got this question in semester exam.This key question is from Requirement Elicitation Techniques -1 in section Requirement Engineering of Software Engineering

Answer»

The correct answer is (C) CORE

To EXPLAIN I would say: Controlled Requirements Expression(CORE) SAYS that any system can be viewed from a number of view POINTS and that a complete picture of system requirements can only emerge by putting together the various VIEWPOINTS.

50.

How many Scenarios are there in elicitation activities ?(a) One(b) Two(c) Three(d) FourThis question was posed to me in my homework.This intriguing question comes from Requirement Elicitation topic in division Requirement Engineering of Software Engineering

Answer»

The CORRECT CHOICE is (d) FOUR

Easiest explanation: As-is Scenario, VISIONARY Scenario, EVALUATION Scenario and Training Scenario are the four scenarios in requirement elicitation activities.