OO Process and Metrics for Effort Estimation
Overview: Software development remains difficult to plan. Object-orientation
has not changed the picture thus far. However due to the greater continuity
in OO across the life-cycle - objects everywhere - there is hope that OO
may improve the predictability of OO projects.
This workshop is a continuation of a similar, very successful workshop held
at OOPSLA95 with the same theme.
Goals: This workshop will focus on the two ingredients required for
planning SW projects:
- More detailed processes than what is currently available (waterfall,
spiral, fountain, clean-room, etc.). This would help to identify more
intermediate milestones.
- Effort tracking and estimation metrics. This would help to measure
progress and to recognize earlier that unexpected roadblocks are
encountered.
Focus: The emphasis of this workshop is expected to be exercised on the
following questions:
- What are good micro processes for OO analysis, design, implementation,
testing, maintenance?
- How do we preserve the developers creativity when development processes
are defined with a finer granularity than is currently customary?
- How do we ensure compatibility of micro processes and macro processes
like waterfall, spiral, fountain, clean-room, etc.
- What are project characteristics for choosing a macro process?
- How does reuse fits in the development process?
- Can the Albrecht function point technique be used (as is? modified?) for
an initial effort estimation?
- Are task points or use case points a good alternative to traditional
measures?
- How do we estimate remaining effort during development?
- How do we correct effort estimation for reuse?
- Which product metrics, if any, can be used for effort estimation?
- Effort estimation is rooted in reasoning by analogy. Can we have
a generic estimation technique or will they be domain/ company/ product
line specific?
- Effort estimation requires systematic collection of data. At what
granularity? Per subsystem? Per class? Per attribute? Per transition
network? Per member function?
- What role can/ should OO CASE tools play?
Requirements for Attendance:
Potential attendants are required to submit a position paper with a minimum
of three double space pages, 12 points, postscript (or ascii) format, on
one or more of the proposed topics (or somehow explicitly related to them).
Experience reports and research papers are equally welcomed.
A selected number of these papers will be presented during the workshop.
Please pay attention to the following dates:
- Submission deadline: August 1st, 1996
- Acceptance notification: August 15th, 1996
Organizers:
Fernando Brito e Abreu (Lisbon Technical University / INESC, Portugal)
Dennis de Champeaux (OntoOO, USA)
Brian Henderson-Sellers (Swinburne University of Technology, Australia)
Simon Horner (IBM, UK)
Granville Miller (BroadBand Technologies Inc, USA)
Submissions:
Granville Miller
BroadBand Technologies, Inc.
5305 Burning Oak Ct.
Raleigh, N.C. 27606
USA
Telephone:
(919) 405-4558
Fax:
(919) 544-5356
Email:
ggm@bbt.com
