Software-Engineering
Question 1 |
Match the following:
(P) Condition coverage (i) Black-box testing (Q) Equivalence class partitioning (ii) System testing (R) Volume testing (iii) White-box testing (S) Alpha testing (iv) Performance testing
P-ii, Q-iii, R-i, S-iv | |
P-iii, Q-iv, R-ii, S-i | |
P-iii, Q-ii, R-iv, S-ii | |
P-iii, Q-i, R-ii, S-iv |
Equivalence class partitioning ⇒ is a software testing technique that divides the input data of a software unit into partitions of equivalent data from which test cases can be derived, which is nothing but black box testing. Hence B-1.
Volume testing ⇒ volume testing refers to testing a software application with certain amount of data which is nothing but system testing C-2.
Alpha testing ⇒ Alpha testing is simulated or actual operation testing by potential user/customers, which is nothing but performance testing. D-4.
Question 2 |
Consider the basic COCOMO model where E is the effort applied in person-months, D is the development time in chronological months, KLOC is the estimated number of delivered lines of code (in thousands) and ab, bb, cb, db have their usual meanings. The basic COCOMO equations are of the form
E = a b(KLOC)exp (b b, D = c b(E)exp (d b) | |
E = a b(KLOC)exp (b b, D = c b(E)exp (d b) | |
E = a bexp(b b), D = c b(KLOC)exp (d b) | |
E = a bexp(D b), D = c b(KLOC)exp (b b) |
Effort applied (E) = ab(KLOC)bb
Development time (D) = cb(E)db
Question 3 |
A software requirements specification(SRS) document should avoid discussing which one of the following?
User interface issues | |
Non-functional requirements | |
Design specification | |
Interfaces with third party software
|
Question 4 |
Which one of the following assertions concerning code inspection and code walkthrough is true?
Code inspection is carried out once the code has been unit tested | |
Code inspection and code walkthrough are synonyms | |
Adherence to coding standards is checked during code inspection
| |
Code walkthrough is usually carried out by an independent test team |
Question 5 |
Consider a software project with the following information domain characteristic for calculation of function point metric.
-
Number of external inputs (I) = 30
Number of external output (O) = 60
Number of external inquiries (E) = 23
Number of files (F) = 08
Number of external interfaces (N) = 02
It is given that the complexity weighting factors for I, O, E, F and N are 4, 5, 4, 10 and 7, respectively. It is also given that, out of fourteen value adjustment factors that influence the development effort, four factors are not applicable, each of he other four factors have value 3, and each of the remaining factors have value 4. The computed value of function point metric is __________.
612.06 | |
612.07 | |
612.08 | |
612.09 |
Question 6 |
Consider a software program that is artificially seeded with 100 faults. While testing this program, 159 faults are detected, out of which 75 faults are from those artificially seeded faults. Assuming that both are and seeded faults are of same nature and have same distribution, the estimated number of undetected real fault is _____ .
175 | |
176 | |
177 | |
178 |
Question 7 |
Match the following:
1) Waterfall model a) Specifications can be developed incrementally 2) Evolutionary model b) Requirements compromises are inevitable 3) Component-based c) Explicit recognition of risk software engineering 4) Spiral development d) Inflexible partitioning of the project into stages
1-a, 2-b, 3-c, 4-d | |
1-d, 2-a, 3-b, 4-c | |
1-d, 2-b, 3-a, 4-c | |
1-c, 2-a, 3-b, 4-d |
Question 8 |
Which one of the following is TRUE?
The requirements document also describes how the requirements that are listed in the document are implemented efficiently. | |
Consistency and completeness of functional requirements are always achieved in practice. | |
Prototyping is a method of requirements validation. | |
Requirements review is carried out to find the errors in system design. |
Question 9 |
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 |
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.
Question 10 |
Match the problem domains in GROUP I with the solution technologies in GROUP II
GROUP I GROUP II (P) Service oriented computing (1) Interoperability (Q) Heterogeneous communicating systems (2) BPMN (R) Information representation (3) Publish-find-bind (S) Process description (4) XML
P-1, Q-2, R-3, S-4 | |
P-3, Q-4, R-2, S-1 | |
P-3, Q-1, R-4, S-2 | |
P-4, Q-3, R-2, S-1 |
Question 11 |
The following figure represents access graphs of two modules M1 and M2. The filled circles represent methods and the unfilled circles represent attributes. If method m is moved to module M2 keeping the attributes where they are, what can we say about the average cohesion and coupling between modules in the system of two modules?

There is no change. | |
Average cohesion goes up but coupling is reduced. | |
Average cohesion goes down and coupling also reduces. | |
Average cohesion and coupling increase. |
Question 12 |
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 13 |
The Function Point (FP) calculated for a software project 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 14 |
The availability of a 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?
205 days | |
300 days | |
500 days | |
700 days |
Question 15 |
In a data flow diagram, the segment shown below is identified as having transaction flow characteristics, with p2 identified as the transaction center

A first level architectural design of this segment will result in a set of process modules with an associated invocation sequence. The most appropriate architecture is
p1 invokes p2, p2 invokes either p3, or p4, or p5 | |
p2 invokes p1, and then invokes p3, or p4, or p5 | |
A new module Tc is defined to control the transaction flow. This module Tc first invokes p1 and then invokes p2, p2 in turn invokes p3, or p4, or p5 | |
A new module Tc is defined to control the transaction flow. This module Tc invokes p2, p2 invokes p1, and then invokes p3, or p4, or p5 |
Question 16 |
In a software project, COCOMO (Constructive Cost Model) is used to estimate
effort and duration based on the size of the software | |
size and duration based on the effort of the software | |
effort and cost based on the duration of the software | |
size, effort and duration based on the cost of the software |
Question 17 |
The diagram that helps in understanding and representing user requirements for a software project using UML (Unified Modeling Language) is:
Entity Relationship Diagram | |
Deployment Diagram | |
Data Flow Diagram | |
Use Case Diagram |
Question 18 |
A software organization has been assessed at SEI CMM Level 4. Which of the following does the organization need to practice beside Process Change Management and Technology Change Management in order to achieve Level 5?
Defect Detection | |
Defect Prevention | |
Defect Isolation | |
Defect Propagation |
Question 19 |
A software configuration management tool helps is
keeping track of the schedule based on the milestones reached | |
maintaining different versions of the configurable items | |
managing manpower distribution by changing the project structure | |
all of the above |
Question 20 |
In a particular Unix OS, each data block is of size 1024 bytes, each node has 10 direct data block addresses and three additional addresses: one for single indirect block, one for double indirect block and one for triple indirect block. Also, each block can contain addresses for 128 blocks. Which one of the following is approximately the maximum size of a file in the file system?
512 MB | |
2 GB | |
8 GB | |
16 GB |
= (10 + 27 + 27 × 27 + 7 × 7 × 7) × 210
≈ 231
≈ 2 GB
Question 21 |
A software project involves execution of 5 tasks T1, T2, T3, T4 and T5 of duration 10, 15, 18, 30 and 40 days, respectively. T2 and T4 can start only after T1 completes. T3 can start after T2 completes. T5 can start only after both T3 and T4 complete. What is the slack time of the task T3 in days?
0 | |
3 | |
18 | |
30 |
Question 22 |
Consider the following program module:
int module1 (int x, int y) { while (x! = y) { if (x > y) x = x - y, else y = y - x; } return x; }What is Cyclomatic complexity of the above module?
1 | |
2 | |
3 | |
4 |
Question 23 |
Assume that the delivered lines of code L of a software is related to the effort E in person months and duration t in calendar months by the relation L = P* (E/B)1/3 * t4/3, where P and B are two constants for the software process and skills factor. For a software project, the effort was estimated to be 20 person months and the duration was estimated to be 8 months. However, the customer asked the project team to complete the software project in 4 months. What would be the required effort in person months?
10 | |
40 | |
160 | |
320 |
Question 24 |
A software was tested using the error seeding strategy in which 20 errors were seeded in the code. When the code was tested using the complete test suite, 16 of the seeded errors were detected. The same test suite also detected 200 non-seeded errors. What is the estimated number of undetected errors in the code after this testing?
4 | |
50 | |
200 | |
250 |
Question 25 |
What is the availability of a software with the following reliability figures?
Mean Time Between Failure (MTBF) = 25 days Mean Time To Repair (MTTR) = 6 hours
1% | |
24% | |
99% | |
99.009% |
Question 26 |
Greater than 0.9 | |
Equal to 0.9 | |
At most 0.81 | |
At least 0.81 |
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 27 |
Use Case | |
Class Diagram | |
Analysis Diagram | |
Swimlane Diagram |
Question 28 |
Black Box Testing | |
Alpha Testing | |
Recovery Testing | |
White Box Testing |
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 29 |
SPICE(ISO/IEC15504) | |
Standard CMMI Assessment Method for process improvement | |
ISO 9001:2000 | |
IEEE 2000:2001 |
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 30 |
what processes will be used | |
who generates data and who processes it | |
what each person in an organization does | |
which data will be generated |
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 31 |
state of object cannot be represented | |
state is irrelevant | |
state is represented as an attribute | |
state is represented as a result of an operation |
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 32 |
Waterfall | |
Musa | |
COCOMO | |
Rayleigh |
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 33 |
Calculated from user requirement | |
Calculated from lines of code | |
Calculated from software complexity assessment | |
None of the above |
→ 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 34 |
Logical Cohesion | |
Coincidental Cohesion | |
Procedural Cohesion | |
Communicational Cohesion |

Question 35 |
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 |
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 36 |
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 37 |
develop and refine an organization’s software development process | |
develop the software | |
test the software | |
All of the above |
CMM levels:
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimizing
Question 38 |
Spiral model | |
Prototyping model | |
Waterfall model | |
Capability maturity model |
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 39 |

21 | |
19 | |
20 | |
10 |
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 40 |
Corrective maintenance | |
Perfective maintenance | |
Adaptive maintenance | |
Preventive maintenance |
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 41 |
High cohesion and high coupling | |
High cohesion and low coupling | |
Low cohesion and high coupling | |
Low cohesion and low coupling |
→ So in the context of modular software design, there should be high cohesion and low coupling.
Question 42 |
Reliability | |
Robustness | |
Fault tolerance | |
Portability |
→ Robustness is the ability of a computer system to cope with errors during execution and cope with erroneous input
Question 43 |
Maintainability | |
Portability | |
Robustness | |
None of the mentioned |
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 44 |
controlling changes to the source code | |
choice of a hardware configuration for an application | |
controlling documentation changes | |
maintaining versions of software |
Question 45 |

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 |
L2 = 2X
Total cost of project: x/1000*1000000+5+100000
=2x/10000*750000+50000*5
=100×+500000
=150×+250000
⟹50×=500000-250000
Question 46 |
196.77 | |
206.56 | |
199.56 | |
210.68 |
Effort Applied (E) = ab(KLOC)bb [ person-months ]
= 2.2 x(20)1.50
= 2.2 x 89.44
= 196.77
Question 47 |
Iteration size | |
Cost | |
Adopted process such as Rational Unified Process or Extreme Programming | |
Risk |
→ 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 48 |
Verification | |
Validation | |
Maintenance | |
Modeling |
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 49 |
Regression Testing | |
Integration Testing | |
Unit Testing | |
System Testing |
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 50 |
LEVEL-0 DFD
| |
LEVEL-1 DFD | |
LEVEL-2 DFD | |
LEVEL-3 DFD |
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 51 |
Boundary condition of the software | |
Control structure of the software | |
Functional requirement of the software | |
Independent paths of the software |
Question 52 |
Warnier Diagram enables the analyst to represent | |
Information Hierarchy | |
Data Flow | |
State Transition |
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 53 |

3 | |
4 | |
5 | |
6 |
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 54 |
50% | |
60% | |
70% | |
10% |
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 55 |
unit testing | |
beta testing | |
stress testing | |
mutation testing |
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 56 |
4 | |
5 | |
6 | |
7 |
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 57 |
Pathological coupling | |
Control coupling | |
Data coupling | |
Message coupling |
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 58 |
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 |
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 59 |
Initial | |
Measurable | |
Repeatable | |
Optimized |
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimized
Question 60 |
0.665 to 0.95 | |
At the most 0.665 | |
At the most 0.95 | |
At least 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 61 |
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 |
→ 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 62 |
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) |
- 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 63 |
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)
|
→ 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 64 |
Which one of the following is not typically provided by Source Code Management Software ?
Synchronisation
| |
Versioning and Revision history | |
Syntax highlighting
| |
Project forking
|
→ Source Code Management Software includes
1. Synchronisation
2. Versioning and Revision history
3. Project forking
Question 65 |
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%
|
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 66 |
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) |
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 67 |
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
|
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 68 |
A software design pattern often used to restrict access to an object is :
adapter | |
decorator | |
delegation
| |
proxy
|
→ 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 69 |
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
|
→ 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 70 |
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
|
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 71 |
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 |
→ 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 72 |
Rapid Application Development | |
Rapid Application Design | |
Relative Application Development | |
Recent Application Development |
Question 73 |
Project planning | |
Project estimation | |
Scope management | |
All mentioned above |
Question 74 |
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 |
● 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 75 |
Waterfall model | |
Prototyping | |
Iterative | |
All of these |
● 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 76 |
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 |
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 77 |
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 |
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 78 |
Cyclomatic number | |
Hamiltonian Circuit | |
Eulerian cycle | |
None of these |
● 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 79 |
10% | |
20% | |
40% | |
50% |
● 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 80 |

19 | |
21 | |
20 | |
10 |
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 81 |

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 |
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 82 |
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
|
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 83 |
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
|
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 84 |

4000 | |
5000 | |
4333 | |
4667 |
Now,
(x/10000)*1000000 + 5*100000 = (2x/10000)*750000 + 5*50000
Solving for x, we get x =5000
Question 85 |
234.25 | |
932.50 | |
287.80 | |
122.40 |
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 86 |
Functional requirements | |
Non Functional requirements | |
Goals of implementation | |
Algorithm for software implementation |
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
Question 87 |
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 88 |
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 |
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 89 |
Rotation | |
Scaling | |
Translation | |
Morphism |
→ 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 90 |
Level 0 DFD | |
Level 1 DFD | |
Level 2 DFD | |
Level 3 DFD |
→ 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 91 |
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)
|
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 92 |
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 |
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 93 |
Non reusable module | |
serially usable | |
Re-enterable module | |
recursive module |
● 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 94 |
n(n-1)/2 | |
nlogn | |
n | |
n(n+1)/2 |
● 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 95 |
reliability | |
robustness | |
fault tolerance | |
Portability |
● 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 96 |
E=a*(KLOC) 6 | |
E=a*(KLOC) 5 | |
E=a*(KLOC) 7 | |
E=a*(KLOC) 3 | |
None of These |
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 97 |
3.6PM | |
0.36PM | |
0.0036PM | |
7.23PM |
=3.6(1) 1.2 =3.6 Programmer months.
Question 98 |
Modular approach | |
Top down approach | |
Bottom up approach | |
Left right 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.
Question 99 |
Which of the following is not one of the principles of agile software development method ?
Following the plan
| |
Embrace change
| |
Customer involvement | |
Incremental delivery |
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 100 |
Suppose a cloud contains software stack such as Operating system, Application software, etc. This model is referred as _________ model.
SaaS | |
IaaS | |
MaaS | |
PaaS
|
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 101 |
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
|
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 102 |
Functional requirement | |
Goals of implementation | |
Nonfunctional requirement | |
Algorithm for software implementation |
An SRS document should clearly document the following aspects of a system: Functional Requirements, Non-Functional Requirements and Goals of implementation
Question 103 |
White box testing | |
Integrated testing | |
Acceptance testing | |
Black box testing |
Question 104 |
Indirect measures | |
Coding | |
Direct measures | |
none of the above |
→ It comes under direct measures.
Question 105 |
Compatibility | |
Interoperability | |
Performance | |
Security |
● 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 106 |
Data flow | |
Data storage | |
Data structures | |
Data elements |
● 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 107 |
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 |
● 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 108 |
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 |
● 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 109 |
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 110 |
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 |
● 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 111 |
205 days | |
300 days | |
500 days | |
700 days |
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 112 |
Acceptance testing | |
Integration testing | |
System testing | |
Unit testing |
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 113 |
The productivity if effort = 70 percent-month is
110.54 | |
408.74 | |
304.78 | |
220.14 |

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 114 |
Which of the following is a white box testing technique?
Data flow testing
| |
Equivalence class testing
| |
Cause effect graphing
| |
State based 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 115 |
Independency | |
low cohesiveness | |
High coupling | |
Multifunctional |
Question 116 |
50% | |
10% | |
60% | |
70% |
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 117 |
Data flow diagram | |
Prototype model | |
Entity Relationship diagram | |
Data dictionary |
Question 118 |
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 |
● They do not usually have very good user interfaces.
Question 119 |
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 |
→ 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 120 |
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 |
● They do not usually have very good user interfaces.
Question 121 |
0 | |
2 | |
3 | |
1 |
→ The modality is 1 if an occurrence of the relationship is mandatory
Question 122 |
Which of the following is NOT a goal of the software testing?
Failure detection
| |
Fault detection
| |
Size reduction | |
Error detection
|
Question 123 |
What is the Cyclomatic Complexity of the following flow-graph of a software code?

10 | |
4 | |
8 | |
2 |
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 124 |
Independency | |
Low Cohesiveness | |
High Coupling | |
Multifunctional |
● 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 125 |
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 |
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 126 |
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 127 |
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 128 |
Re-constructing the original source code from the existing machine (low level) code program and modifying it to make it more user - friendly. | |
Scrapping the source code of a software and re writing it entirely from scratch. | |
Re-organising and modifying existing software systems to make them more maintainable. | |
Translating source code of an existing software to a new machine (low level) language. |
→ Reengineering is the modification of a software system that takes place after it has been reverse engineered, generally to add new functionality, or to correct errors.
Question 129 |
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 130 |
(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) |

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 131 |
Path Testing | |
Integration Testing | |
Unit Testing | |
Regression Testing |
→ 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 132 |
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 133 |
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 134 |
Ability to undergo change | |
Adaptability to new environments | |
Operational characteristics | |
Production costs and scheduling |
1. Product operation factors − Correctness, Reliability, Efficiency, Integrity, Usability.
2. Product revision factors − Maintainability, Flexibility, Testability.
3. Product transition factors − Portability, Reusability, Interoperability.

Question 135 |
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 |
→ 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 136 |
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. |
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 137 |
Adapter | |
Decorator | |
Delegation | |
Proxy |
→ Decorator will attach additional responsibilities to an object dynamically keeping the same interface.
→ Decorators provide a flexible alternative to subclassing for extending functionality.
Question 138 |
n 1 / n 2 | |
n 2 / n 1 | |
n 1 + n 2 | |
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
Question 139 |
The difficulty in accommodating changes after requirement analysis. | |
The difficult in accommodating changes after feasibility analysis. | |
The system testing | |
The maintenance of system. |
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 140 |
iterative model | |
prototype model | |
spiral model | |
waterfall 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)
Question 141 |
4k – 1 | |
4k | |
4k + 1 | |
2 k – 1 |
Question 142 |
Robustness | |
Correctness | |
Reliability | |
Accuracy |
→ 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 143 |
1 + (S 3 / S 1 ) | |
1 - (S 3 / S 1 ) | |
1 + (S 1 / S 3 ) | |
1 - (S 1 / S 3 ) |
S3 = The number of modules whose correct function depends on prior processing.
Module not dependent on prior processing is 1- (S3/S1)
Question 144 |
Rapid Application Development | |
Rational Unified Process | |
Evolutionary Model | |
Waterfall 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 145 |
Requirement analysis | |
Risk analysis | |
Design | |
Coding |
1.Feasibility Study
2.Analysis
3.Design
4.Coding and Testing
5.Integration & System testing
6.Maintenance
Question 146 |
Accuracy | |
Reliability | |
Correctness | |
Robustness |
→ Robustness is the ability of a computer system to cope with errors during execution and cope with erroneous input.
→ Accuracy is a description of systematic errors, a measure of statistical bias.
→ Software reliability is the probability that software will work properly in a specified environment and for a given amount of time.
→ Correctness of an algorithm is asserted when it is said that the algorithm is correct with respect to a specification. Functional correctness refers to the input-output behaviour of the algorithm (i.e., for each input it produces the expected output).
Question 147 |
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. |
→ 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 148 |
Prototyping | |
Iterative | |
Time-boxing | |
Glass-boxing |
Time boxing model:
The development is done iteratively as in the iterative enhancement model and each iteration is done in a timebox of fixed duration. The functionality to be developed is adjusted to fit the duration of the timebox. Moreover, each timebox is divided into a sequence of fixed stages where each stage performs a clearly defined task (analysis, implementation, and deploy) that can be done independently. This model also requires that the time duration of each stage is approximately equal so that pipelining concept is employed to have the reduction in development time and product releases.
Question 149 |

(a)-(iii), (b)-(iv), (c)-(i), (d)-(ii) | |
(a)-(ii), (b)-(i), (c)-(iv), (d)-(iii) | |
(a)-(iv), (b)-(ii), (c)-(iii), (d)-(i) | |
(a)-(iii), (b)-(i), (c)-(iv), (d)-(ii) |
Function-oriented metrics → uses number of external interfaces as one of the measurement parameter
Extended Function Point metrics → uses algorithm characteristics as one of the measurement parameter
Function point → originally designed to be applied to business information systems.
Question 150 |
Validation testing | |
Integration testing | |
Regression testing | |
System testing |
It answers to the question, Are we building the right product?
Question 151 |
Waterfall model | |
RAD model | |
Prototyping model | |
Incremental 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 152 |
Abstraction concept | |
Refinement concept | |
Information hiding concept | |
Modularity |
→ Cohesion is an extension of Information hiding concept.
Question 153 |
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). |
1. Compare actual and planned progress and costs.
2. Identify the activities, milestones and deliverables produced by a project.
Question 154 |
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. |
→ 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 155 |
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 |
→ So in the context of modular software design there should be high cohesion and low coupling.
Question 156 |
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 |
Essential components:
1.Software size estimation
2.Effort estimation
3.Time estimation
4.Cost estimation
Question 157 |
Number of errors present in software | |
Documentation | |
Testing suites | |
Development Processes |
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
Question 158 |
Calculated from user requirements | |
Calculated from Lines of code | |
Calculated from software s complexity assessment | |
None of the above |
→ 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 159 |
Acceptance testing | |
Integration testing | |
Regression testing | |
Series testing |
→ 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 160 |
logical cohesion | |
coincidental cohesion | |
procedural cohesion | |
communicational cohesion |
Given a list is least desirable to most desirable types in module cohesion

Question 161 |
Quality of the design | |
Programmer s experience | |
Number of error | |
Set of user requirements |
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
Question 162 |
Layer of Definement | |
Layer of Construction | |
Layer of abstraction | |
None of the above |
Question 163 |
Preparation of comprehensible plan | |
Preparation of the various stages of development | |
Ad-hoc planning | |
Requirement analysis |
→ 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 164 |
CASE Tool | |
RAD Tool | |
Reverse engineering tool | |
None of these |
→ 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 165 |
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. |
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 166 |
Linear sequential model | |
Prototyping model | |
The spiral model | |
COCOMO model |
Question 167 |
(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 168 |
Number of lines of code (LOC) | |
Number of man years | |
Number of function points (FP) | |
All of the above | |
Both LOC and FP |
→ 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 169 |
Content coupling | |
Data coupling | |
Control coupling | |
Common 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 170 |
Case tool | |
RAD tool | |
Reverse engineering | |
None of these |
→ 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 171 |
[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 |
Cost Performance Index = BCWP stands for Budgeted Cost of Work Performed / ACWP stands for Actual Cost of Work Performed
CPI = BCWP/ACWP
Question 172 |
risk magnitude and risk impact | |
risk probability and risk impact | |
risk maintenance and risk impact | |
risk development and risk impact |
Question 173 |
quality of the design | |
number of errors present | |
software engineer’s experience | |
user requirement |
→ Software Reliability is the probability of failure-free software operation for a specified period of time in a specified environment.
Question 174 |
First | |
Final | |
Last | |
Middle |
Question 175 |
A graph | |
A tree | |
A Eulars graph | |
None of the above |
1. Functional WBS
2. Activity WBS
WBS tree structure:

Question 176 |
c=e-n+2p | |
c=e-n-2p | |
c=e+n+2p | |
c=e-n* 2p |
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 177 |
Highest | |
Lowest | |
Internal | |
External |
→ So in the context of modular software design there should be high cohesion and low coupling.
Question 178 |
Requirement specifications | |
Prevailing process description | |
Data source identification | |
All the above |
Question 179 |
software design | |
software cost estimation | |
software cost approximation | |
software analysis |
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 180 |
Framework activities | |
Umbrella activities | |
Planning activities | |
Construction activities |
→ 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 181 |
Performed | |
Managed | |
Defined | |
Optimized |
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 182 |
Design | |
Architecture | |
Process | |
Requirement |
Question 183 |
Simple and computable | |
Consistent and objective | |
Consistent in the use of units and dimensions | |
Programming language dependent |
Question 184 |
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. |
1. Number of regions + 1
2. Predicate + 1
3. Edges-Vertices+2
Question 185 |
Correct | |
Consistent | |
Unambiguous | |
Verifiable |
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 186 |
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 |
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 187 |
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 |
Reverse engineering: It is also called as back engineering which is done to examine the working of a product.
Question 188 |
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 |
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 189 |


(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) |
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 190 |
0.725 | |
0.923 | |
0.849 | |
0.524 |
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 191 |
Key Process Area | |
Key Product Area | |
Key Principal Area | |
Key Performance Area |
A Process Area is a cluster of related practices in an area that, when implemented collectively, satisfy a set of goals considered important for making significant improvement in that area. All CMMI process areas are common to both continuous and staged representations.
Question 192 |
Detailed multi source cost and schedule estimation. | |
Design cost | |
Incremental development | |
Information hiding |
Question 193 |
Software construction | |
Software evolution | |
Software architecture | |
Software reuse |
Question 194 |
10 | |
12 | |
14 | |
20 |
→ The adjusted function point denoted by FP is given by the formula:
FP = total UFP * (0.65 + (0.01 * Total complexity adjustment value)) or
FP = total UFP * (Complexity adjustment factor)
→ Total complexity adjustment value is counted based on responses to questions called complexity weighting factors in the table below. Each complexity weighting factor is assigned a value (complexity adjustment value) that ranges between 0 (not important) to 5 (absolutely essential).
Table Adjusted Function Points

Question 195 |
Functional testing | |
Development testing | |
Data flow testing | |
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 196 |
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 |
→ A software program that runs on the client as well as on the application server used in distributed systems.
Question 197 |
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 |
→ 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 198 |
Following the plan | |
Embrace change | |
Customer involvement | |
Incremental delivery |
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 199 |
SaaS | |
IaaS | |
MaaS | |
PaaS |
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 200 |
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. |
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 201 |
ISO9001 | |
RMMM | |
CMM | |
None of the above |
CMM levels:
→Initial
→Repeatable
→Defined
→Managed
→Optimizing
Question 202 |
E-R diagram | |
Data flow diagram | |
Software architecture
| |
Software design |
Question 203 |
Waterfall model | |
Prototyping model | |
Incremental model | |
Evolutionary Development model |
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 204 |
White box | |
Black box | |
Regression | |
Smoke |
Black box testing methods are
→Graph-Based Testing Methods
→Equivalence Partitioning
→Boundary Value Analysis
→Orthogonal Array Testing
Question 205 |
(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) |
→Correct and unambiguous
→Complete and consistent
→Ranked for importance and/or stability and verifiable
→Modifiable and Traceable
Question 206 |
- 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) |
- 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 207 |

(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) |
→ 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 208 |
Synchronisation | |
Versioning and Revision history | |
Syntax highlighting | |
Project forking |
→ Source Code Management Software includes
1. Synchronisation
2. Versioning and Revision history
3. Project forking
Question 209 |
96.9924% | |
97.9924% | |
98.9924% | |
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 210 |
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 |
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 211 |
adapter | |
decorator | |
delegation | |
proxy |
→ 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 212 |
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 |
→ 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 213 |
Formal specification | |
Dynamic verification | |
Incremental development | |
Statistical testing of the system |
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 214 |
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 |
→ 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 215 |
Flow oriented analysis | |
Class based analysis | |
Both of the above | |
None of the above |

Question 216 |
Initial, Repeatable, Defined, Managed, Optimized. | |
Primary, Secondary, Defined, Managed, Optimized. | |
Initial, Stating, Defined, Managed, Optimized. | |
None of the above |
CMM levels: →Initial
→Repeatable
→Defined
→Managed
→Optimizing
Question 217 |
Rapid and Design | |
Rapid Aided Development | |
Rapid Application Development | |
Rapid Application Design |
→ 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 218 |
system testing | |
white box testing | |
white box testing | |
unit testing |
→Data flow testing
→Branch testing
→Statement coverage
→Decision coverage
→Modified condition/decision coverage
→Prime path testing
→Path testing
Question 219 |
Debugging | |
Testing | |
Designing | |
Software quality assurance |
Question 220 |
Coupling | |
Modularity | |
Cohesion | |
Granularity |
→ In the context of modular software design there should be high cohesion and low coupling.
Question 221 |
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 |
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 222 |
Requirement elicitation | |
Requirement analysis | |
Requirement design | |
Requirement documentation |
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 223 |
Alpha testing | |
Beta testing | |
Regression testing | |
None of the above |
→ 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 224 |
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 |
1. Business application
2. Internal format conversion
3. EDI translator
4. EDI envelope

Question 225 |
program | |
software | |
within budget | |
software within budget in the given schedule |
Question 226 |
CMM level 2 | |
CMM level 3 | |
CMM level 5 | |
All of the above
|
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 227 |
are we building the product right | |
are we building the right product | |
verification of fields | |
None of the above |
→ Verification: Are we building the product right?
→ Validation: Are we building the right product?
Question 228 |
minimize cohesion and maximize coupling | |
maximize cohesion and minimize coupling | |
maximize cohesion and maximize coupling | |
minimize cohesion and minimize coupling |
→ 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 229 |
quality of the design | |
number of errors present | |
software engineers experience | |
user requirement |
→ 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 230 |
Spiral model | |
Component based model | |
Prototyping | |
Waterfall model |
Question 231 |
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. |
→ 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 232 |
e | |
n | |
e – n + p | |
e – n + 2p |
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 233 |
adaptive maintenance | |
perfective maintenance | |
corrective maintenance | |
none of the above |
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 234 |
reverse engineering | |
re-engineering | |
reuse | |
all of the above |
Question 235 |
Functional testing | |
Path testing | |
Stress testing | |
Regression 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.
Question 236 |
Risk magnitude and risk impact | |
Risk probability and risk impact | |
Risk maintenance and risk impact | |
Risk development 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
Question 237 |
Process | |
Manufacturing | |
Method | |
Tools |
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 238 |
Specification and design | |
System Analysis | |
Testing | |
None of the above |
1. System Analysis
2. Specification and design
3. Coding and unit testing
4. Maintenance
Question 239 |
Communication, planning, modelling, construction, deployment | |
Communication, risk management, measurement, production, reviewing | |
Analysis, designing, programming, Debugging, maintenance | |
Analysis, planning, designing, programming, testing |
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 240 |
Management Myths | |
Customer Myths | |
Practitioner Myths | |
All of the above |
Question 241 |
COmposite COst MOdel | |
COnstructive COst MOdel | |
COnstructive Composite MOdel | |
COmprehensive Construction MOdel |
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 242 |

a-iii, b-ii, c-iv, d-i | |
a-ii, b-iii, c-iv, d-i | |
a-i, b-ii, c-iv, d-iii | |
a-i, b-ii, c-iii, d-iv |
Correctness→ Meets the functional requirements
Predictable→ Process is under statistical control
Reliable→ Program does not fail for a specified time in a given environment
Question 243 |
Length of code | |
Size of software | |
Functionality of software | |
None of the above |
→ 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 244 |
High module coupling, High module cohesion | |
High module coupling, Low module cohesion | |
Low module coupling, High module cohesion | |
Low module coupling, Low module cohesion |
→ Coupling and Cohesion are used in software design. Cohesion measures strength of a module while coupling measures interdependency between modules.
Question 245 |
Characters of the movie “Black” | |
I–O is hidden | |
Design is hidden | |
Users are hidden |
Question 246 |
test the software as an end product | |
expand design details | |
refine and establish requirements gathering | |
None of the above |
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 247 |
Error correction | |
Adaptation | |
Implementation of Enhancement | |
Establishing scope |
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 248 |
Functional Description | |
Cost | |
Schedule | |
Technical Analysis |
→ 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 249 |
Abraham Silberschatz | |
Barry Boehm | |
C.J. Date | |
D.E. Knuth |
Question 250 |
to represent information hierarchy in a compact manner | |
to further identify requirement | |
to estimate the total cost involved | |
None of the above |
Question 251 |
reliable software | |
cost effective software | |
reliable and cost effective software | |
none of the above |
Question 252 |
Waterfall model | |
Prototyping | |
Iterative | |
None of these |
Question 253 |
top-down | |
bottom-up | |
random | |
centre fringing |
Question 254 |
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 255 |
Product | |
Process | |
Product and Process | |
None of the above |
CMM levels:
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimizing
Question 256 |
Programs | |
Data | |
Documentation | |
All of the above |
Question 257 |
ISO 9000 | |
ISO 9001 | |
ISO 9003 | |
ISO 9000–3 |
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 258 |
White Box | |
Black Box | |
Boundary value analysis | |
All of the above |
Question 259 |
Size measurement | |
Cost measurement | |
Design recovery | |
All of the above |
Question 260 |
Process | |
Methods | |
Tools | |
All |
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 261 |
Internal error | |
External error | |
Inherent error | |
Logic error |
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 262 |
(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) |
1. Cost and schedule estimates.
2. Software product reliability predictions.
3. Managing the development process.
Question 263 |
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. |
Black box testing methods are
1. Graph-Based Testing Methods
2. Equivalence Partitioning
3. Boundary Value Analysis
4. Orthogonal Array Testing
Question 264 |
Verification | |
Validation | |
Both verification and validation | |
None of the above |
→ 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 265 |
level 0 | |
level 3 | |
level 4 | |
level 1 |
CMM levels:
1. Initial
2. Repeatable
3. Defined
4. Managed
5. Optimizing
Question 266 |
Product quality estimation | |
Product complexity estimation
| |
Product cost estimation | |
All of the above |
Question 267 |
a top down approach. | |
a bottom up approach. | |
a sequential approach. | |
a consequential approach. |
Phases:
1. Feasibility study
2. Analysis
3. Design
4. Coding & Unit testing
5. Integration & System Testing
6. Maintenance
Question 268 |
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. |
→ 14 Value adjustment factors are using in functional points maximum.
Question 269 |
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 270 |
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 271 |
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. |
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 272 |
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 273 |
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 274 |
always the error code | |
the list of mistakes done by the user displayed | |
a non-judgmental approach | |
the past records of the occurrence of the same mistake |
Question 275 |
of paucity of examples | |
the data can be totally incorrect | |
the expertise and resource available are not used | |
the problem is being over simplified |