Software Engineering Previous Year Questions

Explanation

Regression testing is the process of testing changes to computer program to make sure that the older programming still works with the new changes. This happens only in case of maintenance. So it relates to the maintenance testing, hence the answer is option (d).

Explanation

We know our aim is to maximize cohesion & minimum coupling Strong form of cohesion is functional cohesion weakest form of coupling is data coupling.

Explanation

Adaptive maintenance is a modification of a software product performed after delivery to keep it usable in a changed or changing environment, e.g. porting the existing software to a new environment.

Explanation

Requirement validation is an activity in the requirements phase where the gathered requirements are checked for completeness, consistency and correctness. Prototyping is a technique for requirement analysis that builds a working model to get user feedback. Function points are a commonly used size metric for requirements. The modeling-oriented approach is not one of the methods for specifying the functional specifications, so statement (c) is incorrect.

Explanation

The waterfall model is a sequential (non-iterative) process; it includes requirements, design, implementation, verification and maintenance. Risk analysis is used in the spiral model.

Explanation

(i) Coupling measures how dependent modules are on each other – (D). (ii) Cohesion reflects how well a module's elements work toward a single purpose – (C). (iii) Scalability means the system can grow (add functionality/workload) without redesign – (B). (iv) Readable code is easy to inspect and understand – (A).

Explanation

The main drawback of the waterfall model is the difficulty of accommodating change after the process is under way. (1) Difficult to address change: Inflexible partitioning of the project into distinct stage makes it difficult to respond to changing customer requirements. Therefore, this model is only appropriate when the requirement are well understood and changes will be fairly limited during the design process

Explanation

Prototype typically simulates only a few aspects of, and may be completely different from, the final product. Prototyping has several benefits. The software designer and implementer can get valuable feedback from the user early in the project.

Explanation

Code-and-fix: write some code, debug it, repeat (A-5). Evolutionary prototyping: the system is developed incrementally by evolving the specification and code (B-2). Spiral model: assess risks at each step (C-1). Staged delivery: requirements for several releases first, then design and code in sequence (D-3). Waterfall model: sequential, non-iterative standard phases (E-4).

Explanation

The 9001 : 2000 is the quality assurance standard that applies to software engineering. The standard contains 20 requirement that must be present for an effective quality assurance system.

Explanation

This model allows for the creation of a preliminary version (prototype) of the software, which can be refined iteratively based on user feedback until satisfactory version is achieved. Clarifies Requirements– The prototyping process helps customers visualize and understand what the final product will look like and how it will function. Reduce Risk– By identifying potential issues early on through prototyping, developers can avoid costly rework and delays later in the development cycle.

Explanation

S1 and S2 swap the definitions: cohesion measures how well the things grouped in a module belong together, and coupling measures the degree of interaction between modules. S3 is true: if coupling is low and cohesion is high, it is easier to change one module without affecting others.

Explanation

Agile philosophy stresses self-organizing teams, collaboration with customers, welcoming change and rapid delivery of working software. Testing is done continuously along with development, not as a separate phase after the build phase.

Explanation

Traditional testing starts with unit testing, followed by integration testing, then system testing and finally validation (acceptance) testing: (C), (A), (B), (D).

Explanation

Regression testing verifies that previously developed and tested software still performs correctly after it has been changed, e.g. after enhancements or patches during maintenance.

Explanation

Statistical software quality assurance in software engineering involves tracing each defect to its underlying cause, isolating the vital few causes, and moving to correct them.

Explanation

S1 and S2 interchange white-box and black-box testing: black-box tests are based on specifications and white-box tests are based on code, so both are false. S3 correctly describes alpha testing. So only S1 and S2 are FALSE.