Streamlining the project cycle with object-oriented requirements

Authors:
Richard Jordan;Ruth Smilan;Alex Wilkinson
Affiliations:
AT&T Bell Loboratories, 6200 East Broad Street, Room 1D-259S, Columbus, Ohio;AT&T Bell Loboratories, 6200 East Broad Street, Room 1E-254, Columbus, Ohio;AT&T Bell Loboratories, 290 Davidson Avenue, Room E1C-143, Somerset, New Jersey
Venue:
OOPSLA '94 Proceedings of the ninth annual conference on Object-oriented programming systems, language, and applications
Year:
1994

Citing 4
Cited 2

An object-oriented requirements specifications method

Communications of the ACM
A laboratory for teaching object oriented thinking

OOPSLA '89 Conference proceedings on Object-oriented programming systems, languages and applications
Object-oriented software engineering

Object-oriented software engineering
Essays on object-oriented software engineering (vol. 1)

Essays on object-oriented software engineering (vol. 1)

A practical approach to combining requirements definition and object-oriented analysis

Annals of Software Engineering
Making way for Java in an information technology masters program

Current issues in IT education

Quantified Score

Hi-index	0.00

Visualization

Abstract

We have succeeded in streamlining the product development cycle by incorporating object-oriented technology into the requirements definition phase. We have developed a general format, supporting tools and a methodology for describing requirements in an object-oriented fashion. We have validated our approach by incorporating it into the new object-oriented methods being applied to our current project and observing the benefits that resulted. We describe the problems with our earlier requirements specifications which make them unsuitable for developing good object-oriented systems and then explain our approach which eliminates these pitfalls.