Software Engineering

Software engineering aims to produce software that is both reliable (meets requirements) and cost-effective (within budget).

Structured programming is built on three fundamental control structures: sequence, selection (often called alteration), and iteration (loops).

Abstraction, refinement, and information hiding are all core design principles used during the software design phase to manage complexity.

A good specification must be clear, unambiguous, and precise to ensure the developers and stakeholders have a shared understanding.

A desirable module should have high cohesion and low coupling, making it independent and easier to maintain or replace.

In many software development methodologies, particularly those following a structured or hierarchical approach, coding and testing are often performed in a top-down manner.

SDLC phases typically include planning, analysis, design, implementation, and maintenance. Defining the latest technology is a technical decision made during design or planning, not a formal phase of the lifecycle.

Information hiding is a design principle where internal implementation details are encapsulated. The goal is to prevent users from accessing or manipulating internal data structures that could lead to system instability or malicious interference.

The spiral model is an evolutionary process model that combines the iterative nature of prototyping with the controlled aspects of the waterfall model. It emphasizes repeated cycles of risk analysis and development.

Data design is the phase where data structures, such as files or database schemas, are defined and evaluated for their suitability to the application requirements.

Readability is crucial in coding because software is maintained over long periods by different developers. Code that is easy to read is easier to debug, test, and update.

In object-oriented design, an object is defined as an entity that encapsulates both data (attributes) and the behaviors (operations) that act upon that data, identified by a unique name.

The black box concept assumes that the system's behavior is predictable and consistent based on its inputs. If the relationship between inputs and outputs were unstable, the black box model would not be applicable.

Design metrics are used to evaluate the quality of the design at various levels, including the overall architecture, individual components, and the interfaces between them.

Configuration management focuses on the software artifacts, such as source code, documentation, and version control. The choice of physical hardware is generally outside the scope of software configuration management.

Functional testing is used for acceptance testing to verify that the software meets the specified functional requirements as expected by the end user.

An integrative approach combines top-down (starting from high-level modules) and bottom-up (starting from low-level modules) strategies to build and test a system.

Readability is improved by using clear naming conventions, avoiding complex control flow like goto, and utilizing modular programming to break code into manageable pieces.

Before any physical work or procurement begins, the implementation phase must start with a formal planning stage to define scope, resources, and timelines.

An organization manual is a formal document that outlines the procedures, regulations, and structure that govern the operations of an organization.

Robustness is the ability of a system to continue operating correctly despite invalid inputs or stressful conditions, distinguishing it from general reliability.

An assertion is a logical statement that is assumed to be true at a specific point in the program's execution; if it is false, the program typically halts or throws an error.

CASE (Computer-Aided Software Engineering) tools are designed to automate various stages of the software development lifecycle, including generating documentation, diagrams, and code.

A computer program that mimics the behavior of a physical system is called a simulation. It allows researchers to study the system without needing the physical entity.

In a decision table, each condition can typically have two states (true or false). For n conditions, there are 2^n possible combinations of conditions, resulting in 2^n columns.