Xref: utzoo comp.edu:2657 comp.software-eng:2397
Path: utzoo!yunexus!ists!jarvis.csri.toronto.edu!mailrus!uunet!ncrlnk!ncrcae!hubcap!billwolf%hazel.cs.clemson.edu
From: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu (William Thomas Wolfe, 2847 )
Newsgroups: comp.edu,comp.software-eng
Subject: Re: CS education
Message-ID: <7091@hubcap.clemson.edu>
Date: 16 Nov 89 23:27:16 GMT
Article-I.D.: hubcap.7091
References: <1054@scotty.Atlanta.NCR.COM>
Sender: news@hubcap.clemson.edu
Reply-To: billwolf%hazel.cs.clemson.edu@hubcap.clemson.edu
Lines: 20

From kcby@scotty.Atlanta.NCR.COM (K. C. Yakemovic):
> It is my opinion that one of the greatest weaknesses we have in industry is
> in the *requirements analysis* area.  I'll agree you can teach most of the
> other software engineering processes with "uncomplicated" domains.  But it
> seems to me that learning to do requirements analysis requires a reasonably
> complicated domain.  

    The limited time factor will probably preclude doing this in
    the first course; but when it *is* done (in a more advanced 
    course), I would think that having the students do requirements
    analysis by looking up the domain in a textbook someplace (as is 
    possible with operating systems and compilers) is unlikely to be 
    of maximum value; instead, a domain should be selected from the 
    "real world", for which little advance documentation is available, 
    and in which real users will have to be satisfied.  Local industries
    would probably be very happy to have some real problems solved for 
    them for free... they would be an excellent source for "real" projects.

 
    Bill Wolfe, wtwolfe@hubcap.clemson.edu