Overview
This unit is a capstone for the application development specialisation of the undergraduate BIT course. Students are required to apply, synthesise and demonstrate the skills that they have developed in earlier core and application development specialisation units. This will be demonstrated through the conduct of a group project addressing a significant authentic learning task. The project will have a designated customer and students will be required to produce the typical project management artefacts associated with a commercial project - e.g. a project plan, a quality plan, progress reports and a project review, together with appropriate software engineering artefacts such as requirements and design specifications, a test plan, an implementation and documentation. Students will also be expected to participate in both regular progress meetings involving relevant stakeholders and technical meetings. Students are encouraged to include the artefacts produced in the project as part of a work portfolio.
Details
Pre-requisites or Co-requisites
Prerequisite: COIT12200, (COIT12207 or COIT13224) and (COIT12208 or COIS13064) Co-requisite: COIT13229 and COIT13234
Important note: Students enrolled in a subsequent unit who failed their pre-requisite unit, should drop the subsequent unit before the census date or within 10 working days of Fail grade notification. Students who do not drop the unit in this timeframe cannot later drop the unit without academic and financial liability. See details in the Assessment Policy and Procedure (Higher Education Coursework).
Offerings For Term 1 - 2017
Attendance Requirements
All on-campus students are expected to attend scheduled classes – in some units, these classes are identified as a mandatory (pass/fail) component and attendance is compulsory. International students, on a student visa, must maintain a full time study load and meet both attendance and academic progress requirements in each study period (satisfactory attendance for International students is defined as maintaining at least an 80% attendance record).
Recommended Student Time Commitment
Each 12-credit Undergraduate unit at CQUniversity requires an overall time commitment of an average of 25 hours of study per week, making a total of 300 hours for the unit.
Class Timetable
Assessment Overview
Assessment Grading
This is a graded unit: your overall grade will be calculated from the marks or grades for each assessment task, based on the relative weightings shown in the table above. You must obtain an overall mark for the unit of at least 50%, or an overall grade of 'pass' in order to pass the unit. If any 'pass/fail' tasks are shown in the table above they must also be completed successfully ('pass' grade). You must also meet any minimum mark requirements specified for a particular assessment task, as detailed in the 'assessment task' section (note that in some instances, the minimum mark for a task may be greater than 50%). Consult the University's Grades and Results Policy for more details of interim results and final grades.
All University policies are available on the CQUniversity Policy site.
You may wish to view these policies:
- Grades and Results Policy
- Assessment Policy and Procedure (Higher Education Coursework)
- Review of Grade Procedure
- Student Academic Integrity Policy and Procedure
- Monitoring Academic Progress (MAP) Policy and Procedure - Domestic Students
- Monitoring Academic Progress (MAP) Policy and Procedure - International Students
- Student Refund and Credit Balance Policy and Procedure
- Student Feedback - Compliments and Complaints Policy and Procedure
- Information and Communications Technology Acceptable Use Policy and Procedure
This list is not an exhaustive list of all University policies. The full list of University policies are available on the CQUniversity Policy site.
Feedback, Recommendations and Responses
Every unit is reviewed for enhancement each year. At the most recent review, the following staff and student feedback items were identified and recommendations were made.
Feedback from Self reflection
To review assessment strategy to suit Agile software development procedure.
Teaching team to review the assessment types and criteria.
- Analyse software requirements and create technically sound and well documented software designs.
- Analyse software design documents and create test plans and technically sound and well documented software implementations.
- Apply quality assurance processes in the design and implementation phases of a software development project.
- Produce the project management artefacts required in a typical software development project
- Manage a small software development project.
- Demonstrate technical skills, communication skills, and both professional and ethical behaviour.
- Program ming/Software Development (PROG),
Alignment of Assessment Tasks to Learning Outcomes
Assessment Tasks | Learning Outcomes | |||||
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | |
1 - Practical and Written Assessment - 100% |
Alignment of Graduate Attributes to Learning Outcomes
Graduate Attributes | Learning Outcomes | |||||
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | |
1 - Communication | ||||||
2 - Problem Solving | ||||||
3 - Critical Thinking | ||||||
4 - Information Literacy | ||||||
5 - Team Work | ||||||
6 - Information Technology Competence | ||||||
7 - Cross Cultural Competence | ||||||
8 - Ethical practice | ||||||
9 - Social Innovation | ||||||
10 - Aboriginal and Torres Strait Islander Cultures |
Alignment of Assessment Tasks to Graduate Attributes
Assessment Tasks | Graduate Attributes | |||||||||
---|---|---|---|---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | |
1 - Practical and Written Assessment - 100% |
Textbooks
There are no required textbooks.
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- NetBeans IDE
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
l.li@cqu.edu.au
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Form groups.
Identify project titles.
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Artifact 1 - Submit and present project plan.
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Artifact 2 (a) - Submit and present progress report 1.
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Artifact 3 - Submit and present requirements specification.
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Artifact 2(b) - Submit and present progress report 2.
Artifact 4 - Submit and present design document.
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Artifact 2(c) - Submit and present progress report 3.
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Artifact 2(d) - Submit and present progress report 4.
Artifact 5 - Submit and present implementation document.
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Project Presentation
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Artifact 6 - Project review and final submission.
(submit final project report and related files)
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
1 Practical and Written Assessment
In this assignment, students will work in teams to produce the following artefacts for a small software development project:
- Project Plan
- Progress Reports
- Requirements Specification
- Design Document
- Documented Implementation
- Project Review and final submission
The Agile Software Development principles will be adopted in the project development.
Contact time is allocated each week in the form of a workshop. During these workshops, the local lecturer will provide teams with assistance and monitor progress. Teams will be required to give presentations for each of the above artefacts in the week that the artefact is due. They will also be required to submit the artefact in electronic form by noon on the day prior to the presentation. For distance students, the time of the "presentation" and the technology employed for communication will be determined on an individual basis.
The project itself will be concerned with the development of a 3-layered information system; details will be available on the unit website.
Refer to the unit schedule for due dates.
Assessment items will be returned within two weeks of submission.
- As the Agile software development principles are adopted, the marks listed for each Artefact below are all provisional. The final results will need to be reviewed at the end.
- The assessment criteria are designed for a typical 3-layered software application. If your project is not a 3-layered application, the criteria will need to be adjusted accordingly. You need to contact your lecturer or the unit coordinator for the details.
Artefact 1: Project Plan | Total = 15 marks |
Objectives and Constraints | 1 |
Hardware and Software Requirements | 1 |
Project Organisation | 1 |
WBS | 2 |
Schedule | 2 |
Monitoring and Reporting | 1 |
Risk Plan | 2 |
Quality Plan | 2 |
Presentation | 3 |
|
||||||||
Artefact 3: Requirements Specification | Total = 10 marks |
Functional and non-functional requirements | 3 |
Use cases (UML) | 2 |
Use cases (text description) | 2 |
Mapping of requirements to use cases | 1 |
Presentation | 2 |
Artefact 4: Design Document | Total = 15 marks |
Software architecture | 1 |
Layer modelling | 1 |
Database design | 1 |
Class modelling | 2 |
Behaviour modelling | 2 |
User Interface design | 2 |
User Interface/Application Layer interaction | 1 |
Application Layer/Data access layer interaction | 1 |
Requirements mapping | 1 |
Presentation | 3 |
Artefact 5: Implementation | Total = 30 marks |
Test plan | 5 |
Documentation: Mapping of design to implementation | 2 |
Documentation: Source code (e.g. JavaDoc) | 2 |
Documentation: User manual | 5 |
Application Layer implementation | 3 |
User Interface implementation | 3 |
Data Access Layer implementation | 3 |
User Interface/Application Layer interaction | 2 |
Application Layer/Data Access Layer interaction | 2 |
Presentation | 3 |
Artefact 6: Final submission | Total = 22 marks |
Project portfolio (including artefact 1, 3, 4, 5 and reflections) | 8 |
Reflections (WBS/schedule, risk management, quality and lessons learnt) | 4 |
Final presentation (clarity, confidence, Q/A and PPT file) | 10 |
- Communication
- Problem Solving
- Critical Thinking
- Information Literacy
- Team Work
- Information Technology Competence
- Ethical practice
- Analyse software requirements and create technically sound and well documented software designs.
- Analyse software design documents and create test plans and technically sound and well documented software implementations.
- Apply quality assurance processes in the design and implementation phases of a software development project.
- Produce the project management artefacts required in a typical software development project
- Manage a small software development project.
- Demonstrate technical skills, communication skills, and both professional and ethical behaviour.
As a CQUniversity student you are expected to act honestly in all aspects of your academic work.
Any assessable work undertaken or submitted for review or assessment must be your own work. Assessable work is any type of work you do to meet the assessment requirements in the unit, including draft work submitted for review and feedback and final work to be assessed.
When you use the ideas, words or data of others in your assessment, you must thoroughly and clearly acknowledge the source of this information by using the correct referencing style for your unit. Using others’ work without proper acknowledgement may be considered a form of intellectual dishonesty.
Participating honestly, respectfully, responsibly, and fairly in your university study ensures the CQUniversity qualification you earn will be valued as a true indication of your individual academic achievement and will continue to receive the respect and recognition it deserves.
As a student, you are responsible for reading and following CQUniversity’s policies, including the Student Academic Integrity Policy and Procedure. This policy sets out CQUniversity’s expectations of you to act with integrity, examples of academic integrity breaches to avoid, the processes used to address alleged breaches of academic integrity, and potential penalties.
What is a breach of academic integrity?
A breach of academic integrity includes but is not limited to plagiarism, self-plagiarism, collusion, cheating, contract cheating, and academic misconduct. The Student Academic Integrity Policy and Procedure defines what these terms mean and gives examples.
Why is academic integrity important?
A breach of academic integrity may result in one or more penalties, including suspension or even expulsion from the University. It can also have negative implications for student visas and future enrolment at CQUniversity or elsewhere. Students who engage in contract cheating also risk being blackmailed by contract cheating services.
Where can I get assistance?
For academic advice and guidance, the Academic Learning Centre (ALC) can support you in becoming confident in completing assessments with integrity and of high standard.