cse3pra industry project 3a
INDUSTRY PROJECT 3A
CSE3PRA
2016
Credit points: 15
Subject outline
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. 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 CSE3PRA and must enrol in CSE3PRB in order to complete and receive a mark for this subject.
SchoolSchool Engineering&Mathematical Sciences
Credit points15
Subject Co-ordinatorScott Mann
Available to Study Abroad StudentsYes
Subject year levelYear Level 3 - UG
Exchange StudentsYes
Subject particulars
Subject rules
Prerequisites CSE2DES or CSE2ISD
Co-requisitesN/A
Incompatible subjects CSE3PRO, CSE4PRO, CSE40PRJ, CSE30PRJ, CSE3PRG, CSE4PRG, CSE4PRA, CSE4PRB, CSE5PRA, CSE5PRB AND students enrolled in any Graduate Diploma or Masters by Coursework course.
Equivalent subjectsN/A
Special conditions This unit of study represents the first semester of a year-long program. Students MUST complete both CSE3PRA and CSE3PRB in two consecutive semesters. All students must complete a 'Team Formation' form and submit this to the subject co-ordinator a week before the semester. Deadline for enrolment in this subject is seven days prior to commencement of term.
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. |
Graduate capabilities & intended learning outcomes
01. Describe and demonstrate the skills and knowledge to effectively manage, participate, contribute, manage conflicts, and document of running team project meetings.
- Activities:
- Highlight the importance of managing and running of team as a very important aspect of running a project. Show examples and videos of effective team work and project management. Provide weekly feedback to project teams.
- Related graduate capabilities and elements:
- Discipline-specific GCs(Discipline-specific GCs)
- Speaking(Speaking)
- Teamwork(Teamwork)
- Writing(Writing)
- Ethical Awareness(Ethical Awareness)
02. Describe and document the requirement and managing the process software system using UML, and articulate the system workflow and architecture using UML standards.
- Activities:
- Provide the process and approach for managing and developing business requirement and explain examples of business requirement. Student participation in technical workshops to learn and practice necessary skills. Highlight the importance of developing and managing a good and consistent design.
- Related graduate capabilities and elements:
- Discipline-specific GCs(Discipline-specific GCs)
- Quantitative Literacy/ Numeracy(Quantitative Literacy/ Numeracy)
- Creative Problem-solving(Creative Problem-solving)
- Critical Thinking(Critical Thinking)
- Writing(Writing)
- Inquiry/ Research(Inquiry/ Research)
- Teamwork(Teamwork)
03. Communicate and professionally present the business requirement, project management plan, and design of software system to both technical and non-technical audiences.
- Activities:
- Highlight the standards, expectations, guidelines management process, and content for presentation of project plan and business requirement. Present seminars and workshops to practice the content and process of a good presentation.
- Related graduate capabilities and elements:
- Teamwork(Teamwork)
- Discipline-specific GCs(Discipline-specific GCs)
- Writing(Writing)
- Inquiry/ Research(Inquiry/ Research)
- Ethical Awareness(Ethical Awareness)
- Speaking(Speaking)
04. Articulate and develop the detail design of a system using professional UML standards and guidelines provided in the subject handbook.
- Activities:
- Discuss the detail design of a system by applying UML standrard notation. Provide practical workshops and seminars for developing design and testing a system.
- Related graduate capabilities and elements:
- Writing(Writing)
- Teamwork(Teamwork)
- Creative Problem-solving(Creative Problem-solving)
- Quantitative Literacy/ Numeracy(Quantitative Literacy/ Numeracy)
- Critical Thinking(Critical Thinking)
- Inquiry/ Research(Inquiry/ Research)
- Discipline-specific GCs(Discipline-specific GCs)
05. Communicate how professionally prepare and run a group presentation for the detail design of a system and scenario implementaion and evidences of system to present system design and functionality to both technical and non-technical audiences.
- Activities:
- Emphasis on the standards, expectations, guidelines process and content for presentation of system design and scenario implementation. Present examples, feedback, and seminars to practice the content of a good design and presentation.
- Related graduate capabilities and elements:
- Discipline-specific GCs(Discipline-specific GCs)
- Writing(Writing)
- Speaking(Speaking)
- Inquiry/ Research(Inquiry/ Research)
- Teamwork(Teamwork)
- Ethical Awareness(Ethical Awareness)
Subject options
Select to view your study options…
Dandenong, 2016, Semester 1, Day
Overview
Online enrolmentYes
Maximum enrolment sizeN/A
Enrolment information
Subject Instance Co-ordinatorScott Mann
Class requirements
Evidence Based LearningWeek: 10 - 22
One 1.0 hours evidence based learning per week on weekdays during the day from week 10 to week 22 and delivered via face-to-face.
"Evidence based learning/problem based learning"
Laboratory ClassWeek: 10 - 22
One 1.0 hours laboratory class per week on weekdays during the day from week 10 to week 22 and delivered via face-to-face.
LectureWeek: 10 - 22
One 1.0 hours lecture per week on weekdays during the day from week 10 to week 22 and delivered via face-to-face.
SeminarWeek: 10 - 22
One 1.0 hours seminar per week on weekdays during the day from week 10 to week 22 and delivered via face-to-face.
Assessments
| Assessment element | Comments | % | ILO* |
|---|---|---|---|
| Release 1 Presentation: User stories + project plan + prototype presentation 20-minutes (team) | 15 | 02, 03 | |
| Design and prototype submission 80-pages (team) | 30 | 04 | |
| One-hour team meeting practice and one-hour team client interview (team) | 5 | 01, 02 | |
| Release 2 Presentation: User stories + prototype + Future Plan presentation 20-minutes (team) | 20 | 05 | |
| Weekly 1-hour workshop & practical project management and system development activities (individual) | 10 | 01 | |
| Sprint project management reports 200-words weeks 5,9,7,11(individual) | 20 | 01 |
Melbourne, 2016, Semester 1, Day
Overview
Online enrolmentYes
Maximum enrolment sizeN/A
Enrolment information
Subject Instance Co-ordinatorScott Mann
Class requirements
Evidence Based LearningWeek: 10 - 22
One 1.0 hours evidence based learning per week on weekdays during the day from week 10 to week 22 and delivered via face-to-face.
"Evidence based learning/problem based learning"
Laboratory ClassWeek: 10 - 22
One 1.0 hours laboratory class per week on weekdays during the day from week 10 to week 22 and delivered via face-to-face.
LectureWeek: 10 - 22
One 1.0 hours lecture per week on weekdays during the day from week 10 to week 22 and delivered via face-to-face.
SeminarWeek: 10 - 22
One 1.0 hours seminar per week on weekdays during the day from week 10 to week 22 and delivered via face-to-face.
Assessments
| Assessment element | Comments | % | ILO* |
|---|---|---|---|
| Release 1 Presentation: User stories + project plan + prototype presentation 20-minutes (team) | 15 | 02, 03 | |
| Design and prototype submission 80-pages (team) | 30 | 04 | |
| One-hour team meeting practice and one-hour team client interview (team) | 5 | 01, 02 | |
| Release 2 Presentation: User stories + prototype + Future Plan presentation 20-minutes (team) | 20 | 05 | |
| Weekly 1-hour workshop & practical project management and system development activities (individual) | 10 | 01 | |
| Sprint project management reports 200-words weeks 5,9,7,11(individual) | 20 | 01 |