home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.software-eng:5197 comp.edu:2266
- Newsgroups: comp.software-eng,comp.edu
- Path: sparky!uunet!munnari.oz.au!cs.mu.OZ.AU!munta.cs.mu.OZ.AU!tja
- From: tja@munta.cs.mu.OZ.AU (Tim Arnold)
- Subject: Re: Class Project For Software Engineering Course
- Message-ID: <9300509.25626@mulga.cs.mu.OZ.AU>
- Sender: news@cs.mu.OZ.AU
- Organization: Computer Science, University of Melbourne, Australia
- References: <1i4lfqINN849@crcnis1.unl.edu> <1ia3e0INN9m5@aludra.usc.edu>
- Date: Mon, 4 Jan 1993 22:09:36 GMT
- Lines: 13
-
- karrer@aludra.usc.edu (Anthony Karrer) writes:
-
- [stuff about suitable projects]
-
- >These are particularly well suited to this class because they are
- >fairly well known by students or can easily be learned. As such you
- >avoid the many of the problems of ill-defined requirements specifications
- >leading to heart-ache at the end of the semester.
-
- Surely one of the major lessons to learn in Software Engineering is
- the problem of adequately defining requirements. The actual project
- here changes every year or so but it is intentionally ill-defined.
- Tutors play the role of client in clarifying requirements.
-