The primary purpose of Computer Aided Software Engineering (CASE) tools has been to assist in organizing and expediting the work performed by a systems analyst. Based upon the opinions of some experts in the field, learning should also be emphasized in the construction of CASE tools. Some general criticisms of CASE tools are considered in this article with respect to their educational implications. As a solution to these problems, the author proposes several modifications to the standard CASE software. Some of these changes are to be incorporated into a special educational version of a CASE tool. The modifications are designed to incorporate teacher-student interaction factors.
Get full access to this article
View all access options for this article.
References
1.
CareyJ. M. and McCleodR.Jr., Use of System Development Methodology and Tools, Journal of Systems Management, 41: 3, pp. 30–35, 1988.
2.
GaneC. and SarsonT., Structured Methodology: What Have We Learned?, Computer World/EXTRA, 14: 38, pp. 52–57, 1980.
3.
MannR. J., Incorporating Analyst/Designer Workbenches into the Systems Analysis and Design Curriculum, Journal of Systems Management, 41: 6, pp. 22–27, 1988.
4.
NeccoC. R.TsaiN. W., and HolgesonK. W., Current Usage of Case Software, Journal of Systems Management, 42: 5, pp. 6–11, 1989.
5.
ColterM. A., A Comparative Examination of Systems Analysis Techniques, MIS Quarterly, 8: 1, pp. 51–66, 1984.
6.
YadavS. B.BravocoR. R.ChatfieldA. T., and RajkumarT. M., Comparison of Analysis Techniques for Information Requirement Determination, Communications of the ACM, 31: 9, pp. 1090–1097, 1988.
7.
GoodwinA. N.GleesonJ. W., and GwillianD., An Assessment of the IDEF Notations as Descriptive Tools, Information Systems, 14: 1, pp. 13–28, 1989.
8.
ReasonJ., Cognitive Aids in Process Environments: Prothesis or Tools?, International Journal of Man-Machine Studies, 27: 5, pp. 463–470, 1987.
9.
FittsP. M., Human Engineering for an Effective Air Navigation and Traffic Control System, National Research Council, Washington, D.C., 1951.
10.
KozarK., Adopting Systems Development Methods, Journal of Management Information Systems, 5: 4, pp. 73–86, 1984.
11.
ZelkowitzM. B.YehR. T.HamletR. C.GannonJ. D., and BasiliV. R., Software Engineering Practice in the U.S. and Japan, Computer, IEEE Computer Society, 17: 6, pp. 57–65, 1984.
12.
MartinJ., Information Engineering-Book I, Introduction, Prentice Hall, Englewood Cliffs, New Jersey, pp. 29–55, 1989.
13.
BravocoR. R. and YadavS. B., Requirement Definition Architecture-An Overview, Computers in Industry, 6: 4, pp. 237–251, 1985.
14.
WindsorJ. C., Are Automated Tools Changing Systems Analysis and Design?, Journal of Systems Management, 39: 11, pp. 28–32, 1986.
15.
YourdonE., Modern Structured Analysis, Yourdon Press, Englewood Cliffs, New Jersey, 1989.
16.
CervenyR. P.GarrityE. J., and SandersG. L., A Problem-Solving Perspective on Systems Development, Journal of Management Information Systems, 6: 4, pp. 103–122, 1990.
17.
McIntyreS. C. and HigginsL. F., Object-Oriented Systems Analysis and Design, Journal of Management Information Systems, 5: 1, pp. 25–35, 1988.
18.
MingersJ., Comparing Conceptual Models and Data Flow Diagrams, Computer Journal, 31: 4, pp. 376–379, 1988.
