cse5prb industry project b
INDUSTRY PROJECT B
CSE5PRB
2018
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 CSE5PRA 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 CSE5PRA 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 5 - Masters
Exchange StudentsYes
Subject particulars
Subject rules
Prerequisites CSE5PRA
Co-requisitesN/A
Incompatible subjects CSE3PRO, CSE4PRO, CSE3PRG, CSE4PRG, CSE4PRB, CSE3PRA, CSE3PRB, CSE5ITP AND Students in the following courses are not permitted to enrol: SBCS, SBIT, SBCSGT, SVCSE, SZCSC, SBITP and SBBIY.
Equivalent subjectsN/A
Special conditionsN/A
Learning resources
Readings
| Resource Type | Title | Resource Requirement | Author and Year | Publisher |
|---|---|---|---|---|
| Readings | Software Engineering | Prescribed | Sommerville, I 2009 | 9TH EDISION, ADDISON-WESLEY |
| Readings | Industry Project Guidelines: a 70 page Handbook is a complete guideline for process, organisation, assessments, standards, and templates based on IEEE body for development of the project | Recommended | Torabi, T | LATROBE UNIVERSITY |
Graduate capabilities & intended learning outcomes
01. Critically evaluate, describe and demonstrate the skills and knowledge to effectively participate, contribute, manage conflicts, and document the running of 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 effective team management. Provide weekly feedback to project teams.
02. Verify and describe and document the design of a software system using UML, and articulate the system design using standards.
- Activities:
- Provide the process and approach for developing business requirement and explain examples of business requirement by example. Paticapate in workshops to practice necessary skills. Highlight the importance of consistancy in design.
03. Analyse, communicate and professionally present the system prototype, project plan, and testing of the system to both technical and non-technical audiences.
- Activities:
- Highlight the standands, expectations, guidelines process, and content for presentation of project plan and system prototype. Present seminars and workshops to practise the content and process of a good presentation.
04. Articulate and develop the detailed user and maintenance document of a system using professional standards and guidelines provided in the subject handbook.
- Activities:
- Discuss the detail user and maintenance of a system by applying standrard notation. Provide practical workshops and seminars for developing documentation and testing the system.
05. Communicate and professionally present the detail implementation of the system and evidence of system operations to both technical and non-technical audiences.
- Activities:
- Emphasise the standands, expectations, guidelines process, and content for presentation of system implementation and testing. Present feedback and seminars to practise the content of a good testing and presentation.
Subject options
Select to view your study options…
Melbourne, 2018, Semester 2, Day
Overview
Online enrolmentNo
Maximum enrolment sizeN/A
Enrolment information
Subject Instance Co-ordinatorTorab Torabi
Class requirements
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.
Laboratory ClassWeek: 31 - 43
One 1.0 hours laboratory class 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.
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 | % | ILO* |
|---|---|---|---|
| Final system presentation (Group task: 10 mins per student, 1,000-words equivalent) | 25 | 05 | |
| Presentation of the system to client and staff (Group task: 10 mins per student, 1,000-words equiv) | 15 | 02, 03 | |
| User & maintenance document & final system implementation (Group task: 2,000-words equiv / student) | Weekly maintenance document upgrade and consistency check | 30 | 04 |
| Sprint project management reports (750-words equivalent) Weeks 1, 2, 3, 4 | Reports include self reflective evaluations | 30 | 01 |