Lessons learned in managing object-oriented development
- 1 January 1993
- journal article
- Published by Institute of Electrical and Electronics Engineers (IEEE) in IEEE Software
- Vol. 10 (1) , 43-53
- https://doi.org/10.1109/52.207226
Abstract
The author relates experience gained in developing tightly constrained, custom object-oriented systems, in which success depends on delivering a functional system on time and on budget, often for a fixed price. Many of the systems developed had the additional constraint of real-time requirements, and most had some kind of reuse goals. The organization, planning, and progress tracking of an object-oriented project are discussed. The management model and resources used in such a project are described.Keywords
This publication has 3 references indexed in Scilit:
- Software risk management: principles and practicesIEEE Software, 1991
- A laboratory for teaching object oriented thinkingACM SIGPLAN Notices, 1989
- On visual formalismsCommunications of the ACM, 1988