Software Estimation Techniques Quiz

True (A)

Lines of Code

<p>LOC</p> Signup and view all the answers

<p>Empirical = Based on past experience Heuristic = Expressed in mathematical terms Analytical = Derived from simple assumptions Statistical = Uses data analysis techniques</p> Signup and view all the answers

<p>Measures structural complexity (D)</p> Signup and view all the answers

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

<p>It correlates poorly with quality and efficiency of code.</p> Signup and view all the answers

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

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

<p>The size of a function is considered independent of its complexity.</p> Signup and view all the answers

<p>meet</p> Signup and view all the answers

<p>Expert Judgement = Estimates made by individual experts based on their experience. Delphi Estimation = Estimates prepared independently followed by Rationale sharing. Heuristic Estimation = Uses established rules or characteristics to make estimates. COCOMO Model = A model proposed by Boehm for cost estimation.</p> Signup and view all the answers

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

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

<p>To include Algorithm Complexity in addition to the Function Point metric.</p> Signup and view all the answers

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

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

<p>Product size</p> Signup and view all the answers

<p>upwards</p> Signup and view all the answers

<p>Product = Inherent complexity and reliability requirements Computer = Execution time and storage requirements Personnel = Experience of personnel Development Environment = Sophistication of development tools</p> Signup and view all the answers

<p>Sub-system complexity (D)</p> Signup and view all the answers

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

<p>They affect the effort and development time.</p> Signup and view all the answers

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

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

<p>state of technology constant</p> Signup and view all the answers

<p>maximum</p> Signup and view all the answers

<p>Operators = Basic functional units in programming Operands = Data items in a program KLOC = Thousands of Lines of Code Rayleigh-Norden curve = Relation between delivered lines of code and effort</p> Signup and view all the answers

<p>Total personnel required (D)</p> Signup and view all the answers

<p>1976</p> Signup and view all the answers

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

<p>It initially increases, reaches a peak, and then decreases. (C)</p> Signup and view all the answers

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

<p>A small compression in the delivery schedule can result in a substantial penalty on human effort.</p> Signup and view all the answers

<p>L^3/Ck^3</p> Signup and view all the answers

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

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

<p>The number of project staff falls until product installation and delivery.</p> Signup and view all the answers

<p>When early completion is essential and the task is well understood (A)</p> Signup and view all the answers

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

<p>The staffing level during the life cycle of a software product development.</p> Signup and view all the answers

<p>mathematical expression</p> Signup and view all the answers

<p>It combines democratic and chief-programmer team approaches (A)</p> Signup and view all the answers

<p>Empirical Techniques = Based on systematic guesses by experts Heuristic Techniques = Modeling software characteristics with mathematical expressions Analytical Techniques = Deriving estimates from basic assumptions Expert Judgement = Utilizes the knowledge of experienced professionals</p> Signup and view all the answers

<p>Empirical Techniques</p> Signup and view all the answers

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

A document that outlines the project plan, including estimates, resources, schedules, and risk management.

The first step in cost estimation involves determining the size of the software product.

Techniques used to estimate software development effort, cost, and duration.

A method that relies on past experience to estimate software development costs.

This approach uses mathematical formulas and relationships to estimate costs based on software characteristics.

Lines of Code (LOC) is a widely used metric for measuring software size, but it has limitations.

LOC can vary based on coding style and does not reflect quality or efficiency.

LOC focuses on textual complexity and does not capture structural or logical complexity, making it difficult to accurately assess effort.

A software sizing metric that counts the number of lines of code in a program. It is simple to use but can be unreliable because it doesn't account for code complexity or different programming languages.

A software sizing metric that accounts for the functionality of a software system by assigning points to different types of inputs, outputs, inquiries, files, and interfaces.

A variation of the Function Point Metric that adds a complexity parameter to account for the algorithms used in the software.

A size estimation technique that relies on the judgement of a single expert. It is prone to bias based on the individual's experience and knowledge.

A size estimation technique that involves a group of experts who independently estimate the size of a project. Their estimates are then shared and discussed, and the process is repeated until a consensus is reached. This helps to mitigate the problem of individual bias found in Expert Judgement.

A broad category of size estimation techniques that rely on mathematical formulas to predict the size of a software project based on certain characteristics or variables.

A specific example of a multivariable heuristic estimation model that uses a set of factors and formulas to estimate the effort required to develop a software project. These factors include the size of the project, the complexity of the project, the experience of the developers, and the quality requirements.

Software development effort and time depend solely on the size of the software product.

Several factors other than size influence software development effort and time, like reliability requirements, tools used, and data volume.

Intermediate COCOMO model considers these additional factors using cost drivers, refining the initial estimate from the basic model.

Factors like using modern programming practices decrease initial estimates, while strict reliability requirements increase them.

Cost drivers are rated on a scale of 1 to 3 to reflect their impact on development, then multiplied with the initial estimate.

Cost driver classes categorize factors: product complexity, computer constraints, personnel experience, and development environment.

Basic and intermediate COCOMO models treat software as a single entity, neglecting the potential differences among its components.

Complete COCOMO addresses this by estimating each sub-system individually and combining costs for an accurate overall estimate.

A software development model that estimates project size, effort, and time using a combination of software parameters, including the number of operators and operands.

A curve representing the number of full-time personnel required at any time during a development project. The curve reaches its maximum at a specific time (td) and has a total area (K) under it.

A software development model that estimates software development effort and time based on the number of lines of code (LOC) and a state-of-technology constant (Ck) that accounts for factors affecting productivity.

The state of technology constant (Ck) in Putnam's model, reflecting factors affecting programmer productivity. A lower value (e.g., 2) indicates poor development environments with limited methodology and documentation.

The time at which the Rayleigh curve reaches its maximum, indicating the peak effort required during a project.

The total area under the Rayleigh Curve, representing the total effort expended on a development project.

The Software Development process model that works by developing and deploying the system in small portions.

The Software Development process model that works by developing and deploying the whole system at once.

The point on the Rayleigh Curve where the number of engineers reaches its maximum, typically coinciding with system testing and product release.

Putnam's model claims that compressing the development time by even a relatively small amount can result in a significant increase in effort, and thus cost.

Putnam's model suggests that extending the schedule beyond a certain point leads to significant gains in efficiency, lowering the overall effort required.

A rule of thumb stating that compressing a software project's schedule beyond 25% of the original estimate is unlikely to succeed.

The point beyond which adding more resources to a project will not significantly reduce the development time.

A software development environment with a Ck value of 8, indicating a good environment for software development.

A team structure where a single, highly skilled programmer takes on a leadership role, responsible for design, coding, and overall project management.

A team structure that combines aspects of both democratic and chief programmer teams. It focuses communication on a smaller, skilled group, while still providing input opportunities for the wider team.

The process of estimating the resources, time, and cost required to develop software. This involves determining the size of the product first, then using that to estimate effort.

The relationship between changes in a project's schedule and the corresponding effort required. The relationship is often non-linear, meaning a small schedule change can have a significant impact on the effort needed.