Handbook 1996 : Faculty of Engineering (Volume 4 page 106)
Computer Science subject : Next:433-341 | Prev:433-332 | Search | Help
433-340 "Software Engineering Project" appears differently in several places - choose the one you want:
1. Computer Science, Faculty of Engineering (v4, p106) : Next:433-341 | Prev:433-332
Credit points: 20.00
Coordinator: Dr. L. Johnston
Corequisite: Computer Science 433-341
Contact: Ten one-hour tutorials and 120 hours project work
Timetable: Double semester.
Objectives:
On successful completion of this subject students should:
- have experienced team-oriented software engineering
- appreciate the importance of planning and managing the software process
- have been involved in requirements elicitation and the subsequent phases of software development including documentation, requirements analysis, specification, design, implementation and testing
- be familiar with some of the problems that can arise during execution of the software development process
Content:
Students will work on a substantial practical team project drawn from areas such as system software, applications software, graphics or networks. They will be involved in all phases of the project, including requirements analysis, functional specification, system design, implementation, documentation and testing.
Assessment:
Satisfactory contribution to the group project, including system and user documentation, progress and final reports, as specified at the start of the subject.
1. Computer Science, Faculty of Engineering (v4, p106) : Next:433-341 | Prev:433-332
2. Computer Science, Faculty of Science (v4, p183) : Next:433-341 | Prev:433-332
Credit points: 20.0
Coordinator: Dr L Johnston.
Corequisite: Computer Science 433-341
Contact: Ten 1-hour tutorials and 120 hours project work
Timetable: Double semester.
Objectives:
On successful completion of this subject, students should:
- have experienced team-oriented software engineering;
- appreciate the importance of planning and managing the software process;
- have been involved in requirements elicitation and the subsequent phases of software development including documentation, requirements analysis, specification, design, implementation and testing;
- be familiar with some of the problems that can arise during execution of the software development process.
Content:
Students will work on a substantial practical team project drawn from areas such as system software, applications software, graphics, or networks. They will be involved in all phases of the project, including requirements analysis, functional specification, system design, implementation, documentation, and testing.
Assessment:
Satisfactory contribution to the group project, including system and user documentation, progress and final reports, as specified at the start of the subject.
* Note that CONTACT, CONTENT, COORDINATOR, OBJECTIVES, POINTS differs from the maintainer's version above. A log of variations is available.
2. Computer Science, Faculty of Science (v4, p183) : Next:433-341 | Prev:433-332
Status: Official 1996 Date created: Oct 9 1995 Last modified: Oct 9 1995 Authorised by: Academic Registrar Email enquiries: Course_Information@registrar.unimelb.edu.au
Maintained by: Dept. of Computer Science, Faculty of Engineering.
Copyright © University of Melbourne 1995,1996.