Examius
🇮🇳 UGC NET Computer Science · flashcards
UGC NET Computer Science Software Engineering Flashcards
60 question-and-answer cards covering Software Engineering as it is examined in UGC NET Computer Science. 24 of them are printed below, taken from across the deck — no signup, no paywall on the preview.
24 sample cards from the Software Engineering deck
Sampled from the end of the deck, so these are different cards from the ones shown on the syllabus page.
What are the six quality characteristics defined by ISO 9126?
Functionality, Reliability, Usability, Efficiency, Maintainability, and Portability—each further broken into sub-characteristics.
Differentiate Quality Assurance (QA) from Quality Control (QC).
QA is process-oriented—preventing defects by improving processes (audits, standards, reviews). QC is product-oriented—detecting defects in the actual product through inspection and testing.
What are the main strategies for risk mitigation, monitoring, and management (RMMM)?
Mitigation: avoid the risk/reduce its probability. Monitoring: track factors indicating whether a risk is becoming more/less likely. Management: contingency plans to handle the risk if it materializes (RMMM plan).
How is risk exposure (impact) computed in risk projection?
Risk Exposure (RE) = Probability of the risk × Cost (impact) if the risk occurs. It quantifies the overall impact for prioritization.
Distinguish project risks, technical risks, and business risks.
Project risks threaten the schedule/resources/cost; technical risks threaten the quality/timeliness of the product (design, implementation); business risks threaten the viability of the software (market, budget, strategy).
What is software reliability and how is MTBF expressed?
The probability of failure-free operation for a specified time in a specified environment. MTBF (Mean Time Between Failures) = MTTF + MTTR; Availability = MTTF / (MTTF + MTTR) × 100%.
What is Function Point (FP) estimation based on?
Measuring functionality from the user's view using five information domain values: external inputs, external outputs, external inquiries, internal logical files, and external interface files—weighted and adjusted by 14 complexity factors.
State the Function Point formula.
FP = Count Total × [0.65 + 0.01 × Σ(Fi)], where Count Total is the weighted sum of the five information domain counts and Σ(Fi) is the sum of the 14 value adjustment factors (each rated 0-5).
What is LOC-based estimation and a key drawback?
Estimating size/effort using Lines of Code as the metric. Drawbacks: language-dependent, penalizes concise code, hard to estimate early, and not suitable for non-procedural languages.
State the Basic (Organic) COCOMO effort and time equations.
Effort E = a(KLOC)^b person-months; Time D = c(E)^d months. For organic: a=2.4, b=1.05, c=2.5, d=0.38. Persons = E/D.
Name the three modes of the COCOMO model and their meaning.
Organic (small, simple, experienced team), Semi-detached (intermediate size/complexity, mixed experience), and Embedded (large, complex, tight constraints). Each has different coefficient values.
What are the levels of the COCOMO model family?
Basic COCOMO (rough estimate from size), Intermediate COCOMO (adds 15 cost-driver multipliers), and Detailed/Advanced COCOMO (applies cost drivers per phase). COCOMO II updates these for modern practices.
What does a timeline (Gantt) chart show in project scheduling?
A bar chart plotting project tasks against time, showing start/end dates, durations, task overlap, milestones, and resource assignments, used to track schedule progress.
Differentiate verification from validation.
Verification: 'Are we building the product right?'—conformance to specifications (reviews, static analysis). Validation: 'Are we building the right product?'—conformance to user needs (testing, acceptance).
Distinguish error, fault/bug, and failure.
Error: a human mistake during development. Fault/Bug/Defect: the manifestation of the error in code/artifact. Failure: the observable incorrect behavior when the fault executes.
Differentiate unit testing from integration testing, and top-down from bottom-up.
Unit testing checks individual modules in isolation; integration testing checks interactions between combined modules. Top-down integration uses stubs (tests upper modules first); bottom-up uses drivers (tests lower modules first).
Differentiate white-box from black-box testing.
White-box (structural/glass-box) tests internal logic and code paths knowing the implementation. Black-box (functional) tests inputs/outputs against specifications without knowledge of internal structure.
What is basis path testing and how is cyclomatic complexity computed?
A white-box technique deriving a basis set of independent paths from the control flow graph. Cyclomatic complexity V(G) = E − N + 2 = P + 1 (P = predicate nodes); it equals the number of independent paths and minimum test cases needed.
Name common black-box test case design techniques.
Equivalence partitioning, boundary value analysis, cause-effect graphing, comparison testing, orthogonal array testing, and error guessing.
Differentiate alpha testing from beta testing.
Alpha testing is conducted by users at the developer's site in a controlled environment. Beta testing is conducted by end users at their own sites without the developer present, in a real environment.
What is regression testing and when is it performed?
Re-executing a subset of previously passed tests to ensure that recent changes (bug fixes, enhancements, integration) have not introduced new defects or broken existing functionality.
Differentiate performance testing from stress testing.
Performance testing measures responsiveness, throughput, and resource usage under expected load. Stress testing pushes the system beyond normal capacity (abnormal/peak loads) to find breaking points and recovery behavior.
Differentiate change control from version control in SCM.
Change control is the formal procedure to evaluate, approve, and track changes to configuration items. Version control manages and records different versions/revisions of artifacts, enabling retrieval and parallel development.
Differentiate reverse engineering, re-engineering, and software reuse.
Reverse engineering recovers design/specification from existing code. Re-engineering examines and alters an existing system to reconstitute it in a new form (restructure + forward engineer). Reuse builds new software from existing components/assets.
What this deck covers
The Software Engineering deck follows the UGC NET Computer Science Software Engineering syllabus — 7 chapters and 59 topics — so questions land on material that is genuinely examinable rather than trivia around it. That works out to roughly 8.6 cards per chapter.
Answers are written to be recallable, not just readable — averaging about 193 characters, which is long enough to carry the reasoning and short enough to say out loud.
A deck like this earns its keep on the second and third pass. Read the syllabus first so you know the shape of the subject, then use the cards to find the specific facts that have not stuck.
Software Engineering flashcards FAQ
How many Software Engineering flashcards are in this UGC NET Computer Science deck?
60 cards. This page previews 24 of them, sampled evenly across the deck so you can judge the difficulty before installing anything.
Are these UGC NET Computer Science flashcards free?
Yes. The preview here is free to read with no signup, and the full 60-card deck is free inside the Examius app.
What do the Software Engineering cards cover?
They follow the UGC NET Computer Science Software Engineering syllabus — 7 chapters and 59 topics — so the questions track what is actually examinable.
How should I use these flashcards?
Read the syllabus first so you know the shape of the subject, then drill the deck. Examius schedules each card with spaced repetition, so cards you keep missing come back sooner and ones you know drift further apart.