INDUSTRY PROJECT 3B

CSE3PRB

2017

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.

SchoolSchool Engineering&Mathematical Sciences

Credit points15

Subject Co-ordinatorTorab Torabi

Available to Study Abroad StudentsYes

Subject year levelYear Level 3 - UG

Exchange StudentsYes

Subject particulars

Subject rules

Prerequisites CSE3PRA

Co-requisitesN/A

Incompatible subjects CSE4PRO, CSE40PRJ, CSE4PRG, CSE4PRA, CSE4PRB, CSE5PRB AND students enrolled in any Graduate Diploma or Masters by Coursework course.

Equivalent subjectsN/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 TypeTitleResource RequirementAuthor and YearPublisher
ReadingsIndustry Project GuidelinesPrescribedTorabi, T.LA TROBE UNIVERSITY
ReadingsSoftware Engineering (Ninth Edition)PrescribedSommerville, I.ADDISON-WESLEY, 2009.

Graduate capabilities & intended learning outcomes

01. Describe and demonstrate the skills and knowledge to participate, contribute, manage conflicts, and document of running a team project meetings.

Activities:
Highlight the importance of running of team as a very important aspect of running a project. Show examples and videos of team management. Provide weekly feedback to project teams.
Related graduate capabilities and elements:
Teamwork (Teamwork)
Speaking (Speaking)
Ethical Awareness (Ethical Awareness)
Discipline-specific GCs (Discipline-specific GCs)
Writing (Writing)

02. Describe how to improve design document a software system using UML, and articulate the system design using UML standards. Describe the importance of good reference maintenance and user documentation.

Activities:
Provide the process and approach for developing software system and explain examples of user and maintenance documentation. Participate in workshops to practice necessary skills and improving such skills. Highlight the importance of consistency in reference design and software implementation.
Related graduate capabilities and elements:
Creative Problem-solving (Creative Problem-solving)
Writing (Writing)
Teamwork (Teamwork)
Discipline-specific GCs (Discipline-specific GCs)
Inquiry/ Research (Inquiry/ Research)
Critical Thinking (Critical Thinking)
Quantitative Literacy/ Numeracy (Quantitative Literacy/ Numeracy)

03. Communicate and professionally present the system prototype, plan, and maintenance and testing of the system to both technical and non-technical audiences.

Activities:
Highlight the standards, expectations, guidelines process, and content for presentation of system testing and system prototype. Present seminars and workshops to practice the content and process of a good presentation.
Related graduate capabilities and elements:
Discipline-specific GCs (Discipline-specific GCs)
Speaking (Speaking)
Inquiry/ Research (Inquiry/ Research)
Teamwork (Teamwork)
Ethical Awareness (Ethical Awareness)
Writing (Writing)

04. Articulate and develop the detail user and maintenance document of a system using professional standards and guidelines provided in the subject handbook.

Activities:
Discuss the detail user and maintenance documentation of a system by applying standrard notation. Provide practical workshops and seminars for developing documentation and testing a the system.
Related graduate capabilities and elements:
Creative Problem-solving (Creative Problem-solving)
Teamwork (Teamwork)
Critical Thinking (Critical Thinking)
Writing (Writing)
Inquiry/ Research (Inquiry/ Research)
Discipline-specific GCs (Discipline-specific GCs)
Quantitative Literacy/ Numeracy (Quantitative Literacy/ Numeracy)

05. Communicate and professionally present the detail implementation of the system and evidences of system opreations to both technical and non-technical audiences.

Activities:
Emphasis on the standards, expectations, guidelines process and content for presentation of system implementation and testing. Present and provide feedback and seminars so students can practice the content of a good system testing and presentation.
Related graduate capabilities and elements:
Discipline-specific GCs (Discipline-specific GCs)
Speaking (Speaking)
Inquiry/ Research (Inquiry/ Research)
Ethical Awareness (Ethical Awareness)
Teamwork (Teamwork)
Writing (Writing)

Subject options

Select to view your study options…

Start date between: and    Key dates

Dandenong, 2017, Semester 2, Day

Overview

Online enrolmentYes

Maximum enrolment sizeN/A

Enrolment information

Subject Instance Co-ordinatorTorab Torabi

Class requirements

Computer Laboratory Week: 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 Learning Week: 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"

Lecture Week: 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.

Seminar Week: 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 elementComments% ILO*
Final system presentation to client and staff 1-hour(team)20 05
Presentation of the system to client and staff 30-minutes (team)15 02, 03
System prototype and poster presentation to staff 30-minutes (team)5 02, 03
User documentation (20-pages) & revised Maintenance document,Fortnightly maintenance document upgrade and consistency check (80 pages) & system implementation (team)30 02, 04
Sprint project management reports (200-words) weeks 2,4,6,8,10 (indvidual)30 01, 02

Melbourne, 2017, Semester 2, Day

Overview

Online enrolmentYes

Maximum enrolment sizeN/A

Enrolment information

Subject Instance Co-ordinatorTorab Torabi

Class requirements

Seminar Week: 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.

Lecture Week: 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 Learning Week: 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 Laboratory Week: 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 elementComments% ILO*
Final system presentation to client and staff 1-hour(team)20 05
Presentation of the system to client and staff 30-minutes (team)15 02, 03
System prototype and poster presentation to staff 30-minutes (team)5 02, 03
User documentation (20-pages) & revised Maintenance document,Fortnightly maintenance document upgrade and consistency check (80 pages) & system implementation (team)30 02, 04
Sprint project management reports (200-words) weeks 2,4,6,8,10 (indvidual)30 01, 02