We plan to examine more carefully the effort and bug data obtained in this small study. We also hope to refine it and run a study again next year with different students. But the preliminary results suggest that a commercial software developer might do well to adhere carefully to A/E/L principles on a realistically large software project, collecting as much similar and related data as possible, in an attempt to document a convincing empirical case for the productivity and quality advantages of A/E/L. By knowing the cost of design and coding time, maintenance activities, etc., and having estimates of the different amounts of time involved in these tasks, a manager should be able to make a more informed trade-off between software engineering costs and run-time performance costs of design decisions.