Overview
This unit is a capstone for the application development specialisation of the Bachelor of Information Technology (BIT) course. You are required to apply, synthesise and demonstrate the skills that you have developed in earlier core and application development specialisation units through the conduct of a group project addressing a significant authentic learning task. The scope of the project will include requirements gathering, design and implementation.The project will have a designated customer and your group will identify and employ a software development methodology appropriate for the project. You are encouraged to include the project management, quality assurance and software engineering artefacts produced in the project as part of a project portfolio.
Details
Pre-requisites or Co-requisites
Pre-requisite: 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 2 - 2021
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 Student evaluation
Assignment marking criteria should reflect each team member's contribution.
Suggest to review and update the marking criteria for the last assignment to increase the mark allocation of individual contributions.
Feedback from Student evaluation
More learning resources are expected.
Provide more reading materials or project examples to support learning.
- Analyse software requirements and create well designed and documented software implementations.
- Work effectively as part of a development team.
- Develop and implement a quality management plan for a small software development project.
- Identify and produce the project management artefacts required for a smalll software development project
- Manage a small software development project
- Demonstrate work readiness in terms of technical skills, communication skills and both professional and ethical behaviour.
- Programming/software development (PROG)
- Project management (PRMG)
- Quality assurance (QUAS)
- Quality standards (QUST)
- User experience analysis (UNAN)
- User experience design (HCEV)
- User experience evaluation (HSEV)
- System design (DESN)
- Database design (DBDS)
- Testing (TEST)
- Configuration management (SYSP)
Alignment of Assessment Tasks to Learning Outcomes
| Assessment Tasks | Learning Outcomes | |||||
|---|---|---|---|---|---|---|
| 1 | 2 | 3 | 4 | 5 | 6 | |
| 1 - Project (applied) - 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 - Project (applied) - 100% | ||||||||||
Textbooks
There are no required textbooks.
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- Webcam and headset
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
j.shield@cqu.edu.au
Module/Topic
Workshop:
- Skills Development plan
- Feasibility study
- Review software engineering and project management topics
Chapter
Events and Submissions/Topic
- Identify project
- Form groups
Module/Topic
Chapter
Events and Submissions/Topic
- Submit Skills Development plan
- Submit Feasibility study
- Submit Sprint 1 artefacts
Module/Topic
Product Owner (PO) (tutor) meeting
Chapter
Events and Submissions/Topic
- Submit Sprint 2 artefacts
Module/Topic
Product Owner (PO) (tutor) meeting
Chapter
Events and Submissions/Topic
- Submit Design artefacts
- Practise presentation of Sprint 2 review & refine Sprint 3 plan with PO
Module/Topic
Product Owner (PO) (tutor) meeting
Chapter
Events and Submissions/Topic
- Submit Quality & Risk management plans
- Present Sprint 3 review to tutor
- Refine Sprint 4 plan with PO. The plan will be marked at the next meeting.
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Product Owner (PO) (tutor) meeting
Chapter
Events and Submissions/Topic
- Present Sprint 4 review
- Refine Sprint 5 plan with PO.
Module/Topic
Presentation
Chapter
Events and Submissions/Topic
- Present project to class
Module/Topic
Product Owner (PO) (tutor) meeting
Chapter
Events and Submissions/Topic
- Review Sprint 5 & refine Sprint 6 plan with PO. Sprints 5-8 will marked at the end of the term.
Module/Topic
Product Owner (PO) (tutor) meeting
Chapter
Events and Submissions/Topic
- Review Sprint 6 & refine Sprint 7 plan.
Module/Topic
Product Owner (PO) (tutor) meeting
Chapter
Events and Submissions/Topic
- Review Sprint 7 & refine Sprint 8 plan.
Module/Topic
Presentation
Chapter
Events and Submissions/Topic
- Present project to public
- Submit Maturity increment report
- Submit all project artefacts including all code, the PM tool contents including the product backlog, user stories, sprint plans, updated quality and risk management plans and updated designs
Module/Topic
No meeting
Chapter
Events and Submissions/Topic
Unit Coordinator: Jamie Shield, Cairns, j.shield@cqu.edu.au,
Office: 07 4037 4750
You are expected to attend each week to, for example, present your sprint reviews.
Even if you enrol on campus, you might be required to join a distance team.
To ease deployment, some teams might choose to use cloud resources. Some cloud resources require a credit card and/or payment.
1 Project (applied)
You will work in teams using an Agile approach on the realisation of a small software development project. You will develop your project over eight sprints. Some weeks will require the submission of additional artefacts such as your design and quality and risk management plans. Towards the end of the project you will be required to plan and implement an innovation or change to increase the maturity of your software development project skills. There are two major presentations at which you will demonstrate your project to an audience other than your tutor.
You will be required to submit project artefacts such as:
- Skills development plan: assess your own Skills Framework for the Information Age (SFIA) skills against those required by your future career, and create a plan to acquire those skills.
-
Feasibility study: you will need to perform a feasibility study to create a business case for the project. You will need to create a budget to plan for expenditures such as cloud computing resources.
- Sprints: you will need to submit artefacts such as code, virtual machines, product backlogs, user stories, sprint plans, sprint reviews, acceptance tests, developer focussed subtasks, issues, videos and presentations to demonstrate that you are delivering business value each week.
- Design: you will need to submit artefacts that communicate your design using techniques such as activity diagramming, and user interface prototyping.
- Quality and Risk management plans: you will need to submit artefacts that provide evidence that you produce quality software and that you manage project risk effectively.
- Maturity increment: you will need to submit a report of an innovation or change that would improve the maturity of some aspect of your project. You will be expected to collect evidence and use industry and research literature to support your arguments.
More details are provided on the unit website.
Assessments Due
| Week | Assessment due | Weight |
| 2 |
- Skills development plan - Feasibility study - Sprint 1 artefacts |
10% |
| 3 | Sprint 2 artefacts | 10% |
| 4 | Design artefacts | 10% |
| 5 |
- Quality & Risk management artefacts - Sprint 3 review |
10% |
| 6 | Sprint 4 review | 10% |
| 7 | Practice Presentation | 10% |
| 11 |
- Public Presentation - Maturity increment report - All project artefacts |
40% |
Refer to the unit schedule for due dates.
Ontime submissions will generally be returned within 1 week. Feedback for the final submission will be returned on Certification day.
The following are examples of the marking criteria:
| Skills development plan | An excellent plan including choice of certificate(s), SFIA codes, goal, rationales and “next steps”. |
| Feasibility study | Feasibility study contains a realistic budget and business case with excellent arguments which include calculations such as the ROI. |
| Code repo | Repo contains high-quality sprint code & build scripts. Code adheres to a referenced coding standard. |
| User stories | The product backlog contains high-value user stories and is appropriately prioritised. User stories adhere to template & INVEST. Estimated effort & value are included. Includes excellent acceptance tests. |
| Sprint plan | User stories in the current plan are decomposed into excellent developer subtasks. |
| Agile PM tool | The PM tool captures the state of the project completely & accurately |
| Sprint review | Excellent walkthrough of implemented user stories & explanation of current status of project using PM tool |
| Design | The most important design choices have been identified & well justified. Reasonable design alternatives have been provided for the 2 most important design choices. Excellent use of appropriate modelling techniques. |
| Quality | Excellent quality management plan which addresses the encouragement of quality, how quality is measured, and how the team identifies where quality efforts need to focus |
| Risk | Excellent risk management plan which addresses risk management processes and assesses and responds to the project’s risks |
| Stage presence | Excellent stage presence including well prepared, stands up straight, loud clear voice, good eye contact, does not speak too fast or too slow; appropriate use of cue cards: does not read; appropriate use of time, e.g. all team members present an appropriate amount of time. |
| Maturity increment | Excellent innovation or change with rationale, implementation, issues encountered & evidence of results. Excellent use of industry & research literature to justify arguments. |
Where possible the assessment criteria will be marked based on your team’s submission. However, the tutor may mark team criteria individually to account for aspects such as individual productivity and attendance. Criteria related to the skills development plan, sprint 1 artefacts and stage presence will be marked individually.
Submission Summary
A variety of tool will be used for submission, for example, Moodle, GitHub, Taiga, Jira and OneDrive. You will be submitting links to shared documents and videos. Marks will be deducted if the tutor cannot access the documents and videos through the links. You will need to maintain these links throughout the term to ensure the tutor always has access. In Week 11 you will need to export all documents, excluding videos, and submit them to Moodle.
Code, scripts and other developments artefacts will be submitted weekly to a shared code repository such as GitHub. You will need to perform weekly walkthroughs of your system at your tutor meetings. Each week you will need to deploy the system so that the tutor can use your system on their own device. In Week 11 you will need to export all contents of the code repository and submit it to Moodle.
Project management artefacts such as sprint plans will be submitted by keeping your team’s shared Agile project management tool up-to-date and presenting them at your tutor meetings. In Week 11 you will need to export all contents of your project management tool and submit it to Moodle.
Reports such as the following will be submitted as Word documents to Moodle:
- Week 2 Skills development plan
- Week 2 Feasibility study
- Week 11 Maturity increment report
Presentation slides such as the following will be submitted as Powerpoint documents to Moodle:
- Week 4 Design
- Week 5 Quality and Risk management plans
- Week 7 Presentation
- Week 11 Presentation
Every person needs to submit the Skills development plan and Sprint 1. Only one submission per team is required for team submissions.
- Analyse software requirements and create well designed and documented software implementations.
- Work effectively as part of a development team.
- Develop and implement a quality management plan for a small software development project.
- Identify and produce the project management artefacts required for a smalll software development project
- Manage a small software development project
- Demonstrate work readiness in terms of technical skills, communication skills and both professional and ethical behaviour.
- Communication
- Problem Solving
- Critical Thinking
- Information Literacy
- Team Work
- Information Technology Competence
- Cross Cultural Competence
- Ethical practice
- Social Innovation
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.
What can you do to act with integrity?
