INDUSTRY PROJECT A
Credit points: 15
The industry project enables students to experience real-life involvement in the planning and development of a medium sized software project. It utilises a teamwork approach to software engineering and integrates previously learned skills and knowledge relating to technical, social and ethical issues. The subject covers project management, team organisation and communication, project estimation and planning, documentation and reporting and milestone presentation, self-reflective evaluation of project management process. Project teams must be finalised by the first week of term. The project is completed over two consecutive semesters, students will receive an X grade for CSE5PRA and must enrol in CSE5PRB in order to complete and receive a mark for this subject.
SchoolSchool Engineering&Mathematical Sciences
Subject Co-ordinatorScott Mann
Available to Study Abroad StudentsYes
Subject year levelYear Level 5 - Masters
Prerequisites CSE5DES OR admission in the following courses: SMCSC, SMITCN, SMIT, SMICT or SGCS.
Incompatible subjects CSE3PRO, CSE4PRO, CSE3PRG, CSE4PRG, CSE4PRA, CSE4PRB, CSE3PRA, CSE3PRB, CSE5ITP AND Students in the following courses are not permitted to enrol: SBCS, SBIT, SBCSGT, SVCSE, SZCSC, SBITP and SBBIY.
Special conditions All students enrolled in this subject must enrol in CSE5PRB.
|Resource Type||Title||Resource Requirement||Author and Year||Publisher|
|Readings||Software Engineering||Prescribed||Sommerville, I 2009||9TH EDITION, ADDISON-WESLEY|
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.
- Highlight the importance of running of team as a very improtant aspect of running a project. Show examples and videos of effective team management. Provide weekly feedback to project teams.
02. Verify, describe and document the requirement of a software system using UML, and articulate the system workflow and architecture using standards.
- Provide the process and approach for developing business requirement and explain examples of business requirement by example. Paticipate in workshops to practise necessary skills. Highlight the importance of consistency in design.
03. Evaluate, communicate and professionally present the business requirement, project plan, and design of the system to both technical and non-technical audiences.
- Highlight the standands, expectations, guidelines process, and content for presentation of project plan and busines requirement. Present seminars and workshops to practice the content and process of a good presentation.
04. Articulate and develop the detailed design of a system using professional standards and guidelines provided in the subject handbook.
- Discuss the detail design of a system by applying UML standrard notation. Provide practical workshops and seminars for developing design and testing a system.
05. Communicate and professionally present the detailed system design and scenario implementation to both technical and non-technical audiences.
- Emphasise the standands, expectations, guidelines process, and content for presentation of system design and scenario implementation. Present feedback and seminars to practise the content of a good design and presentation.
Select to view your study options…
Melbourne, 2019, Semester 1, Day
Maximum enrolment sizeN/A
Subject Instance Co-ordinatorScott Mann
One 1.0 hours seminar per week and delivered via face-to-face.
One 1.0 hours lecture per week and delivered via face-to-face.
One 1.0 hours laboratory class per week and delivered via face-to-face.
Evidence Based Learning
One 1.0 hours evidence based learning per week and delivered via face-to-face.
|Release 1 Presentation: User stories + project plan + prototype presentation 20-minutes (team)||15||02, 03|
|Release 2 Presentation: User stories + prototype + Future Plan presentation 20-minutes (team)||20||05|
|Design and Prototype Submission (team)||30||04|
|Meeting and Client Interview (team)||5||01, 02|
|Sprint project management reports 200-words weeks 5,9,7,11, plus self-reflective evaluation report||20||01|
|Workshop outcome and attendance||10||01|