Software Engineering

CASE systems support multiple phases of software development - gathering requirements from users, analyzing feasibility of those requirements, and designing general algorithms. All the listed functions are valid uses of CASE tools.

The top-down approach starts from the general and moves to specific details, while bottom-up starts from specifics and builds to general. Combining these two complementary approaches is called the integrative approach.

A system flowchart shows the overall flow of data and major steps in a system at a high level - the big picture. Program flowcharts show detailed logic of individual programs, while block diagrams are different representations.

Software costs increase due to multiple factors: each application needs new programs to be written, new equipment requires software modification or rewriting, and programming is labor-intensive affected by inflation. All three factors contribute to rising costs.

The correct sequence in system study is: 1) Problem definition, 2) System analysis, 3) System design, 4) Programming analysis, 5) Program preparation, and 6) Implementation. Option D lists these steps in the correct order.

Lex is a well-known tool used to generate lexical analyzers (scanners) for various programming languages. It reads specification files and produces C code for lexical analysis. Yaac, EQN, and TeX serve different purposes.

Yaac

parser

Top-down parsing

BNF (Backus-Naur Form) is a formal notation used to specify the syntax of programming languages and other formal languages. It defines grammar rules and production rules, not how programs work or shell programming.

Recursion enhances logical clarity by expressing solutions in terms of themselves, and it typically reduces code size by eliminating repetitive loops. However, it doesn't necessarily reduce execution time, make debugging easier, or guarantee bug-free software.

Structured programming languages minimize or eliminate GOTO statements in favor of control structures like if-then-else and loops. They emphasize single entry and exit points for program blocks to improve code readability and maintainability. Both statements correctly describe key principles of structured programming.

descibes what processing is to be done without specifying the particular procedures to be used

Structured programming is a programming paradigm that aims to improve code clarity and quality by reducing the use of GOTO statements. Instead, it uses control structures like loops (for, while), conditionals (if-then-else), and subroutines. The absence of GOTO statements is a defining characteristic of structured programming.

helps make large programs more understandable

what the software system is to do

In programming languages, an l-value (locator value) refers to a memory location that has an address and can appear on the left side of an assignment statement. The target of an assignment must be an l-value because it needs to specify where to store the value. r-values represent actual data values and appear on the right side.

failures

All of the above

Software engineering fundamentally revolves around two critical trade-offs: software quality (correctness, reliability, maintainability) and cost (development time, resources, budget). Every software engineering decision balances these competing factors. Engineering and design are activities, not core issues. Hardware and software are components, while programs and instructions are too narrow in scope.

NATO - Science Committee Europe, 1960

The fundamental goal of software engineering is to produce high-quality software while managing costs effectively. Quality alone without cost consideration is not practical, and cost alone without quality is not valuable. Software engineering seeks the optimal balance between delivering reliable, maintainable software and doing so within reasonable time and resource constraints.

the INTERNIST,a medical diagnosis program