INDUSTRY PROJECT 3B
CSE3PRB
2014
Credit points: 15
Subject outline
The industry project enables students to experience real-life involvement in the planning and development of a medium sized team-based ICT project. It utilises a teamwork approach to software engineering and integrates previously learned skills and knowledge relating to social and ethical issues. This subject follows on from CSE3PRA and covers project management, team organisation and communication, implementation, testing, integration, re-use, configuration management, user and system documentation, reporting, milestone and final presentation. The project is completed over two semesters, students will receive an X grade for CSE3PRA and must enrol in this unit in order to complete and receive a mark for the project.
Faculty: Faculty of Science, Tech & Engineering
Credit points: 15
Subject Co-ordinator: Torab Torabi
Available to Study Abroad Students: Yes
Subject year level: Year Level 3 - UG
Exchange Students: Yes
Subject particulars
Subject rules
Prerequisites: CSE3PRA
Co-requisites: N/A
Incompatible subjects: CSE4PRO, CSE40PRJ, CSE4PRG, CSE4PRA, CSE4PRB, CSE5PRB
Equivalent subjects: N/A
Special conditions: This unit of study represents the second semester of a year-long program. Students MUST complete both CSE3PRA and CSE3PRB in two consecutive semesters.
Learning resources
Readings
| Resource Type | Title | Resource Requirement | Author and Year | Publisher |
|---|---|---|---|---|
| Readings | Industry Project Guidelines | Prescribed | Torabi, T. | LA TROBE UNIVERSITY |
| Readings | Software Engineering (Ninth Edition) | Prescribed | Sommerville, I. | ADDISON-WESLEY, 2009. |
Dandenong, 2014, Semester 2, Day
Overview
Online enrolment: Yes
Maximum enrolment size: N/A
Enrolment information:
Subject Instance Co-ordinator: Torab Torabi
Class requirements
Computer LaboratoryWeek: 31 - 43
One 1.0 hours computer laboratory per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.
Evidence Based LearningWeek: 31 - 43
One 1.0 hours evidence based learning per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.
"Evidence based learning/problem based learning"
LectureWeek: 31 - 43
One 1.0 hours lecture per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.
SeminarWeek: 31 - 43
One 1.0 hours seminar per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.
Assessments
| Assessment element | Comments | % |
|---|---|---|
| Final system presentation to client and staff 1-hour(team) | 20 | |
| Second prototype of the system to client and staff 30-minutes (team) | 10 | |
| System prototype and poster presentation to staff 30-minutes (team) | 8 | |
| User documentation (20-pages) & revised design document (80-pages) & system implementation (team) | 30 | |
| Weekly system implementation progress evaluation report (200-words) and presentation (individual) | 32 |
Melbourne, 2014, Semester 2, Day
Overview
Online enrolment: Yes
Maximum enrolment size: N/A
Enrolment information:
Subject Instance Co-ordinator: Torab Torabi
Class requirements
SeminarWeek: 31 - 43
One 1.0 hours seminar per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.
LectureWeek: 31 - 43
One 1.0 hours lecture per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.
Evidence Based LearningWeek: 31 - 43
One 1.0 hours evidence based learning per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.
"Evidence based learning/problem based learning"
Computer LaboratoryWeek: 31 - 43
One 1.0 hours computer laboratory per week on weekdays during the day from week 31 to week 43 and delivered via face-to-face.
Assessments
| Assessment element | Comments | % |
|---|---|---|
| Final system presentation to client and staff 1-hour(team) | 20 | |
| Second prototype of the system to client and staff 30-minutes (team) | 10 | |
| System prototype and poster presentation to staff 30-minutes (team) | 8 | |
| User documentation (20-pages) & revised design document (80-pages) & system implementation (team) | 30 | |
| Weekly system implementation progress evaluation report (200-words) and presentation (individual) | 32 |