Computer Science, asked by Anonymous, 6 days ago

When performing a Use Case point's estimation, you estimate the number of Use Case Points at 500 UCP. The benchmark productivity for the software development lifecycle in that technology is 0.5 UCP per person-day What would be the estimated effort for that project only for the software development life cycle _ ? ✨⭐

Select one:

a. 250 person-days✨

b. 500 person-days✨

c. None of the other answers is correct✨

d. 1000 person-days​✨

❤✨__ THANK YOU SO MUCH __✨❤

@Payalahuja899___✨❤
@Princyspears26___✨❤

.•♫•♬•❤GOOD EVENING GUY'S❤•♬•♫•.

Answers

Answered by Anonymous
9

Answer:

Use-Case is a series of related interactions between a user and a system that enables the user to achieve a goal.

Use-Cases are a way to capture functional requirements of a system. The user of the system is referred to as an ‘Actor’. Use-Cases are fundamentally in text form.

Use-Case Points – Definition

Use-Case Points (UCP) is a software estimation technique used to measure the software size with use cases. The concept of UCP is similar to FPs.

The number of UCPs in a project is based on the following −

The number and complexity of the use cases in the system.

The number and complexity of the actors on the system.

Various non-functional requirements (such as portability, performance, maintainability) that are not written as use cases.

The environment in which the project will be developed (such as the language, the team’s motivation, etc.)

Estimation with UCPs requires all use cases to be written with a goal and at approximately the same level, giving the same amount of detail. Hence, before estimation, the project team should ensure they have written their use cases with defined goals and at detailed level. Use case is normally completed within a single session and after the goal is achieved, the user may go on to some other activity.

History of Use-Case Points

The Use-Case Point estimation method was introduced by Gustav Karner in 1993. The work was later licensed by Rational Software that merged into IBM.

Use-Case Points Counting Process

The Use-Case Points counting process has the following steps −

Calculate unadjusted UCPs

Adjust for technical complexity

Adjust for environmental complexity

Calculate adjusted UCPs

Step 1: Calculate Unadjusted Use-Case Points.

You calculate Unadjusted Use-Case Points first, by the following steps −

Determine Unadjusted Use-Case Weight

Determine Unadjusted Actor Weight

Calculate Unadjusted Use-Case Points

Step 1.1 − Determine Unadjusted Use-Case Weight.

Step 1.1.1 − Find the number of transactions in each Use-Case.

If the Use-Cases are written with User Goal Levels, a transaction is equivalent to a step in the Use-Case. Find the number of transactions by counting the steps in the Use-Case.

Step 1.1.2 − Classify each Use-Case as Simple, Average or Complex based on the number of transactions in the Use-Case. Also, assign Use-Case Weight as shown in the following table

Explanation:

ur most wlc prince☺️

l hope it will help u

Attachments:
Answered by Anonymous
4

Answer:

I HOPE HELP YOU

CORRECT OPTION [ C ]

Similar questions