⚙️ Chapter 7: Software Construction

Explanation: Software Construction is defined as detailed creation of working, meaningful software through a combination of coding, verification, unit testing, integration testing, and debugging.

Explanation: The fundamentals include: minimizing complexity, anticipating change, constructing for verification, and standards in construction. Maximizing code length is not a goal.

Explanation: Minimizing complexity is one of the strongest drivers in software construction. It is achieved by emphasizing code creation that is simple and readable.

Explanation: Anticipation of change affects: use of control structures, handling of errors, source code organization, code documentation, and coding standards. Marketing is not part of construction.

Explanation: Reuse has two closely related facets: Construction for reuse (create reusable software assets) and Construction with reuse (reuse software assets in construction).

Explanation: Unit Testing is testing where individual units or components are tested. The purpose is to validate that each unit of software code performs as expected. A unit is the smallest testable portion.

Explanation: Walkthrough is semi-formal, author is presenter, led by author, reviewers not aware. Inspection is formal, author not presenter, led by moderator, reviewers are aware and well prepared.

Explanation: Integration Testing involves combining different software modules and testing them as a group. It focuses on checking data flow from one module to another.

Explanation: Top-down Integration takes place from top to down following the control flow. It uses stubs for testing and allows early prototyping, but needs many stubs.

Explanation: In test-driven development, developers write tests first before writing code. This helps clarify what the code should actually do. An automated unit test framework runs tests after every code contribution.

Explanation: Refactoring means improving the structure, readability, efficiency and security of a program. Developers refactor code as soon as potential improvements are found to keep code simple and maintainable.

Explanation: XP practices include on-site customer (not off-site), pair programming, sustainable pace, small releases, test-first development, refactoring, continuous integration, and others.

Explanation: Applying external or internal development standards during construction helps achieve a project's objectives for efficiency, quality, and cost. This includes restricting complex language structures.

Explanation: Open source software is released under a license where the copyright holder grants users the right to use, change, and distribute the software and its source code to anyone for any purpose.

Explanation: Internal documentation includes: header comment blocks, meaningful variable names, program comments, and formatting. External documentation includes: problem description, algorithm description, and data description.

Explanation: Skipping unit testing leads to higher defect fixing costs during System Testing, Integration Testing and Beta Testing. Proper unit tests help fix bugs early and save time and money.

Explanation: The priority in defect testing is to find those inputs in the set that reveal problems with the system. These inputs cause anomalous behavior and outputs that reveal the presence of defects.

Explanation: Integration testing is necessary because modules designed by different developers may have different logic and need to work together. Also, interfaces with databases, hardware, and exception handling could be erroneous.

Explanation: Construction activities include: Coding & Debugging (appears twice), Unit Testing, Integration, and Integration Testing. These fall between detailed design and system testing.

Explanation: The preparation level, not team size, determines inspection effectiveness. The team's effectiveness and efficiency depend on their familiarity with their product.

Explanation: Software engineers should commit to making analysis, specification, design, development, testing and maintenance a beneficial and respected profession committed to health, safety, and welfare of the public.

Explanation: Reuse enables developing new systems more quickly, with fewer development risks and lower costs. It also improves software reliability.

Explanation: Anticipating change means building extensible software that can be enhanced without disrupting the underlying structure. It's supported by specific coding techniques.

Explanation: Top-down integration takes help of stubs for testing. Stubs are temporary substitute modules that simulate the behavior of lower-level modules not yet integrated.

Explanation: Proper unit tests help fix bugs early in the development cycle, save time and money, help developers understand the code base, serve as project documentation, and help with code reuse.