Software-Engineering
Question 1 |
In unit testing of a module, it is found that for a set of test data, at the maximum 90% of the code alone were tested with the probability of success 0.9. The reliability of the module is
Greater than 0.9 | |
Equal to 0.9 | |
At most 0.81 | |
At least 0.81 |
Question 1 Explanation:
Given data
Step-1: 90% of code were tested,
Testing with the probability=0.9
Step-2: We can write tested data into 0.9 because it is given in percentages.
Step-3: Reliability of the module = Tested data * probability
= 0.9 * 0.9
= 0.81(at most)
Step-1: 90% of code were tested,
Testing with the probability=0.9
Step-2: We can write tested data into 0.9 because it is given in percentages.
Step-3: Reliability of the module = Tested data * probability
= 0.9 * 0.9
= 0.81(at most)
Question 2 |
The Functions Point (FP) metric is
Calculated from user requirement | |
Calculated from lines of code | |
Calculated from software complexity assessment | |
None of the above |
Question 2 Explanation:
→ The functional user requirements of the software are identified and each one is categorized into one of five types: outputs, inquiries, inputs, internal files, and external interfaces.
→ Once the function is identified and categorized into a type, it is then assessed for complexity and assigned a number of function points.
→ Each of these functional user requirements maps to an end-user business function, such as a data entry for an Input or a user query for an Inquiry.
→ This distinction is important because it tends to make the functions measured in function points map easily into user-oriented requirements, but it also tends to hide internal functions (e.g. algorithms), which also require resources to implement.
→ Once the function is identified and categorized into a type, it is then assessed for complexity and assigned a number of function points.
→ Each of these functional user requirements maps to an end-user business function, such as a data entry for an Input or a user query for an Inquiry.
→ This distinction is important because it tends to make the functions measured in function points map easily into user-oriented requirements, but it also tends to hide internal functions (e.g. algorithms), which also require resources to implement.
Question 3 |
The lower degree of cohesion is kind of
Logical Cohesion | |
Coincidental Cohesion | |
Procedural Cohesion | |
Communicational Cohesion |
Question 3 Explanation:
Cohesion is a measure of the degree to which elements of a module are functional related.
Question 4 |
Which of the following is not a UML DIAGRAM?
Use Case | |
Class Diagram | |
Analysis Diagram | |
Swimlane Diagram |
Question 4 Explanation:
Use Case, Class Diagram and Swimlane Diagram are all three UML diagrams but Analysis Diagram is not.
Question 5 |
To execute all loops at their boundaries and within their operational bounds is an example of
Black Box Testing | |
Alpha Testing | |
Recovery Testing | |
White Box Testing |
Question 5 Explanation:
White box testing is a testing technique which evaluates the code and the internal structure of a program. It involves looking at the structure of the code, when a tester already know the internal structure of a product, tests can be conducted to ensure that the internal operations performed according to the specification and all internal components have been adequately exercised.
White Box Testing is coverage of the specification in the code:
1. Code coverage
2. Segment coverage: Ensure that each code statement is executed once.
3. Branch Coverage or Node Testing: Coverage of each code branch in from all possible was.
4. Compound Condition Coverage: For multiple conditions test each condition with multiple paths and combination of the different path to reach that condition.
5. Basis Path Testing: Each independent path in the code is taken for testing.
6. Data Flow Testing (DFT): It is defining the set of intermediate paths through the code.
7. Path Testing: Path testing is where all possible paths through the code are defined and covered.
8. Loop Testing: these strategies relate to testing single loops, concatenated loops, and nested loops.
White Box Testing is coverage of the specification in the code:
1. Code coverage
2. Segment coverage: Ensure that each code statement is executed once.
3. Branch Coverage or Node Testing: Coverage of each code branch in from all possible was.
4. Compound Condition Coverage: For multiple conditions test each condition with multiple paths and combination of the different path to reach that condition.
5. Basis Path Testing: Each independent path in the code is taken for testing.
6. Data Flow Testing (DFT): It is defining the set of intermediate paths through the code.
7. Path Testing: Path testing is where all possible paths through the code are defined and covered.
8. Loop Testing: these strategies relate to testing single loops, concatenated loops, and nested loops.
Question 6 |
Which of the following is not an approach to Software Process Assessment?
SPICE(ISO/IEC15504) | |
Standard CMMI Assessment Method for process improvement | |
ISO 9001:2000 | |
IEEE 2000:2001 |
Question 6 Explanation:
The process assessment leads to process capability determination and process improvement. Process capability determination is an organized assessment, which analyzes the software processes in an organization.The process improvement identifies the changes to be made in the software processes.
Different approaches are used for assessing software process. These approaches are SPICE (ISO/IEC15504), ISO 9001:2000, standard CMMI assessment method for process improvement, CMM-based appraisal for internal process improvement, and Bootstrap.
Different approaches are used for assessing software process. These approaches are SPICE (ISO/IEC15504), ISO 9001:2000, standard CMMI assessment method for process improvement, CMM-based appraisal for internal process improvement, and Bootstrap.
Question 7 |
A physical DFD specifies
what processes will be used | |
who generates data and who processes it | |
what each person in an organization does | |
which data will be generated |
Question 7 Explanation:
Physical DFD specifies actual flow of physical documentation and depicts how the system will be implemented.
The processes represent the programs, program modules, and manual procedures.
The data stores represent the physical files and databases, manual files.
It show controls for validating input data, for obtaining a record, for ensuring successful completion of a process, and for system security.
The processes represent the programs, program modules, and manual procedures.
The data stores represent the physical files and databases, manual files.
It show controls for validating input data, for obtaining a record, for ensuring successful completion of a process, and for system security.
Question 8 |
In UML diagram of a class
state of object cannot be represented | |
state is irrelevant | |
state is represented as an attribute | |
state is represented as a result of an operation |
Question 8 Explanation:
The Unified Modeling Language (UML) is a general-purpose, developmental, modeling language in the field of software engineering, that is intended to provide a standard way to visualize the design of a system.
A class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system’s classes as attributes, operations and the relationships among objects.
A class diagram in the Unified Modeling Language (UML) is a type of static structure diagram that describes the structure of a system by showing the system’s classes as attributes, operations and the relationships among objects.
Question 9 |
Which of the following models used for software reliability
Waterfall | |
Musa | |
COCOMO | |
Rayleigh |
Question 9 Explanation:
Rayleigh Model:
This model predicts fault detection over the life of the software development effort and can be used in conjunction with the other prediction techniques. Software management may use this profile to gauge the defect status. This model assumes that over the life of the project that the faults detected per month will resemble a Raleigh curve
Musa Model:
This prediction technique is used to predict, prior to system testing, what the failure rate will be at the start of system testing. This prediction can then later be used in the reliability growth modelling. For this prediction method, it is assumed that the only thing known about the hypothetical program is a prediction of its size and the processor speed.
COCOMO:
The constructive cost model was developed as a model for estimating effort, cost, and schedule for software projects.
Waterfall Model:
Waterfall is the software development life cycle model which depicts the phases of conception, initiation, analysis, design, construction, testing, deployment and maintenance.
Musa model is also used for software reliability testing but Rayleigh model is very popularly used with higher accuracy.
This model predicts fault detection over the life of the software development effort and can be used in conjunction with the other prediction techniques. Software management may use this profile to gauge the defect status. This model assumes that over the life of the project that the faults detected per month will resemble a Raleigh curve
Musa Model:
This prediction technique is used to predict, prior to system testing, what the failure rate will be at the start of system testing. This prediction can then later be used in the reliability growth modelling. For this prediction method, it is assumed that the only thing known about the hypothetical program is a prediction of its size and the processor speed.
COCOMO:
The constructive cost model was developed as a model for estimating effort, cost, and schedule for software projects.
Waterfall Model:
Waterfall is the software development life cycle model which depicts the phases of conception, initiation, analysis, design, construction, testing, deployment and maintenance.
Musa model is also used for software reliability testing but Rayleigh model is very popularly used with higher accuracy.
Question 10 |
Estimation of software development effort for organic software in basic COCOMO is
E = 2.0(KLOC)1.05 Per Month | |
E = 3.4(KLOC)1.06 Per Month | |
E = 2.4(KLOC)1.05 Per Month | |
E = 2.4(KLOC)1.07 Per Month |
Question 10 Explanation:
The basic COCOMO equations take the form
1. Effort Applied (E) = ab(KLOC)bb [ man-months ]
2. Development Time (D) = cb(Effort Applied)db [months]
3. People required (P) = Effort Applied / Development Time [count]
where, KLOC is the estimated number of delivered lines (expressed in thousands ) of code for project. The constants ab, bb, cb and db are given in the following table (note: the values listed below are from the original analysis, with a modern reanalysis producing different values)
1. Effort Applied (E) = ab(KLOC)bb [ man-months ]
2. Development Time (D) = cb(Effort Applied)db [months]
3. People required (P) = Effort Applied / Development Time [count]
where, KLOC is the estimated number of delivered lines (expressed in thousands ) of code for project. The constants ab, bb, cb and db are given in the following table (note: the values listed below are from the original analysis, with a modern reanalysis producing different values)
Question 11 |
Which of the following UML 2.0 diagrams capture behavioural aspects of a system?
Use Case Diagram, Object Diagram, Activity Diagram, and State Machine Diagram | |
Use Case Diagram, Activity Diagram, and State Machine Diagram | |
Object Diagram, Communication Diagram, Timing Diagram, and Interaction diagram | |
Object Diagram, Composite Structure Diagram, Package Diagram, and Deployment Diagram |
Question 11 Explanation:
UML diagram are two types:
Question 12 |
Capability Maturity Model (CMM) is a methodology to
develop and refine an organization’s software development process | |
develop the software | |
test the software | |
All of the above |
Question 12 Explanation:
CMM stands for Capability Maturity Model is a process model which specifies the process improvement approach in software development.
CMM levels:
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimizing
CMM levels:
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimizing
Question 13 |
Which of the following is not a life cycle model?
Spiral model | |
Prototyping model | |
Waterfall model | |
Capability maturity model |
Question 13 Explanation:
→ 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.
1. Waterfall model
2. Iterative model
3. Spiral model
4. Incremental model
5. Modified waterfall model
6. RAD model
7. Agile model
→ CMM stands for Capability Maturity Model is a process model which specifies the process improvement approach in software development.
1. Waterfall model
2. Iterative model
3. Spiral model
4. Incremental model
5. Modified waterfall model
6. RAD model
7. Agile model
→ CMM stands for Capability Maturity Model is a process model which specifies the process improvement approach in software development.
Question 14 |
The cyclomatic complexity of each of the modules X and Y shown below is 10. What is the cyclomatic complexity of the sequential integration shown on the right-hand side?
21 | |
19 | |
20 | |
10 |
Question 14 Explanation:
Cyclomatic complexity uses 3 formulas
1. Number of regions + 1
2. Predicate + 1
3. Edges-Vertices+2
But here they already given complexity. So each module complexity is 10.
There are 2 modules named A and B having decision points are (10-1)+(10-1).
Cyclomatic complexity of the sequential integration is = Number of decision points + 1
= 18+ 1
= 19
1. Number of regions + 1
2. Predicate + 1
3. Edges-Vertices+2
But here they already given complexity. So each module complexity is 10.
There are 2 modules named A and B having decision points are (10-1)+(10-1).
Cyclomatic complexity of the sequential integration is = Number of decision points + 1
= 18+ 1
= 19
Question 15 |
In software maintenance tackling the changes in the hardware or software environment where the software works, is
Corrective maintenance | |
Perfective maintenance | |
Adaptive maintenance | |
Preventive maintenance |
Question 15 Explanation:
Software Maintenance activities into four classes:
1. Adaptive – modifying the system to cope with changes in the software environment
2. Perfective – implementing new or changed user requirements which concern functional enhancements to the software
3. Corrective – diagnosing and fixing errors, possibly ones found by users
4. Preventive – increasing software maintainability or reliability to prevent problems in the future
1. Adaptive – modifying the system to cope with changes in the software environment
2. Perfective – implementing new or changed user requirements which concern functional enhancements to the software
3. Corrective – diagnosing and fixing errors, possibly ones found by users
4. Preventive – increasing software maintainability or reliability to prevent problems in the future
Question 16 |
In the context of modular software design, which one of the following combinations is desirable?
High cohesion and high coupling | |
High cohesion and low coupling | |
Low cohesion and high coupling | |
Low cohesion and low coupling |
Question 16 Explanation:
→ Cohesion is a measure of internal strength within a module, whereas coupling is a measure of inter dependency among the modules.
→ So in the context of modular software design, there should be high cohesion and low coupling.
→ So in the context of modular software design, there should be high cohesion and low coupling.
Question 17 |
Activities which ensure that the software that has been built, is traceable to customer requirement is covered as part of
Verification | |
Validation | |
Maintenance | |
Modeling |
Question 17 Explanation:
Verification is the process of evaluating products of a development phase to find out whether they meet the specified requirements.
Validation is the process of evaluating software at the end of the development process to determine whether software meets the customer expectations and requirements.
Validation is the process of evaluating software at the end of the development process to determine whether software meets the customer expectations and requirements.
Question 18 |
A testing method which is normally used as the acceptance test for a software system, is
Regression Testing | |
Integration Testing | |
Unit Testing | |
System Testing |
Question 18 Explanation:
System testing is the type of testing to check the behaviour of a complete and fully where to buy generic modafinil integrated software product based on the software requirements specification (SRS) document. The main focus of this testing is to evaluate Business / Functional / End-user requirements.
Regression testing is type of testing carried out to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality. It is executed after enhancement or defect fixes in the software or its environment.
A Unit testing is a Level of Testing where smallest part of individual unit / component (called unit) is tested to determine if they are fit for use
Regression testing is type of testing carried out to ensure that changes made in the fixes or any enhancement changes are not impacting the previously working functionality. It is executed after enhancement or defect fixes in the software or its environment.
A Unit testing is a Level of Testing where smallest part of individual unit / component (called unit) is tested to determine if they are fit for use
Question 19 |
The extent to which the software can continue to operate correctly despite the introduction of invalid inputs is called as
Reliability | |
Robustness | |
Fault tolerance | |
Portability |
Question 19 Explanation:
→ The extent to which the s/w can continue to operate correctly despite the introduction of invalid inputs is called as robustness
→ Robustness is the ability of a computer system to cope with errors during execution and cope with erroneous input
→ Robustness is the ability of a computer system to cope with errors during execution and cope with erroneous input
Question 20 |
Which one of the following is a functional requirement
Maintainability | |
Portability | |
Robustness | |
None of the mentioned |
Question 20 Explanation:
Functional Requirements include:
1. Descriptions of data to be entered into the system
2. Descriptions of operations performed by each screen
3. Descriptions of work-flows performed by the system
4. Descriptions of system reports or other outputs
→ The Functional Requirements Specification is designed to be read by a general audience. Readers should understand the system, but no particular technical knowledge should be required to understand the document.
Examples:
1. Interface requirements
2. Business requirements
3. Regulatory/Compliance requirements
4. Security requirements
1. Descriptions of data to be entered into the system
2. Descriptions of operations performed by each screen
3. Descriptions of work-flows performed by the system
4. Descriptions of system reports or other outputs
→ The Functional Requirements Specification is designed to be read by a general audience. Readers should understand the system, but no particular technical knowledge should be required to understand the document.
Examples:
1. Interface requirements
2. Business requirements
3. Regulatory/Compliance requirements
4. Security requirements
Question 21 |
Configuration management is not concerned with
controlling changes to the source code | |
choice of a hardware configuration for an application | |
controlling documentation changes | |
maintaining versions of software |
Question 21 Explanation:
Configuration management is not concerned with choice of hardware configuration for an application.
Question 22 |
A company needs to develop a strategy for software product development for which it has a choice of two programming languages L1 and L2. The number of lines of code (LOC) developed using L2 is estimated to be twice the LOC developed with Ll. The product will have to be maintained for five years. Various parameters for the company are given in the table below.
Total cost of the project includes cost of development and maintenance.
What is the LOC for L1 for which the cost of the project using L1 is equal to the cost of the project using L2?
Total cost of the project includes cost of development and maintenance.
What is the LOC for L1 for which the cost of the project using L1 is equal to the cost of the project using L2?
10,000 | |
5,000 | |
7,500 | |
75,000 |
Question 22 Explanation:
LOC L1 = X
L2 = 2X
Total cost of project: x/1000*1000000+5+100000
=2x/10000*750000+50000*5
=100×+500000
=150×+250000
⟹50×=500000-250000
L2 = 2X
Total cost of project: x/1000*1000000+5+100000
=2x/10000*750000+50000*5
=100×+500000
=150×+250000
⟹50×=500000-250000
Question 23 |
A company needs to develop digital signal processing software for one of its newest inventions. The software is expected to have 20000 lines of code. The company needs to determine the effort in person-months needed to develop this software using the basic COCOMO model. The multiplicative factor for this model is given as 2.2 for the software development on embedded systems, while the exponentiation factor is given as 1.50. What is the estimated effort in person-months?
196.77 | |
206.56 | |
199.56 | |
210.68 |
Question 23 Explanation:
Constructive Cost Model (COCOMO) formula for effort applied is
Effort Applied (E) = ab(KLOC)bb [ person-months ]
= 2.2 x(20)1.50
= 2.2 x 89.44
= 196.77
Effort Applied (E) = ab(KLOC)bb [ person-months ]
= 2.2 x(20)1.50
= 2.2 x 89.44
= 196.77
Question 24 |
In the Spiral model of software development, the primary determinant in selecting activities in each iteration is
Iteration size | |
Cost | |
Adopted process such as Rational Unified Process or Extreme Programming | |
Risk |
Question 24 Explanation:
→ In the Spiral model of software development, the primary determinant in selecting activities in each iteration is risk handling
→ The spiral model is a risk-driven software development process model. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.
→ The spiral model is a risk-driven software development process model. Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.
Question 25 |
A context model of a software system can be shown by drawing a
LEVEL-0 DFD
| |
LEVEL-1 DFD | |
LEVEL-2 DFD | |
LEVEL-3 DFD |
Question 25 Explanation:
Explanation:
1. A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs and outputs. As its name indicates its focus is on the flow of information, where data comes from, where it goes and how it gets stored.
2. Context Diagram. A context diagram is a top level (also known as "Level 0") data flow diagram. It only contains one process node ("Process 0") that generalizes the function of the entire system in relationship to external entities.
1. A data flow diagram (DFD) illustrates how data is processed by a system in terms of inputs and outputs. As its name indicates its focus is on the flow of information, where data comes from, where it goes and how it gets stored.
2. Context Diagram. A context diagram is a top level (also known as "Level 0") data flow diagram. It only contains one process node ("Process 0") that generalizes the function of the entire system in relationship to external entities.
Question 26 |
Black Box Software Testing method focuses on the
Boundary condition of the software | |
Control structure of the software | |
Functional requirement of the software | |
Independent paths of the software |
Question 26 Explanation:
Black box testing, which is also known as behavioral, opaque-box, closed-box, specification-based or eye-to-eye testing, is a Software Testing method that analyses the functionality of a software/application without knowing much about the internal structure/design of the item that is being tested and compares the input value with the output value
Question 27 |
Warnier Diagram enables the analyst to represent
Warnier Diagram enables the analyst to represent | |
Information Hierarchy | |
Data Flow | |
State Transition |
Question 27 Explanation:
A Warnier/Orr diagram (also known as a logical construction of a program/system) is a kind of hierarchical flow chart that allows the description of the organization of data and procedures.
This method aids the design of program structures by identifying the output and processing results and then working backwards to determine the steps and combinations of input needed to produce them.
The simple graphic method used in Warnier/Orr diagrams makes the levels in the system evident and the movement of the data between them vivid.
This method aids the design of program structures by identifying the output and processing results and then working backwards to determine the steps and combinations of input needed to produce them.
The simple graphic method used in Warnier/Orr diagrams makes the levels in the system evident and the movement of the data between them vivid.
Question 28 |
The Cyclomatic Complexity metric V(G) of the following control flow graph
3 | |
4 | |
5 | |
6 |
Question 28 Explanation:
Cyclomatic complexity is the measurement of a source code complexity.
It is calculated through a control flow graph which is developed on the basis of source code which measures the number of linearly-independent paths through a program module
The Cyclomatic Complexity of a graph = E − N + 2*P, where
where,
E = represents a number of edges in the control flow graph.
N = represents a number of nodes in the control flow graph.
P = represents a number of nodes that have exit points in the control flow graph.
From the given graph has: E = 7, N = 5 and P = 1
Cyclomatic Complexity = 7 – 5 + 2(1) = 4
It is calculated through a control flow graph which is developed on the basis of source code which measures the number of linearly-independent paths through a program module
The Cyclomatic Complexity of a graph = E − N + 2*P, where
where,
E = represents a number of edges in the control flow graph.
N = represents a number of nodes in the control flow graph.
P = represents a number of nodes that have exit points in the control flow graph.
From the given graph has: E = 7, N = 5 and P = 1
Cyclomatic Complexity = 7 – 5 + 2(1) = 4
Question 29 |
If a program P calls two subprograms P1 and P2 and P1 can fail 50% of the time and P2 can fail 40% of the time, what is the failure rate of program P
50% | |
60% | |
70% | |
10% |
Question 29 Explanation:
Method-1:
Based upon the success rate, we can find the solution.
Success rate=(1-failure rate)
Given failure rates are P1=50% P2=40%
P1 success rate= (1-failure rate)
= (1-0.5)
= 0.5
P2 success rate= (1-failure rate)
= (1-0.4)
= 0.6
Success rate of both P1 and P2 = 0.5 *0.6
= 0.3
Failure rate of both P1 and P2
= 1 - success rate
= 1 - 0.3
= 0.7 (or) 70%
Method-2:
Based upon the failure rate we can find the solution.
Program P is divided into two subprograms.
We can calculate total failure rate by considering the two subprograms
P(P1 U P2)= P1+P2-(P1*P2) /*Check note point */
= (50/100)+(40/100)-(50*40)/100
=90-20
=70%
Note: Failure of P1 + Failure of P2 - (Failure of P1 ∩ Failure of P2)
Based upon the success rate, we can find the solution.
Success rate=(1-failure rate)
Given failure rates are P1=50% P2=40%
P1 success rate= (1-failure rate)
= (1-0.5)
= 0.5
P2 success rate= (1-failure rate)
= (1-0.4)
= 0.6
Success rate of both P1 and P2 = 0.5 *0.6
= 0.3
Failure rate of both P1 and P2
= 1 - success rate
= 1 - 0.3
= 0.7 (or) 70%
Method-2:
Based upon the failure rate we can find the solution.
Program P is divided into two subprograms.
We can calculate total failure rate by considering the two subprograms
P(P1 U P2)= P1+P2-(P1*P2) /*Check note point */
= (50/100)+(40/100)-(50*40)/100
=90-20
=70%
Note: Failure of P1 + Failure of P2 - (Failure of P1 ∩ Failure of P2)
Question 30 |
Which of the following testing methods uses fault simulation technique?
unit testing | |
beta testing | |
stress testing | |
mutation testing |
Question 30 Explanation:
Mutation testing is used to design new software tests and evaluate the quality of existing software tests.
The purpose of mutation testing is to evaluate the effectiveness of the test cases to detect errors in the event of modification or changes in the program code
The purpose of mutation testing is to evaluate the effectiveness of the test cases to detect errors in the event of modification or changes in the program code
Question 31 |
What is the cyclomatic complexity of a module which has seventeen edges and thirteen nodes?
4 | |
5 | |
6 | |
7 |
Question 31 Explanation:
From the given question,
The number of edges are (E)=17
The number of Nodes are (N)=13
We can calculate the cyclomatic complexity of a module by using the formulae E – N + 2
Substitute the given values in the above formulae.
Cyclomatic complexity = 17 – 13 + 2 = 6
The number of edges are (E)=17
The number of Nodes are (N)=13
We can calculate the cyclomatic complexity of a module by using the formulae E – N + 2
Substitute the given values in the above formulae.
Cyclomatic complexity = 17 – 13 + 2 = 6
Question 32 |
Which of the following types of coupling has the weakest coupling?
Pathological coupling | |
Control coupling | |
Data coupling | |
Message coupling |
Question 32 Explanation:
Coupling is the degree of interdependence between software modules; a measure of how closely connected two routines or modules are the strength of the relationships between module
Coupling can be "low" (also "loose" and "weak") or "high" (also "tight" and "strong").
Some types of coupling, in order of highest to lowest coupling, are as follows:
Content coupling (high)
Content coupling is said to occur when one module uses the code of other module, for instance a branch. This violates information hiding - a basic design concept.
Common coupling
Common coupling is said to occur when several modules have access to the same global data. But it can lead to uncontrolled error propagation and unforeseen side-effects when changes are made.
External coupling
External coupling occurs when two modules share an externally imposed data format, communication protocol, or device interface. This is basically related to the communication to external tools and devices.
Control coupling
Control coupling is one module controlling the flow of another, by passing it information on what to do (e.g., passing a what-to-do flag).
Stamp coupling (data-structured coupling)
Stamp coupling occurs when modules share a composite data structure and use only parts of it, possibly different parts
Data coupling
Data coupling occurs when modules share data through, for example, parameters. Each datum is an elementary piece, and these are the only data shared (e.g., passing an integer to a function that computes a square root).
Coupling can be "low" (also "loose" and "weak") or "high" (also "tight" and "strong").
Some types of coupling, in order of highest to lowest coupling, are as follows:
Content coupling (high)
Content coupling is said to occur when one module uses the code of other module, for instance a branch. This violates information hiding - a basic design concept.
Common coupling
Common coupling is said to occur when several modules have access to the same global data. But it can lead to uncontrolled error propagation and unforeseen side-effects when changes are made.
External coupling
External coupling occurs when two modules share an externally imposed data format, communication protocol, or device interface. This is basically related to the communication to external tools and devices.
Control coupling
Control coupling is one module controlling the flow of another, by passing it information on what to do (e.g., passing a what-to-do flag).
Stamp coupling (data-structured coupling)
Stamp coupling occurs when modules share a composite data structure and use only parts of it, possibly different parts
Data coupling
Data coupling occurs when modules share data through, for example, parameters. Each datum is an elementary piece, and these are the only data shared (e.g., passing an integer to a function that computes a square root).
Question 33 |
Consider the following pseudo code
while (m < n)
if (x > y ) and (a < b) then
a=a+1
y=y-1
end if
m=m+1
end while
What is cyclomatic complexity of the above pseudo code?
while (m < n)
if (x > y ) and (a < b) then
a=a+1
y=y-1
end if
m=m+1
end while
What is cyclomatic complexity of the above pseudo code?
2 | |
3 | |
4 | |
5 |
Question 33 Explanation:
Finding cyclomatic complexity using 3 formulas
1. E-V+2
2. P+1
3. No.of Regions
According to above code segment.
→ Edges-Vertices+2
= 8-6+2 = 4
→ Total number of regions = 4
→ Predicates+1 = 3+1 = 4
Note: We can use any one of above formulas.
1. E-V+2
2. P+1
3. No.of Regions
According to above code segment.
→ Edges-Vertices+2
= 8-6+2 = 4
→ Total number of regions = 4
→ Predicates+1 = 3+1 = 4
Note: We can use any one of above formulas.
Question 34 |
Which of the following is not a maturity level as per the Capability Maturity Model?
Initial | |
Measurable | |
Repeatable | |
Optimized |
Question 34 Explanation:
Capability Maturity Model levels
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimized
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimized
Question 35 |
The test suite (set of test input) used to perform unit testing on module could cover 70% of the code. What is the reliability of the module if the probability of success is 0.95 during testing?
0.665 to 0.95 | |
At the most 0.665 | |
At the most 0.95 | |
At least 0.665 |
Question 35 Explanation:
Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
From the given question the module code covers 70% of the entire code, so we need to check with reliability for that module only.
Reliability = percentage of code coverage * probability of success = 0.7 * 0.95 = 0.665.
Probability of success is at most 0.665 %
From the given question the module code covers 70% of the entire code, so we need to check with reliability for that module only.
Reliability = percentage of code coverage * probability of success = 0.7 * 0.95 = 0.665.
Probability of success is at most 0.665 %
Question 36 |
For a software project, the spiral model was employed. When will the spiral stop?
When the software product is retired | |
When the software product is released after Beta testing | |
When the risk analysis is completed | |
After completing five loops |
Question 36 Explanation:
→ The spiral model is a risk-driven software development process model.
→ Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.
→ Spiral model stop, when the software product is retired
→ Based on the unique risk patterns of a given project, the spiral model guides a team to adopt elements of one or more process models, such as incremental, waterfall, or evolutionary prototyping.
→ Spiral model stop, when the software product is retired
Question 37 |
Assume the following regarding the development of a software system P:
-
- Estimated lines of code of P : 33, 480 LOC
- Average productivity for P : 620 LOC per person-month
- Number of software developers : 6
- Average salary of a software developer : 50,000 per month
If E, D and C are the estimated development effort (in person-months), estimated development time (in months), and estimated development cost (in Lac) respectively, then (E, D, C) =
(48, 8, 24) | |
(54, 9, 27) | |
(60, 10, 30) | |
(42, 7, 21) |
Question 37 Explanation:
Given data,
- Estimated lines of code of P : 33480 LOC
- Average productivity for P : 620 LOC per person-month
- Number of software developers : 6
- Average salary of a software developer : 50000 per month
Step-1: Estimated development effort (in person-months) = 33480 /620
E = 54
Step-2: Estimated development time (in months) = 54/6
D = 9 months
Step-3: Estimated development cost (in Lac) = 50000 * 6 * 9 = 27 lacs
- Estimated lines of code of P : 33480 LOC
- Average productivity for P : 620 LOC per person-month
- Number of software developers : 6
- Average salary of a software developer : 50000 per month
Step-1: Estimated development effort (in person-months) = 33480 /620
E = 54
Step-2: Estimated development time (in months) = 54/6
D = 9 months
Step-3: Estimated development cost (in Lac) = 50000 * 6 * 9 = 27 lacs
Question 38 |
Match the following in Software Engineering :
List-I List-II (a) Product Complexity (i) Software Requirements Definition (b) Structured System Analysis (ii) Software Design (c) Coupling and Cohesion (iii) Validation Technique (d) Symbolic Execution (iv) Software Cost Estimation
(a)-(ii), (b)-(iii), (c)-(iv), (d)-(i) | |
(a)-(iii), (b)- (i), (c)-(iv), (d)-(ii) | |
(a)-(iv), (b)- (i), (c)-(ii), (d)-(iii) | |
(a)-(iii), (b)- (iv), (c)-(i), (d)-(ii)
|
Question 38 Explanation:
→ Coupling and Cohesion are used in software design. Cohesion measures strength of a module while coupling measures interdependency between modules.
→ Software cost estimation must be done more diligently throughout the project life cycle so that in the future there are fewer surprises and unforeseen delays in the release of a product.
→ Validation Technique → Symbolic Execution
→ Software Requirements Definition → Structured System Analysis
→ Software cost estimation must be done more diligently throughout the project life cycle so that in the future there are fewer surprises and unforeseen delays in the release of a product.
→ Validation Technique → Symbolic Execution
→ Software Requirements Definition → Structured System Analysis
Question 39 |
Which one of the following is not typically provided by Source Code Management Software ?
Synchronisation
| |
Versioning and Revision history | |
Syntax highlighting
| |
Project forking
|
Question 39 Explanation:
Source Code Management Software is the management of changes to documents, computer programs, large web sites, and other collections of information. Changes are usually identified by a number or letter code, termed the "revision number", "revision level", or simply "revision".
→ Source Code Management Software includes
1. Synchronisation
2. Versioning and Revision history
3. Project forking
→ Source Code Management Software includes
1. Synchronisation
2. Versioning and Revision history
3. Project forking
Question 40 |
A software system crashed 20 times in the year 2017 and for each crash, it took 2 minutes to restart. Approximately, what was the software availability in that year ?
96.9924% | |
97.9924% | |
98.9924% | |
99.9924%
|
Question 40 Explanation:
Software availability:
It is a software used to ensure that systems are running and available most of the time. High availability is a high percentage of time that the system is functioning. It can be formally defined as (1 – (down time/ total time))*100%. Although the minimum required availability varies by task, systems typically attempt to achieve 99.999% (5-nines) availability. This characteristic is weaker than fault tolerance, which typically seeks to provide 100% availability, albeit with significant price and performance penalties.
Given data,
- Software crashed 20 times in the year 2017
- Each crash = 2 minutes to restart
- Software availability = ?
1 year = 365 days = 365 * 1440 minutes = 525600 minutes
→ Crash time = 20 * 2
= 40 minutes
→ Software availability = (525600 - 40) / 525600
= 0.999924
= (0.999924 * 100)
= 99.9924 %
It is a software used to ensure that systems are running and available most of the time. High availability is a high percentage of time that the system is functioning. It can be formally defined as (1 – (down time/ total time))*100%. Although the minimum required availability varies by task, systems typically attempt to achieve 99.999% (5-nines) availability. This characteristic is weaker than fault tolerance, which typically seeks to provide 100% availability, albeit with significant price and performance penalties.
Given data,
- Software crashed 20 times in the year 2017
- Each crash = 2 minutes to restart
- Software availability = ?
1 year = 365 days = 365 * 1440 minutes = 525600 minutes
→ Crash time = 20 * 2
= 40 minutes
→ Software availability = (525600 - 40) / 525600
= 0.999924
= (0.999924 * 100)
= 99.9924 %
Question 41 |
Match the 5 CMM Maturity levels/CMMI staged representations in List-I with their characterizations in List-II :
List-I List-II (a) Initial (i) Processes are improved quantitatively and continually. (b) Repeatable (ii) The plan for a project comes from a template for plans. (c) Defined (iii) The plan uses processes that can be measured quantitatively. (d) Managed (iv) There may not exist a plan or it may be abandoned. (e) Optimizing (v) There’s a plan and people stick to it.Code :
(a)-(iv), (b)-(v), (c)-(i), (d)-(iii), (e)-(ii) | |
(a)-(i), (b)-(ii), (c)-(iv), (d)-(v), (e)-(iii) | |
(a)-(v), (b)-(iv), (c)-(ii), (d)-(iii), (e)-(i) | |
(a)- (iv), (b)-(v), (c)-(ii), (d)-(iii), (e)-(i) |
Question 41 Explanation:
Initial Stage: There may not exist a plan or it may be abandoned.
Repeatable: There’s a plan and people stick to it.
Defined: The plan for a project comes from a template for plans.
Managed: The plan uses processes that can be measured quantitatively.
Optimizing: Processes are improved quantitatively and continually.
Repeatable: There’s a plan and people stick to it.
Defined: The plan for a project comes from a template for plans.
Managed: The plan uses processes that can be measured quantitatively.
Optimizing: Processes are improved quantitatively and continually.
Question 42 |
Coupling is a measure of the strength of the interconnections between software modules. Which of the following are correct statements with respect to module coupling ?
- P : Common coupling occurs when one module controls the flow of another module by passing it information on what to do.
Q : In data coupling, the complete data structure is passed from one module to another through parameters.
R : Stamp coupling occurs when modules share a composite data structure and use only parts of it.
P and Q only
| |
P and R only | |
Q and R only | |
All of P, Q and R
|
Question 42 Explanation:
Common Coupling: Common coupling occurs if two modules share same global data.
Data Coupling: Data coupling occurs when two modules communicate using elementary data items that are passed as parameters between two modules.
Stamp Coupling: Stamp coupling occurs if two modules communicate using composite items such as records in Pascal or structure in C.
Data Coupling: Data coupling occurs when two modules communicate using elementary data items that are passed as parameters between two modules.
Stamp Coupling: Stamp coupling occurs if two modules communicate using composite items such as records in Pascal or structure in C.
Question 43 |
A software design pattern often used to restrict access to an object is :
adapter | |
decorator | |
delegation
| |
proxy
|
Question 43 Explanation:
Proxy pattern: A class functioning as an interface to another thing. In the proxy, extra functionality can be provided, for example caching when operations on the real object are resource intensive, or checking preconditions before operations on the real object are invoked.
→ For the client, usage of a proxy object is similar to using the real object, because both implement the same interface.
→ Proxy pattern solve the access to an object should be controlled and functionality should be provided when accessing an object.
→ When accessing sensitive objects, for example, it should be possible to check that clients have the needed access rights.
→ For the client, usage of a proxy object is similar to using the real object, because both implement the same interface.
→ Proxy pattern solve the access to an object should be controlled and functionality should be provided when accessing an object.
→ When accessing sensitive objects, for example, it should be possible to check that clients have the needed access rights.
Question 44 |
Reasons to re-engineer a software include :
-
P : Allow legacy software to quickly adapt to the changing requirements
Q : Upgrade to newer technologies/platforms/paradigm (for example, object-oriented)
R : Improve software maintainability
S : Allow change in the functionality and architecture of the software
P, R and S only | |
P and R only
| |
P, Q and S only
| |
P, Q and R only
|
Question 44 Explanation:
→ Software re-engineering is the examination and alteration of a system to reconstitute it in a new form. It is done to improve the maintainability of the software.
→ Software reengineering encompasses inventory analysis, document restructuring, reverse engineering, program and data restructuring, and forward engineering. The intent of these activities is to create versions of existing programs that exhibit higher quality and better Maintainability.
A software reengineering process model:
→ Software reengineering encompasses inventory analysis, document restructuring, reverse engineering, program and data restructuring, and forward engineering. The intent of these activities is to create versions of existing programs that exhibit higher quality and better Maintainability.
A software reengineering process model:
Question 45 |
Which of the following is not a key strategy followed by the clean room approach to software development ?
Formal specification | |
Dynamic verification
| |
Incremental development | |
Statistical testing of the system
|
Question 45 Explanation:
The basic principles of the cleanroom process are
1. Software development based on formal methods:
Software tool support based on some mathematical formalism includes model checking, process algebras, and Petri nets. The Box Structure Method might be one such means of specifying and designing a software product. Verification that the design correctly implements the specification is performed through team review, often with software tool support.
2. Incremental implementation under statistical quality control:
Cleanroom development uses an iterative approach, in which the product is developed in increments that gradually increase the implemented functionality. The quality of each increment is measured against pre-established standards to verify that the development process is proceeding acceptably. A failure to meet quality standards results in the cessation of testing for the current increment, and a return to the design phase.
3. Statistically sound testing:
Software testing in the cleanroom process is carried out as a statistical experiment. Based on the formal specification, a representative subset of software input/output trajectories is selected and tested. This sample is then statistically analyzed to produce an estimate of the reliability of the software, and a level of confidence in that estimate.
1. Software development based on formal methods:
Software tool support based on some mathematical formalism includes model checking, process algebras, and Petri nets. The Box Structure Method might be one such means of specifying and designing a software product. Verification that the design correctly implements the specification is performed through team review, often with software tool support.
2. Incremental implementation under statistical quality control:
Cleanroom development uses an iterative approach, in which the product is developed in increments that gradually increase the implemented functionality. The quality of each increment is measured against pre-established standards to verify that the development process is proceeding acceptably. A failure to meet quality standards results in the cessation of testing for the current increment, and a return to the design phase.
3. Statistically sound testing:
Software testing in the cleanroom process is carried out as a statistical experiment. Based on the formal specification, a representative subset of software input/output trajectories is selected and tested. This sample is then statistically analyzed to produce an estimate of the reliability of the software, and a level of confidence in that estimate.
Question 46 |
Which of the following statements is/are True ?
-
P : Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves the internal architecture.
Q : An example of refactoring is adding new features to satisfy a customer requirement discovered after a project is shipped.
P only | |
Q only | |
Both P and Q
| |
Neither P nor Q |
Question 46 Explanation:
→ Refactoring allows a software engineer to improve the internal structure of a design (or source code) without changing its external functionality or behavior of the code yet improves the internal structure. In essence, refactoring can be used to improve the efficiency, readability, or performance of a design or the code that implements a design.
→ It is a disciplined way to clean up code [and modify/simplify the internal design] that minimizes the chances of introducing bugs. In essence, when you refactor you are improving the design of the code after it has been written.
Note:
It won’t add any new featuring to satisfy a customer requirement. So, statement Q is false.
→ It is a disciplined way to clean up code [and modify/simplify the internal design] that minimizes the chances of introducing bugs. In essence, when you refactor you are improving the design of the code after it has been written.
Note:
It won’t add any new featuring to satisfy a customer requirement. So, statement Q is false.
Question 47 |
RAD software process model stands for:
Rapid Application Development | |
Rapid Application Design | |
Relative Application Development | |
Recent Application Development |
Question 47 Explanation:
Rapid Application Development focuses on gathering customer requirements through workshops or focus groups, early testing of the prototypes by the customer using iterative concept, reuse of the existing prototypes (components), continuous integration and rapid
delivery.
Question 48 |
Software projects management comprises of a number of activities, which contains:
Project planning | |
Project estimation | |
Scope management | |
All mentioned above |
Question 48 Explanation:
Software project management is an art and science of planning and leading software projects. It is a sub-discipline of project management in which software projects are planned, implemented, monitored and controlled.
Question 49 |
What are the characteristics of software?
Software is developed or engineered;It is not manufacturing in the classical sense | |
Software can be custom built or custom build | |
Software doesn't "wear out" | |
All mentioned above |
Question 49 Explanation:
Software characteristics are
● Functionality: Refers to the degree of performance of the software against its intended purpose.
● Reliability: Refers to the ability of the software to provide desired functionality under the given conditions.
● Usability: Refers to the extent to which the software can be used with ease.
● Efficiency: Refers to the ability of the software to use system resources in the most effective and efficient manner.
● Maintainability: Refers to the ease with which the modifications can be made in a software system to extend its functionality, improve its performance, or correct errors.
● Portability: Refers to the ease with which software developers can transfer software from one platform to another, without (or with minimum) changes
● Robustness refers to the degree to which the software can keep on functioning in spite of being provided with invalid data
● integrity refers to the degree to which unauthorized access to the software or data can be prevented
● Functionality: Refers to the degree of performance of the software against its intended purpose.
● Reliability: Refers to the ability of the software to provide desired functionality under the given conditions.
● Usability: Refers to the extent to which the software can be used with ease.
● Efficiency: Refers to the ability of the software to use system resources in the most effective and efficient manner.
● Maintainability: Refers to the ease with which the modifications can be made in a software system to extend its functionality, improve its performance, or correct errors.
● Portability: Refers to the ease with which software developers can transfer software from one platform to another, without (or with minimum) changes
● Robustness refers to the degree to which the software can keep on functioning in spite of being provided with invalid data
● integrity refers to the degree to which unauthorized access to the software or data can be prevented
Question 50 |
The advantage of better testing in software development is in
Waterfall model | |
Prototyping | |
Iterative | |
All of these |
Question 50 Explanation:
● Iterative development was created as a response to inefficiencies and problems found in the waterfall model. A simplified version of a typical iteration cycle in agile project management.
● The basic idea behind this method is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental), allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system. Learning comes from both the development and use of the system, where possible key steps in the process start with a simple implementation of a subset of the software requirements and iteratively enhance the evolving versions until the full system is implemented. At each iteration, design modifications are made and new functional capabilities are added.
● The basic idea behind this method is to develop a system through repeated cycles (iterative) and in smaller portions at a time (incremental), allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system. Learning comes from both the development and use of the system, where possible key steps in the process start with a simple implementation of a subset of the software requirements and iteratively enhance the evolving versions until the full system is implemented. At each iteration, design modifications are made and new functional capabilities are added.
Question 51 |
The graph theoretic concept will be useful in software testing is
Cyclomatic number | |
Hamiltonian Circuit | |
Eulerian cycle | |
None of these |
Question 51 Explanation:
● Cyclomatic complexity is a software metric used to indicate the complexity of a program.
● It is a quantitative measure of the number of linearly independent paths through a program's source code.
● Cyclomatic complexity is computed using the control flow graph of the program: the nodes of the graph correspond to indivisible groups of commands of a program, and a directed edge connects two nodes if the second command might be executed immediately after the first command.
● Cyclomatic complexity may also be applied to individual functions, modules, methods or classes within a program
● It is a quantitative measure of the number of linearly independent paths through a program's source code.
● Cyclomatic complexity is computed using the control flow graph of the program: the nodes of the graph correspond to indivisible groups of commands of a program, and a directed edge connects two nodes if the second command might be executed immediately after the first command.
● Cyclomatic complexity may also be applied to individual functions, modules, methods or classes within a program
Question 52 |
In testing phase, the effort distribution is upto
10% | |
20% | |
40% | |
50% |
Question 52 Explanation:
● Effort estimation is the process of predicting the most realistic amount of effort (expressed in terms of person-hours or money) required to develop or maintain software based on incomplete, uncertain and noisy input.
● Effort estimates may be used as input to project plans, iteration plans, budgets, investment analyses, pricing processes and bidding rounds.
● The strong overconfidence in the accuracy of the effort estimates is illustrated by the finding that, on average, if a software professional is 90% confident or “almost sure” to include the actual effort in a minimum-maximum interval, the observed frequency of including the actual effort is only 60-70%.
● Currently the term “effort estimate” is used to denote as different concepts such as most likely use of effort (modal value), the effort that corresponds to a probability of 50% of not exceeding (median), the planned effort, the budgeted effort or the effort used to propose a bid or price to the client
● Effort estimates may be used as input to project plans, iteration plans, budgets, investment analyses, pricing processes and bidding rounds.
● The strong overconfidence in the accuracy of the effort estimates is illustrated by the finding that, on average, if a software professional is 90% confident or “almost sure” to include the actual effort in a minimum-maximum interval, the observed frequency of including the actual effort is only 60-70%.
● Currently the term “effort estimate” is used to denote as different concepts such as most likely use of effort (modal value), the effort that corresponds to a probability of 50% of not exceeding (median), the planned effort, the budgeted effort or the effort used to propose a bid or price to the client
Question 53 |
The Software Requirement Specification(SRS) is said to be _________ if and only if no subset of individual requirements described in it conflict with each other.
Correct
| |
Consistent
| |
Unambiguous
| |
Verifiable |
Question 53 Explanation:
Consistent :
The Software Requirement Specification(SRS) is said to be Consistent if and only if no subset of individual requirements described in it conflict with each other.
Unambiguous :
SRS said to be unambiguous if there exist no word that have more than one meaning and this will not confuse testers to get the exact reference.
Correct :
SRS is said to be correct if it is error free and accurate.
The Software Requirement Specification(SRS) is said to be Consistent if and only if no subset of individual requirements described in it conflict with each other.
Unambiguous :
SRS said to be unambiguous if there exist no word that have more than one meaning and this will not confuse testers to get the exact reference.
Correct :
SRS is said to be correct if it is error free and accurate.
Question 54 |
Which of the following statements is/are false?
- P: The clean-room strategy to software engineering is based on the incremental software process model.
Q: The clean-room strategy to software engineering is one of the ways to overcome “unconscious” copying of copyrighted code.
Choose the correct answer from the code given below:
Code:Neither P and Q
| |
P only | |
Both P and Q | |
Q only |
Question 54 Explanation:
Clean-room Strategy:
Cleanroom software engineering (CSE) is a process model that removes defects before they can precipitate serious hazards. It is a team-oriented, theory based software, which is developed using the formal methods, correctness verification and Statistical Quality Assurance (SQA).
→ Clean room management is based on the incremental model of software development, which accumulates into the final product. The approach combines mathematical-based methods of software specification, design and correctness verification with statistical, usage-based testing to certify software fitness for use.
→ The main goal of clean room engineering is to produce zero error-based software by allowing correct designs, which avoid rework.
Cleanroom software engineering (CSE) is a process model that removes defects before they can precipitate serious hazards. It is a team-oriented, theory based software, which is developed using the formal methods, correctness verification and Statistical Quality Assurance (SQA).
→ Clean room management is based on the incremental model of software development, which accumulates into the final product. The approach combines mathematical-based methods of software specification, design and correctness verification with statistical, usage-based testing to certify software fitness for use.
→ The main goal of clean room engineering is to produce zero error-based software by allowing correct designs, which avoid rework.
Question 55 |
Which of the following statements is/are true?
- P: Software Reengineering is preferable for software products having high failure rates, having poor design and/or having poor code structure
Q: Software Reverse Engineering is the process of analyzing software with the objective of recovering its design and requirement specification.
Choose the correct answer from the code given below:
Code:P only
| |
Neither P nor Q
| |
Q only | |
Both P and Q
|
Question 55 Explanation:
Re-Engineering:
Re-engineering refers to the rewriting the the part or whole system without changing its functionality. Re-Engineering is done for maintaining a system, to make the system compatible with the latest technologies.
Reverse engineering:
It is also called as back engineering which is done to examine the working of a product.
Re-engineering refers to the rewriting the the part or whole system without changing its functionality. Re-Engineering is done for maintaining a system, to make the system compatible with the latest technologies.
Reverse engineering:
It is also called as back engineering which is done to examine the working of a product.
Question 56 |
Software coupling involves dependencies among pieces of software called modules. Which of the following are correct statements with respect to module coupling?
-
P: Common Coupling occurs when two modules share the same global data
Q: control Coupling occur when modules share a composite data structure and use only part of it.
R: Content coupling occurs when one module modifies or relies on the internal working of another module.
Choose a correct answer from the code given below:
Code:P and Q only
| |
P and R only | |
Q and R only
| |
All of P, Q and R
|
Question 56 Explanation:
Control Coupling : It exists between two modules if data from one module to other is used to direct the order of instruction execution in other module.
Common Coupling : Common coupling take place when two modules share global data.
Content Coupling : Content coupling exists between two modules if their code is shared.
Common Coupling : Common coupling take place when two modules share global data.
Content Coupling : Content coupling exists between two modules if their code is shared.
Question 57 |
Match each UML diagram in List-I with appropriate description in List-II
List-I List-II (a) State Diagram (i) Describe how the external entities (people, devices) can interact with the system (b) Use case diagram (ii) Used to describe the static or structural view of a system (c) Class diagram (iii) Usd to show the flow of a business process, the steps of a use case or the logic of an object behaviour (d) Activity diagram (iv) Used to describe the dynamic behaviour of objects and could also be used to describe the entire system behaviourCode:
(a)-(i), (b)-(iv), (c)-(iii), (d)-(ii)
| |
(a)-(iv), (b)-(ii), (c)-(i), (d)-(iii) | |
(a)-(iv), (b)-(i), (c)-(ii), (d)-(iii) | |
(a)-(i), (b)-(iv), (c)-(ii), (d)-(iii)
|
Question 57 Explanation:
State diagram: Used to describe the dynamic behaviour of objects and could also be used to describe the entire system behaviour. Statechart diagram describes the flow of control from one state to another state. States are defined as a condition in which an object exists and it changes when some event is triggered. The most important purpose of Statechart diagram is to model lifetime of an object from creation to termination.
Use case diagram: Describe how the external entities (people, devices) can interact with the system. Use case diagrams are used to gather the requirements of a system including internal and external influences.
Class diagram: The purpose of class diagram is to model the static view of an application. Class diagrams are the only diagrams which can be directly mapped with object-oriented languages and thus widely used at the time of construction.
Activity diagram: Usd to show the flow of a business process, the steps of a use case or the logic of an object behaviour.
Use case diagram: Describe how the external entities (people, devices) can interact with the system. Use case diagrams are used to gather the requirements of a system including internal and external influences.
Class diagram: The purpose of class diagram is to model the static view of an application. Class diagrams are the only diagrams which can be directly mapped with object-oriented languages and thus widely used at the time of construction.
Activity diagram: Usd to show the flow of a business process, the steps of a use case or the logic of an object behaviour.
Question 58 |
A legacy software system has 940 modules. The latest release require that 90 of these modules be changed. In addition, 40 new modules were added and 12 old modules were removed. Compute the software maturity index for the system.
0.725 | |
0.923 | |
0.849 | |
0.524 |
Question 58 Explanation:
Software Maturity Index(SMI) = [MT - (Fc + Fa + Fd )] / MT
Where, MT = The number of modules in the current release
Fc = The number of modules in the current release that have been changed
Fa = The number of modules in the current release that have been added
Fd = The number of modules from the preceding release that were deleted in the current release
SMI = [940 - (90 + 40 + 12)]/940
SMI = 0.849
Where, MT = The number of modules in the current release
Fc = The number of modules in the current release that have been changed
Fa = The number of modules in the current release that have been added
Fd = The number of modules from the preceding release that were deleted in the current release
SMI = [940 - (90 + 40 + 12)]/940
SMI = 0.849
Question 59 |
Which of the following is not one of the principles of agile software development method ?
Following the plan
| |
Embrace change
| |
Customer involvement | |
Incremental delivery |
Question 59 Explanation:
Agile Software Development is based on twelve principles:
1. Customer satisfaction by early and continuous delivery of valuable software.
2. Welcome changing requirements, even in late development.
3. Deliver working software frequently (weeks rather than months).
4. Close, daily cooperation between business people and developers.
5. Projects are built around motivated individuals, who should be trusted.
6. Face-to-face conversation is the best form of communication (co-location).
7. Working software is the primary measure of progress.
8. Sustainable development, able to maintain a constant pace.
9. Continuous attention to technical excellence and good design.
10. Simplicity—the art of maximizing the amount of work not done—is essential.
11. Best architectures, requirements, and designs emerge from self-organizing teams.
12. Regularly, the team reflects on how to become more effective, and adjusts accordingly.
1. Customer satisfaction by early and continuous delivery of valuable software.
2. Welcome changing requirements, even in late development.
3. Deliver working software frequently (weeks rather than months).
4. Close, daily cooperation between business people and developers.
5. Projects are built around motivated individuals, who should be trusted.
6. Face-to-face conversation is the best form of communication (co-location).
7. Working software is the primary measure of progress.
8. Sustainable development, able to maintain a constant pace.
9. Continuous attention to technical excellence and good design.
10. Simplicity—the art of maximizing the amount of work not done—is essential.
11. Best architectures, requirements, and designs emerge from self-organizing teams.
12. Regularly, the team reflects on how to become more effective, and adjusts accordingly.
Question 60 |
Suppose a cloud contains software stack such as Operating system, Application software, etc. This model is referred as _________ model.
SaaS | |
IaaS | |
MaaS | |
PaaS
|
Question 60 Explanation:
The following explains the 3 services offered by cloud computing for businesses:
1) Platform as a Service (PaaS):
PaaS clouds are created, often times inside IaaS clouds by specialists to deliver the scalability and distribution of any application and to aid make a company’s expenses predictable.
2) Infrastructure as a Service (IaaS):
This service provides business access to essential web infrastructure such as servers, connections, storage space, without the need to buy or manage internet infrastructure themselves.
3) Software as a Service (SaaS):
This service offered by cloud computing is relatively mature and its phrases use those included in cloud computing. Cloud applications permit the cloud to be leveraged for software infrastructure. This reduces the burden of support, maintenance and operations because the application is run on computers that are owned by the vendor.
1) Platform as a Service (PaaS):
PaaS clouds are created, often times inside IaaS clouds by specialists to deliver the scalability and distribution of any application and to aid make a company’s expenses predictable.
2) Infrastructure as a Service (IaaS):
This service provides business access to essential web infrastructure such as servers, connections, storage space, without the need to buy or manage internet infrastructure themselves.
3) Software as a Service (SaaS):
This service offered by cloud computing is relatively mature and its phrases use those included in cloud computing. Cloud applications permit the cloud to be leveraged for software infrastructure. This reduces the burden of support, maintenance and operations because the application is run on computers that are owned by the vendor.
Question 61 |
Software products need perfective maintenance for which of the following reasons ?
To rectify bugs observed while the system is in use.
| |
When the customers need the product to run on new platforms | |
To support the new features that users want it to support | |
To overcome wear and tear caused by the repeated use of the software
|
Question 61 Explanation:
Maintenance:
Maintenance can be referred as a process of enhancement in the software product according to the changing requirements of user.
4 types of maintenance:
1. Adaptive – modifying the system to cope with changes in the software environment (DBMS, OS).
2. Perfective – implementing new or changed user requirements which concern functional enhancements to the software.
3. Corrective – diagnosing and fixing errors, possibly ones found by users.
4. Preventive – increasing software maintainability or reliability to prevent problems in the future.
Maintenance can be referred as a process of enhancement in the software product according to the changing requirements of user.
4 types of maintenance:
1. Adaptive – modifying the system to cope with changes in the software environment (DBMS, OS).
2. Perfective – implementing new or changed user requirements which concern functional enhancements to the software.
3. Corrective – diagnosing and fixing errors, possibly ones found by users.
4. Preventive – increasing software maintainability or reliability to prevent problems in the future.
Question 62 |
The cyclomatic complexity of each of the modules A and B shown below is 10. what is the cyclomatic complexity of the sequential integration shown on the right hand side?
19 | |
21 | |
20 | |
10 |
Question 62 Explanation:
Cyclomatic complexity is a software metric used to indicate the complexity of a program.
It is a quantitative measure of the number of linearly independent paths through a program's source code.
Cyclomatic Complexity of module = Number of decision points of program + 1
Number of decision points in module-A = 10 - 1 = 9
Number of decision points in module-B = 10 - 1 = 9
Cyclomatic Complexity of the integration(both A and B) = Number of decision points + 1
= (9 + 9) + 1
= 19
It is a quantitative measure of the number of linearly independent paths through a program's source code.
Cyclomatic Complexity of module = Number of decision points of program + 1
Number of decision points in module-A = 10 - 1 = 9
Number of decision points in module-B = 10 - 1 = 9
Cyclomatic Complexity of the integration(both A and B) = Number of decision points + 1
= (9 + 9) + 1
= 19
Question 63 |
What is the appropriate pairing items in the two columns listing various activities encountered in a software life cycle?
P-3, Q-2,R-4,S-1 | |
P-2,Q-3,R-1,S-4 | |
P-3,Q-2,R-1,S-4 | |
P-2,Q-3,R-4,S-1 |
Question 63 Explanation:
A requirement is a capability to which a project outcome (product or service) should conform and cover functional and non-functional aspects of a system.
Requirements Capture is the process of analysing and identifying the requirements of a system and often involves a series of facilitated workshops attended by stakeholders of the system.
Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes.
Software design is the process by which an agent creates a specification of a software artifact, intended to accomplish goals, using a set of primitive components and subject to constraints.
Implementation is the realization of an application, or execution of a plan, idea, model, design, specification, standard, algorithm, or policy.
Requirements Capture is the process of analysing and identifying the requirements of a system and often involves a series of facilitated workshops attended by stakeholders of the system.
Software maintenance in software engineering is the modification of a software product after delivery to correct faults, to improve performance or other attributes.
Software design is the process by which an agent creates a specification of a software artifact, intended to accomplish goals, using a set of primitive components and subject to constraints.
Implementation is the realization of an application, or execution of a plan, idea, model, design, specification, standard, algorithm, or policy.
Question 64 |
A company needs to develop a strategy for software product development for which it has a choice of two programming languages L1 and L2. The number of lines of code (LOC) developed using L2 is estimated to be twice the LOC developed with Ll. The product will have to be maintained for five years. Various parameters for the company are given in the table below
4000 | |
5000 | |
4333 | |
4667 |
Question 64 Explanation:
Let LOC of L1=x, so LOC of L2=2x
Now,
(x/10000)*1000000 + 5*100000 = (2x/10000)*750000 + 5*50000
Solving for x, we get x =5000
Now,
(x/10000)*1000000 + 5*100000 = (2x/10000)*750000 + 5*50000
Solving for x, we get x =5000
Question 65 |
A company needs to develop digital signal processing software for one of its newest inventions. The software is expected to have 40000 lines of code. The company needs to determine the effort in person-months needed to develop this software using the basic COCOMO model. The multiplicative factor for this model is given as 2.8 for the software development on embedded systems, while the exponentiation factor is given as 1.20. What is the estimated effort in person-months?
234.25 | |
932.50 | |
287.80 | |
122.40 |
Question 65 Explanation:
The Constructive Cost Model (COCOMO) is an algorithmic software cost estimation model developed by Barry Boehm. The model uses a basic regression formula, with parameters that are derived from historical project data and current project characteristics
In the Constructive Cost Model (COCOMO), following is formula for effort applied
Effort Applied (E) = ab(KLOC)b [ person-months ]
= 2.8 x(40)1.20
= 2.8 x 83.65
= 234.25
In the Constructive Cost Model (COCOMO), following is formula for effort applied
Effort Applied (E) = ab(KLOC)b [ person-months ]
= 2.8 x(40)1.20
= 2.8 x 83.65
= 234.25
Question 66 |
Which one of the following is NOT desired in a good software requirement specifications(SRS) document?
Functional requirements | |
Non Functional requirements | |
Goals of implementation | |
Algorithm for software implementation |
Question 66 Explanation:
The software requirements specification document is a requirements specification for a software system, is a complete description of the behavior of a system to be developed and may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints)
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
Question 67 |
Bug means
A logical error in a program | |
A difficult syntax error in a program | |
Documenting programs using an efficient documentation tool | |
All of the above |
Question 67 Explanation:
A bug is an error in a software program. It may cause a program to unexpectedly quit or behave in an unintended manner. For example, a small bug may cause a button within a program's interface not to respond when you click it. A more serious bug may cause the program to hang or crash due to an infinite calculation or memory leak.
Question 68 |
In a risk based approach the risks identified mayn’t be used to:
Determine the test technique to be employed | |
Determine the extent of testing to be carried out | |
Prioritize testing in an attempt to find critical defects as early as possible | |
Determine the cost of the project |
Question 68 Explanation:
Risk identification is the process of determining risks that could potentially prevent the program, enterprise, or investment from achieving its objectives. It includes documenting and communicating the concern.
Tasks of risk identification:
1. Determine the test technique to be employed
2. Determine the extent of testing to be carried out
3. Prioritize testing in an attempt to find critical defects as early as possible
Tasks of risk identification:
1. Determine the test technique to be employed
2. Determine the extent of testing to be carried out
3. Prioritize testing in an attempt to find critical defects as early as possible
Question 69 |
Transformation that moves objects without deformation is called:
Rotation | |
Scaling | |
Translation | |
Morphism |
Question 69 Explanation:
→ A translation process moves every point a constant distance in a specified direction. It can be described as a rigid motion.
→ A translation can also be interpreted as the addition of a constant vector to every point, or as shifting the origin of the coordinate system.
→ A translation can also be interpreted as the addition of a constant vector to every point, or as shifting the origin of the coordinate system.
Question 70 |
A DFD that can be used to plan or record the specific makeup of a system is called:
Level 0 DFD | |
Level 1 DFD | |
Level 2 DFD | |
Level 3 DFD |
Question 70 Explanation:
→ A level 2 data flow diagram (DFD) offers a more detailed look at the processes that make up an information system than a level 1 DFD does It.
→ Higher level DFDs can be transformed into more specific lower level DFDs with deeper level of understanding unless the desired level of specification is achieved.
→ Higher level DFDs can be transformed into more specific lower level DFDs with deeper level of understanding unless the desired level of specification is achieved.
Question 71 |
In what module multiple instances of execution will yield the same result even if one instance has not terminated before the next one has begun?
Non reusable module | |
serially usable | |
Re-enterable module | |
recursive module |
Question 71 Explanation:
● A reenterable load module does not modify itself. Only one copy of the load module is loaded to satisfy the requirements of any number of tasks in a job step. This means that even though there are several tasks in the job step and each task concurrently uses the load module, the only central storage needed is an area large enough to hold one copy of the load module (plus a few bytes for control blocks).
● A non-reusable module can only be loaded for one task - the code is assumed to be self-modifying (data and code are in the same load module).
● A reusable module can be used by a second task when the first is finished with it (generally the module will acquire its own data space dynamically).
● A non-reusable module can only be loaded for one task - the code is assumed to be self-modifying (data and code are in the same load module).
● A reusable module can be used by a second task when the first is finished with it (generally the module will acquire its own data space dynamically).
Question 72 |
According to Brooks, if n is the number of programmers in a project team, then the number of communication path is
n(n-1)/2 | |
nlogn | |
n | |
n(n+1)/2 |
Question 72 Explanation:
● Brooks' law is an observation about software project management according to which "adding human resources to a late software project makes it later.
● According to Brooks, there is an incremental person who, when added to a project, makes it take more, not less time.
● Brooks introduced a formula to measure the volume of communication within the team. It assumes that every team member needs to communicate with every other team member, in order to perform his or her work.
● Group intercommunication formula measures the number of channels of communication within the project team and can be expressed as n*(n-1)/2, where n is the number of people working on a project.
●With 5 software developers working on a project, the number of channels of communication within the project team becomes 5*(5-1)/2 = 10
● With 10 software developers the number of channels of communication within the project team becomes 10*(10-1)/2 = 45
● According to Brooks, there is an incremental person who, when added to a project, makes it take more, not less time.
● Brooks introduced a formula to measure the volume of communication within the team. It assumes that every team member needs to communicate with every other team member, in order to perform his or her work.
● Group intercommunication formula measures the number of channels of communication within the project team and can be expressed as n*(n-1)/2, where n is the number of people working on a project.
●With 5 software developers working on a project, the number of channels of communication within the project team becomes 5*(5-1)/2 = 10
● With 10 software developers the number of channels of communication within the project team becomes 10*(10-1)/2 = 45
Question 73 |
The extent to which the software can control to operate correctly despite the introduction of invalid input is called as
reliability | |
robustness | |
fault tolerance | |
Portability |
Question 73 Explanation:
● Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
● robustness is the ability of a computer system to cope with errors during execution[1and cope with erroneous input
● Fault tolerance is the property that enables a system to continue operating properly in the event of the failure of some (one or more faults within) of its components.
● Portability in high-level computer programming is the usability of the same software in different environments.
● robustness is the ability of a computer system to cope with errors during execution[1and cope with erroneous input
● Fault tolerance is the property that enables a system to continue operating properly in the event of the failure of some (one or more faults within) of its components.
● Portability in high-level computer programming is the usability of the same software in different environments.
Question 74 |
Relation of COCOMO model is
E=a*(KLOC) 6 | |
E=a*(KLOC) 5 | |
E=a*(KLOC) 7 | |
E=a*(KLOC) 3 | |
None of These |
Question 74 Explanation:
The basic COCOMO equations take the form
Effort Applied (E) = a b (KLOC) b b [ man-months ]
Development Time (D) = c b (Effort Applied) d b [months]
People required (P) = Effort Applied / Development Time [count]
Effort Applied (E) = a b (KLOC) b b [ man-months ]
Development Time (D) = c b (Effort Applied) d b [months]
People required (P) = Effort Applied / Development Time [count]
Question 75 |
On an average, the programmer months is given by 3.6 * (KLOC) 1.2 . If so, a project requiring one thousand source instructions will require
3.6PM | |
0.36PM | |
0.0036PM | |
7.23PM |
Question 75 Explanation:
Given programmer months is given by 3.6 * (KLOC) 1.2 and lines of codes are 1000 =1K.
=3.6(1) 1.2 =3.6 Programmer months.
=3.6(1) 1.2 =3.6 Programmer months.
Question 76 |
Dividing a project into segments and smaller units in order to simplify analysis,design and programming efforts is called
Modular approach | |
Top down approach | |
Bottom up approach | |
Left right approach |
Question 76 Explanation:
● Dividing a project into segments and smaller units in order to simplify analysis,design and programming efforts is called Modular approach
● Modular design or “modularity in design”, is a design approach that subdivides a system into smaller parts called modules or skids that can be independently created and then used in different systems.
● Modular design or “modularity in design”, is a design approach that subdivides a system into smaller parts called modules or skids that can be independently created and then used in different systems.
Question 77 |
The Software Requirement Specification(SRS) is said to be _________ if and only if no subset of individual requirements described in it conflict with each other.
Correct | |
Consistent | |
Unambiguous | |
Verifiable |
Question 77 Explanation:
The Software Requirement Specification(SRS) is said to be Consistent if and only if no subset of individual requirements described in it conflict with each other.
Unambiguous : SRS said to be unambiguous if there exist no word that have more than one meaning and this will not confuse testers to get the exact reference.
Correct : SRS is said to be correct if it is error free and accurate.
Unambiguous : SRS said to be unambiguous if there exist no word that have more than one meaning and this will not confuse testers to get the exact reference.
Correct : SRS is said to be correct if it is error free and accurate.
Question 78 |
Which of the following statements is/are false?
P: The clean-room strategy to software engineering is based on the incremental software process model.
Q: The clean-room strategy to software engineering is one of the ways to overcome “unconscious” copying of copyrighted code.
Choose the correct answer from the code given below:
P: The clean-room strategy to software engineering is based on the incremental software process model.
Q: The clean-room strategy to software engineering is one of the ways to overcome “unconscious” copying of copyrighted code.
Choose the correct answer from the code given below:
Neither P and Q | |
P only | |
Both P and Q | |
Q only |
Question 78 Explanation:
Clean-room Strategy:
Cleanroom software engineering (CSE) is a process model that removes defects before they can precipitate serious hazards. It is a team-oriented, theory based software, which is developed using the formal methods, correctness verification and Statistical Quality Assurance (SQA).
→ Clean room management is based on the incremental model of software development, which accumulates into the final product. The approach combines mathematical-based methods of software specification, design and correctness verification with statistical, usage-based testing to certify software fitness for use.
→ The main goal of clean room engineering is to produce zero error-based software by allowing correct designs, which avoid rework.
Cleanroom software engineering (CSE) is a process model that removes defects before they can precipitate serious hazards. It is a team-oriented, theory based software, which is developed using the formal methods, correctness verification and Statistical Quality Assurance (SQA).
→ Clean room management is based on the incremental model of software development, which accumulates into the final product. The approach combines mathematical-based methods of software specification, design and correctness verification with statistical, usage-based testing to certify software fitness for use.
→ The main goal of clean room engineering is to produce zero error-based software by allowing correct designs, which avoid rework.
Question 79 |
Which of the following statements is/are true?
P: Software Reengineering is preferable for software products having high failure rates, having poor design and/or having poor code structure
Q: Software Reverse Engineering is the process of analyzing software with the objective of recovering its design and requirement specification.
P: Software Reengineering is preferable for software products having high failure rates, having poor design and/or having poor code structure
Q: Software Reverse Engineering is the process of analyzing software with the objective of recovering its design and requirement specification.
P only | |
Neither P nor Q | |
Q only | |
Both P and Q |
Question 79 Explanation:
Re-Engineering: Re-engineering refers to the rewriting the the part or whole system without changing its functionality. Re-Engineering is done for maintaining a system, to make the system compatible with the latest technologies.
Reverse engineering: It is also called as back engineering which is done to examine the working of a product.
Reverse engineering: It is also called as back engineering which is done to examine the working of a product.
Question 80 |
Software coupling involves dependencies among pieces of software called modules. Which of the following are correct statements with respect to module coupling?
P: Common Coupling occurs when two modules share the same global data
Q: control Coupling occur when modules share a composite data structure and use only part of it.
R: Content coupling occurs when one module modifies or relies on the internal working of another module.
P: Common Coupling occurs when two modules share the same global data
Q: control Coupling occur when modules share a composite data structure and use only part of it.
R: Content coupling occurs when one module modifies or relies on the internal working of another module.
P and Q only | |
P and R only | |
Q and R only | |
All of P,Q and R |
Question 80 Explanation:
Control Coupling : It exists between two modules if data from one module to other is used to direct the order of instruction execution in other module.
Common Coupling : Common coupling take place when two modules share global data.
Content Coupling : Content coupling exists between two modules if their code is shared.
Common Coupling : Common coupling take place when two modules share global data.
Content Coupling : Content coupling exists between two modules if their code is shared.
Question 81 |
Match each UML diagram in List 1 with Appropriate description in List 2
(a)-(i), (b)-(iv), (c) -(iii), (d)-(ii) | |
(a)-(iv), (b)-(ii), (c) -(i), (d)-(iii) | |
(a)-(iv), (b)-(i), (c) -(ii), (d)-(iii) | |
(a)-(i), (b)-(iv), (c) -(ii), (d)-(iii) |
Question 81 Explanation:
State diagram: Used to describe the dynamic behaviour of objects and could also be used to describe the entire system behaviour.
Statechart diagram describes the flow of control from one
state to another state. States are defined as a condition in which an object exists and it changes when some event is triggered. The most important purpose of Statechart diagram is to model
lifetime of an object from creation to termination.
Use case diagram: Describe how the external entities (people, devices) can interact with the system. Use case diagrams are used to gather the requirements of a system including internal and external influences.
Class diagram: The purpose of class diagram is to model the static view of an application. Class diagrams are the only diagrams which can be directly mapped with object-oriented languages and thus widely used at the time of construction.
Activity diagram: Usd to show the flow of a business process, the steps of a use case or the logic of an object behaviour.
Use case diagram: Describe how the external entities (people, devices) can interact with the system. Use case diagrams are used to gather the requirements of a system including internal and external influences.
Class diagram: The purpose of class diagram is to model the static view of an application. Class diagrams are the only diagrams which can be directly mapped with object-oriented languages and thus widely used at the time of construction.
Activity diagram: Usd to show the flow of a business process, the steps of a use case or the logic of an object behaviour.
Question 82 |
A legacy software system has 940 modules. The latest release require that 90 of these modules be changed. In addition, 40 new modules were added and 12 old modules were removed. Compute the software maturity index for the system.
0.725 | |
0.923 | |
0.849 | |
0.524 |
Question 82 Explanation:
Software Maturity Index(SMI) = [M T - (F c + F a + F d )] / M T
Where, M T = The number of modules in the current release
F c = The number of modules in the current release that have been changed F a =The number of modules in the current release that have been added
F d =The number of modules from the preceding release that were deleted in the current release
SMI = [940-(90+40+12)]/940
SMI = 0.849
Where, M T = The number of modules in the current release
F c = The number of modules in the current release that have been changed F a =The number of modules in the current release that have been added
F d =The number of modules from the preceding release that were deleted in the current release
SMI = [940-(90+40+12)]/940
SMI = 0.849
Question 83 |
Which of the following is not one of the principles of agile software development method ?
Following the plan | |
Embrace change | |
Customer involvement | |
Incremental delivery |
Question 83 Explanation:
Agile Software Development is based on twelve principles:
1. Customer satisfaction by early and continuous delivery of valuable software.
2. Welcome changing requirements, even in late development.
3. Deliver working software frequently (weeks rather than months)
4. Close, daily cooperation between business people and developers
5. Projects are built around motivated individuals, who should be trusted
6. Face-to-face conversation is the best form of communication (co-location)
7. Working software is the primary measure of progress
8. Sustainable development, able to maintain a constant pace
9. Continuous attention to technical excellence and good design
10. Simplicity—the art of maximizing the amount of work no done—is essential
11. Best architectures, requirements, and designs emerge from self-organizing teams
12. Regularly, the team reflects on how to become more effective, and adjusts accordingly
1. Customer satisfaction by early and continuous delivery of valuable software.
2. Welcome changing requirements, even in late development.
3. Deliver working software frequently (weeks rather than months)
4. Close, daily cooperation between business people and developers
5. Projects are built around motivated individuals, who should be trusted
6. Face-to-face conversation is the best form of communication (co-location)
7. Working software is the primary measure of progress
8. Sustainable development, able to maintain a constant pace
9. Continuous attention to technical excellence and good design
10. Simplicity—the art of maximizing the amount of work no done—is essential
11. Best architectures, requirements, and designs emerge from self-organizing teams
12. Regularly, the team reflects on how to become more effective, and adjusts accordingly
Question 84 |
Suppose a cloud contains software stack such as Operating system, Application software, etc. This model is referred as _________ model.
SaaS | |
IaaS | |
MaaS | |
PaaS |
Question 84 Explanation:
The following explains the 3 services offered by cloud computing for businesses:
1) Platform as a Service (PaaS): PaaS clouds are created, often times inside IaaS clouds by specialists to deliver the scalability and distribution of any application and to aid make a company’s expenses predictable.
2) Infrastructure as a Service (IaaS): This service provides business access to essential web infrastructure such as servers, connections, storage space, without the need to buy or manage internet infrastructure themselves.
3) Software as a Service (SaaS): This service offered by cloud computing is relatively mature and its phrases use those included in cloud computing. Cloud applications permit the cloud to be leveraged for software infrastructure. This reduces the burden of support, maintenance and operations because the application is run on computers that are owned by the vendor.
1) Platform as a Service (PaaS): PaaS clouds are created, often times inside IaaS clouds by specialists to deliver the scalability and distribution of any application and to aid make a company’s expenses predictable.
2) Infrastructure as a Service (IaaS): This service provides business access to essential web infrastructure such as servers, connections, storage space, without the need to buy or manage internet infrastructure themselves.
3) Software as a Service (SaaS): This service offered by cloud computing is relatively mature and its phrases use those included in cloud computing. Cloud applications permit the cloud to be leveraged for software infrastructure. This reduces the burden of support, maintenance and operations because the application is run on computers that are owned by the vendor.
Question 85 |
Software products need perfective maintenance for which of the following reasons ?
To rectify bugs observed while the system is in use. | |
When the customers need the product to run on new platforms | |
To support the new features that users want it to support | |
To overcome wear and tear caused by the repeated use of the software. |
Question 85 Explanation:
Maintenance: Maintenance can be referred as a process of enhancement in the software product according to the changing requirements of user.
4 types of maintenance
1. Adaptive – modifying the system to cope with changes in the software environment (DBMS, OS).
2. Perfective – implementing new or changed user requirements which concern functional enhancements to the software
3. Corrective – diagnosing and fixing errors, possibly ones found by users.
4. Preventive – increasing software maintainability or reliability to prevent problems in the future.
4 types of maintenance
1. Adaptive – modifying the system to cope with changes in the software environment (DBMS, OS).
2. Perfective – implementing new or changed user requirements which concern functional enhancements to the software
3. Corrective – diagnosing and fixing errors, possibly ones found by users.
4. Preventive – increasing software maintainability or reliability to prevent problems in the future.
Question 86 |
Which of the following is not defined in a good software requirement specification(SRS) document?
Functional requirement | |
Goals of implementation | |
Nonfunctional requirement | |
Algorithm for software implementation |
Question 86 Explanation:
The software requirements specification document is a requirements specification for a software system, is a complete description of the behavior of a system to be developed and
may include a set of use cases that describe interactions the users will have with the software. In addition it also contains non-functional requirements. Non-functional requirements impose
constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints)
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
Question 87 |
Software requirement Specification(SRS) is also known as specification of:
White box testing | |
Integrated testing | |
Acceptance testing | |
Black box testing |
Question 87 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.
Question 88 |
Line of code(LOC) of the product comes under which type of measures?
Indirect measures | |
Coding | |
Direct measures | |
none of the above |
Question 88 Explanation:
Source lines of code (SLOC), also known as lines of code (LOC), is a software metric used to measure the size of a computer program by counting the number of lines in the text of the program's source code. SLOC is typically used to predict the amount of effort that will be required to develop a program, as well as to estimate programming productivity or maintainability once the software is produced.
→ It comes under direct measures.
→ It comes under direct measures.
Question 89 |
What is the testing to ensure the WebApp property interfaces with other applications or databases?
Compatibility | |
Interoperability | |
Performance | |
Security |
Question 89 Explanation:
● Compatibility Testing is a type of Software testing to check whether your software is capable of running on different hardware, operating systems, applications, network environments or Mobile devices.
● Interoperability testing is defined as a software testing type, that checks whether software can interoperate with other software component, software or systems.
● In other words, interoperability testing means to prove that end-to-end functionality between two communicating systems is as required by the standard on which those systems are based.
● Performance testing is in general, a testing practice performed to determine how a system performs in terms of responsiveness and stability under a particular workload.
● Interoperability testing is defined as a software testing type, that checks whether software can interoperate with other software component, software or systems.
● In other words, interoperability testing means to prove that end-to-end functionality between two communicating systems is as required by the standard on which those systems are based.
● Performance testing is in general, a testing practice performed to determine how a system performs in terms of responsiveness and stability under a particular workload.
Question 90 |
What is described by means DFDs as studied earlier and represented in algebraic form?
Data flow | |
Data storage | |
Data structures | |
Data elements |
Question 90 Explanation:
● A data flow diagram (DFD) is a way of representing a flow of a data of a process or a system (usually an information system)
● The DFD also provides information about the outputs and inputs of each entity and the process itself.
● A data flow diagram has no control flow, there are no decision rules and no loops. Specific operations based on the data can be represented by a flowchart.
● The DFD also provides information about the outputs and inputs of each entity and the process itself.
● A data flow diagram has no control flow, there are no decision rules and no loops. Specific operations based on the data can be represented by a flowchart.
Question 91 |
The coupling between different modules of a software is categorized as follows:
I. Content coupling
II.Common coupling
III.Control coupling
IV.Stamp Coupling
V.Data Coupling
Coupling between modules can be ranked in the order of strongest(lease desirable) to weakes(most desirable) as follows:
I. Content coupling
II.Common coupling
III.Control coupling
IV.Stamp Coupling
V.Data Coupling
Coupling between modules can be ranked in the order of strongest(lease desirable) to weakes(most desirable) as follows:
I-II-III-IV-V | |
V-IV-III-II-I | |
I-III-V-II-IV | |
IV-II-V-III-I |
Question 91 Explanation:
One of the most widely used for software and systems is Myers’ classification, which defines seven levels of coupling, from tightest to loosest:
● Content coupling - modules rely on each others’ internal data or internal organization
● Common coupling - modules share the same global data
● External coupling - modules share an externally imposed data format, communication protocol or device interface
● Control coupling - one module controls the flow of another, such as by passing it a flag or other information
● Stamp coupling - modules share a composite data structure but use different parts of it
● Data coupling - modules share data through parameters, such as in a subroutine call
● Message coupling - modules communicate by passing messages
● Content coupling - modules rely on each others’ internal data or internal organization
● Common coupling - modules share the same global data
● External coupling - modules share an externally imposed data format, communication protocol or device interface
● Control coupling - one module controls the flow of another, such as by passing it a flag or other information
● Stamp coupling - modules share a composite data structure but use different parts of it
● Data coupling - modules share data through parameters, such as in a subroutine call
● Message coupling - modules communicate by passing messages
Question 92 |
Which of the following statements are TRUE?
I. The context diagram should be identified clearly at all levels of DFDs
II.Control information should not be represented in a DFD
III. Control information should not be represented in a DFD
IV. A data store can be connected either to another datastore or to an external entity.
I. The context diagram should be identified clearly at all levels of DFDs
II.Control information should not be represented in a DFD
III. Control information should not be represented in a DFD
IV. A data store can be connected either to another datastore or to an external entity.
II and IV | |
II and III | |
I and III | |
I,II and III |
Question 92 Explanation:
● A system context diagram (SCD) in engineering is a diagram that defines the boundary between the system, or part of a system, and its environment, showing the entities that interact with it.This diagram is a high level view of a system. It is similar to a block diagram.
● A data flow diagram (DFD) is a way of representing a flow of a data of a process or a system (usually an information system) The DFD also provides information about the outputs and inputs of each entity and the process itself. A data flow diagram has no control flow, there are no decision rules and no loops. Specific operations based on the data can be represented by a flowchart.
● A data flow diagram (DFD) is a way of representing a flow of a data of a process or a system (usually an information system) The DFD also provides information about the outputs and inputs of each entity and the process itself. A data flow diagram has no control flow, there are no decision rules and no loops. Specific operations based on the data can be represented by a flowchart.
Question 93 |
The following program is to be tested for statement coverage:
begin
if(a==b)
{
S1;
exit;
}
else if (c==d)
{
S2;
}
else
{
S3;
Exit;
}
S4;
end
The test cases T1,T2,T3 and T4 given below are expressed in terms of the properties satisfied by the values of variables a,b,c and d. The exact values are not given
T1:a,b,c and d are all equal
T1:a,b,c and d are all distinct
T3:a=b and c!=d
T4:a!b and c=d
Which of the test suites given below ensures coverage of statements S1,S2,S3 and S4?
begin
if(a==b)
{
S1;
exit;
}
else if (c==d)
{
S2;
}
else
{
S3;
Exit;
}
S4;
end
The test cases T1,T2,T3 and T4 given below are expressed in terms of the properties satisfied by the values of variables a,b,c and d. The exact values are not given
T1:a,b,c and d are all equal
T1:a,b,c and d are all distinct
T3:a=b and c!=d
T4:a!b and c=d
Which of the test suites given below ensures coverage of statements S1,S2,S3 and S4?
T1,T2,T3 | |
T2,T4 | |
T3,T4 | |
T1,T2,T4 |
Question 93 Explanation:
The test cases T1 covers S1 ,T2 covers S3 and T4 covers S2, S4.
Question 94 |
The Function Points(FP) calculated for software projects are often used to obtain an estimate of Lines of code(LOC) required for that project. Which of the following statements is FALSE in this context?
The relationship between FP and LOC depends on the programming language used to implement the software | |
LOC requirement for an assembly language implementation will be more for a given FP value, than LOC for implementation in COBOL. | |
On an average, one LOC of C++ provides approximately 1.6 times the functionality of a single LOC of FORTRAN | |
FP and LOC are not related to each other |
Question 94 Explanation:
● A function point (FP) is a component of software development which helps to approximate the cost of development early in the process.
● A function point calculates software size with the help of logical design and performance of functions as per user requirements.
● “Lines of code” (LOC) is a metric generally used to evaluate a software program or codebase according to its size. It is a general identifier taken by adding up the number of lines of code used to write a program
● A function point calculates software size with the help of logical design and performance of functions as per user requirements.
● “Lines of code” (LOC) is a metric generally used to evaluate a software program or codebase according to its size. It is a general identifier taken by adding up the number of lines of code used to write a program
Question 95 |
The availability of complex software is 90% its Mean Time Between Failure(MTBF) is 200 days. Because of the critical nature of the usage, the organization deploying the software further enhanced it to obtain an availability of 95%. In the process, the Mean Time To Repair(MTTR) increased by 5 days. What is the MTBF of the enhanced software?(choose the nearest option)
205 days | |
300 days | |
500 days | |
700 days |
Question 95 Explanation:
Case-1:Availability of complex software =90% =0.9
Mean Time Between Failure(MTBF)=200
MTTR =?(we need to find )
Case-2:After enhancement modified ,availability= 95%=0.95,For this case,Mean Time To Repair(MTTR) increased by 5 days.
MTBF=?(we need to find )
Availability = MTBF/(MTBF + MTTR)
Case-1:
By substituting option-1 value, 0.9 = 200/(200 + MTTR) then
MTTR= 22.22
Case 2 :0.95 = MTBF/( MTBF+22.22+5)
MTBF= 517.18
Mean Time Between Failure(MTBF)=200
MTTR =?(we need to find )
Case-2:After enhancement modified ,availability= 95%=0.95,For this case,Mean Time To Repair(MTTR) increased by 5 days.
MTBF=?(we need to find )
Availability = MTBF/(MTBF + MTTR)
Case-1:
By substituting option-1 value, 0.9 = 200/(200 + MTTR) then
MTTR= 22.22
Case 2 :0.95 = MTBF/( MTBF+22.22+5)
MTBF= 517.18
Question 96 |
Alpha and Beta testing are forms of
Acceptance testing | |
Integration testing | |
System testing | |
Unit testing |
Question 96 Explanation:
Acceptance testing can mean one of two things:
A smoke test is used as a build acceptance test prior to further testing, e.g., before integration or regression.
Acceptance testing performed by the customer, often in their lab environment on their own hardware, is known as user acceptance testing (UAT). Acceptance testing may be performed as part of the hand-off process between any two phases of development.
Alpha testing:
Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site
. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing before the software goes to beta testing.
Beta testing
Beta testing comes after alpha testing and can be considered a form of external user acceptance testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team known as beta testers.
The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Beta versions can be made available to the open public to increase the feedback field to a maximal number of future users and to deliver value earlier, for an extended or even indefinite period of time (perpetual beta).
A smoke test is used as a build acceptance test prior to further testing, e.g., before integration or regression.
Acceptance testing performed by the customer, often in their lab environment on their own hardware, is known as user acceptance testing (UAT). Acceptance testing may be performed as part of the hand-off process between any two phases of development.
Alpha testing:
Alpha testing is simulated or actual operational testing by potential users/customers or an independent test team at the developers' site
. Alpha testing is often employed for off-the-shelf software as a form of internal acceptance testing before the software goes to beta testing.
Beta testing
Beta testing comes after alpha testing and can be considered a form of external user acceptance testing. Versions of the software, known as beta versions, are released to a limited audience outside of the programming team known as beta testers.
The software is released to groups of people so that further testing can ensure the product has few faults or bugs. Beta versions can be made available to the open public to increase the feedback field to a maximal number of future users and to deliver value earlier, for an extended or even indefinite period of time (perpetual beta).
Question 97 |
If in a software project the number of user input, user output, enquiries, files and external interfaces are (15, 50, 24, 12, 8), respectively, with complexity average weighting factor.
The productivity if effort = 70 percent-month is
The productivity if effort = 70 percent-month is
110.54 | |
408.74 | |
304.78 | |
220.14 |
Question 97 Explanation:
Given in question, average weighting factor.
=(External Inputs(EI)*4) + (External Output(EO) * 5) + (External Inquiries(EQ) * 4) + (External logical files(ILF) * 10) + (External Interface file(EIF) * 7)
=(15*4 + 50*5 + 24*4 +12*10 + 8*7
= 582
And, productivity month is 70%
=582*0.7
=407.4
Question 98 |
Which of the following is a white box testing technique?
Data flow testing
| |
Equivalence class testing
| |
Cause effect graphing
| |
State based testing
|
Question 98 Explanation:
White box testing techniques analyze the internal structures the used data structures, internal design, code structure and the working of the software rather than just the functionality as in black box testing. It is also called glass box testing or clear box testing or structural testing.
White box testing techniques
1. Statement coverage
2. Branch CoverAge
3. Condition Coverage
4. Multiple Condition Coverage
5. Basis Path Testing
6. Flow graph notation
7. Loop Testing
White box testing techniques
1. Statement coverage
2. Branch CoverAge
3. Condition Coverage
4. Multiple Condition Coverage
5. Basis Path Testing
6. Flow graph notation
7. Loop Testing
Question 99 |
Which of the following DFD levels depicts the entire information system as one diagram concealing all the underlying details?
Level 0 | |
Level 1 | |
Level 3 | |
Level 2 |
Question 99 Explanation:
DFD level 0:
→ It Highest abstraction level DFD is known as Level 0 DFD, which depicts the entire information system as one diagram concealing all the underlying details.
→ Level 0 DFDs are also known as context level DFDs.
→ It shows a data system as a whole and emphasizes the way it interacts with external entities.
→ This DFD level 0 example shows how such a system might function within a typical retail business.
DFD level 1:
→ DFD depicts basic modules in the system and flow of data among various modules.
→ Level 1 DFD also mentions basic processes and sources of information.
→ It breaks down the main processes in to subprocesses that can then be analyzed and improved on a more intimate level.
DFD level 2:
A level 2 data flow diagram (DFD) offers a more detailed look at the processes that make up an information system than a level 1 DFD does it. Higher level DFDs can be transformed into more specific lower level DFDs with deeper level of understanding unless the desired level of specification is achieved.
→ It Highest abstraction level DFD is known as Level 0 DFD, which depicts the entire information system as one diagram concealing all the underlying details.
→ Level 0 DFDs are also known as context level DFDs.
→ It shows a data system as a whole and emphasizes the way it interacts with external entities.
→ This DFD level 0 example shows how such a system might function within a typical retail business.
DFD level 1:
→ DFD depicts basic modules in the system and flow of data among various modules.
→ Level 1 DFD also mentions basic processes and sources of information.
→ It breaks down the main processes in to subprocesses that can then be analyzed and improved on a more intimate level.
DFD level 2:
A level 2 data flow diagram (DFD) offers a more detailed look at the processes that make up an information system than a level 1 DFD does it. Higher level DFDs can be transformed into more specific lower level DFDs with deeper level of understanding unless the desired level of specification is achieved.
Question 100 |
Which of the following is NOT a goal of the software testing?
Failure detection
| |
Fault detection
| |
Size reduction | |
Error detection
|
Question 100 Explanation:
Size reduction is not goal of software testing because their intention is to find bugs and detection of bugs.
Question 101 |
What is the Cyclomatic Complexity of the following flow-graph of a software code?
10 | |
4 | |
8 | |
2 |
Question 101 Explanation:
Step-1: To find cyclomatic complexity we have 3 formulas.
Number of regions(R) + 1
Predicates(P) + 1
Edges(E) - Vertex(V) + 2
Step-2: We can apply any formula to find cyclomatic complexity.
Step-3: 8 vertex and 10 edges.
10 - 8 + 2 = 4
Number of regions(R) + 1
Predicates(P) + 1
Edges(E) - Vertex(V) + 2
Step-2: We can apply any formula to find cyclomatic complexity.
Step-3: 8 vertex and 10 edges.
10 - 8 + 2 = 4
Question 102 |
Which of the following is a desirable property of module?
Independency | |
low cohesiveness | |
High coupling | |
Multifunctional |
Question 102 Explanation:
The goal of software engineering is high cohesion and low coupling. The desirable property of module is independency.
Question 103 |
A program p calls two subprograms P1 and P2. P1 can fail 50% time and P2 can fail 40% times. The program P can fail
50% | |
10% | |
60% | |
70% |
Question 103 Explanation:
Program P fails when either P1 fails or P2 fails, i.e., failure of P1 + failure of P2 .
But this will also contain the case when both P1 and P2 fails at the same time, i.e., failure of P1 ∩ failure of P2 , since this case will be already be counted on ( P1+P2 ).
Therefore, our final answer will be failure of P1 + failure of P2 - (failure of P1 ∩ failure of P2)
But this will also contain the case when both P1 and P2 fails at the same time, i.e., failure of P1 ∩ failure of P2 , since this case will be already be counted on ( P1+P2 ).
Therefore, our final answer will be failure of P1 + failure of P2 - (failure of P1 ∩ failure of P2)
Question 104 |
By open domain CASE tools we mean
tools available in open domain | |
Software packages which can be downloaded from the internet | |
Software packages to aid each phase of the systems analysis and design which an be downloaded free of cost from the internet | |
Source codes of CASE tools |
Question 104 Explanation:
● Tools are also in the open domain which can be downloaded and used.
● They do not usually have very good user interfaces.
● They do not usually have very good user interfaces.
Question 105 |
Which of the following is not a deliverable of the structured system analysis?
Data flow diagram | |
Prototype model | |
Entity Relationship diagram | |
Data dictionary |
Question 105 Explanation:
→ Prototype model is used when the customers do not know the exact project requirements beforehand. In this model, a prototype of the end product is first developed, tested and refined as per customer feedback repeatedly till a final acceptable prototype is achieved which forms the basis for developing the final product.
Question 106 |
By open domain CASE tools we mean
tools available in open domain | |
Software packages which can be downloaded from the internet | |
Software packages to aid each phase of the systems analysis and design which an be downloaded free of cost from the internet | |
Source codes of CASE tools |
Question 106 Explanation:
● Tools are also in the open domain which can be downloaded and used.
● They do not usually have very good user interfaces.
● They do not usually have very good user interfaces.
Question 107 |
What is the modality of relationship, if there is no explicit need for relationship to occur?
0 | |
2 | |
3 | |
1 |
Question 107 Explanation:
→ The modality of a relationship is 0 if there is no explicit need for the relationship to occur or the relationship is optional.
→ The modality is 1 if an occurrence of the relationship is mandatory
→ The modality is 1 if an occurrence of the relationship is mandatory
Question 108 |
Which of the following is a desirable property of module?
Independency | |
Low Cohesiveness | |
High Coupling | |
Multifunctional |
Question 108 Explanation:
● Highly coupled have program units dependent on each other.
● Loosely coupled are made up of units that are independent or almost independent.
● The desirable property is High cohesion and low coupling
● From the above options , the suitable option is independency
● Loosely coupled are made up of units that are independent or almost independent.
● The desirable property is High cohesion and low coupling
● From the above options , the suitable option is independency
Question 109 |
Which of the following represents the life cycle of software development?
Design → Analysis → Coding→ Operations and maintenance→ Testing | |
Analysis→ Design→ Coding→ Testing→ Operation and Maintenance | |
Design→ Analysis→ Coding→ Testing→ Operation and Maintenance | |
Analysis→ Design→ Coding→ Operation and maintenance→ Testing |
Question 109 Explanation:
Life cycle of software development phases
1. Planning: Without the perfect plan, calculating the strengths and weaknesses of the project, development of software is meaningless. Planning kicks off a project flawlessly and affects its progress positively.
2. Analysis: This step is about analyzing the performance of the software at various stages and making notes on additional requirements. Analysis is very important to proceed further to the next step.
3. Design: Once the analysis is complete, the step of designing takes over, which is basically building the architecture of the project. This step helps remove possible flaws by setting a standard and attempting to stick to it.
4. Development & Implementation: The actual task of developing the software starts here with data recording going on in the background. Once the software is developed, the stage of implementation comes in where the product goes through a pilot study to see if it’s functioning properly.
5. Testing: The testing stage assesses the software for errors and documents bugs if there are any.
6. Maintenance: Once the software passes through all the stages without any issues, it is to undergo a maintenance process wherein it will be maintained and upgraded from time to time to adapt to changes.
1. Planning: Without the perfect plan, calculating the strengths and weaknesses of the project, development of software is meaningless. Planning kicks off a project flawlessly and affects its progress positively.
2. Analysis: This step is about analyzing the performance of the software at various stages and making notes on additional requirements. Analysis is very important to proceed further to the next step.
3. Design: Once the analysis is complete, the step of designing takes over, which is basically building the architecture of the project. This step helps remove possible flaws by setting a standard and attempting to stick to it.
4. Development & Implementation: The actual task of developing the software starts here with data recording going on in the background. Once the software is developed, the stage of implementation comes in where the product goes through a pilot study to see if it’s functioning properly.
5. Testing: The testing stage assesses the software for errors and documents bugs if there are any.
6. Maintenance: Once the software passes through all the stages without any issues, it is to undergo a maintenance process wherein it will be maintained and upgraded from time to time to adapt to changes.
Question 110 |
If customer is to be involved in all phases of software development, which software model can be selected:
Prototype model
| |
Waterfall model
| |
RAD model
| |
Component model
|
Question 110 Explanation:
Rapid Application Development focuses on gathering customer requirements through workshops or focus groups, early testing of the prototypes by the customer using iterative concept, reuse of the existing prototypes (components), continuous integration and rapid delivery.
Question 111 |
Software does not wear-out in the traditional sense of the term, but software does tend to deteriorate as it evolves, because :
Software suffers from exposure to hostile environments. | |
Defects are more likely to arise after software has been used often. | |
Multiple change requests introduce errors in component interactions. | |
Software spare parts become harder to order. |
Question 111 Explanation:
Software is not susceptible to the same environmental problems that cause hardware to wear out. In theory, therefore, the failure rate curve for software should take the form shown below.
Question 112 |
Which of the following is not a key issue stressed by an agile philosophy of software engineering ?
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. |
Question 112 Explanation:
→ Agile software development testing is completed in the same iteration as programming. One phase is completed in its entirety before moving on to the next phase because testing is done in
every iteration which develops a small piece of the software users can frequently use those new pieces of software and validate the value.
Question 113 |
What is the normal order of activities in which traditional software testing is organized?
(a) Integration Testing
(b) System Testing
(c) Unit Testing
(d) Validation Testing
(a) Integration Testing
(b) System Testing
(c) Unit Testing
(d) Validation Testing
(c),(a),(b),(d) | |
(c),(a),(d),(b) | |
(d),(c),(b),(a) | |
(b),(d),(a),(c) |
Question 113 Explanation:
Unit testing: Unit testing starts at the centre and each unit is implemented in source code.
Integration testing: An integration testing focuses on the construction and design of the software.
Validation testing: Check all the requirements like functional, behavioral and performance requirement are validate against the construction software.
System testing: System testing confirms all system elements and performance are tested entirely.
Question 114 |
Which of the following testing techniques ensures that the software product runs correctly after the changes during maintenance ?
Path Testing | |
Integration Testing | |
Unit Testing | |
Regression Testing |
Question 114 Explanation:
→ Regression testing is the re-execution of some subset of tests that have already been conducted to ensure that changes have not propagated unintended side effects Whenever software is corrected, some aspect of the software configuration (the program, its documentation, or the data that support it) is changed.
→ Regression testing helps to ensure that changes (due to testing or for other reasons) do not introduce unintended behavior or additional errors.
→ Regression testing may be conducted manually, by re-executing a subset of all test cases or using automated capture/playback tools.
→ Regression testing helps to ensure that changes (due to testing or for other reasons) do not introduce unintended behavior or additional errors.
→ Regression testing may be conducted manually, by re-executing a subset of all test cases or using automated capture/playback tools.
Question 115 |
Which of the following Supercomputers is the fastest Supercomputer ?
Sunway TaihuLight | |
Titan | |
Piz Daint | |
Sequoia |
Question 115 Explanation:
→ The Sunway TaihuLight is a Chinese supercomputer which, as of November 2018, is ranked third in the TOP500 list, with a LINPACK benchmark rating of 93 petaflops.[ The name is translated as divine power, the light of Taihu Lake.
Question 116 |
Which of the following statements about ERP system is true ?
Most ERP software implementations fully achieve seamless integration | |
ERP software packages are themselves combinations of separate applications for manufacturing, materials, resource planning, general ledger, human resources, procurement and order entry. | |
Integration of ERP systems can be achieved in only one way | |
An ERP package implemented uniformly throughout an enterprise is likely to contain very flexible connections to allow charges and software variations. |
Question 116 Explanation:
ERP software packages are themselves combinations of separate applications for manufacturing, materials, resource planning, general ledger, human resources, procurement and order entry.
Question 117 |
Software Engineering is an engineering discipline that is concerned with:
how computer systems work | |
theories and methods that underlie computers and software systems. | |
all aspects of software production | |
all aspects of computer-based systems development, including hardware, software and process engineering. |
Question 117 Explanation:
→ Software Engineering is an engineering discipline that is concerned with all aspects of software production
→ It follows some basic activities are software specification, software development, software validation and software evolution.
Question 118 |
Which of the following is not one of three software product aspects addressed by McCall’s software quality factors ?
Ability to undergo change | |
Adaptability to new environments | |
Operational characteristics | |
Production costs and scheduling |
Question 118 Explanation:
McCall’s software quality factors
1. Product operation factors − Correctness, Reliability, Efficiency, Integrity, Usability.
2. Product revision factors − Maintainability, Flexibility, Testability.
3. Product transition factors − Portability, Reusability, Interoperability.
1. Product operation factors − Correctness, Reliability, Efficiency, Integrity, Usability.
2. Product revision factors − Maintainability, Flexibility, Testability.
3. Product transition factors − Portability, Reusability, Interoperability.
Question 119 |
Which of the following statement(s) is/are true with respect to software architecture ?
S1 : Coupling is a measure of how well the things grouped together in a module belong together logically.
S2 : Cohesion is a measure of the degree of interaction between software modules.
S3 : If coupling is low and cohesion is high then it is easier to change one module without affecting others.
S1 : Coupling is a measure of how well the things grouped together in a module belong together logically.
S2 : Cohesion is a measure of the degree of interaction between software modules.
S3 : If coupling is low and cohesion is high then it is easier to change one module without affecting others.
Only S1 and S2 | |
Only S3 | |
All of S1, S2 and S3 | |
Only S1 |
Question 119 Explanation:
→ Cohesion is the indication of the relationship within a module.
→ Coupling is the indication of the relationships between modules.
→ If coupling is low and cohesion is high then it is easier to change one module without affecting others.
→ High cohesion within modules and low coupling between modules are often regarded as related to high quality in software architecture as well as object oriented programming languages.
→ Coupling is the indication of the relationships between modules.
→ If coupling is low and cohesion is high then it is easier to change one module without affecting others.
→ High cohesion within modules and low coupling between modules are often regarded as related to high quality in software architecture as well as object oriented programming languages.
Question 120 |
The prototyping model of software development is:
a reasonable approach when requirements are well-defined | |
a useful approach when a customer cannot define requirements clearly. | |
the best approach to use for projects with large development teams. | |
a risky model that rarely produces a meaningful product. |
Question 120 Explanation:
→ The prototyping model of software development is a useful approach when a customer cannot define requirements clearly.
Advantage:
1. We can develop the software where requirements are unclear
2. Customer satisfaction
Disadvantage:
1. Who pay cost of prototype
2. Required the design expertise
Advantage:
1. We can develop the software where requirements are unclear
2. Customer satisfaction
Disadvantage:
1. Who pay cost of prototype
2. Required the design expertise
Question 121 |
A software design pattern used to enhance the functionality of an object at run-time is:
Adapter | |
Decorator | |
Delegation | |
Proxy |
Question 121 Explanation:
→ Software design pattern used to enhance the functionality of an object at run-time is Decorator.
→ Decorator will attach additional responsibilities to an object dynamically keeping the same interface.
→ Decorators provide a flexible alternative to subclassing for extending functionality.
→ Decorator will attach additional responsibilities to an object dynamically keeping the same interface.
→ Decorators provide a flexible alternative to subclassing for extending functionality.
Question 122 |
Which of the following is used to determine the specificity of requirements?
[ Where n 1 is the number of requirements for which all reviewers have identical interpretations, n 2 is number of requirements in a specification.]
n 1 / n 2 | |
n 2 / n 1 | |
n 1 + n 2 | |
n 1 - n 2 |
Question 122 Explanation:
T he specificity of requirements determines n 1 / n 2
n 1 is the number of requirements for which all reviewers have identical interpretations
n 2 is number of requirements in a specification
n 1 is the number of requirements for which all reviewers have identical interpretations
n 2 is number of requirements in a specification
Question 123 |
The major shortcoming of waterfall model is
The difficulty in accommodating changes after requirement analysis. | |
The difficult in accommodating changes after feasibility analysis. | |
The system testing | |
The maintenance of system. |
Question 123 Explanation:
Advantages:
1. Waterfall model is simple and easy to understand.
2. It works as reference model for others.
Disadvantage:
1. Real projects cannot be sequential
2. Initially all requirements should known i.e requirements are frozen. It may be suited for static projects.
3. Error omission too costly
4. Maintenance is too costly(We have to redesign the whole project from scratch)
5. Customer must have patience
6. It is based on Big-Bang approach
1. Waterfall model is simple and easy to understand.
2. It works as reference model for others.
Disadvantage:
1. Real projects cannot be sequential
2. Initially all requirements should known i.e requirements are frozen. It may be suited for static projects.
3. Error omission too costly
4. Maintenance is too costly(We have to redesign the whole project from scratch)
5. Customer must have patience
6. It is based on Big-Bang approach
Question 124 |
The quick design of a software that is visible to end users leads to _____.
iterative model | |
prototype model | |
spiral model | |
waterfall model |
Question 124 Explanation:
The quick design of a software that is visible to end users leads to prototype model.
Advantages:
1. We can develop software where requirements are unclear
2. Customer satisfaction
Disadvantage:
1. Who pay cost of prototype
2. Required the design expertise
3. Throwaway approach (or) evolutionary approach ( In this approach we develop the software by enhancing protype)
Advantages:
1. We can develop software where requirements are unclear
2. Customer satisfaction
Disadvantage:
1. Who pay cost of prototype
2. Required the design expertise
3. Throwaway approach (or) evolutionary approach ( In this approach we develop the software by enhancing protype)
Question 125 |
For a program of k variables, boundary value analysis yields ______ test cases.
4k – 1 | |
4k | |
4k + 1 | |
2 k – 1 |
Question 125 Explanation:
For a program of k variables, boundary value analysis yields 4k + 1 test cases.
Question 126 |
The extent to which a software performs its intended functions without failures, is termed as__
Robustness | |
Correctness | |
Reliability | |
Accuracy |
Question 126 Explanation:
→ The extent to which a software performs its intended functions without failures, is termed as Reliability.
→ Software reliability is defined as the ability of a system or component to perform its required functions under stated conditions for a specified period of time. It is the probability of a failure free operation of a program for a specified time in a specified environment.
→ Robustness is the ability of a computer system to cope with errors during execution and cope with erroneous input.
→ Correctness of an algorithm is asserted when it is said that the algorithm is correct with respect to a specification.
→ Accuracy of a measurement system is the degree of closeness of measurements of a quantity to that quantity's true value.
→ Software reliability is defined as the ability of a system or component to perform its required functions under stated conditions for a specified period of time. It is the probability of a failure free operation of a program for a specified time in a specified environment.
→ Robustness is the ability of a computer system to cope with errors during execution and cope with erroneous input.
→ Correctness of an algorithm is asserted when it is said that the algorithm is correct with respect to a specification.
→ Accuracy of a measurement system is the degree of closeness of measurements of a quantity to that quantity's true value.
Question 127 |
If S 1 is total number of modules defined in the program architecture, S 3 is the number of modules whose correct function depends on prior processing then the number of modules not dependent on prior processing is :
1 + (S 3 / S 1 ) | |
1 - (S 3 / S 1 ) | |
1 + (S 1 / S 3 ) | |
1 - (S 1 / S 3 ) |
Question 127 Explanation:
S1 = The total number of modules defined in the program architecture.
S3 = The number of modules whose correct function depends on prior processing.
Module not dependent on prior processing is 1- (S3/S1)
S3 = The number of modules whose correct function depends on prior processing.
Module not dependent on prior processing is 1- (S3/S1)
Question 128 |
The ________ model is preferred for software development when the requirements are not clear.
Rapid Application Development | |
Rational Unified Process | |
Evolutionary Model | |
Waterfall Model |
Question 128 Explanation:
→ Rapid Application Development(RAD) is used when the requirements cannot or will not be specified.
→ Evolutionary Model is preferred for software development when the requirements are not clear.
→ The evolutionary software process model, is more commonly known as the “spiral model”.
→ Evolutionary Model is preferred for software development when the requirements are not clear.
→ The evolutionary software process model, is more commonly known as the “spiral model”.
Question 129 |
Which of the following is not included in waterfall model?
Requirement analysis | |
Risk analysis | |
Design | |
Coding |
Question 129 Explanation:
Waterfall model steps:
1.Feasibility Study
2.Analysis
3.Design
4.Coding and Testing
5.Integration & System testing
6.Maintenance
1.Feasibility Study
2.Analysis
3.Design
4.Coding and Testing
5.Integration & System testing
6.Maintenance
Question 130 |
In software testing, how the error, fault and failure are related to each other?
Error leads to failure but fault is not related to error and failure. | |
Fault leads to failure but error is not related to fault and failure. | |
Error leads to fault and fault leads to failure. | |
Fault leads to error and error leads to failure. |
Question 130 Explanation:
→ Error: A human action that produces an incorrect result. This is also sometimes referred to as Mistake.
→ Fault: A manifestation of an error in software, also known as Defect or Bug.
→ Failure: A deviation of the software from its expected delivery or service.
Relation between Error,Fault and Failure
→ Fault: A manifestation of an error in software, also known as Defect or Bug.
→ Failure: A deviation of the software from its expected delivery or service.
Relation between Error,Fault and Failure
Question 131 |
In which testing strategy requirements established during requirements analysis are validated against developed software?
Validation testing | |
Integration testing | |
Regression testing | |
System testing |
Question 131 Explanation:
Validation Testing ensures that the product actually meets the client's needs. It can also be defined as to demonstrate that the product fulfills its intended use when deployed on appropriate environment.
It answers to the question, Are we building the right product?
It answers to the question, Are we building the right product?
Question 132 |
Which process model is also called as classic life cycle model?
Waterfall model | |
RAD model | |
Prototyping model | |
Incremental model |
Question 132 Explanation:
→ The classical waterfall model is intuitively the most obvious way to develop software. Though the classical waterfall model is elegant and intuitively obvious, it is not a practical model in the sense that it can not be used in actual software development projects.
→ This model can be considered to be a theoretical way of developing software. But all other life cycle models are essentially derived from the classical waterfall model. So, in order to be able to appreciate other life cycle models it is necessary to learn the classical waterfall model.
→ This model can be considered to be a theoretical way of developing software. But all other life cycle models are essentially derived from the classical waterfall model. So, in order to be able to appreciate other life cycle models it is necessary to learn the classical waterfall model.
Question 133 |
Cohesion is an extension of:
Abstraction concept | |
Refinement concept | |
Information hiding concept | |
Modularity |
Question 133 Explanation:
→ Cohesion refers to the degree to which the elements inside a module belong together.
→ Cohesion is an extension of Information hiding concept.
→ Cohesion is an extension of Information hiding concept.
Question 134 |
Which one from the following is highly associated activity of project planning?
Keep track of the project progress. | |
Compare actual and planned progress and costs. | |
Identify the activities, milestones and deliverables produced by a project. | |
Both (2) and (3). |
Question 134 Explanation:
Project planning activities(High priority):
1. Compare actual and planned progress and costs.
2. Identify the activities, milestones and deliverables produced by a project.
1. Compare actual and planned progress and costs.
2. Identify the activities, milestones and deliverables produced by a project.
Question 135 |
Which of the following statements is incorrect for Parallel Virtual Machine (PVM) ?
The PVM communication model provides asynchronous blocking send, asynchronous blocking receive, and non-blocking receive function. | |
Message buffers are allocated dynamically. | |
The PVM communication model assumes that any task can send a message to any other PVM task and that there is no limit to the size or number of such messages. | |
In PVM model, the message order is not preserved. |
Question 135 Explanation:
PVM (Parallel Virtual Machine) is a software package that permits a heterogeneous collection of Unix and/or Windows computers hooked together by a network to be used as a single large parallel computer. Thus large computational problems can be solved more cost effectively by using the aggregate power and memory of many computers. The software is very portable. The source, which is available free thru netlib, has been compiled on everything from laptops to CRAYs.
→ PVM enables users to exploit their existing computer hardware to solve much larger problems at minimal additional cost. Hundreds of sites around the world are using PVM to solve important scientific, industrial, and medical problems in addition to PVM's use as an educational tool to teach parallel programming. With tens of thousands of users, PVM has become the de facto standard for distributed computing world-wide.
→ PVM enables users to exploit their existing computer hardware to solve much larger problems at minimal additional cost. Hundreds of sites around the world are using PVM to solve important scientific, industrial, and medical problems in addition to PVM's use as an educational tool to teach parallel programming. With tens of thousands of users, PVM has become the de facto standard for distributed computing world-wide.
Question 136 |
The main objective of designing various modules of a software system is :
To decrease the cohesion and to increase the coupling | |
To increase the cohesion and to decrease the coupling | |
To increase the coupling only | |
To increase the cohesion only |
Question 136 Explanation:
→ Cohesion is a measure of internal strength within a module, whereas coupling is a measure of inter dependency among the modules.
→ So in the context of modular software design there should be high cohesion and low coupling.
→ So in the context of modular software design there should be high cohesion and low coupling.
Question 137 |
Three essential components of a software project plan are :
Team structure, Quality assurance plans, Cost estimation | |
Cost estimation, Time estimation, Quality assurance plan | |
Cost estimation, Time estimation, Personnel estimation | |
Cost estimation, Personnel estimation, Team structure |
Question 137 Explanation:
→ A project is a success if it meets the objectives of time, cost, technical and business.
Essential components:
1.Software size estimation
2.Effort estimation
3.Time estimation
4.Cost estimation
Essential components:
1.Software size estimation
2.Effort estimation
3.Time estimation
4.Cost estimation
Question 138 |
Reliability of software is dependent on :
Number of errors present in software | |
Documentation | |
Testing suites | |
Development Processes |
Question 138 Explanation:
→ Reliability of software is dependent on number of errors present in software.
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
Question 139 |
The Function Point (FP) metric is :
Calculated from user requirements | |
Calculated from Lines of code | |
Calculated from software s complexity assessment | |
None of the above |
Question 139 Explanation:
→ The Function Point (FP) metric is calculated from software s complexity assessment.
→ A Function Point (FP) is a unit of measurement to express the amount of business functionality, an information system (as a product) provides to a user.
→ FPs measure software size. They are widely accepted as an industry standard for functional sizing.
→ A Function Point (FP) is a unit of measurement to express the amount of business functionality, an information system (as a product) provides to a user.
→ FPs measure software size. They are widely accepted as an industry standard for functional sizing.
Question 140 |
The testing of software against SRS is called :
Acceptance testing | |
Integration testing | |
Regression testing | |
Series testing |
Question 140 Explanation:
→ Acceptance testing is a test conducted to determine if the requirements of a specification or contract are met. This is test works on SRS document.
→ In software testing in which individual software modules are combined and tested as a group. Some different types of integration testing are big-bang, mixed (sandwich), risky-hardest, top-down, and bottom-up.
→ Regression testing is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. If not, that would be called a regression. Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components.
→ In software testing in which individual software modules are combined and tested as a group. Some different types of integration testing are big-bang, mixed (sandwich), risky-hardest, top-down, and bottom-up.
→ Regression testing is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. If not, that would be called a regression. Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components.
Question 141 |
The lower degree of cohesion is :
logical cohesion | |
coincidental cohesion | |
procedural cohesion | |
communicational cohesion |
Question 141 Explanation:
Cohesion is a measure of degree to which elements of a module are functionally related.
Given a list is least desirable to most desirable types in module cohesion
Given a list is least desirable to most desirable types in module cohesion
Question 142 |
The Reliability of the software is directly dependent upon :
Quality of the design | |
Programmer s experience | |
Number of error | |
Set of user requirements |
Question 142 Explanation:
→ Reliability of software is dependent on number of errors present in software.
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
Question 143 |
Successive layer of design in software using bottom-up design is called :
Layer of Definement | |
Layer of Construction | |
Layer of abstraction | |
None of the above |
Question 143 Explanation:
Successive layer of design in software using bottom-up design is called layer of abstraction.
Question 144 |
Sliding window concept of software project management is :
Preparation of comprehensible plan | |
Preparation of the various stages of development | |
Ad-hoc planning | |
Requirement analysis |
Question 144 Explanation:
→ In the sliding window technique, starting with an initial plan, the project is planned more accurately in successive development stages.
→ At the start of a project, project managers have incomplete knowledge about the details of the project. Their information base gradually improves as the project progresses through different phases. After the completion of every phase, the project managers can plan each subsequent phase more accurately and with increasing levels of confidence.
→ At the start of a project, project managers have incomplete knowledge about the details of the project. Their information base gradually improves as the project progresses through different phases. After the completion of every phase, the project managers can plan each subsequent phase more accurately and with increasing levels of confidence.
Question 145 |
Which of the following tools is not required during system analysis phase of system development Life cycle ?
CASE Tool | |
RAD Tool | |
Reverse engineering tool | |
None of these |
Question 145 Explanation:
→ Reverse engineering tools are using debuggers. The debuggers are either user mode or Kernel mode.
→ Computer aided software engineering (CASE) is the domain of software tools used to design and implement applications. CASE tools are similar to and were partly inspired by computer aided design (CAD) tools used for designing hardware products. CASE tools are used for developing high-quality, defect-free, and maintainable software.
→ Rapid Application Development refers to a software development approach which puts less emphasis on planning and even design specifications, and more on rapid development and quick feedback. Prototypes are rapidly delivered to users to ensure they’re directly involved in feedback and development. There are also tools for collecting data, designing personal workflows, and setting up unique rules for each new application.
→ Computer aided software engineering (CASE) is the domain of software tools used to design and implement applications. CASE tools are similar to and were partly inspired by computer aided design (CAD) tools used for designing hardware products. CASE tools are used for developing high-quality, defect-free, and maintainable software.
→ Rapid Application Development refers to a software development approach which puts less emphasis on planning and even design specifications, and more on rapid development and quick feedback. Prototypes are rapidly delivered to users to ensure they’re directly involved in feedback and development. There are also tools for collecting data, designing personal workflows, and setting up unique rules for each new application.
Question 146 |
A black hole in a DFD is a :
A data store with no inbound flows | |
A data store with only in bound flows | |
A data store with more than one in bound flow | |
None of these. |
Question 146 Explanation:
Black Hole: A processing step may have input flows but no output flows.
Miracle: A processing step may have output flows but now input flows.
Grey Hole: A processing step may have outputs that are greater than the sum of its inputs - e.g., its inputs could not produce the output shown.
Miracle: A processing step may have output flows but now input flows.
Grey Hole: A processing step may have outputs that are greater than the sum of its inputs - e.g., its inputs could not produce the output shown.
Question 147 |
Which one of the following is not a software process model ?
Linear sequential model | |
Prototyping model | |
The spiral model | |
COCOMO model |
Question 147 Explanation:
The Constructive Cost Model (COCOMO) is a procedural software cost estimation model but not software process model. Linear sequential,prototype and spiral models are software process
models.
Question 148 |
System Development Life-cycle has following stages :
(I) Requirement analysis
(II) Coding
(III) Design
(IV) Testing
Which option describes the correct sequence of stages ?
(I) Requirement analysis
(II) Coding
(III) Design
(IV) Testing
Which option describes the correct sequence of stages ?
III, I, IV, II | |
II, III, I, IV | |
I, III, IV, II | |
None of the above |
Question 148 Explanation:
Question 149 |
Which one is measure of software complexity ?
Number of lines of code (LOC) | |
Number of man years | |
Number of function points (FP) | |
All of the above | |
Both LOC and FP |
Question 149 Explanation:
→ A function point is a "unit of measurement" to express the amount of business functionality an information system (as a product) provides to a user. Function points are used to compute a
functional size measurement (FSM) of software.
→ Lines of code (LOC) is a software metric used to measure the size of a computer program by counting the number of lines in the text of the program's source code.
→ Lines of code (LOC) is a software metric used to measure the size of a computer program by counting the number of lines in the text of the program's source code.
Question 150 |
Which type of coupling is least preferred ?
Content coupling | |
Data coupling | |
Control coupling | |
Common coupling |
Question 150 Explanation:
Data coupling is the weakest coupling and it is most desirable coupling in a software, as a low degree of coupling is good for a software.
Coupling in the order from highest(least desirable) to the least (most desirable)
I. Content coupling
II. Common coupling
III. Control coupling
IV. Stamp coupling
V. Data coupling
Coupling in the order from highest(least desirable) to the least (most desirable)
I. Content coupling
II. Common coupling
III. Control coupling
IV. Stamp coupling
V. Data coupling
Question 151 |
Which of the following tools is not required during system analysis phase of system development life cycle ?
Case tool | |
RAD tool | |
Reverse engineering | |
None of these |
Question 151 Explanation:
→ Reverse engineering tools are using debuggers. The debuggers are either user mode or Kernel mode.
→ Computer aided software engineering (CASE) is the domain of software tools used to design and implement applications. CASE tools are similar to and were partly inspired by computer aided design (CAD) tools used for designing hardware products. CASE tools are used for developing high-quality, defect-free, and maintainable software.
→ Rapid Application Development refers to a software development approach which puts less emphasis on planning and even design specifications, and more on rapid development and quick feedback. Prototypes are rapidly delivered to users to ensure they’re directly involved in feedback and development. There are also tools for collecting data, designing personal workflows, and setting up unique rules for each new application.
→ Computer aided software engineering (CASE) is the domain of software tools used to design and implement applications. CASE tools are similar to and were partly inspired by computer aided design (CAD) tools used for designing hardware products. CASE tools are used for developing high-quality, defect-free, and maintainable software.
→ Rapid Application Development refers to a software development approach which puts less emphasis on planning and even design specifications, and more on rapid development and quick feedback. Prototypes are rapidly delivered to users to ensure they’re directly involved in feedback and development. There are also tools for collecting data, designing personal workflows, and setting up unique rules for each new application.
Question 152 |
Software Cost Performance index (CPI) is given by :
[Where : BCWP stands for Budgeted Cost of Work Performed.
BCWS stands for Budget Cost of Work Scheduled
ACWP stands for Actual Cost of Work Performed
[Where : BCWP stands for Budgeted Cost of Work Performed.
BCWS stands for Budget Cost of Work Scheduled
ACWP stands for Actual Cost of Work Performed
BCW P/ ACW P | |
No option given | |
BCWP−ACWP | |
BCWP−BCWS |
Question 152 Explanation:
The Cost Performance Index can be determined by dividing the earned value by actual cost.
Cost Performance Index = BCWP stands for Budgeted Cost of Work Performed / ACWP stands for Actual Cost of Work Performed
CPI = BCWP/ACWP
Cost Performance Index = BCWP stands for Budgeted Cost of Work Performed / ACWP stands for Actual Cost of Work Performed
CPI = BCWP/ACWP
Question 153 |
Software Risk estimation involves following two tasks :
risk magnitude and risk impact | |
risk probability and risk impact | |
risk maintenance and risk impact | |
risk development and risk impact |
Question 153 Explanation:
Software Risk estimation involves risk probability and risk impact.
Question 154 |
Reliability of software is directly dependent on :
quality of the design | |
number of errors present | |
software engineer’s experience | |
user requirement |
Question 154 Explanation:
→ Reliability of software is dependent on number of errors present in software.
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
Question 155 |
‘Abstraction’ is ____________ step of Attribute in a software design.
First | |
Final | |
Last | |
Middle |
Question 155 Explanation:
‘Abstraction’ is first step of Attribute in a software design. The process of removing physical, spatial, or temporal details or attributes in the study of objects or systems in order to more
closely attend to other details of interest.
Question 156 |
In software project planning, work Breakdown structure must be __________ .
A graph | |
A tree | |
A Eulars graph | |
None of the above |
Question 156 Explanation:
Work Breakdown structure(WBS) must be tree. The tree structure will give overall view of a project. Normally we can divide two types of WBS
1. Functional WBS
2. Activity WBS
WBS tree structure:
1. Functional WBS
2. Activity WBS
WBS tree structure:
Question 157 |
In Software Metrics, McCABE S cyclomatic number is given by following formula :
c=e-n+2p | |
c=e-n-2p | |
c=e+n+2p | |
c=e-n* 2p |
Question 157 Explanation:
Cyclomatic complexity uses 3 formulas
1. Number of regions + 1
2. Predicate + 1
3. Edges-Vertices+2
As per the above question, c=cyclomatic complexity
e=number of edges
n=number of vertices
p=predicates
1. Number of regions + 1
2. Predicate + 1
3. Edges-Vertices+2
As per the above question, c=cyclomatic complexity
e=number of edges
n=number of vertices
p=predicates
Question 158 |
In a good software design, __________ coupling is desirable between modules.
Highest | |
Lowest | |
Internal | |
External |
Question 158 Explanation:
→ Cohesion is a measure of internal strength within a module, whereas coupling is a measure of inter dependency among the modules.
→ So in the context of modular software design there should be high cohesion and low coupling.
→ So in the context of modular software design there should be high cohesion and low coupling.
Question 159 |
System study yields the following :
Requirement specifications | |
Prevailing process description | |
Data source identification | |
All the above |
Question 159 Explanation:
System study yields the following requirement specifications. A Software requirements specification document describes the intended purpose, requirements and nature of a software to be developed. It also includes the yield and cost of the software.
Question 160 |
The COCOMO model is used for __________ .
software design | |
software cost estimation | |
software cost approximation | |
software analysis |
Question 160 Explanation:
The COCOMO model is used for software cost estimation.
The basic COCOMO equations take the form
1. Effort Applied (E) = a(KLOC) b
2. Development Time (D) = c(Effort Applied) d
3. People required (P) = Effort Applied / Development Time [count]
where, KLOC is the estimated number of delivered lines (expressed in thousands ) of code for project. The constants a, b, c and d are given in the following table (note: the values listed below are from the original analysis, with a modern reanalysis producing different values).
The basic COCOMO equations take the form
1. Effort Applied (E) = a(KLOC) b
2. Development Time (D) = c(Effort Applied) d
3. People required (P) = Effort Applied / Development Time [count]
where, KLOC is the estimated number of delivered lines (expressed in thousands ) of code for project. The constants a, b, c and d are given in the following table (note: the values listed below are from the original analysis, with a modern reanalysis producing different values).
Question 161 |
__________ are applied throughout the software process.
Framework activities | |
Umbrella activities | |
Planning activities | |
Construction activities |
Question 161 Explanation:
→ The umbrella activities occur throughout the software process they are applied evenly across the process, the analysis encompasses a set of work tasks (eg. requirement gathering,
elaboration, negotiation specification and validation).
→ These activities include Software project tracking and control, Risk management, Software quality assurance, and formal technical reviews, measurement, Software configuration management, reusability management and work product preparation and production.
→ These activities include Software project tracking and control, Risk management, Software quality assurance, and formal technical reviews, measurement, Software configuration management, reusability management and work product preparation and production.
Question 162 |
Requirement Development, Organizational Process Focus, Organizational Training, Risk Management and Integrated Supplier Management are process areas required to achieve maturity level
Performed | |
Managed | |
Defined | |
Optimized |
Question 162 Explanation:
Managed maturity level focuses on software metrics. Two metrics are
1. Product Metric: It measures the characteristics of product being developed. Product metrics are size, reliability, understandability etc..,
2. Process Metrics: It reflect the effectiveness of process. Process metrics are average defect correction on time, number of failures detected during testing per LOC etc.,
This level focuses on improving product and process quality. The Key process areas are quantitative process metric and software quality management.
1. Product Metric: It measures the characteristics of product being developed. Product metrics are size, reliability, understandability etc..,
2. Process Metrics: It reflect the effectiveness of process. Process metrics are average defect correction on time, number of failures detected during testing per LOC etc.,
This level focuses on improving product and process quality. The Key process areas are quantitative process metric and software quality management.
Question 163 |
The software _________ of a program or a computing system is the structure or structures of the system, which comprise software components, the externally visible properties of those components, and the relationships among them.
Design | |
Architecture | |
Process | |
Requirement |
Question 163 Explanation:
The software Architecture of a program or a computing system is the structure or structures of the system, which comprise software components, the externally visible properties of those components, and the relationships among them.
Question 164 |
Which one of the following set of attributes should not be encompassed by effective software metrics ?
Simple and computable | |
Consistent and objective | |
Consistent in the use of units and dimensions | |
Programming language dependent |
Question 164 Explanation:
Programming language dependent attributes should not be encompassed by effective software metrics.
Question 165 |
Which one of the following is used to compute cyclomatic complexity ?
The number of regions – 1 | |
E – N + 1, where E is the number of flow graph edges and N is the number of flow graph nodes. | |
P – 1, where P is the number of predicate nodes in the flow graph G. | |
P + 1, where P is the number of predicate nodes in the flow graph G. |
Question 165 Explanation:
Cyclomatic complexity uses 3 formulas
1. Number of regions + 1
2. Predicate + 1
3. Edges-Vertices+2
1. Number of regions + 1
2. Predicate + 1
3. Edges-Vertices+2
Question 166 |
Which one of the following is not a risk management technique for managing the risk due to unrealistic schedules and budgets ?
Detailed multi source cost and schedule estimation. | |
Design cost | |
Incremental development | |
Information hiding |
Question 166 Explanation:
Information hiding is not a risk management technique for managing the risk due to unrealistic schedules and budgets.
Question 167 |
_______ of a system is the structure or structures of the system which comprise software elements, the externally visible properties of these elements and the relationship amongst them.
Software construction | |
Software evolution | |
Software architecture | |
Software reuse |
Question 167 Explanation:
Software architecture of a system is the structure or structures of the system which comprise software elements, the externally visible properties of these elements and the relationship amongst them.
Question 168 |
Regression testing is primarily related to
Functional testing | |
Development testing | |
Data flow testing | |
Maintenance testing |
Question 168 Explanation:
→ Regression testing is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. If not, that would be called a regression.
→ Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components.
→ As regression test suites tend to grow with each found defect, test automation is frequently involved.
→ Regression testing is primarily related to Maintenance testing.
→ Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components.
→ As regression test suites tend to grow with each found defect, test automation is frequently involved.
→ Regression testing is primarily related to Maintenance testing.
Question 169 |
Object Request Broker (ORB) is
I. A software program that runs on the client as well as on the application server.
II. A software program that runs on the client side only.
III. A software program that runs on the application server, where most of the components reside.I, II & III
I. A software program that runs on the client as well as on the application server.
II. A software program that runs on the client side only.
III. A software program that runs on the application server, where most of the components reside.I, II & III
I, II & III | |
I & II | |
II & III | |
I only |
Question 169 Explanation:
Object Request Broker (ORB) is a middleware which allows program calls to be made from one computer to another via a computer network, providing location transparency through remote procedure calls. ORBs promote interoperability of distributed object systems, enabling such systems to be built by piecing together objects from different vendors, while different parts communicate with each other via the ORB.
→ A software program that runs on the client as well as on the application server used in distributed systems.
→ A software program that runs on the client as well as on the application server used in distributed systems.
Question 170 |
A software agent is defined as
I. A software developed for accomplishing a given task.
II. A computer program which is capable of acting on behalf of the user in order to accomplish a given computational task.
III. An open source software for accomplishing a given task.
I. A software developed for accomplishing a given task.
II. A computer program which is capable of acting on behalf of the user in order to accomplish a given computational task.
III. An open source software for accomplishing a given task.
I | |
II | |
III | |
All of the above |
Question 170 Explanation:
→ A software agent is a computer program that acts for a user or other program in a relationship of agency, which derives from the Latin agere (to do): an agreement to act on one's behalf. Such "action on behalf of" implies the authority to decide which, if any, action is appropriate. Agents are colloquially known as bots, from robot.
→ Software agents interacting with people (e.g. chatbots, human-robot interaction environments) may possess human-like qualities such as natural language understanding and speech, personality or embody humanoid form.
→ Software agents interacting with people (e.g. chatbots, human-robot interaction environments) may possess human-like qualities such as natural language understanding and speech, personality or embody humanoid form.
Question 171 |
The ______ of a program or computing system is the structure or structures of the system, which comprise software components, the externally visible properties of these components, and the relationship among them.
E-R diagram | |
Data flow diagram | |
Software architecture
| |
Software design |
Question 171 Explanation:
The software architecture of a program or computing system is the structure or structures of the system, which comprise software components, the externally visible properties of these components, and the relationship among them.
Question 172 |
Working software is not available until late in the process in
Waterfall model | |
Prototyping model | |
Incremental model | |
Evolutionary Development model |
Question 172 Explanation:
Waterfall Model: We can not go back in previous project phase as soon as as we proceed to next phase ,So inflexible
Advantages:
→Waterfall model is simple and easy to understand.
→It works as reference model for others.
Disadvantage:
→Real projects cannot be sequential
→Initially all requirements should known i.e requirements are frozen. It may be suited for static projects.
→Error omission too costly
→Maintenance is too costly(We have to redesign the whole project from scratch)
→Customer must have patience
→It is based on Big-Bang approach
Advantages:
→Waterfall model is simple and easy to understand.
→It works as reference model for others.
Disadvantage:
→Real projects cannot be sequential
→Initially all requirements should known i.e requirements are frozen. It may be suited for static projects.
→Error omission too costly
→Maintenance is too costly(We have to redesign the whole project from scratch)
→Customer must have patience
→It is based on Big-Bang approach
Question 173 |
Equivalence partitioning is a ______ testing method that divides the input domain of a program into classes of data from which test cases can be derived.
White box | |
Black box | |
Regression | |
Smoke |
Question 173 Explanation:
Equivalence partitioning is a black box testing method that divides the input domain of a program into classes of data from which test cases can be derived.
Black box testing methods are
→Graph-Based Testing Methods
→Equivalence Partitioning
→Boundary Value Analysis
→Orthogonal Array Testing
Black box testing methods are
→Graph-Based Testing Methods
→Equivalence Partitioning
→Boundary Value Analysis
→Orthogonal Array Testing
Question 174 |
Consider the following characteristics :
(i) Correct and unambiguous
(ii) Complete and consistent
(iii) Ranked for importance and/or stability and verifiable
(iv) Modifiable and Traceable
Which of the following is true for a good SRS ?
(i) Correct and unambiguous
(ii) Complete and consistent
(iii) Ranked for importance and/or stability and verifiable
(iv) Modifiable and Traceable
Which of the following is true for a good SRS ?
(i), (ii) and (iii) | |
(i), (iii) and (iv) | |
(ii), (iii) and (iv) | |
(i), (ii), (iii) and (iv) |
Question 174 Explanation:
A good software requirement specification(SRS) characteristics are
→Correct and unambiguous
→Complete and consistent
→Ranked for importance and/or stability and verifiable
→Modifiable and Traceable
→Correct and unambiguous
→Complete and consistent
→Ranked for importance and/or stability and verifiable
→Modifiable and Traceable
Question 175 |
Basis path testing falls under
system testing | |
white box testing | |
white box testing | |
unit testing |
Question 175 Explanation:
White-box test design techniques include the following code coverage criteria:
→Control flow testing
→Data flow testing
→Branch testing
→Statement coverage
→Decision coverage
→Modified condition/decision coverage
→Prime path testing
→Path testing
→Data flow testing
→Branch testing
→Statement coverage
→Decision coverage
→Modified condition/decision coverage
→Prime path testing
→Path testing
Question 176 |
______ is an “umbrella” activity that is applied throughout the software engineering process.
Debugging | |
Testing | |
Designing | |
Software quality assurance |
Question 176 Explanation:
Umbrella Activities
1. Software project tracking and control
2. Risk Management
3. Software Quality Assurance
4. Technical review
5. Software Configuration management
6. Reusability management
7. Work Product preparation and production
Question 177 |
Assume the following regarding the development of a software system P:
- Estimated lines of code of P : 33, 480 LOC
- Average productivity for P : 620 LOC per person-month
- Number of software developers : 6
- Average salary of a software developer : 50,000 per month
If E, D and C are the estimated development effort (in person-months), estimated development time (in months), and estimated development cost (in Lac) respectively, then (E, D, C) =
- Estimated lines of code of P : 33, 480 LOC
- Average productivity for P : 620 LOC per person-month
- Number of software developers : 6
- Average salary of a software developer : 50,000 per month
If E, D and C are the estimated development effort (in person-months), estimated development time (in months), and estimated development cost (in Lac) respectively, then (E, D, C) =
(48, 8, 24) | |
(54, 9, 27) | |
(60, 10, 30) | |
(42, 7, 21) |
Question 177 Explanation:
- Estimated lines of code of P : 33480 LOC
- Average productivity for P : 620 LOC per person-month
- Number of software developers : 6
- Average salary of a software developer : 50000 per month
Step-1: Estimated development effort (in person-months)= 33480 /620
E=54
Step-2: Estimated development time (in months) =54/6
D= 9 months
Step-3: Estimated development cost (in Lac) = 50000*6*9
=27 lacs
- Average productivity for P : 620 LOC per person-month
- Number of software developers : 6
- Average salary of a software developer : 50000 per month
Step-1: Estimated development effort (in person-months)= 33480 /620
E=54
Step-2: Estimated development time (in months) =54/6
D= 9 months
Step-3: Estimated development cost (in Lac) = 50000*6*9
=27 lacs
Question 178 |
Match the following in Software Engineering :
(a)-(ii), (b)-(iii), (c)-(iv), (d)-(i) | |
(a)-(iii), (b)- (i), (c)-(iv), (d)-(ii) | |
(a)-(iv), (b)- (i), (c)-(ii), (d)-(iii) | |
(a)-(iii), (b)- (iv), (c)-(i), (d)-(ii) |
Question 178 Explanation:
→ Coupling and Cohesion are used in software design. Cohesion measures strength of a module while coupling measures interdependency between modules.
→ Software cost estimation must be done more diligently throughout the project life cycle so that in the future there are fewer surprises and unforeseen delays in the release of a product.
→ Validation Technique→ Symbolic Execution
→ Software Requirements Definition→ Structured System Analysis
→ Software cost estimation must be done more diligently throughout the project life cycle so that in the future there are fewer surprises and unforeseen delays in the release of a product.
→ Validation Technique→ Symbolic Execution
→ Software Requirements Definition→ Structured System Analysis
Question 179 |
Which one of the following is not typically provided by Source Code Management Software ?
Synchronisation | |
Versioning and Revision history | |
Syntax highlighting | |
Project forking |
Question 179 Explanation:
Source Code Management Software is the management of changes to documents, computer programs, large web sites, and other collections of information. Changes are usually identified
by a number or letter code, termed the "revision number", "revision level", or simply "revision".
→ Source Code Management Software includes
1. Synchronisation
2. Versioning and Revision history
3. Project forking
→ Source Code Management Software includes
1. Synchronisation
2. Versioning and Revision history
3. Project forking
Question 180 |
A software system crashed 20 times in the year 2017 and for each crash, it took 2 minutes to restart. Approximately, what was the software availability in that year ?
96.9924% | |
97.9924% | |
98.9924% | |
99.9924% |
Question 180 Explanation:
Software availability: It is a software used to ensure that systems are running and available most of the time. High availability is a high percentage of time that the system is functioning. It can be formally defined as (1 – (down time/ total time))*100%. Although the minimum required availability varies by task, systems typically attempt to achieve 99.999% (5-nines) availability. This characteristic is weaker than fault tolerance, which typically seeks to provide 100% availability, albeit with significant price and performance penalties.
Given data,
-Software crashed 20 times in the year 2017
-each crash=2 minutes to restart.
-Software availability=?
1 year=365 days = 365*1440 minutes =525600 minutes.
→ Crash time =20*2
=40 minutes
→ Software availability = (525600-40) / 525600
= 0.999924
= (0.999924 * 100)
= 99.9924 %
Given data,
-Software crashed 20 times in the year 2017
-each crash=2 minutes to restart.
-Software availability=?
1 year=365 days = 365*1440 minutes =525600 minutes.
→ Crash time =20*2
=40 minutes
→ Software availability = (525600-40) / 525600
= 0.999924
= (0.999924 * 100)
= 99.9924 %
Question 181 |
Coupling is a measure of the strength of the interconnections between software modules. Which of the following are correct statements with respect to module coupling ?
P : Common coupling occurs when one module controls the flow of another module by passing it information on what to do.
Q : In data coupling, the complete data structure is passed from one module to another through parameters.
R : Stamp coupling occurs when modules share a composite data structure and use only parts of it.
P : Common coupling occurs when one module controls the flow of another module by passing it information on what to do.
Q : In data coupling, the complete data structure is passed from one module to another through parameters.
R : Stamp coupling occurs when modules share a composite data structure and use only parts of it.
P and Q only | |
P and R only | |
Q and R only | |
All of P, Q and R |
Question 181 Explanation:
Common Coupling: Common coupling occurs if two modules share same global data.
Data Coupling : Data coupling occurs when two modules communicate using elementary data items that are passed as parameters between two modules.
Stamp Coupling : Stamp coupling occurs if two modules communicate using composite items such as records in Pascal or structure in C
Data Coupling : Data coupling occurs when two modules communicate using elementary data items that are passed as parameters between two modules.
Stamp Coupling : Stamp coupling occurs if two modules communicate using composite items such as records in Pascal or structure in C
Question 182 |
A software design pattern often used to restrict access to an object is :
adapter | |
decorator | |
delegation | |
proxy |
Question 182 Explanation:
Proxy pattern: a class functioning as an interface to another thing. In the proxy, extra functionality can be provided, for example caching when operations on the real object are resource intensive, or checking preconditions before operations on the real object are invoked.
→ For the client, usage of a proxy object is similar to using the real object, because both implement the same interface.
→ Proxy pattern solve the access to an object should be controlled and functionality should be provided when accessing an object.
→ When accessing sensitive objects, for example, it should be possible to check that clients have the needed access rights.
→ For the client, usage of a proxy object is similar to using the real object, because both implement the same interface.
→ Proxy pattern solve the access to an object should be controlled and functionality should be provided when accessing an object.
→ When accessing sensitive objects, for example, it should be possible to check that clients have the needed access rights.
Question 183 |
Reasons to re-engineer a software include :
P : Allow legacy software to quickly adapt to the changing requirements
Q : Upgrade to newer technologies/platforms/paradigm (for example, object-oriented)
R : Improve software maintainability
S : Allow change in the functionality and architecture of the software
P : Allow legacy software to quickly adapt to the changing requirements
Q : Upgrade to newer technologies/platforms/paradigm (for example, object-oriented)
R : Improve software maintainability
S : Allow change in the functionality and architecture of the software
P, R and S only | |
P and R only | |
P, Q and S only | |
P, Q and R only |
Question 183 Explanation:
→ Software re-engineering is the examination and alteration of a system to reconstitute it in a new form. It is done to improve the maintainability of the software.
→ Software reengineering encompasses inventory analysis, document restructuring, reverse engineering, program and data restructuring, and forward engineering. The intent of these activities is to create versions of existing programs that exhibit higher quality and better Maintainability.
A software reengineering process model:
→ Software reengineering encompasses inventory analysis, document restructuring, reverse engineering, program and data restructuring, and forward engineering. The intent of these activities is to create versions of existing programs that exhibit higher quality and better Maintainability.
A software reengineering process model:
Question 184 |
Which of the following is not a key strategy followed by the clean room approach to software development ?
Formal specification | |
Dynamic verification | |
Incremental development | |
Statistical testing of the system |
Question 184 Explanation:
The basic principles of the clean room process are
1. Software development based on formal methods: Software tool support based on some mathematical formalism includes model checking, process algebras, and Petri nets. The Box Structure Method might be one such means of specifying and designing a software product. Verification that the design correctly implements the specification is performed through team review, often with software tool support.
2. Incremental implementation under statistical quality control Cleanroom development uses an iterative approach, in which the product is developed in increments that gradually increase the implemented functionality. The quality of each increment is measured against pre-established standards to verify that the development process is proceeding acceptably. A failure to meet quality standards results in the cessation of testing for the current increment, and a return to the design phase.
3. Statistically sound testing
Software testing in the cleanroom process is carried out as a statistical experiment. Based on the formal specification, a representative subset of software input/output trajectories is selected and tested. This sample is then statistically analyzed to produce an estimate of the reliability of the software, and a level of confidence in that estimate.
1. Software development based on formal methods: Software tool support based on some mathematical formalism includes model checking, process algebras, and Petri nets. The Box Structure Method might be one such means of specifying and designing a software product. Verification that the design correctly implements the specification is performed through team review, often with software tool support.
2. Incremental implementation under statistical quality control Cleanroom development uses an iterative approach, in which the product is developed in increments that gradually increase the implemented functionality. The quality of each increment is measured against pre-established standards to verify that the development process is proceeding acceptably. A failure to meet quality standards results in the cessation of testing for the current increment, and a return to the design phase.
3. Statistically sound testing
Software testing in the cleanroom process is carried out as a statistical experiment. Based on the formal specification, a representative subset of software input/output trajectories is selected and tested. This sample is then statistically analyzed to produce an estimate of the reliability of the software, and a level of confidence in that estimate.
Question 185 |
Which of the following statements is/are True ?
P : Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves the internal architecture.
Q : An example of refactoring is adding new features to satisfy a customer requirement discovered after a project is shipped.
P : Refactoring is the process of changing a software system in such a way that it does not alter the external behavior of the code yet improves the internal architecture.
Q : An example of refactoring is adding new features to satisfy a customer requirement discovered after a project is shipped.
P only | |
Q only | |
Both P and Q | |
Neither P nor Q |
Question 185 Explanation:
→ Refactoring allows a software engineer to improve the internal structure of a design (or source code) without changing its external functionality or behavior of the code yet improves the
internal structure. In essence, refactoring can be used to improve the efficiency, readability, or performance of a design or the code that implements a design.
→ It is a disciplined way to clean up code [and modify/simplify the internal design] that minimizes the chances of introducing bugs. In essence, when you refactor you are improving the design of the code after it has been written.
Note: It won’t add any new featuring to satisfy a customer requirement. So, statement Q is false.
→ It is a disciplined way to clean up code [and modify/simplify the internal design] that minimizes the chances of introducing bugs. In essence, when you refactor you are improving the design of the code after it has been written.
Note: It won’t add any new featuring to satisfy a customer requirement. So, statement Q is false.
Question 186 |
The relationship of data elements in a module is called
Coupling | |
Modularity | |
Cohesion | |
Granularity |
Question 186 Explanation:
→ Cohesion is a measure of internal strength within a module and relationship of data elements in a module, whereas coupling is a measure of inter dependency among the modules.
→ In the context of modular software design there should be high cohesion and low coupling.
→ In the context of modular software design there should be high cohesion and low coupling.
Question 187 |
Software Configuration Management is the discipline for systematically controlling
the changes due to the evolution of work products as the project proceeds. | |
the changes due to defects (bugs) being found and then fixed. | |
the changes due to requirement changes | |
all of the above |
Question 187 Explanation:
Software Configuration Management is the discipline for systematically controlling
1. The changes due to the evolution of work products as the project proceeds.
2. The changes due to defects(bugs) being found and then fixed.
3. The changes due to requirement changes
1. The changes due to the evolution of work products as the project proceeds.
2. The changes due to defects(bugs) being found and then fixed.
3. The changes due to requirement changes
Question 188 |
Which one of the following is not a step of requirement engineering ?
Requirement elicitation | |
Requirement analysis | |
Requirement design | |
Requirement documentation |
Question 188 Explanation:
Requirements engineering (RE) refers to the process of defining, documenting and maintaining requirements in the engineering design process.
Requirement Analysis Steps:
1. Requirements inception or requirements elicitation: Developers and stakeholders meet, the latter are inquired concerning their needs and wants regarding the software product.
2. Requirements analysis and negotiation: Requirements are identified (including new ones if the development is iterative) and conflicts with stakeholders are solved. Both written and graphical tools (the latter commonly used in the design phase but some find them helpful at this stage, too) are successfully used as aids.
3. System modeling: Some engineering fields (or specific situations) require the product to be completely designed and modeled before its construction or fabrication starts and, therefore, the design phase must be performed in advance.
4. Requirements specification: Requirements are documented in a formal artifact called a Requirements Specification (RS), which will become official only after validation.
5. Requirements validation: Checking that the documented requirements and models are consistent and meet the needs of the stakeholder. Only if the final draft passes the validation process, the RS becomes official.
6. Requirements management: Managing all the activities related to the requirements since inception, supervising as the system is developed and, even until after it is put into use (e. g., changes, extensions, etc.)
Requirement Analysis Steps:
1. Requirements inception or requirements elicitation: Developers and stakeholders meet, the latter are inquired concerning their needs and wants regarding the software product.
2. Requirements analysis and negotiation: Requirements are identified (including new ones if the development is iterative) and conflicts with stakeholders are solved. Both written and graphical tools (the latter commonly used in the design phase but some find them helpful at this stage, too) are successfully used as aids.
3. System modeling: Some engineering fields (or specific situations) require the product to be completely designed and modeled before its construction or fabrication starts and, therefore, the design phase must be performed in advance.
4. Requirements specification: Requirements are documented in a formal artifact called a Requirements Specification (RS), which will become official only after validation.
5. Requirements validation: Checking that the documented requirements and models are consistent and meet the needs of the stakeholder. Only if the final draft passes the validation process, the RS becomes official.
6. Requirements management: Managing all the activities related to the requirements since inception, supervising as the system is developed and, even until after it is put into use (e. g., changes, extensions, etc.)
Question 189 |
Testing of software with actual data and in actual environment is called
Alpha testing | |
Beta testing | |
Regression testing | |
None of the above |
Question 189 Explanation:
→ Alpha test: is conducted at the developer’s site by end-users and conducted in a controlled environment
→ Beta test: is conducted at end-user sites and it is a “live” application of the software in an environment that cannot be controlled by the developer
→ Regression test: Testing is an important strategy for reducing “side effects” when major change is made to the software
→ Beta test: is conducted at end-user sites and it is a “live” application of the software in an environment that cannot be controlled by the developer
→ Regression test: Testing is an important strategy for reducing “side effects” when major change is made to the software
Question 190 |
Electronic Data Interchange Software consists of the following four layers :
Business application, Internal format conversion, Network translator, EDI envelope | |
Business application, Internal format conversion, EDI translator, EDI envelope | |
Application layer, Transport layer, EDI translator, EDI envelope | |
Application layer, Transport layer, IP layer, EDI envelope |
Question 190 Explanation:
Electronic Data Interchange(EDI) software consists of the following 4 layers
1. Business application
2. Internal format conversion
3. EDI translator
4. EDI envelope
1. Business application
2. Internal format conversion
3. EDI translator
4. EDI envelope
Question 191 |
Main aim of software engineering is to produce
program | |
software | |
within budget | |
software within budget in the given schedule |
Question 191 Explanation:
Main aim of software engineering is to produce software within budget in the given schedule.
Question 192 |
Key process areas of CMM level 4 are also classified by a process which is
CMM level 2 | |
CMM level 3 | |
CMM level 5 | |
All of the above
|
Question 192 Explanation:
CMM stands for Capability Maturity Model is a process model which specifies the process improvement approach in software development.
CMM levels:
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimizing
Level-4 (Managed): the process is quantitatively managed in accordance with agreed-upon metrics. It also classified by a process which is in level-5.
Level-5(Optimizing): Process management includes deliberate process optimization (or) improvement.
CMM levels:
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimizing
Level-4 (Managed): the process is quantitatively managed in accordance with agreed-upon metrics. It also classified by a process which is in level-5.
Level-5(Optimizing): Process management includes deliberate process optimization (or) improvement.
Question 193 |
Validation means
are we building the product right | |
are we building the right product | |
verification of fields | |
None of the above |
Question 193 Explanation:
Verification and validation are not the same things, although they are often confused. Boehm succinctly expressed the difference as
→ Verification: Are we building the product right?
→ Validation: Are we building the right product?
→ Verification: Are we building the product right?
→ Validation: Are we building the right product?
Question 194 |
In a function oriented design, we
minimize cohesion and maximize coupling | |
maximize cohesion and minimize coupling | |
maximize cohesion and maximize coupling | |
minimize cohesion and minimize coupling |
Question 194 Explanation:
→ Cohesion is a measure of internal strength within a module, whereas coupling is a measure of inter dependency among the modules.
→ In a functional oriented design/modular software design there should be high cohesion and low coupling.
→ It requires High Fan-In and Low fan-out.
→ In a functional oriented design/modular software design there should be high cohesion and low coupling.
→ It requires High Fan-In and Low fan-out.
Question 195 |
Reliability of software is directly dependent on
quality of the design | |
number of errors present | |
software engineers experience | |
user requirement |
Question 195 Explanation:
→ Reliability of software is directly dependent on number of errors present.
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
→ The program does not fail for a specified time in a given environment
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
→ The program does not fail for a specified time in a given environment
Question 196 |
For a data entry project for office staff who have never used computers before (user interface and user friendliness are extremely important), one will use
Spiral model | |
Component based model | |
Prototyping | |
Waterfall model |
Question 197 |
An SRS
establishes the basis for agreement between client and the supplier. | |
provides a reference for validation of the final product. | |
is a prerequisite to high quality software. | |
all of the above. |
Question 197 Explanation:
→ Software Requirement Specification(SRS) establishes the basis for agreement between client and the supplier. It provides a reference for validation of the final product. SRS is a prerequisite to high quality software.
→ 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.
→ The Software Requirement Specification(SRS) is said to be Consistent if and only if no subset of individual requirements described in it conflict with each other.
→ 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.
→ The Software Requirement Specification(SRS) is said to be Consistent if and only if no subset of individual requirements described in it conflict with each other.
Question 198 |
McCabe’s cyclomatic metric V(G) of a graph G with n vertices, e edges and p connected component ise
e | |
n | |
e – n + p | |
e – n + 2p |
Question 198 Explanation:
Cyclomatic complexity uses 3 formulas
1. Number of regions + 1
2. Predicate + 1
3.Edges-Vertices+2(Connected components)
As per the above question, c=cyclomatic complexity
e=number of edges
n=number of vertices
p=predicates
1. Number of regions + 1
2. Predicate + 1
3.Edges-Vertices+2(Connected components)
As per the above question, c=cyclomatic complexity
e=number of edges
n=number of vertices
p=predicates
Question 199 |
Emergency fixes known as patches are result of
adaptive maintenance | |
perfective maintenance | |
corrective maintenance | |
none of the above |
Question 199 Explanation:
Software maintenance is the modification of a software product after delivery to correct faults, to improve performance or other attributes.
Software maintenance types: 1. Adaptive: modifying the system to cope with changes in the software environment (DBMS, OS)
2. Perfective: Implementing new or changed user requirements which concern functional enhancements to the software.
3. Corrective: Diagnosing and fixing errors, possibly ones found by users.
4. Preventive: Increasing software maintainability or reliability to prevent problems in the future.
Software maintenance types: 1. Adaptive: modifying the system to cope with changes in the software environment (DBMS, OS)
2. Perfective: Implementing new or changed user requirements which concern functional enhancements to the software.
3. Corrective: Diagnosing and fixing errors, possibly ones found by users.
4. Preventive: Increasing software maintainability or reliability to prevent problems in the future.
Question 200 |
Design recovery from source code is done during
reverse engineering | |
re-engineering | |
reuse | |
all of the above |
Question 200 Explanation:
Design recovery from source code is done during reverse engineering, re-engineering and reusability.
Question 201 |
Following is used to demonstrate that the new release of software still performs the old one did by rerunning the old tests :
Functional testing | |
Path testing | |
Stress testing | |
Regression testing |
Question 201 Explanation:
→ Regression testing is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. If not, that would be called a regression.
→ Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components.
→ As regression test suites tend to grow with each found defect, test automation is frequently involved.
→ Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components.
→ As regression test suites tend to grow with each found defect, test automation is frequently involved.
Question 202 |
Software risk estimation involves following two tasks :
Risk magnitude and risk impact | |
Risk probability and risk impact | |
Risk maintenance and risk impact | |
Risk development and risk impact |
Question 202 Explanation:
Software Risk estimation involves risk probability and risk impact.
→ Risk impact factors are
1. Negligible [low]
2. Marginal
3. Critical
4. Catastrophic [High]
→ Risk exposure:
RE=P*C
P=The probability of occurrence for a risk
C=The cost to the project should the risk actually occur
→ Risk impact factors are
1. Negligible [low]
2. Marginal
3. Critical
4. Catastrophic [High]
→ Risk exposure:
RE=P*C
P=The probability of occurrence for a risk
C=The cost to the project should the risk actually occur
Question 203 |
Which one of the items listed below is not one of the software engineering layers ?
Process | |
Manufacturing | |
Method | |
Tools |
Question 203 Explanation:
- Software Engineering is divided into four layers:
1. A quality Process
- Any engineering approach must rest on an quality.
- The "Bedrock" that supports software Engineering is Quality Focus.
2. Process
- Foundation for software engineering is the Process Layer.
- Software engineering process holds all the technology layers together and enables the timely development of computer software.
- It forms the base for management control of software project.
3. Methods
- Software engineering methods provide the "Technical Questions" for building Software.
- Methods contain a broad array of tasks that include communication requirement analysis, design modelling, program construction testing and support.
4. Tools
- Software engineering tools provide automated or semi-automated support for the "Process" and "Methods".
- Tools are integrated so that information created by one tool can be used by another.
1. A quality Process
- Any engineering approach must rest on an quality.
- The "Bedrock" that supports software Engineering is Quality Focus.
2. Process
- Foundation for software engineering is the Process Layer.
- Software engineering process holds all the technology layers together and enables the timely development of computer software.
- It forms the base for management control of software project.
3. Methods
- Software engineering methods provide the "Technical Questions" for building Software.
- Methods contain a broad array of tasks that include communication requirement analysis, design modelling, program construction testing and support.
4. Tools
- Software engineering tools provide automated or semi-automated support for the "Process" and "Methods".
- Tools are integrated so that information created by one tool can be used by another.
Question 204 |
What is the first stage in program development ?
Specification and design | |
System Analysis | |
Testing | |
None of the above |
Question 204 Explanation:
Stages in program development:
1. System Analysis
2. Specification and design
3. Coding and unit testing
4. Maintenance
1. System Analysis
2. Specification and design
3. Coding and unit testing
4. Maintenance
Question 205 |
Which of these are the 5 generic software engineering framework activities ?
Communication, planning, modelling, construction, deployment | |
Communication, risk management, measurement, production, reviewing | |
Analysis, designing, programming, Debugging, maintenance | |
Analysis, planning, designing, programming, testing |
Question 205 Explanation:
The following generic process framework is applicable to the vast majority of S/W projects.
1,Communication: involves heavy communication with the customer (and other stakeholders) and encompasses requirements gathering.
2. Planning: Describes the technical tasks to be conducted, the risks that are likely, resources that will be required, the work products to be produced and a work schedule.
3. Modeling: encompasses the creation of models that allow the developer and customer to better understand S/W req. and the design that will achieve those req.
4. Construction: combines code generation and the testing required uncovering errors in the code.
5. Deployment: deliver the product to the customer who evaluates the delivered product and provides feedback.
1,Communication: involves heavy communication with the customer (and other stakeholders) and encompasses requirements gathering.
2. Planning: Describes the technical tasks to be conducted, the risks that are likely, resources that will be required, the work products to be produced and a work schedule.
3. Modeling: encompasses the creation of models that allow the developer and customer to better understand S/W req. and the design that will achieve those req.
4. Construction: combines code generation and the testing required uncovering errors in the code.
5. Deployment: deliver the product to the customer who evaluates the delivered product and provides feedback.
Question 206 |
Many causes of the software crisis can be traced to mythology based on
Management Myths | |
Customer Myths | |
Practitioner Myths | |
All of the above |
Question 206 Explanation:
Many causes of the software crisis can be traced to mythology based on management Myths,Customer Myths and Practitioner Myths.
Question 207 |
COCOMO stands for
COmposite COst MOdel | |
COnstructive COst MOdel | |
COnstructive Composite MOdel | |
COmprehensive Construction MOdel |
Question 207 Explanation:
COCOMO stands for COnstructive COst MOdel. It is a procedural software cost estimation model but not software process model. Linear sequential,prototype and spiral models are software process models.
The basic COCOMO equations take the form
1. Effort Applied (E) = a(KLOC)b [ man-months ]
2. Development Time (D) = c(Effort Applied)d [months]
3. People required (P) = Effort Applied / Development Time [count]
The basic COCOMO equations take the form
1. Effort Applied (E) = a(KLOC)b [ man-months ]
2. Development Time (D) = c(Effort Applied)d [months]
3. People required (P) = Effort Applied / Development Time [count]
Question 208 |
While estimating the cost of software, Lines Of Code(LOC) and Function Points(FP) are used to measure which one of the following ?
Length of code | |
Size of software | |
Functionality of software | |
None of the above |
Question 208 Explanation:
→ A function point is a "unit of measurement" to express the amount of business functionality an information system (as a product) provides to a user. Function points are used to compute a functional size measurement (FSM) of software. The cost (in dollars or hours) of a single unit is calculated from past projects.
→ Lines of code (LOC) is a software metric used to measure the size of a computer program by counting the number of lines in the text of the program's source code.
→ Lines of code (LOC) is a software metric used to measure the size of a computer program by counting the number of lines in the text of the program's source code.
Question 209 |
A good software design must have
High module coupling, High module cohesion | |
High module coupling, Low module cohesion | |
Low module coupling, High module cohesion | |
Low module coupling, Low module cohesion |
Question 209 Explanation:
→ A good software design must have low module coupling and high module cohesion.
→ Coupling and Cohesion are used in software design. Cohesion measures strength of a module while coupling measures interdependency between modules.
→ Coupling and Cohesion are used in software design. Cohesion measures strength of a module while coupling measures interdependency between modules.
Question 210 |
“Black” refers in the “Black-box” testing means
Characters of the movie “Black” | |
I–O is hidden | |
Design is hidden | |
Users are hidden |
Question 210 Explanation:
Black box testing means design is hidden. Specific knowledge of the application's code, internal structure and programming knowledge in general is not required.
Question 211 |
Prototyping is used to
test the software as an end product | |
expand design details | |
refine and establish requirements gathering | |
None of the above |
Question 211 Explanation:
Prototyping is used to refine and establish requirements gathering. The quick design of a software that is visible to end users leads to prototype model.
Advantages: 1. We can develop software where requirements are unclear
2. Customer satisfaction
Disadvantage:
1. Who pay cost of prototype
2. Required the design expertise
3. Throwaway approach (or) evolutionary approach ( In this approach we develop the software by enhancing protype)
Advantages: 1. We can develop software where requirements are unclear
2. Customer satisfaction
Disadvantage:
1. Who pay cost of prototype
2. Required the design expertise
3. Throwaway approach (or) evolutionary approach ( In this approach we develop the software by enhancing protype)
Question 212 |
Which one of these are not software maintenance activity ?
Error correction | |
Adaptation | |
Implementation of Enhancement | |
Establishing scope |
Question 212 Explanation:
Software maintenance is the modification of a software product after delivery to correct faults, to improve performance or other attributes.
Software maintenance types: 1. Adaptive: modifying the system to cope with changes in the software environment (DBMS, OS)
2. Perfective: Implementing new or changed user requirements which concern functional enhancements to the software.
3. Corrective: Diagnosing and fixing errors, possibly ones found by users.
4. Preventive: Increasing software maintainability or reliability to prevent problems in the future.
Software maintenance types: 1. Adaptive: modifying the system to cope with changes in the software environment (DBMS, OS)
2. Perfective: Implementing new or changed user requirements which concern functional enhancements to the software.
3. Corrective: Diagnosing and fixing errors, possibly ones found by users.
4. Preventive: Increasing software maintainability or reliability to prevent problems in the future.
Question 213 |
The system specification is the first deliverable in the computer system engineering process which does not include
Functional Description | |
Cost | |
Schedule | |
Technical Analysis |
Question 213 Explanation:
→ The system specification is the first deliverable in the computer system engineering process which does not include functional description.
→ The system specification document describes the system and gives a high-level view of what the system will provide. The system specification is the guide that will allow details on hardware,software and test requirements.
→ The system specification document describes the system and gives a high-level view of what the system will provide. The system specification is the guide that will allow details on hardware,software and test requirements.
Question 214 |
The COCOMO model was introduced in the book title “Software Engineering Economics” authored by
Abraham Silberschatz | |
Barry Boehm | |
C.J. Date | |
D.E. Knuth |
Question 214 Explanation:
The COCOMO model was introduced in the book title “Software Engineering Economics” authored by Barry Boehm.
Question 215 |
Software engineering primarily aims on
reliable software | |
cost effective software | |
reliable and cost effective software | |
none of the above |
Question 215 Explanation:
Software engineering primarily aims on reliable and cost effective software.
Question 216 |
Which model is simplest model in Software Development ?
Waterfall model | |
Prototyping | |
Iterative | |
None of these |
Question 216 Explanation:
Waterfall model is simplest and oldest software development life cycle model.
Question 217 |
Design phase will usually be
top-down | |
bottom-up | |
random | |
centre fringing |
Question 217 Explanation:
Design phase will usually be top-down approach.
Question 218 |
Applications-software
is used to control the operating system | |
includes programs designed to help programmers | |
performs a specific task for computer users | |
all of the above |
Question 218 Explanation:
Applications software performs a specific task for computer users.
Question 219 |
In the light of software engineering software consists of :
Programs | |
Data | |
Documentation | |
All of the above |
Question 219 Explanation:
In the light of software engineering software consists of programs,data and documentation.
Question 220 |
Which one of the following ISO standard is used for software process ?
ISO 9000 | |
ISO 9001 | |
ISO 9003 | |
ISO 9000–3 |
Question 220 Explanation:
ISO 9003 is "Quality systems-Model for quality assurance in final inspection and test".
ISO 9001 is a non-industry specific certification.
ISO 9000 refers to the family of standards including ISO 9000, ISO 9001, ISO 9004 and ISO 19011.
ISO 9001 is a non-industry specific certification.
ISO 9000 refers to the family of standards including ISO 9000, ISO 9001, ISO 9004 and ISO 19011.
Question 221 |
Which of the following is used for test data generation ?
White Box | |
Black Box | |
Boundary value analysis | |
All of the above |
Question 221 Explanation:
Boundary testing is the process of testing between extreme ends or boundaries between partitions of the input values. It is used to test data generation.
Question 222 |
Reverse engineering is the process which deals with :
Size measurement | |
Cost measurement | |
Design recovery | |
All of the above |
Question 222 Explanation:
Design recovery from source code is done during reverse engineering, re-engineering and reusability.
Question 223 |
Software Engineering is a discipline that integrates _________ for the development of
computer software.
Process | |
Methods | |
Tools | |
All |
Question 223 Explanation:
Software Engineering is a discipline that integrates process,methods and tools for the development of computer software.
Process:
- Foundation for software engineering is the Process Layer.
- Software engineering process holds all the technology layers together and enables the timely development of computer software.
- It forms the base for management control of software project.
Methods:
- Software engineering methods provide the "Technical Questions" for building Software.
- Methods contain a broad array of tasks that include communication requirement analysis, design modelling, program construction testing and support.
Tools:
- Software engineering tools provide automated or semi-automated support for the "Process" and "Methods".
- Tools are integrated so that information created by one tool can be used by another.
Process:
- Foundation for software engineering is the Process Layer.
- Software engineering process holds all the technology layers together and enables the timely development of computer software.
- It forms the base for management control of software project.
Methods:
- Software engineering methods provide the "Technical Questions" for building Software.
- Methods contain a broad array of tasks that include communication requirement analysis, design modelling, program construction testing and support.
Tools:
- Software engineering tools provide automated or semi-automated support for the "Process" and "Methods".
- Tools are integrated so that information created by one tool can be used by another.
Question 224 |
Any error whose cause cannot be identified anywhere within the software system is
called ________
Internal error | |
External error | |
Inherent error | |
Logic error |
Question 224 Explanation:
Internal errors are due to faulty logic or coding in the program.
1. Bounds errors
2. Inserting a null pointer into a collection
3. Attempting to use a bad date
External errors are due to events beyond the scope of the program.
1. Not easily predicted in advance
2. Encountered at more abstract levels
3. Not costly to detect
4. Detected in both the production and the debug versions of the library
Logical errors(or) semantic errors:
Logical errors are syntactically correct but it will generate error during execution.
1. Divide by zero
Inherent errors in the statement of the problem are called inherent errors.
1. Bounds errors
2. Inserting a null pointer into a collection
3. Attempting to use a bad date
External errors are due to events beyond the scope of the program.
1. Not easily predicted in advance
2. Encountered at more abstract levels
3. Not costly to detect
4. Detected in both the production and the debug versions of the library
Logical errors(or) semantic errors:
Logical errors are syntactically correct but it will generate error during execution.
1. Divide by zero
Inherent errors in the statement of the problem are called inherent errors.
Question 225 |
Recorded software attributes can be used in the following endeavours :
(i) Cost and schedule estimates.
(ii) Software product reliability predictions.
(iii) Managing the development process.
(iv) Nowhere
(i) Cost and schedule estimates.
(ii) Software product reliability predictions.
(iii) Managing the development process.
(iv) Nowhere
(i) (ii) (iv) | |
(ii) (iii) (iv) | |
(i) (ii) (iii) | |
(i) (ii) (iii) (iv) |
Question 225 Explanation:
Recorded software attributes can be used to
1. Cost and schedule estimates.
2. Software product reliability predictions.
3. Managing the development process.
1. Cost and schedule estimates.
2. Software product reliability predictions.
3. Managing the development process.
Question 226 |
Black Box testing is done
to show that s/w is operational at its interfaces i.e. input and output. | |
to examine internal details of code. | |
at client side.
| |
none of above. |
Question 226 Explanation:
Black Box testing is done to show that s/w is operational at its interfaces i.e. input and output.
Black box testing methods are
1. Graph-Based Testing Methods
2. Equivalence Partitioning
3. Boundary Value Analysis
4. Orthogonal Array Testing
Black box testing methods are
1. Graph-Based Testing Methods
2. Equivalence Partitioning
3. Boundary Value Analysis
4. Orthogonal Array Testing
Question 227 |
Software Quality Assurance (SQA) encompasses :
Verification | |
Validation | |
Both verification and validation | |
None of the above |
Question 227 Explanation:
→ Software Quality Assurance (SQA) encompasses both verification and validation.
→ Verification and validation are not the same things, although they are often confused. Boehm succinctly expressed the difference as
→ Verification: Are we building the product right?
→ Validation: Are we building the right product?
→ Verification and validation are not the same things, although they are often confused. Boehm succinctly expressed the difference as
→ Verification: Are we building the product right?
→ Validation: Are we building the right product?
Question 228 |
COCOMO model is used for :
Product quality estimation | |
Product complexity estimation
| |
Product cost estimation | |
All of the above |
Question 228 Explanation:
COCOMO model is used for product cost estimation.
Question 229 |
Waterfall model for software development is :
a top down approach. | |
a bottom up approach. | |
a sequential approach. | |
a consequential approach. |
Question 229 Explanation:
Waterfall model for software development is a linear or sequential approach.
Phases:
1. Feasibility study
2. Analysis
3. Design
4. Coding & Unit testing
5. Integration & System Testing
6. Maintenance
Phases:
1. Feasibility study
2. Analysis
3. Design
4. Coding & Unit testing
5. Integration & System Testing
6. Maintenance
Question 230 |
In software development, value adjustment factors include the following among others :
the criticality of the performance and reusability of the code. | |
number of lines of code in the software. | |
number of technical manpower and hardware costs. | |
time period available and the level of user friendliness. |
Question 230 Explanation:
→ Value adjustment factors include the criticality of the performance and reusability of the code.
→ 14 Value adjustment factors are using in functional points maximum.
→ 14 Value adjustment factors are using in functional points maximum.
Question 231 |
While designing the user interface, one should :
use as many short cuts as possible. | |
use as many defaults as possible. | |
use as many visual layouts as possible. | |
reduce the demand on short-term memory. |
Question 231 Explanation:
→ While designing the user interface, one should reduce the demand on short-term memory.
Question 232 |
In software cost estimation, base estimation is related to :
cost of similar projects already completed. | |
cost of the base model of the present project.
| |
cost of the project with the base minimum profit. | |
cost of the project under ideal situations. |
Question 232 Explanation:
In software cost estimation, base estimation is related to cost of similar projects already completed.
Question 233 |
In cleanroom software engineering :
only eco-friendly hardware is used. | |
only hired facilities are used for development. | |
correctness of the code is verified before testing. | |
implementation is done only after ensuring correctness. |
Question 233 Explanation:
In cleanroom software engineering implementation is done only after ensuring correctness.
Clean-room Strategy:
Cleanroom software engineering (CSE) is a process model that removes defects before they can precipitate serious hazards. It is a team-oriented, theory based software, which is developed using the formal methods, correctness verification and Statistical Quality Assurance (SQA).
→ Clean room management is based on the incremental model of software development, which accumulates into the final product. The approach combines mathematical-based methods of software specification, design and correctness verification with statistical, usage-based testing to certify software fitness for use.
→ The main goal of clean room engineering is to produce zero error-based software by allowing correct designs, which avoid rework.
Clean-room Strategy:
Cleanroom software engineering (CSE) is a process model that removes defects before they can precipitate serious hazards. It is a team-oriented, theory based software, which is developed using the formal methods, correctness verification and Statistical Quality Assurance (SQA).
→ Clean room management is based on the incremental model of software development, which accumulates into the final product. The approach combines mathematical-based methods of software specification, design and correctness verification with statistical, usage-based testing to certify software fitness for use.
→ The main goal of clean room engineering is to produce zero error-based software by allowing correct designs, which avoid rework.
Question 234 |
A major defect in waterfall model in software development is that :
the documentation is difficult | |
a blunder at any stage can be disastrous | |
a trial version is available only at the end of the project | |
the maintenance of the software is difficult |
Question 234 Explanation:
A major defect in waterfall model in software development is that a trial version is available only at the end of the project.
Question 235 |
Function point metric of a software also depends on the :
number of function needed | |
number of final users of the software | |
number of external inputs and outputs | |
time required for one set of output from a set of input data |
Question 235 Explanation:
Function point metric of a software also depends on the number of external inputs and outputs.
Question 236 |
System development cost estimation with use-cases is problematic because :
of paucity of examples | |
the data can be totally incorrect | |
the expertise and resource available are not used | |
the problem is being over simplified |
Question 236 Explanation:
System development cost estimation with use-cases is problematic because the data can be totally incorrect.
Question 237 |
The approach to software testing is to design test cases to :
break the software | |
understand the software | |
analyse the design of sub processes in the software | |
analyze the output of the software |
Question 237 Explanation:
The approach to software testing is to design test cases to break the software.
Question 238 |
Which of the following combination is preferred with respect to cohesion and coupling :
low and low | |
low and high | |
high and low | |
high and high |
Question 238 Explanation:
→ Cohesion is a measure of internal strength within a module, whereas coupling is a measure of inter dependency among the modules.
→ So in the context of modular software design there should be high cohesion and low coupling.
→ So in the context of modular software design there should be high cohesion and low coupling.
Question 239 |
Match the following :
Which of the following is true :
Which of the following is true :
(a)-(ii), (b)-(iii), (c)-(iv), (d)-(i) | |
(a)-(i), (b)-(ii), (c)-(iv), (d)-(iii) | |
(a)-(iii), (b)-(iv), (c)-(i), (d)-(ii) | |
None of the above |
Question 239 Explanation:
Question 240 |
Problems with waterfall model are :
-
- Real projects rarely follow this model proposes
- It is often difficult for the customer
- Working model is available only in the end
- Developers are delayed unnecessarily
1 and 4 only | |
2 and 3 only | |
1, 2 and 3 only | |
1, 2, 3 and 4 |
Question 240 Explanation:
Problems with waterfall model are
1. Real projects rarely follow this model proposes
2. It is often difficult for the customer
3. Working model is available only in the end
4. Developers are delayed unnecessarily
1. Real projects rarely follow this model proposes
2. It is often difficult for the customer
3. Working model is available only in the end
4. Developers are delayed unnecessarily
Question 241 |
Statistical software quality assurance in software engineering involves __________ .
using sampling in place of exhaustive testing of software. | |
surveying customers to find out their opinions about product quality. | |
tracing each defect to its underlying cause, isolating the vital few causes, and moving to correct them. | |
tracing each defect to its underlying causes, and using the Pareto principle to correct each problem found. |
Question 241 Explanation:
→ Statistical software quality assurance in software engineering involves tracing each defect to its underlying cause, isolating the vital few causes, and moving to correct them.
→ Statistical software quality assurance uses pareto principle to identify vital causes (80% of defects can be traced to 20% of causes) and moves to correct the problems that have caused the defects.
→ Statistical software quality assurance uses pareto principle to identify vital causes (80% of defects can be traced to 20% of causes) and moves to correct the problems that have caused the defects.
Question 242 |
Which of the following statements is/are FALSE with respect to software testing ?
S1 : White-box tests are based on specifications; better at telling whether program meets specification, better at finding errors of omission.
S2 : Black- box tests are based on code; better for finding crashes, out of bounds errors, file not closed errors.
S3 : Alpha testing is conducted at the developer’s site by a team of highly skilled testers for software that is developed as a product to be used by many customers.
S1 : White-box tests are based on specifications; better at telling whether program meets specification, better at finding errors of omission.
S2 : Black- box tests are based on code; better for finding crashes, out of bounds errors, file not closed errors.
S3 : Alpha testing is conducted at the developer’s site by a team of highly skilled testers for software that is developed as a product to be used by many customers.
Only S1 and S2 are FALSE. | |
Only S1 and S3 are FALSE. | |
Only S2 and S3 are FALSE. | |
All of S1, S2, and S3 are FALSE. |
Question 242 Explanation:
FALSE: Black box tests are based on specifications; better at telling whether program meets specification, better at finding errors of omission.
FALSE: White box tests are based on code; better for finding crashes, out of bounds errors, file not closed errors.
TRUE: Alpha testing is conducted at the developer’s site by a team of highly skilled testers for software that is developed as a product to be used by many customers.
FALSE: White box tests are based on code; better for finding crashes, out of bounds errors, file not closed errors.
TRUE: Alpha testing is conducted at the developer’s site by a team of highly skilled testers for software that is developed as a product to be used by many customers.
Question 243 |
A signal processor software is expected to operate for 91.25 days after repair, and the mean software repair time is expected to be 5 minutes. Then, the availability of the software is:
96.9862% | |
97.9862% | |
98.9962% | |
99.9962% |
Question 243 Explanation:
Given data,
-- Software expected to operate after repair(MTBF) = 91.25 days
= 91.25 * 24 hours
= 2190 hours
-- Mean software repair time(MTTR) = 5 mins
= 5/60 hrs
= 0.083 hrs
-- Software Availability=?
Step-1: Software Availability =MTBF / (MTBF + MTTR)
= [2190 / (2190 + 0.083)]*100
= (2190 / 2190.083)*100
= 0.9996211481 * 100
= 99.9962%
-- Software expected to operate after repair(MTBF) = 91.25 days
= 91.25 * 24 hours
= 2190 hours
-- Mean software repair time(MTTR) = 5 mins
= 5/60 hrs
= 0.083 hrs
-- Software Availability=?
Step-1: Software Availability =MTBF / (MTBF + MTTR)
= [2190 / (2190 + 0.083)]*100
= (2190 / 2190.083)*100
= 0.9996211481 * 100
= 99.9962%
Question 244 |
Consider the method mcq ( ):
int mcq(boolean a, boolean b, boolean c, boolean d)
{
int ans=1;
if(a) { ans = 2; }
else if (b) { ans = 3; }
else if (c) {
if (d) { ans = 4; }
return ans;
}
if
M1 = Number of tests to exhaustively test mcq( );
M2 = Minimum number of tests to achieve full statement coverage for mcq( ); and
M3 = Minimum number of tests to achieve full branch coverage for mcq( );
then (M1, M2, M3) = __________.
int mcq(boolean a, boolean b, boolean c, boolean d)
{
int ans=1;
if(a) { ans = 2; }
else if (b) { ans = 3; }
else if (c) {
if (d) { ans = 4; }
return ans;
}
if
M1 = Number of tests to exhaustively test mcq( );
M2 = Minimum number of tests to achieve full statement coverage for mcq( ); and
M3 = Minimum number of tests to achieve full branch coverage for mcq( );
then (M1, M2, M3) = __________.
(16, 3, 5) | |
(8, 5, 3) | |
(8, 3, 5) | |
(16, 4, 4) |
Question 244 Explanation:
Question 245 |
A simple stand - alone software utility is to be developed in ‘C’ programming by a team of software experts for a computer running Linux and the overall size of this software is estimated to be 20,000 lines of code. Considering (a, b) = (2.4, 1.05) as multiplicative and exponention factor for the basic COCOMO effort estimation equation and (c, d) = (2.5, 0.38) as multiplicative and exponention factor for the basic COCOMO development time estimation equation, approximately how long does the software project take to complete ?
10.52 months | |
11.52 months | |
12.52 months | |
14.52 months |
Question 245 Explanation:
Given data,
-- lines of code(LOC)= 20,000 (or 20K)
-- Multiplicative value ‘a’=2.4
-- Exponential ‘b’=1.05
-- Basic COCOMO formula= a*(LOC in K)b
-- Multiplicative value ‘c’=2.5
-- Exponential ‘d’=0.38
-- Development=c*(basic COCOMO result)d
Step-1: Basic COCOMO formula= a*(LOC in K)b
= 2.4*(20)1.05
= 55.756
Step-2: Development= c*(basic COCOMO result)d
= 2.5(55.756)0.38
= 11.52 months
-- lines of code(LOC)= 20,000 (or 20K)
-- Multiplicative value ‘a’=2.4
-- Exponential ‘b’=1.05
-- Basic COCOMO formula= a*(LOC in K)b
-- Multiplicative value ‘c’=2.5
-- Exponential ‘d’=0.38
-- Development=c*(basic COCOMO result)d
Step-1: Basic COCOMO formula= a*(LOC in K)b
= 2.4*(20)1.05
= 55.756
Step-2: Development= c*(basic COCOMO result)d
= 2.5(55.756)0.38
= 11.52 months
Question 246 |
In Software Configuration Management (SCM), which of the following is a use-case supported by standard version control systems ?
(a) Managing several versions or releases of a software
(b) Filing bug reports and tracking their progress
(c) Allowing team members to work in parallel
(d) Identifying when and where a regression occurred
(a) Managing several versions or releases of a software
(b) Filing bug reports and tracking their progress
(c) Allowing team members to work in parallel
(d) Identifying when and where a regression occurred
Only (a), (c), and (d) | |
Only (a), (b), and (c) | |
Only (a), (b), and (d) | |
Only (b), (c), and (d) |
Question 246 Explanation:
Software Configuration Management (SCM) is a use-case supported by standard version control systems:
1. Develop the next version of a piece of software while fixing problems with the current one.
2. Share code with other team members in a controlled way, allowing you to develop code in parallel with others and join with the current state of the codeline.
3. Identify what versions of code went into a particular component.
4. Analyze where change happened in the history of a component's development.
1. Develop the next version of a piece of software while fixing problems with the current one.
2. Share code with other team members in a controlled way, allowing you to develop code in parallel with others and join with the current state of the codeline.
3. Identify what versions of code went into a particular component.
4. Analyze where change happened in the history of a component's development.
Question 247 |
Which of the following statement(s) is/are TRUE with regard to software testing ?
I. Regression testing technique ensures that the software product runs correctly after the changes during maintenance.
II. Equivalence partitioning is a white-box testing technique that divides the input domain of a program into classes of data from which test cases can be derived.
I. Regression testing technique ensures that the software product runs correctly after the changes during maintenance.
II. Equivalence partitioning is a white-box testing technique that divides the input domain of a program into classes of data from which test cases can be derived.
only I | |
only II | |
both I and II | |
neither I nor II |
Question 247 Explanation:
Statement-1:
→ Regression testing is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. If not, that would be called a regression.
→ Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components.
→ As regression test suites tend to grow with each found defect, test automation is frequently involved.
Statement-2: Black box testing methods are
1. Graph-Based Testing Methods
2. Equivalence Partitioning: It is a black box testing technique that divides the input domain of a program into classes of data from which test cases can be derived.
3. Boundary Value Analysis
4. Orthogonal Array Testing
→ Regression testing is re-running functional and non-functional tests to ensure that previously developed and tested software still performs after a change. If not, that would be called a regression.
→ Changes that may require regression testing include bug fixes, software enhancements, configuration changes, and even substitution of electronic components.
→ As regression test suites tend to grow with each found defect, test automation is frequently involved.
Statement-2: Black box testing methods are
1. Graph-Based Testing Methods
2. Equivalence Partitioning: It is a black box testing technique that divides the input domain of a program into classes of data from which test cases can be derived.
3. Boundary Value Analysis
4. Orthogonal Array Testing
Question 248 |
Which of the following are facts about a top-down software testing approach?
I. Top-down testing typically requires the tester to build method stubs.
II. Top-down testing typically requires the tester to build test drivers.
I. Top-down testing typically requires the tester to build method stubs.
II. Top-down testing typically requires the tester to build test drivers.
Only I | |
Only II | |
Both I and II | |
Neither I nor II |
Question 248 Explanation:
Statement-1: TRUE: Top-down testing typically requires the tester to build method stubs.
Stub is a dummy subprogram. Stub uses the subordinate module’s interface, may do minimal data manipulation, provides verification of entry, and returns control to the module undergoing testing.
Statement-2: FALSE: Bottom up testing typically requires the tester to build test drivers.
Driver is nothing more than a “main program “ that accepts test case data, passes such data to the component(to be tested) and prints relevant results.
Driver is serve to replace modules that are subordinate to (called by) the component to be tested.
Stub is a dummy subprogram. Stub uses the subordinate module’s interface, may do minimal data manipulation, provides verification of entry, and returns control to the module undergoing testing.
Statement-2: FALSE: Bottom up testing typically requires the tester to build test drivers.
Driver is nothing more than a “main program “ that accepts test case data, passes such data to the component(to be tested) and prints relevant results.
Driver is serve to replace modules that are subordinate to (called by) the component to be tested.
Question 249 |
Match the terms related to Software Configuration Management (SCM) in List – I with the descriptions in List – II.
I-B, II-C, III-A | |
I-C, II-A, III-B | |
I-C, II-B, III-A | |
I-B, II-A, III-C |
Question 249 Explanation:
Version→ An instance of a system that differs, in some way, from other instances.
Release→ An instance of a system that is distributed to customers.
Variant→ An instance of a system which is functionally identical to other instances, but designed for different hardware/software configurations.
Release→ An instance of a system that is distributed to customers.
Variant→ An instance of a system which is functionally identical to other instances, but designed for different hardware/software configurations.
Question 250 |
A software project was estimated at 352 Function Points (FP). A four person team will be assigned to this project consisting of an architect, two programmers, and a tester. The salary of the architect is 80,000 per month, the programmer ₹ 60,000 per month and the tester ₹ 50,000 per month. The average productivity for the team is 8 FP per person month. Which of the following represents the projected cost of the project ?
₹ 28,16,000 | |
₹ 20,90,000 | |
₹ 26,95,000 | |
₹ 27,50,000 |
Question 250 Explanation:
Given data,
-- Functional Point(FP)=352
-- Team=4 persons
-- Average each person(FP) productivity=8
-- Architect month salary=80,000
-- Programmers month salary=2*60,000
-- Tester month salary=50,000
-- projected cost of project=?
Step-1: Total number of months=Functional Point(FP) / (Team* Average each person(FP) productivity)
= 352 / (4*8)
= 352 / 32
= 11 months
Step-2: Total cost of the project= (one Architect month salary + 2*Programmers month salary + one tester month salary) * Total number of months
= (80000 + 2 * 60000 + 50000) * 11
= ₹ 27,50,000
-- Functional Point(FP)=352
-- Team=4 persons
-- Average each person(FP) productivity=8
-- Architect month salary=80,000
-- Programmers month salary=2*60,000
-- Tester month salary=50,000
-- projected cost of project=?
Step-1: Total number of months=Functional Point(FP) / (Team* Average each person(FP) productivity)
= 352 / (4*8)
= 352 / 32
= 11 months
Step-2: Total cost of the project= (one Architect month salary + 2*Programmers month salary + one tester month salary) * Total number of months
= (80000 + 2 * 60000 + 50000) * 11
= ₹ 27,50,000
Question 251 |
Complete each of the following sentences in List – I on the left hand side by filling in the word or phrase from the List – II on the right hand side that best completes the sentence :
I-B, II-D, III-A, IV-C | |
I-B, II-D, III-C, IV-A | |
I-D, II-B, III-C, IV-A | |
I-D, II-B, III-A, IV-C |
Question 251 Explanation:
→ Verification: Are we building the product right?
→ Validation: Are we building the right product?
→ Software debugging is the process of discovering the cause of a defect and fixing it.
→ is the process of demonstrating the existence.
→ Validation: Are we building the right product?
→ Software debugging is the process of discovering the cause of a defect and fixing it.
→ is the process of demonstrating the existence.
Question 252 |
A software company needs to develop a project that is estimated as 1000 function points and is planning to use JAVA as the programming language whose approximate lines of code per function point is accepted as 50. Considering a = 1.4 as multiplicative factor, b = 1.0 as exponential factor for the basic COCOMO effort equation and c = 3.0 as multiplicative factor, d = 0.33 as exponential factor for the basic COCOMO duration equation, approximately how long does the project take to complete ?
11.2 months | |
12.2 months | |
13.2 months | |
10.2 months |
Question 252 Explanation:
Given data,
-- lines of code(LOC)= 50,000 (or 50K)
-- Multiplicative value ‘a’=1.4
-- Exponential ‘b’=1.0
-- Basic COCOMO formula= a*(LOC in K)b
-- Multiplicative value ‘c’=3.0
-- Exponential ‘d’=0.33
-- Development=c*(basic COCOMO result)d
Step-1: Basic COCOMO formula= a*(LOC in K)b
= 1.4*(50)1.0
= 70 Step-2: Development= c*(basic COCOMO result)d
= 3(70)0.33
= 12.18 months
-- lines of code(LOC)= 50,000 (or 50K)
-- Multiplicative value ‘a’=1.4
-- Exponential ‘b’=1.0
-- Basic COCOMO formula= a*(LOC in K)b
-- Multiplicative value ‘c’=3.0
-- Exponential ‘d’=0.33
-- Development=c*(basic COCOMO result)d
Step-1: Basic COCOMO formula= a*(LOC in K)b
= 1.4*(50)1.0
= 70 Step-2: Development= c*(basic COCOMO result)d
= 3(70)0.33
= 12.18 months
Question 253 |
Match each software lifecycle model in List – I to its description in List – II:
I-e, II-b, III-a, IV-c, V-d | |
I-e, II-c, III-a, IV-b, V-d | |
I-d, II-a, III-b, IV-c, V-e | |
I-c, II-e, III-a, IV-b, V-d |
Question 253 Explanation:
Code and Fix → Write some code, debug it, repeat(i.e. ad-hoc)
Evolutionary prototype → Build an initial small requirement specifications, code it, then "evolve" the specifications and code as needed.
Spiral → Assess risks at each step; do most critical action first.
Staged Delivery→ Build initial requirement specification for several releases, then design-and-code in sequence
Waterfall → Standard phases(requirements,design,code,test) in order.
Evolutionary prototype → Build an initial small requirement specifications, code it, then "evolve" the specifications and code as needed.
Spiral → Assess risks at each step; do most critical action first.
Staged Delivery→ Build initial requirement specification for several releases, then design-and-code in sequence
Waterfall → Standard phases(requirements,design,code,test) in order.
Question 254 |
Match each software term in List – I to its description in List – II:
I-d, II-a, III-b, IV-c, V-e | |
I-b, II-a, III-d, IV-c, V-e | |
I-d, II-e, III-b, IV-a, V-c | |
I-e, II-c, III-b, IV-a, V-d |
Question 254 Explanation:
Wizards→ Step-by-step guides in application software
Templates→ Forms that provide structure for a document
Macro→ A series of commands grouped into a single command
Integrated Software→ A single program that incorporates most commonly used tools
Software Suite→ Bundled group of software programs
Templates→ Forms that provide structure for a document
Macro→ A series of commands grouped into a single command
Integrated Software→ A single program that incorporates most commonly used tools
Software Suite→ Bundled group of software programs
Question 255 |
The ISO quality assurance standard that applies to software Engineering is
ISO 9000 : 2004 | |
ISO 9001 : 2000 | |
ISO 9002 : 2001 | |
ISO 9003 : 2004 |
Question 255 Explanation:
→ Software quality assurance (SQA) consists of a means of monitoring the software engineering processes and methods used to ensure quality.
→ The ISO quality assurance standard that applies to software Engineering is ISO 9001 : 2000.
→ The ISO quality assurance standard that applies to software Engineering is ISO 9001 : 2000.
Question 256 |
Which of the following are external qualities of a software product?
Maintainability, reusability, portability, efficiency, correctness. | |
Correctness, reliability, robustness, efficiency, usability. | |
Portability, interoperability, maintainability, reusability. | |
Robustness, efficiency, reliability, maintainability, reusability. |
Question 256 Explanation:
Steve McConnell’s Code describes the characteristics of internal and external qualities
1. External Quality Characteristics: Correctness, Usability, Efficiency, Reliability, Integrity, Adaptability, Accuracy, and Robustness.
2. Internal Quality Characteristics: Maintainability, Flexibility, Portability, Re-usability, Readability, Testability, and Understandability.
1. External Quality Characteristics: Correctness, Usability, Efficiency, Reliability, Integrity, Adaptability, Accuracy, and Robustness.
2. Internal Quality Characteristics: Maintainability, Flexibility, Portability, Re-usability, Readability, Testability, and Understandability.
Question 257 |
Match the following:
(a)-(i), (b)-(ii), (c)-(iv), (d)-(iii) | |
(a)-(i), (b)-(iv), (c)-(ii), (d)-(iii) | |
(a)-(iii), (b)-(ii), (c)-(iv), (d)-(i) | |
(a)-(iii), (b)-(iv), (c)-(ii), (d)-(i) |
Question 257 Explanation:
Question 258 |
Match the software maintenance activities in List – I to its meaning in List – II.
I-(b), II-(d), III-(c), IV-(a) | |
I-(b), II-(c), III-(d), IV-(a) | |
I-(c), II-(b), III-(d), IV-(a) | |
I-(a), II-(d), III-(b), IV-(c) |
Question 258 Explanation:
Corrective → Concerned with fixing errors that are observed when the software is in use.
Adaptive → Concerned with the change in the software than takes place to make the software adaptable to new environment (both hardware and software).
Perfective → Concerned with the change in the software that takes place to make the software adaptable to changing user requirements
Preventive → Concerned with performing activities to reduce the software complexity thereby improving program understandability and increasing software maintainability.
Adaptive → Concerned with the change in the software than takes place to make the software adaptable to new environment (both hardware and software).
Perfective → Concerned with the change in the software that takes place to make the software adaptable to changing user requirements
Preventive → Concerned with performing activities to reduce the software complexity thereby improving program understandability and increasing software maintainability.
Question 259 |
Match each application/software design concept in List – I to its definition in List – II.
I-(b), II-(a), III-(d), IV-(c) | |
I-(b), II-(d), III-(a), IV-(b) | |
I-(d), II-(c), III-(b), IV-(a) | |
I-(d), II-(a), III-(c), IV-(b) |
Question 259 Explanation:
Coupling → Reliance of a code module upon other code modules
Cohesion → Focus of a code upon a single goal.
Scalable → Easy to add functionality to the software without having to redesign it.
Readable → Easy to visually inspect the design of the software and understand its purpose.
→ Cohesion is a measure of internal strength within a module, whereas coupling is a measure of inter dependency among the modules.
→ In a functional oriented design/modular software design there should be high cohesion and low coupling.
→ It requires High Fan-In and Low fan-out.
Cohesion → Focus of a code upon a single goal.
Scalable → Easy to add functionality to the software without having to redesign it.
Readable → Easy to visually inspect the design of the software and understand its purpose.
→ Cohesion is a measure of internal strength within a module, whereas coupling is a measure of inter dependency among the modules.
→ In a functional oriented design/modular software design there should be high cohesion and low coupling.
→ It requires High Fan-In and Low fan-out.
Question 260 |
Software safety is quality assurance activity that focuses on hazards that
affect the reliability of a software component. | |
may cause an entire system to fail. | |
may result from user input errors. | |
prevent profitable marketing of the final product. |
Question 260 Explanation:
Software safety: software quality assurance activity that focuses on the identification and assessment of potential hazards that may affect software negatively and cause an entire system to fail.
→ Modeling and analysis process is conducted as part of software safety.
→ Initially, hazards are identified and categorized by criticality and risk.
→ Modeling and analysis process is conducted as part of software safety.
→ Initially, hazards are identified and categorized by criticality and risk.
Question 261 |
The number of function points of a proposed system is calculated as 500. Suppose that the system is planned to be developed in Java and the LOC/FP ratio of Java is 50. Estimate the effort (E) required to complete the project using the effort formula of basic COCOMO given below :
E = a(KLOC)b
Assume that the values of a and b are 2.5 and 1.0 respectively.
25 person months | |
75 person months | |
62.5 person months | |
72.5 person months |
Question 261 Explanation:
Given data,
-- Functional points(FP)= 500
-- Lines of code(LOC) / FP = 50
-- Effort(E) = a(KLOC)b
-- a = 2.5 and b = 1.0
-- KLOC=?
Step-1: Find out KLOC
KLOC= ((LOC / FP)*FP)/1000
= 25
Where K=1000
Step-2: Find out Effort(E)= 2.5(25)1.0
= 62.5 person months.
-- Functional points(FP)= 500
-- Lines of code(LOC) / FP = 50
-- Effort(E) = a(KLOC)b
-- a = 2.5 and b = 1.0
-- KLOC=?
Step-1: Find out KLOC
KLOC= ((LOC / FP)*FP)/1000
= 25
Where K=1000
Step-2: Find out Effort(E)= 2.5(25)1.0
= 62.5 person months.
Question 262 |
Which one of the following non-functional quality attributes is not highly affected by the architecture of the software?
Performance | |
Reliability | |
Usability | |
Portability |
Question 262 Explanation:
Performance: Performance refers to the response of the system while performing a certain actions in certain period of time. A software can perform better only if it have well structured,easy to maintain architecture.
Reliability: Reliability refers to the ability of a software to continue to operate in the presence of a predefined condition. A software can be reliable if it’s architecture is good enough to work well in inappropriate situations.
Usability: Usability refers to the ease in using the software. The usability is not related to the architecture of the software no matter how complex or simple the software architecture is but the main thing is should be easy to use by the user.
Portability: It refers to the ability to port the software to different platforms or systems. The architecture of a software should be in a way that it can be used at different platforms.
Other than usability all given attributes are somewhere affected by the architecture of the software.
Reliability: Reliability refers to the ability of a software to continue to operate in the presence of a predefined condition. A software can be reliable if it’s architecture is good enough to work well in inappropriate situations.
Usability: Usability refers to the ease in using the software. The usability is not related to the architecture of the software no matter how complex or simple the software architecture is but the main thing is should be easy to use by the user.
Portability: It refers to the ability to port the software to different platforms or systems. The architecture of a software should be in a way that it can be used at different platforms.
Other than usability all given attributes are somewhere affected by the architecture of the software.
Question 263 |
Which one of the following statements, related to the requirements phase in Software Engineering, is incorrect?
“Requirement validation” is one of the activities in the requirements phase. | |
“Prototyping” is one of the methods for requirement analysis. | |
“Modelling-oriented approach” is one of the methods for specifying the functional specifications | |
“Function points” is one of the most commonly used size metric for requirements. |
Question 263 Explanation:
Option(A) is correct because “Requirement verification and validation” is one of the activities in the requirements phase.
Option(B) is correct because we can make a prototype model of a software based upon the customer's basic requirements then the initially developed model can be improved until all customer requirements get fulfilled.
Option(C) is incorrect because “Modelling-oriented approach” is not one of the methods for specifying the functional specifications
Option(D) is correct because “Function points” is one of the most commonly used size metric for requirements.
Option(B) is correct because we can make a prototype model of a software based upon the customer's basic requirements then the initially developed model can be improved until all customer requirements get fulfilled.
Option(C) is incorrect because “Modelling-oriented approach” is not one of the methods for specifying the functional specifications
Option(D) is correct because “Function points” is one of the most commonly used size metric for requirements.
Question 264 |
Match List-I with List-II:
List-I List-II
(Software process Models) (Software System)
(a) Waterfall model (i) e-business that starts with only the basic functionality and then moves on to more advanced
features. (b) Incremental development (ii) An inventory control system for a supermarket to be developed in a highway (c) Prototyping (iii) A virtual reality system for simulating vehicle navigation in a highway. (d) RAD (iv) Automate the manual system for student record maintenance in a school Choose the correct option from those given below:
features. (b) Incremental development (ii) An inventory control system for a supermarket to be developed in a highway (c) Prototyping (iii) A virtual reality system for simulating vehicle navigation in a highway. (d) RAD (iv) Automate the manual system for student record maintenance in a school Choose the correct option from those given below:
(a)-(ii),(b)-(iv),(c)-(i),(d)-(iii) | |
(a)-(i),(b)-(iii),(c)-(iv),(d)-(ii) | |
(a)-(iii),(b)-(ii),(c)-(iv),(d)-(i) | |
(a)-(iv),(b)-(i),(c)-(iii),(d)-(ii) |
Question 264 Explanation:
Waterfall model→ Automate the manual system for student record maintenance in a school
Incremental development→ e-business that starts with only the basic functionality and then moves on to more advanced features.
Prototyping→ A virtual reality system for simulating vehicle navigation in a highway.
RAD→ An inventory control system for a supermarket to be developed in a highway
Incremental development→ e-business that starts with only the basic functionality and then moves on to more advanced features.
Prototyping→ A virtual reality system for simulating vehicle navigation in a highway.
RAD→ An inventory control system for a supermarket to be developed in a highway
Question 265 |
Software Reuse is
The process of analysing software with the objective of recovering its design and specification | |
The process of existing software artifacts and knowledge to build new software | |
Concerned with reimplementing legacy system to make them more maintainable | |
The process of analysing software to create a representation of a higher level of abstraction and breaking software down into its parts to see how it works |
Question 265 Explanation:
Software Reuse is the process of existing software artifacts and knowledge to build new software.
Question 266 |
Software validation mainly checks for inconsistencies between
Use cases and user requirements | |
Implementation and system design blueprints | |
Detailed specifications and user requirements | |
Function specifications and use cases |
Question 266 Explanation:
Software validation checks that the software product satisfies or fits the intended use (high-level checking), i.e., the software meets the user requirements, not as specification artifacts or as needs of those who will operate the software only; but, as the needs of all stakeholders (such as users, operators, administrators, managers, investors, etc.). There are two ways to perform software validation: internal and external. During internal software validation, it is assumed that the goals of the stakeholders were correctly understood and that they were expressed in the requirement artifacts precisely and comprehensively. If the software meets the requirement specification, it has been internally validated. External validation happens when it is performed by asking the stakeholders if the software meets their needs. Different software development methodologies call for different levels of user and stakeholder involvement and feedback; so, external validation can be a discrete or a continuous event.
Question 267 |
In the context of software testing, which of the following statements is/are NOT correct?
P: A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.
Q: A minimal test set that achieves 100% path coverage will generally detect more faults than one that achieves 100% statement coverage
R: A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage
P: A minimal test set that achieves 100% path coverage will also achieve 100% statement coverage.
Q: A minimal test set that achieves 100% path coverage will generally detect more faults than one that achieves 100% statement coverage
R: A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage
R only | |
Q only | |
P and Q only | |
Q and R only |
Question 267 Explanation:
A minimal test set that achieves 100% statement coverage will generally detect more faults than one that achieves 100% branch coverage
Question 268 |
Which of the following statements is/are TRUE?
P: In software engineering, defects that are discovered earlier are more expensive to fix
Q: A software design is said to be a good design, if the components are strongly cohesive and weakly coupled
Select the correct answer from the options given below:
P: In software engineering, defects that are discovered earlier are more expensive to fix
Q: A software design is said to be a good design, if the components are strongly cohesive and weakly coupled
Select the correct answer from the options given below:
P only | |
Q only | |
P and Q | |
Neither P nor Q |
Question 268 Explanation:
Statement-1: Earlier the defect is found lesser is the cost of defect. For example if error is found in the requirement specifications during requirements gathering and analysis, then it is somewhat cheap to fix it. The correction to the requirement specification can be done and then it can be re-issued.
Question 269 |
Software products need are adaptive maintenance for which of the following reasons?
To rectify bugs observed while the system is in use. | |
When the customers need the product to run on new platforms | |
To support the new features that users want it to support | |
To overcome wear and tear caused by the repeated use of the software. |
Question 269 Explanation:
Maintenance: Maintenance can be referred as a process of enhancement in the software product according to the changing requirements of users.
4 types of maintenance:
1. Adaptive – modifying the system to cope with changes in the software environment (DBMS, OS).
2. Perfective – implementing new or changed user requirements which concern functional enhancements to the software
3. Corrective – diagnosing and fixing errors, possibly ones found by users.
4. Preventive – increasing software maintainability or reliability to prevent problems in the future.
4 types of maintenance:
1. Adaptive – modifying the system to cope with changes in the software environment (DBMS, OS).
2. Perfective – implementing new or changed user requirements which concern functional enhancements to the software
3. Corrective – diagnosing and fixing errors, possibly ones found by users.
4. Preventive – increasing software maintainability or reliability to prevent problems in the future.
Question 270 |
Which of the following are the primary objectives of risk monitoring in software project tracking?
P: To assess whether predicted risks do, in fact, occur
Q: To ensure that risk aversion steps defined for the risk are being properly applied
R: To collect information that can be used for future risk analysis
P: To assess whether predicted risks do, in fact, occur
Q: To ensure that risk aversion steps defined for the risk are being properly applied
R: To collect information that can be used for future risk analysis
Only P and Q | |
Only P and R | |
Only Q and R | |
All the P,Q,R |
Question 270 Explanation:
Risk monitoring is a project tracking activity with three primary objectives:
(1) to assess whether predicted risks occur.
(2) to ensure that risk aversion steps defined for the risk are being properly applied; and
(3) to collect information that can be used for future risk analysis.
(1) to assess whether predicted risks occur.
(2) to ensure that risk aversion steps defined for the risk are being properly applied; and
(3) to collect information that can be used for future risk analysis.
Question 271 |
Module design is used to maximize cohesion and minimize coupling. Which of the following is the key to implement this rule?
Inheritance | |
Polymorphism | |
Encapsulation | |
Abstraction |
Question 272 |
Verification:
refers to the set of activities that ensure that software correctly implements a specific function | |
gives answer to the question - Are we building the product right ? | |
requires execution of software | |
both (A) and (B) |
Question 272 Explanation:
Verification: It refers to the set of activities that ensure that software
correctly implements a specific function.
While coding the programmer verifies that whether the code is working correctly or not.
Verification ensures “Are we building the product right”.
While coding the programmer verifies that whether the code is working correctly or not.
Verification ensures “Are we building the product right”.
Question 273 |
Which design metric is used to measure the compactness of the program in terms of lines of code?
Consistency | |
Conciseness | |
Efficiency | |
Accuracy |
Question 273 Explanation:
Consistency: The use of uniform design and documentation techniques throughout the software development project.
Conciseness: used to measure the compactness of the program in terms of lines of code.
Efficiency: It refers to the amount of computing resources and code required by a program to perform its function.
Accuracy: The precision of computations and control.
Conciseness: used to measure the compactness of the program in terms of lines of code.
Efficiency: It refers to the amount of computing resources and code required by a program to perform its function.
Accuracy: The precision of computations and control.
Question 274 |
Requirements prioritisation and negotiation belongs to:
Requirements validation | |
Requirements elicitation | |
Feasibility study | |
Requirements reviews |
Question 274 Explanation:
Requirement Engineering: The broad spectrum of tasks and techniques that lead to an understanding of requirements is called requirements engineering
Inception: At project inception, you establish a basic understanding of the problem, the people who want a solution, the nature of the solution that is desired, and the effectiveness of preliminary communication and collaboration between the other stakeholders and the software team.
Elicitation : To help overcome problems understanding, volatility, scope, you must approach requirements gathering in an organized manner.
Elaboration This task focuses on developing a refined requirements model that identifies various aspects of software function, behavior, and information..
Negotiation Customers, users, and other stakeholders are asked to rank requirements and then discuss conflicts in priority. Using an iterative approach that prioritizes requirements, assesses their cost and risk, and addresses internal conflicts, requirements are eliminated, combined, and/or modified so that each party achieves some measure of satisfaction.
Specification: A specification can be a written document, a set of graphical models, a formal mathematical model, a collection of usage scenarios, a prototype, or any combination of these.
Inception: At project inception, you establish a basic understanding of the problem, the people who want a solution, the nature of the solution that is desired, and the effectiveness of preliminary communication and collaboration between the other stakeholders and the software team.
Elicitation : To help overcome problems understanding, volatility, scope, you must approach requirements gathering in an organized manner.
Elaboration This task focuses on developing a refined requirements model that identifies various aspects of software function, behavior, and information..
Negotiation Customers, users, and other stakeholders are asked to rank requirements and then discuss conflicts in priority. Using an iterative approach that prioritizes requirements, assesses their cost and risk, and addresses internal conflicts, requirements are eliminated, combined, and/or modified so that each party achieves some measure of satisfaction.
Specification: A specification can be a written document, a set of graphical models, a formal mathematical model, a collection of usage scenarios, a prototype, or any combination of these.
Question 275 |
Adaptive maintenance is a maintenance which __________.
correct errors that were not discovered till testing phase | |
is carried out to port the existing software to a new environment. | |
improves the system performance | |
both (2) and (3) |
Question 275 Explanation:
Correction.: Even with the best quality assurance activities, it is likely that the customer will uncover defects in the software. Corrective maintenance changes the software to correct defects.
Adaptation. Over time, the original environment (e.g., CPU, operating system, business rules, external product characteristics) for which the software was developed is likely to change. Adaptive maintenance results in modifications to the software to accommodate changes to its external environment.
Enhancement/Perfective. As software is used, the customer/user will recognize additional functions that will provide benefit. Perfective maintenance extends the software beyond its original functional requirements.
Prevention. Computer software deteriorates due to change, and because of this, preventive maintenance, often called software reengineering, must be conducted to enable the software to serve the needs of its end users. In essence, preventive maintenance makes changes to computer programs so that they can be more easily corrected, adapted, and enhanced.
Adaptation. Over time, the original environment (e.g., CPU, operating system, business rules, external product characteristics) for which the software was developed is likely to change. Adaptive maintenance results in modifications to the software to accommodate changes to its external environment.
Enhancement/Perfective. As software is used, the customer/user will recognize additional functions that will provide benefit. Perfective maintenance extends the software beyond its original functional requirements.
Prevention. Computer software deteriorates due to change, and because of this, preventive maintenance, often called software reengineering, must be conducted to enable the software to serve the needs of its end users. In essence, preventive maintenance makes changes to computer programs so that they can be more easily corrected, adapted, and enhanced.