Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

345 > Task ID and Effort > Flashcards

Task ID and Effort Flashcards

1
Q

A task that we call an action

A

non-decomposable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

A task that we call an activity or process

A

decomposable

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Work package

A

The ideal level of detail, or amount of work that is small and specific enough that it can be estimated reliably

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Work breakdown structure (WBS)

A

A way to identify tasks at a useful level of abstraction.

It is deliverable-oriented hierarchial decomposition of work done by the project team

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What does Work Breakdown structure (WBS) hope to achieve

A

to achieve project goals or produce project delieverables

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

3 formats of WBS

A

tree
hierarchy diagram
hierarchial list

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Parts of WBS tree

A

nodes- are items of work in project
root- is project name
leaves- are more detailed specifications of work

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Decomposition strategies of BS (4)

A

Project phases
Organizational units
Physical decomposition
Geographical location

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Decomposition Levels

A

1) deliverables

2 and 3 - features and functions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

WBS strategy - One hundred percent rule

A

The nodes descended from a parent represent 100% of the work of the parent, but no work outside the project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

WBS strategy = Mutually exclusive siblings

A

No sibling in WBS have overlapping work. (else leads to inflated effort estimate and confusion about work assignments)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

WBS strategy = 8/80 rule

A

Work packages (leaf nodes) require between 8 to 80 person-hours of effort. Helps to determine wether a node should be decomposed (work can be done by one person in one day to two weeks is considered small enough to estimate reliably

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Best process for creating a WBS

A
  • gather project team and stakeholders in a meeting in which WBS is created on whiteboard
  • participants make a list of items at level one on own
  • group comes to consensus on level 1
  • Delieveralbes (product features and fuctions) listed in WBS
  • stakeholders leave
  • lower levels consisting of development tasks and activieties are then filled in by developers
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Effort Estimation - Analogy

A

Current project similar to past project, effort to complete should be roughly same as effort required to complete past project

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Effort Estimation - WBS to Effort

A

Given complete work breakdown structure for project, can estimate effort required for each work package and then sum estimates to generate effort estimate for entire project. (but WBS must be accurate)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Effort Estimation - Size to Effort

A

Given estimate of size of software product, and relationship b/w product size and effort can generate estimate of project effort

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

Functional measures of size

A

Dominated in units that are a direct relection of functionality being provided by the program

  • num of pages in WWW application
  • num of reports in database application
  • num of windows in GUI
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Non functional measures of size

A

Direct reflection of program structure

  • lines of code (hard to count beforehand)
  • nm of classes
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Advantages of functional measures vs nonfunctionla

A

1) largely independent of technology and platform being used

2) user-focused and easier to explain to nontechnical stakeholders

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Function point analysis

A

Functional mesure that has 5 different kinds of functionality (base functiona lcomponenet types)
3 are related to processes/transactions
2 related to data storage

21
Q

External Inputs (EI)

A

Processes that provide data that will be used or stored by the product.

Ex. adds new employees to a file or table of employee records

22
Q

External Queries (EQ)

A

Process that retrieve stored data (without adding value or information but, perhaps, providing formatting)

Ex, retrieves all employees in a file or table

23
Q

External Outputs (EO)

A

Processes that provide derived information to a user (such as reports, messages, or prompts) or other system.

Ex process that calculated average salary of all employees

24
Q

Internal Logical Files (ILF)

A

Logical groupings of data maintained by the product

Ex. file, or table of employee records

25
Q

External Interface Files (EIF)

A

Logical groupings of data that are external to the product (not maintained by product) but are used or referenced by product

Ex. file or table used by multiple products that maps machine-readable codes to human0readable descriptions

26
Q

Scale used to answer questions 0 (not important) to 5 (essential) 14 questions total

A

Likert scale

27
Q

What does M(md) stand for in equation

A

measure of difficulty

28
Q

W(md)

A

weighting factor for measure m of difficulty d

29
Q

V(q)

A

Value adjustment factor for question q

30
Q

F

A

Number of function points

31
Q

COSMIC functional measure

A

counts data movements associated with functional processes thar are initated as a result of trugger events.

32
Q

Roetzheim version of function points

A

Used for Web Aps

33
Q

Boehm

A

uses object points rather than function points (screens in user interface, reports and components/modules)

34
Q

Person-month

A

Traditional effort estimate unit, amount of effort a typical developer expended in one month of work. (month is 4 and a half weeks)

person month has about 22 person days

35
Q

effort estimates include

A 
ally life cycle work :
writing requirements and designs
doing testing
generating documents
collecting data
managing project
ect
36
Q

E = a + BF

what do symbols mean

A

E - denotes the effort (in person months)
F - denotes the size in function points

a and B are constants depending on Albrecht and Gafney or Kemerer model

Best for small products

37
Q

E = aL^B

A

L is number of thousands of lines of code (KLOC)

B< 1 the project exhibits economics of scale (rare)

B> 1 exhibits diseconomies of scale

Watson and Felix
Basili and Preburgere
Boehm

38
Q

What are diseconomies of scale examples

A

Communication problems and integration problems

39
Q

E = a * F^B * N^Y

A

F is product size in function points

N max size of team

International Software Benchmarking Standards Group

40
Q

Constructive Cost Model

A

One of the most complicated models developed by Boehm COCOMO

Use size measured in either lines of code or functional measures can convert from functional measures to LOC

B is the diseconomics of scale (increase rt to left)

W - effort multipliers (increase left to rt)

41
Q

Do planners estimate the software size is Scrum?

A

No they usually just estimate effort for stories and tasks

42
Q

What are effort estimates in scrum called?

A

story days or person month (ideal days or ideal months)

or story point

43
Q

Story point/task point

A

A relative unit of size. These estimates are made by choosing one or a few small stories or tasks of about the same size and using them as a baseline (by declaring them to be of size one).
All stories or tasks are estimated relative to thi standard.

44
Q

Effort estimates become more or less detailed over time

A

more detailed and more accurate

45
Q

The Scrum estimate process has what advantage?

A

It avoids much work and rework on making effort estimates

46
Q

Fallback to Scrum estimation process

A

Can not accurately estimate the release of a product

47
Q

Planning poker

A

Technique for an agile team to come to consensus on effort estimates (Fibonacci sequence)

48
Q

Who participates in planning poker

A

PO and SM but only team embers actually make estimates

PO presents explains and clarifies PBIs when questioned about them during planning poker, records story estimate

SM facilitates participation

345 (7 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions