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 - 2018
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.
Assessment breakdown submission should be revised to satisfy the Agile software development life cycle.
Review assessment submission plan and the marking criteria.
- 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)
- Various Software Development Environment
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
k.petrus@cqu.edu.au
Module/Topic
Workshop:
• Identify project title.
• SCRUM - Agile software project
management method.
Chapter
Events and Submissions/Topic
Form groups.
Identify roles in the team (Scrum
Master, developer, client).
No Submissions this week
Module/Topic
Workshop:
• Project planning
• SCRUM
• Project planning Requirements specification including use cases, user stories, project
charter, product backlog for software release 1.0.
Chapter
Events and Submissions/Topic
Communicate with the client, identify
user stories, prioritize user stories,
decide the iterations and the length of
each milestone
No Submissions
Module/Topic
Workshop:
Chapter
Events and Submissions/Topic
Submit Project Plan and Requirement Specification
Module/Topic
Workshop:
Chapter
Events and Submissions/Topic
No Submissions
Module/Topic
Workshop on Software Design
Chapter
Events and Submissions/Topic
No Submissions
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
• Workshop on Software Design
Chapter
Events and Submissions/Topic
Submit Design Document
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Submit Progress Report
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
No Submissions
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
No Submissions
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
No Submissions
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
No Submissions
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Submit Final Project Document and Presentation
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
1 Project (applied)
In this assignment, students will work in teams to produce the following artefacts for a small software development
project:
1. Project Plan and Requirements Specification: A two parts word document is submitted. The first part includes description of the project scope, schedule, risks, product quality and resources.The second part, describes the process used to elicit software product requirements the stakeholders.It also includes goals and vision of the product and a clear list of non-functional and functional requirements.
2. Design Document: This assessment outlines in detail the architecture and design of the software product. Among the standard software design, the document will include, use case, data flow, sequence and class diagrams of the product. Also, images will be provided of the user interface design
3. Progress Report: This is a word document which includes the developers overview of the accomplishments so far, what remains to be done, problems faced and solutions to them, any critical changes to the proposal and a brief outline for final report.
4. Final Project Document and Presentation: This is final submission which includes three distinctive parts; final project report describing the programming and testing of the product. The second part is a peer review report, which is individual assessment and each member reports his contribution as well as his peers contribution. The last part has two components; a power point file (group assessment) and oral in-class/online presentation (individual assessment). Each student has to submit his own copy of the submission as two separate files (word document and PPT).
The Agile Software Development principles will be adopted in the project development. The artefacts in assessments 1 and 2 may take several iterations.
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 some of the above
artefacts in the week that the artefact is due. They will also be required to submit the artefact in electronic form. 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 or an equivalent application;
details will be available on the unit website.
Refer to the unit schedule for due dates.
Assessments 1, 2 and 3 will be returned within 2 weeks of submission. Assessment 4 will be returned on Certification day.
1. Project Plan and Requirement Specifications (30%)
2. Progress Report (8%)
3. Design Document (20%)
4. Final Project Document and Presentation (42%)
The detailed marking guides are available on the unit website.
No submission method provided.
- 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?
