Industry-academia collaboration to provide CASE tools for software engineering classes
- 132 Downloads
The University of Texas' project-based Software Engineering class for undergraduates has used software tools for development and as final products for several years. When the opportunity arose to use Electronic Data Systems' (EDS) in-house development tool, INCASE, in the class, it was a natural extension to earlier work.
The major change is the emphasis on data rather than process modelling. With a CASE tool, students are able to concentrate on requirements elicitation, prototyping, screen design and other more modern topics than are usually covered in a one semester software engineering course. The project is large enough that the software engineering techniques and tools are seen as valuable. The course and CASE tool are described, together with lessons learned and suggestions for similar collaborative efforts.
KeywordsSoftware Engineering Software Engineer Requirement Elicitation Case Tool State Transition Diagram
Unable to display preview. Download preview PDF.
- [Bru88]Bruce, T. "CASE Brought Down to Earth". Database Programming & Design, Oct. 1988.Google Scholar
- [BYTE90]"Making a Case for CASE". BYTE, Dec 1989.Google Scholar
- [Che85]Chen, P. "Database Design Based on Entity and Relationship". Principals of Data Base Design. Englewood Cliffs, New Jersey: Prentice-Hall Publishing Company, 1985.Google Scholar
- [Cran89]Crandall, V. "The Development of an Industry-Education Relationship in the the Test Environment: The Novell-Brigham Young University Experience". Sixth International Conference on Testing Computer Software, Washington, DC. May 22–24, 1989.Google Scholar
- [EDS90]Electronic Data Systems. INCASE Product Overview. Release 9.5. July 1990.Google Scholar
- [Mac90]Mach, R. "Information Engineers Wanted to Build Enterprise Models". Software Magazine, September, 1990.Google Scholar
- [Park90]Parker, T. "CASE on the PC: The state of the art". Computer Language, Jan 1990.Google Scholar
- [Pre87]Pressman, R. Software Engineering: A Practitioner's Approach. 2nd ed. McGraw-Hill, 1987.Google Scholar
- [Rum91]Rumbaugh, J., M. Blaha, W. Premerlani, F. Eddy, and W. Lorensen. Object-Oriented Modeling and Design. Prentice Hall, 1991.Google Scholar
- [Shn87]Shneidermann, B. Designing the User Interface. Addison-Wesley, 1987.Google Scholar
- [Wei88]Weiderman, N., N. Habermann, M. Borger, M. Klein. "A Methodology and Criteria for Evaluating Ada Programming Support Environments". Software Engineering Institute Annual Report, Carnegie Mellon University, 1988.Google Scholar
- [Wer90a]Werth, L. H. “Object Oriented Programming and Design Class Projects — Macintosh User Interface Tools.” Journal of Object Oriented Programming, Nov/Dec 1990.Google Scholar
- [Wer90b]Werth, L. H. “Graphical Interfaces as Software Engineering Projects”. Proceedings of the Twenty-First Symposium on Computer Science Education, Feb, 1990.Google Scholar
- [Wer89a]Werth, L. H. “Teaching Object-Oriented Programming Using MPW/MacApp on the Macintosh.” July, 1989 at the Software Engineering Institute in Software Engineering Education, L. Deimel (Ed). Springer-Verlag, 1989.Google Scholar
- [Wer89b]Werth, L. H. “Preparing Students for Programming-In-The-Large.” Proceedings of the Twentieth Symposium on Computer Science Education, Feb, 1989.Google Scholar
- [Wer88]Werth, L. H. “Software Tools at the University: Why, What and How.” April, 1988 at the Software Engineering Institute in Software Engineering Education, G. Ford (Ed). Springer-Verlag, 1988.Google Scholar
- [Wer87]Werth, L. H. “A Survey of Software Engineering Education”. SIGSOFT Software Engineering Notes, Oct. 1987.Google Scholar
- [Zue98]Zuehow, T. “Introducing EDS Consolidated Data Modeling”. EDS Technical Journal, Vol. 3, No. 2, 1989.Google Scholar