Comments on: Software Cost Estimation With Use Case Points – Environmental Factors

By: DiegoMarsan

DiegoMarsan — Thu, 16 Dec 2010 16:15:01 +0000

Hi, about “Stable Requirements (2)”, High numbers reduce the factor. ¿Is the description es righ?

By: Estimating With Use Case Points | accidental business analyst

Estimating With Use Case Points | accidental business analyst — Wed, 18 Apr 2007 20:27:37 +0000

[...] Environmental Factors. Mostly characterizing the implementation team, but touching on process as well. [...]

By: Scott Sehlhorst

Scott Sehlhorst — Mon, 19 Feb 2007 22:31:03 +0000

Hey Roger, thanks. And other readers – Roger is about to write about another estimating technique – make sure you check out his article too.

As to your question –

When you organize by usage prior to implementation you (should) see the areas of functional overlap. These might be represented as subordinate use cases.

When you approach delivery of “chunks of usable functionality” scoped and managed by use case, it is (at least to me) very logical to build out those chunks in re-usable ways.

When I use the phrase “OO” I am talking about encapsulation, modularity, and contract-based-programming (to some extent). These are inherently aligned with the general OO principles of software development. And I see it as a natural influence on the design approaches.

You’re right that it doesn’t require implementers to take a particular approach. But it does provide an over-arching perspective that would make oo-avoidance awkward.

By: Roger L. Cauvin

Roger L. Cauvin — Mon, 19 Feb 2007 21:07:03 +0000

It’s great to see a concise but step-by-step description of how to estimate with use case points. I have a question that’s somewhat tangential. You wrote:

“A user-centric or use-case-driven project will have an inherently OO structure in the implementation.”

Would you explain your reasoning here?

It seems to me that it is always possible to achieve the exact same outward behavior and characteristics in software regardless of the use of OO or procedural programming. In fact, use cases are inherently procedural.