Software Engineering Chapter 1

<p>A student who enjoys math, logic, or specialized fields like machine learning (A)</p> Signup and view all the answers

<p>A basic understanding of computer science principles (D)</p> Signup and view all the answers

<p>User Involvement (B)</p> Signup and view all the answers

<p>Ownership (B)</p> Signup and view all the answers

<p>9.6% (D)</p> Signup and view all the answers

<p>Lack of Planning (A)</p> Signup and view all the answers

<p>Strong Vendor Partnerships (C)</p> Signup and view all the answers

<p>Invisibility (D)</p> Signup and view all the answers

<p>Memory capacity (A)</p> Signup and view all the answers

<p>Changeability (B)</p> Signup and view all the answers

<p>It introduces additional complexity (B)</p> Signup and view all the answers

<p>Small input changes causing significant output variation (B)</p> Signup and view all the answers

<p>Software became an independent product (B)</p> Signup and view all the answers

<p>A coherent tradition of scientific research (D)</p> Signup and view all the answers

<p>Software engineers were primarily hardware engineers (C)</p> Signup and view all the answers

<p>A fundamental change in basic concepts and practices (B)</p> Signup and view all the answers

<p>The complexity of software demands exceeding existing capabilities (C)</p> Signup and view all the answers

<p>Waterfall Model (D)</p> Signup and view all the answers

<p>Software development was excessively quick (B)</p> Signup and view all the answers

<p>IBM with OS/360 (B)</p> Signup and view all the answers

<p>Software often did not meet user expectations (B)</p> Signup and view all the answers

<p>The anomaly is not clearly understood or compelling (D)</p> Signup and view all the answers

<p>1968 (A)</p> Signup and view all the answers

<p>It moves down a series of steps from an initial idea to a final product. (A)</p> Signup and view all the answers

<p>Software evolution (D)</p> Signup and view all the answers

<p>The exponential cost of making late changes. (D)</p> Signup and view all the answers

<p>Around 2 – 3.5% per month. (B)</p> Signup and view all the answers

<p>Agile and Extreme Programming (B)</p> Signup and view all the answers

<p>Requirements volatility. (B)</p> Signup and view all the answers

<p>Lack of user input and involvement (C)</p> Signup and view all the answers

<p>Late changes become much more expensive than early changes. (B)</p> Signup and view all the answers

<p>2.9% (A)</p> Signup and view all the answers

<p>Waterfall model (C)</p> Signup and view all the answers

<p>About 30%. (D)</p> Signup and view all the answers

<p>Test-Driven Development (TDD) (A)</p> Signup and view all the answers

<p>It assumes requirements will remain stable through development. (C)</p> Signup and view all the answers

<p>There are still significant areas for improvement in software engineering. (C)</p> Signup and view all the answers

<p>Difficulty accommodating changes in later phases. (C)</p> Signup and view all the answers

<p>Poor project success rates (A)</p> Signup and view all the answers

An observation that contradicts an existing paradigm, prompting a re-evaluation.

A fundamental change in basic concepts and practices in a scientific discipline.

Challenges in software engineering leading to high costs, unreliability, and late deliveries.

The first documented linear model for the software development process, emphasizing sequential phases.

An example of an anomaly leading to a paradigm shift in astronomy.

A driving anomaly in the 1970s that led to the establishment of software engineering as a discipline.

IBM's new operating system highlighted the need for better software practices due to complexity.

The event marking the formal proposal of software engineering as a discipline.

The practical discipline focused on the life cycle of software production and maintenance.

An approach that outlines activities and results in software development.

A sequence of stages in software development from conception to delivery.

CS focuses on theories; SE on practical software production.

Essential background knowledge for Software Engineers to understand software systems.

Software cannot be directly perceived; requires efforts to understand through visualizations or sonifications.

Software is one of the most intricate systems created, challenging due to limited short-term memory (~7 items).

Software is in a constant state of change, and understanding can become outdated quickly.

Software must adhere to the complexities of its larger environment, including hardware and stakeholder demands.

Small input changes in software can lead to unpredictable and significant output changes.

A coherent tradition of scientific research, encompassing theory, application, and cultural aspects in a field.

In the 1950s, software began to be recognized as a separate technology from hardware.

Initial programmers utilized makeshift methods drawn from their previous engineering and mathematics experiences.

The distinct steps a project goes through in the waterfall model.

The expense incurred when making changes during the project lifecycle.

The rapid increase in cost associated with late project changes.

The rate at which project requirements change over time.

The percentage of requirement changes per time period in projects.

Factors that significantly increase software project costs.

Challenges faced by the waterfall model due to its linear approach.

A development approach that involves repeated cycles (iterations) of software design and improvement.

A software development process that provides a structured approach to iterative development.

An iterative approach that emphasizes flexibility and customer collaboration throughout the software lifecycle.

A framework for managing and completing complex projects using iterative processes and teams.

A software development methodology that aims to improve software quality and responsiveness through frequent releases.

A software development process where tests are written before code to ensure functionality.

A research study that assesses the success factors and challenges in software projects.

Major challenges in software projects include lack of user involvement and incomplete requirements.

The active participation of users in a project to achieve better outcomes.

Backing from top management to ensure project resources and focus.

Well-defined project goals and needs that guide development effectively.

The strategic organization of resources and tasks for successful project execution.

Having skilled and knowledgeable team members to execute project tasks.