Software Research Methods and Gender Bias

<p>Men had a larger number of applications but lower acceptance rates. (C)</p> Signup and view all the answers

<p>By assessing team output and quality of code produced. (B)</p> Signup and view all the answers

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

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

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

<p>Producing software in a timely manner (B)</p> Signup and view all the answers

<p>Concurrency and the Actor model (B)</p> Signup and view all the answers

<p>Once a week (B)</p> Signup and view all the answers

<p>To enhance understanding of software engineering (B)</p> Signup and view all the answers

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

<p>Catastrophic failure (C)</p> Signup and view all the answers

<p>Project loses all data (C)</p> Signup and view all the answers

<p>Chronic functionality problems (D)</p> Signup and view all the answers

<p>Theoretical Development Scenario 1 (A)</p> Signup and view all the answers

<p>Software glitch causing crashes (C)</p> Signup and view all the answers

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

<p>Simple user interfaces (B)</p> Signup and view all the answers

<p>Delay in distribution (D)</p> Signup and view all the answers

<p>16.2% (C)</p> Signup and view all the answers

<p>Bad Planning and Estimating (C)</p> Signup and view all the answers

<p>Over time and budget with incomplete features (C)</p> Signup and view all the answers

<p>Clear Statement of Requirements (C)</p> Signup and view all the answers

<p>13.1% (C)</p> Signup and view all the answers

<p>High Market Demand (D)</p> Signup and view all the answers

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

<p>$1,331,000 (D)</p> Signup and view all the answers

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

<p>Safety and efficacy of the vaccine (B)</p> Signup and view all the answers

<p>Development of the first computer programs (D)</p> Signup and view all the answers

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

<p>Research in formal methods and OO methods (B)</p> Signup and view all the answers

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

<p>Emphasis on Agile and test-driven development (D)</p> Signup and view all the answers

<p>Applying scientific principles for efficiency and reliability (C)</p> Signup and view all the answers

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

<p>Complex software problems require multiple approaches (C)</p> Signup and view all the answers

<p>Project delivery and estimation (B)</p> Signup and view all the answers

<p>By comparing budget and time (B)</p> Signup and view all the answers

<p>Very good estimation (C)</p> Signup and view all the answers

<p>Technological advancements (C)</p> Signup and view all the answers

<p>Going beyond the scheduled delivery date (B)</p> Signup and view all the answers

<p>The classification of project success is often incomplete. (A)</p> Signup and view all the answers

<p>EQF = 1 / (Average(Deviation/Actual)) (B)</p> Signup and view all the answers

<p>There was a significant error in estimated versus actual performance. (D)</p> Signup and view all the answers

<p>To overestimate in order to manage expectations. (C)</p> Signup and view all the answers

<p>They had very low success rates. (B)</p> Signup and view all the answers

A phenomenon where software development struggles to keep up with increasing demands and complexity. This is often reflected in projects exceeding budgets, deadlines, and falling short of expectations.

A method to predict the resources (time, money, people) needed to complete a software project.

A set of proven solutions (like blueprints) for common software design problems.

A software development methodology that focuses on flexibility, collaboration, and delivering value quickly.

A model of concurrent computation designed for parallel and distributed systems. It involves autonomous 'actors' that communicate with each other via asynchronous messages.

A software development philosophy that prioritizes adaptability, customer collaboration, and delivering working software in short iterations.

A representation of the dependencies between different parts of a program, showing how changes in one part can affect other parts.

A technique for identifying and isolating sections of code that contribute to a particular output or behavior in a program.

A situation where a software project fails to deliver a product that meets its goals, such as being completed on time and within budget or having the desired functionality.

A software failure that is severe and has significant, often disastrous, consequences. It may result in loss of life, property damage, or major financial losses.

A software failure that is persistent and recurring, leading to delays, budget overruns, and poor quality software. These failures are often related to weak software design and coding practices.

A software failure where the project does not reach completion, often due to lack of resources, poor planning, or unforeseen challenges.

A software failure where the project exceeds the allotted budget, often due to unforeseen costs, inefficient development practices, or changing requirements.

A software failure where the project is riddled with defects and bugs, compromising its quality and reliability.

A software failure where the project takes longer than the planned timeframe to complete, often due to poor planning, inadequate resources, or unforeseen challenges.

A software failure characterized by code that is difficult to understand, modify, and maintain, making it challenging to fix bugs or add new features.

A hypothesis that assumes no significant difference or relationship between the variables being studied.

The process of analyzing data to determine whether an observed result could have occurred by chance or if there's a real effect.

A simplified representation of a real-world phenomenon used to study its characteristics and behavior.

The number of observations or data points used in a study or experiment.

Occurs when an observed effect appears to be caused by one factor, but in reality, it's influenced by another hidden factor.

A technology failure that occurred when a software update from Crowdstrike caused a blue screen of death on Windows PCs, affecting various industries globally.

An AI tool used by CNET to generate articles on compound interest, but the AI produced inaccurate information, demonstrating the limitations of AI in financial writing.

Language models like ChatGPT don't truly understand the meaning of the text they generate; they utilize statistical patterns from their training data to create text.

A report that tracks the success and failure rates of software development projects, highlighting challenges like exceeding budgets and deadlines, and project cancellations.

A successful software development project meets all requirements, finishes on time, and within budget.

Projects that finish late or over budget, or lack some planned features, are considered challenged projects.

Projects that are abandoned before completion are categorized as incomplete projects.

Inaccurate project planning, lack of user involvement, and unclear requirements are a major reason for projects going over budget or not finishing on time.

Standish research shows that successful projects prioritize user involvement, clear requirements, and a well-defined project management process.

Incomplete requirements, lack of user involvement, and unrealistic expectations can lead to failed projects.

The creative application of scientific principles to design and develop software systems. It uses engineering principles to create reliable and efficient software.

A period in software development history characterized by projects exceeding budgets, deadlines, and failing to meet expectations. It highlighted the need for better software development practices.

A stage in software development history marked by early experimentation and exploration of concepts like high-level languages and object-oriented programming.

A set of principles and practices to develop quality software economically. It focuses on achieving efficiency, reliability, and maintainability.

A collection of activities involved in software development, encompassing everything from defining requirements to testing and managing projects.

A methodology that focuses on flexibility, collaboration, and delivering working software in short cycles. It emphasizes adaptability and customer feedback.

A set of proven solutions for common software design challenges, offering blueprints for recurring design problems.

Designing experiments for software engineering is complex because the context of each activity must be considered. The conclusions drawn from research should always be examined critically.

The level of accuracy in predicting the time required for a software project to be completed.

Describes how much a project's actual completion time deviates from its initial estimation. It's often expressed as a ratio.

A measure of how well a software project is managed, typically based on factors like budget, time, and functionality.

An approach to software estimation where sales are prioritized, potentially leading to underestimation and under-resourcing.

An approach to software estimation where the development needs are considered first, potentially leading to more realistic estimations.

A visual model that represents the uncertainty in software project estimations. The uncertainty decreases as the project progresses.

When a project completes earlier or within the budget despite initial underestimation, indicating a positive bias in the estimation process.

The practice of deliberately overestimating project timelines and costs to buffer against unforeseen challenges.

Reports that often analyze the success and failure rates of software projects.

A phenomenon where the initial reports and figures from studies or analyses are significantly skewed, leading to inaccurate conclusions.