Curriculum Committee ("CC") Minutes for 7 October 1994

______________________________________________________________________________


Attending:  Fujimura, Kerr, Long, Ogden, Perlman, Soundararajan, Tavenner,
Weide, Winters, Yagel, Yeack, Zhao


1. Apparently there are four general questions that CC should deal 
   with this year.  In approximately priority order (based on urgency
   and/or likely timeframe for being brought to CC attention), they are:
   
   (a) Introductory courses (100, 101, 201, 211, 221, 294I)
   
       Is there unnecessary duplication?  What are the costs involved in
       having so many introductory courses?  Business School might be
       interested in replacing 211 with something like a beefed-up 101;
       we might want to withdraw 212 altogether; etc.  All of these
       questions are connected.  An ad hoc subcommittee of Cheryl (chair),
       Neelam, Roni, and David will identify specific questions that need
       to be addressed (e.g., enrollments and trends, demographics of
       audiences, other department requirements, current/historical
       rationales, political considerations, likely futures).  They will
       report on Oct 21, and CC will then take action to consider specific
       questions in more detail.
       
   (b) Software "spine" courses for CS majors (221, 222, 321, 560, 680)

       Tim reported that no funding has yet been obtained for this effort.
       DoD funding looks improbable at this point, which means that Ada
       might have a less important role to play (which might help to allay
       fears expressed by some faculty last spring).  The group is pursuing
       other funding sources, including foundations, and would like to know
       what faculty would like to see fleshed out so that its "blessing" can be
       obtained to go ahead immediately in negotiations with potential
       sponsors.  An ad hoc subcommittee of Doug (chair), Kikuo, and Ken
       will identify specific questions that need to be addressed before
       Curriculum Committee and faculty "blessing" can be obtained for this
       direction of curriculum effort.  They will report on Oct 21,
       and CC will decide what to do next from there.

   (c) Scientific computation program
   
       This is a proposed graduate program, so primary responsibility
       should be Graduate Studies'.  But CC can get info on course
       changes and additions in a comprehensive plan, not just piece-meal,
       as a preview.  An ad hoc subcommittee of Gary (chair) and Feng
       will identify specific questions that need to be addressed before
       CC and faculty "blessing" can be obtained for this general
       direction of curriculum effort.  They will report on Oct 21,
       and CC will decide what to do next from there.  Detailed action
       will wait until after the program has been endorsed by Graduate
       Studies Committee and the faculty.
       
   (d) Numbering of capstone design courses
   
       Should our capstone design courses for undergraduate majors be
       numbered as 600-level courses?  Why or why not?  This issue is
       not yet assigned.


2. There are several existing courses where CC attention is required.  In
   approximate priority order (based on urgency, amount of work involved, and
   externally-imposed deadlines) these are:

   (a) 694J (Social and Ethical Issues in Computing)
   
       This will be piloted as a 1-hr course in Winter and should be converted
       to a permanent course ASAP, since it is important for accreditation
       of CSE program.  Ken and Neelam should report on the experience of
       last year's 2-hr pilot, and should make a recommendation on how to
       handle teaching credit for a 1-hr version, before CC does anything
       else.
       
   (b) 681, 781, 782 (Graphics sequence)
   
       Official course descriptions need to be updated to match modern
       course content.  Roni and Rick should prepare paperwork for review
       by CC chair, and should request CC action ASAP.
       
   (c) 694I (Programming in C++)
   
       Should this be converted to a permanent course; e.g., 459.51?  Is it
       possible to teach this material in a 1-hr course?  Would 459.21 (C
       course) go away if this were permanent?  Rafe should report on this
       before CC does anything else.

   (d) 694E (Introduction to High-Performance Computing)
   
       Should this be converted to a permanent course; e.g., 621?  Saday
       should report on this before CC does anything else.

   (e) 650 (Information Storage and Retrieval)
   
       Official course description needs to be updated to match modern
       course content.  Gary should prepare paperwork for review
       by CC chair, and should request CC action ASAP.

   (f) Capstone design course for hardware/software option in ENG
   
       A CIS (as opposed to EE) course suitable as a capstone design course
       for this option has been considered by subcommittees for the past
       two years.  The seeds of a specific proposal are showing.  A
       subcommittee of Feng (chair), Kikuo, Jay, Panda, and Saday will make a
       proposal as soon as feasible later this year.
       
   (g) 360 (Introduction to Computer Systems)
   
       Jay, Judy, and Saday should report on the status of this revised
       course after this quarter.  There may be nothing left for CC to do.

   (h) 675 (Introduction to Computer Architecture)
    
       Should we update prerequisites now that 675.01 and 675.02 are separate?
       Undergraduate Studies will inform CC if and when action is required.

______________________________________________________________________________


Next meeting: Friday, 21 October 1994, 2:30-3:20 PM, in DL 298.


Respectfully submitted,

	Bruce W. Weide, CC Chair