Possible UML-Based Size Measures

@inproceedings{Stutzke1998PossibleUS,
  title={Possible UML-Based Size Measures},
  author={Richard D. Stutzke},
  year={1998}
}
Why do we size software? For many reasons. To estimate effort. To estimate memory requirements. To estimate processing or execution speed. This paper considers size measures that help us predict the effort needed to design, build and test computer software using object-oriented methods. The Unified Modeling Language (UML) is emerging as an industry standard for recording the results of object-oriented analysis and design. We focus specifically on the use of the products of the UML as early… CONTINUE READING

Similar Papers

Citations

Publications citing this paper.

References

Publications referenced by this paper.
SHOWING 1-10 OF 19 REFERENCES

Measuring Object-Oriented System Size with Use Cases

  • Proceedings of the Seventh European Software Control and Metrics Conference
  • 1996

Predicting System Size with Function Points and Use Cases American Management Systems, Best Practices Focus Series

  • AMS
  • 1996

An Introduction to 3D Function Points

Whitmire A Scott, Whitmire
  • Software Development Magazine
  • 1995

Sizing and Estimating Software in Practice: Making Mark 2 FPA Work" Neil Douglas and Steve Treble

  • Sizing and Estimating Software in Practice: Making Mark 2 FPA Work" Neil Douglas and Steve Treble
  • 1995

Sizing for Object-Oriented SystemsFunction Point Counting Practices Manual

Gupta
  • Proceedings of the 1996 Fall IFPUG conference, 2-4
  • 1994

3D Function Points: Scientific and Real-Time Extensions to Function Points

Whitmire A Scott, Whitmire
  • Published in the Proceedings of the 1992 Pacific Northwest Quality Conference. A more accessible version is [Whitmire
  • 1992

Object Lifecycles: States and Processes

Sally Shlaer, Stephen Mellor
  • Object Lifecycles: States and Processes
  • 1992