Software Engineering is part of Computer Science and holds 1,969 questions with answers, free to read and with no account needed.
Questions from this area appear in PPSC, FPSC, NTS, KPPSC and SPSC papers. Each guide explains how that paper is built and which subjects carry it.
Attempt each question before revealing the answer, and keep a note of the ones you get wrong — those are the topics worth reading about properly. If an answer looks wrong, there is a link to report it on every question.
Answer: A. Product Metrics
Size and complexity directly characterize the software product being engineered by the development team. Classifying these attributes as product metrics aligns with standard software measurement frameworks. Evaluating th...
Answer: C. Morphology Metrics
Morphology metrics evaluate overall architectural design patterns rather than individual software components. Component-level metrics focus inward on specific modules measuring complexity cohesion and coupling. Excluding...
Answer: D. All of the Mentioned
Quality complexity and reliability are indirect product measures because they cannot be measured directly in physical units. These attributes are derived mathematically or logically from direct measures such as lines of...
Answer: B. open paradigm
The open paradigm blends closed control structures with random paradigm innovation flexibility. This approach balances formal management oversight with creative developer problem solving. Teams benefit from structured gu...
Answer: D. lines of control
In architectural graph metrics, the variable 'a' specifically stands for the number of arcs. Arcs represent the control connections or calling relationships linking different modules together. Dividing arcs by the node c...
Answer: D. “fan out” of module i
In structural complexity formulas f symbolizes the fan-out of module i. Fan-out counts how many other modules are called by module i. Higher fan-out values indicate greater coupling and architectural complexity. Complexi...
Answer: A. Market
Market conditions drive business strategy rather than directly dictating internal software quality or performance. People, product, and technology constitute the core internal drivers of software engineering capability....
Answer: A. in the current release
Software Maturity Index formulas track changes across consecutive software release cycles to measure stability. The variable Mt explicitly denotes the total number of modules present in the current release. Mathematical...
Answer: B. Technology risks
Technology risks originate directly from the specific hardware or software technologies utilized to build the system. These risks encompass uncertainties regarding tool compatibility performance bottlenecks and unproven...
Answer: D. all of the mentioned
Dynamic web pages serve as a metric to estimate size, complexity, and effort. Database-driven content generation adds significant complexity to web engineering projects. Counting dynamic pages helps planners forecast the...
Answer: A. Technology change
Technology change occurs when foundational platforms or tools become obsolete due to newer advancements. Systems built on older frameworks face severe maintenance challenges when the underlying stack changes. This specif...
Answer: B. Software Maturity Index
SMI stands for Software Maturity Index in quality metric analyses. It tracks how stable a software product becomes across multiple releases. This index helps managers decide when a product is ready for deployment. Softwa...
Answer: C. Albrecht
Allan Albrecht originally formulated function points to quantify software size independently of programming languages. His pioneering work introduced a structured way to measure functionality delivered to end users. Attr...
Answer: B. Testing
Statement and branch coverage metrics measure how thoroughly test cases execute source code paths. Testing phases utilize these coverage indicators to identify untested code blocks and potential logic flaws. Evaluating b...
Answer: B. Process Metrics
The percentage of modules inspected is classified as a process metric used to evaluate software development effectiveness. Process metrics focus on the quality and productivity of the methods used to build the software s...
