CREATING AN I-CASE ENVIRONMENT: PITFALLS AND PROMISES Panel Members Mary J. Granger Assistant Professor Management Science Department George Washington University Washington, DC 20052 202-994-7159 FAX: 202-994-4930 GRANGER@GWWM Joyce Currie Little Professor and Chairperson Computer and Information Sciences Towson State University Towson, Maryland 21204 410-830-3701 FAX: 410-830-3868 JCLIâITLE@TOWSONVX Mary R. Vorgert Academic Programs Manager Texas Instruments 6620 Chase Oaks Blvd. Piano, Texas 75086 214-575-5062 FAX: 214-575-6183 Lois Zells Lois Zells and Associates 11402 N. 53rd Place Scottsdale, Arizona 85254 602-991-0504 FAX: 602-483-8469 Computer-Aided Software/System Software/System Engineering process. Engineering (CASE) and Integrated Computer-Aided of the (I-CASE) are software tools developed to aid the automation similar to other emerging technologies, system development CASE and I-CASE, are constantly changing the world of computing. 1980s. Early CASE in the 1990s is different software engineering software from CASE in the development methods CASE tools supported the introduction traditional (SDMS). However, both industrial I-CASE of diverse SDMS are confounding Universities the integration of CASE in to integrate between and academic settings. and business organizations preparing difference face a great challenge. Contributing to the challenge is the significant systems software development, of an appropriate CASE tool. real-time engineering and business softwaxe development all in need Within
/lp/association-for-computing-machinery/creating-an-i-case-environment-abstract-pitfalls-and-promises-0habxS0Ea7