Software Engineering - 2

Top-down design is a methodology that focuses on breaking a system into smaller, manageable parts. Loop invariants are a concept used in formal verification and algorithm analysis, not a requirement of the design methodology itself.

Referential transparency is a property of expressions in programming where an expression can be replaced by its value without changing the program's behavior.

Recursion allows complex problems to be expressed in a concise, logical manner by breaking them into smaller instances of the same problem, which often leads to cleaner code.

Top-down design relies on modularity to break the problem down, step-wise refinement to detail the logic, and flow charting to visualize the process.

Software errors can be introduced at any stage of the development lifecycle, including requirements gathering, design, coding, and testing.

In programming, the target of an assignment (the left side) must be a memory location that can be written to, which is known as an l-value.

Maintenance is widely recognized as the most expensive phase of the software development lifecycle because it spans the longest duration and involves ongoing updates and bug fixes.

A quality metric is a quantitative measure of the degree to which a system, component, or process possesses a given attribute, used to evaluate software quality.

In the early days of computing, the primary focus was on the physical machinery (hardware) rather than the software, which was often secondary.

Testing is designed to identify failures in the system, which occur when the software does not behave as expected during execution.

In numerical computing, performing many operations with floating-point numbers leads to the accumulation of small inaccuracies known as round-off errors. Syntax, run-time, and logic errors are distinct categories of programming mistakes.

An informal design review is a preliminary assessment of a design's logic and structure before the actual coding phase begins. It is less rigid than a formal design review or a structured walkthrough.

System analysis focuses on the requirements and logic of the system, whereas a program flowchart is a detailed tool used during the design and implementation phase to describe specific code logic.

Top-down and bottom-up are the two standard integration testing strategies used to combine modules into a functional system. Other options listed are unrelated to module integration strategies.

Game programs encompass a wide variety of genres, including adventure, simulation, and arcade styles, making 'all of the above' the correct choice.

Application generators often allow users to define what the program should do (non-procedural) while also providing hooks or extensions for custom logic (procedural), thus combining both.

In Data Flow Diagram (DFD) notation, an asterisk (*) is commonly used to indicate that multiple data flows are required for a process to execute.