CQUniversity Unit Profile
COIT13230 Application Development Project
Application Development Project
All details in this unit profile for COIT13230 have been officially approved by CQUniversity and represent a learning partnership between the University and you (our student).
The information will not be changed unless absolutely necessary and any change will be clearly indicated by an approved correction included in the profile.
General Information

Overview

This capstone unit in the Application Development major of the Bachelor of Information Technology course is designed so that you can demonstrate your learning across the whole course of study before making the transition to the next stage of your career. You are required to demonstrate and apply the skills you have developed in earlier core and application development specialisation units by undertaking an authentic task group project or an industry project. You are required to synthesise and apply your skills developed across the units studied previously. This unit will help you to consolidate your competence with a relevant set of software engineering concepts, practices, and tools. To achieve this, you will work in small teams with a designated customer to identify a problem and develop a software application adhering to software engineering principles and standards. You will document and present the requirement analysis, identify potential cyber threats and system vulnerabilities, design artefacts, and the results from software testing. Your team will develop the project management, quality assurance, and cyber security components within project specifications. You will also evaluate and discuss your contribution to the project team and the overall team performance.

Details

Career Level: Undergraduate
Unit Level: Level 3
Credit Points: 12
Student Contribution Band: 8
Fraction of Full-Time Student Load: 0.25

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 - 2023

Brisbane
Cairns
Melbourne
Online
Rockhampton
Sydney
Townsville

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).

Class and Assessment Overview

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

Bundaberg, Cairns, Emerald, Gladstone, Mackay, Rockhampton, Townsville
Adelaide, Brisbane, Melbourne, Perth, Sydney

Assessment Overview

1. Written Assessment
Weighting: 10%
2. Written Assessment
Weighting: 15%
3. Written Assessment
Weighting: 25%
4. Project (applied)
Weighting: 40%
5. Presentation
Weighting: 10%

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.

Previous Student Feedback

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 Unit Evaluation

Feedback

Redundant and inconsistent assessment requirements need to be rectified.

Recommendation

Review the assessment requirements to eliminate redundancy and inconsistency.

Feedback from Unit Evaluation

Feedback

More useful learning materials would be helpful.

Recommendation

Review the learning materials.

Unit Learning Outcomes
On successful completion of this unit, you will be able to:
  1. Apply software engineering processes in the context of application development, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management
  2. Manage a software development project, particularly the scheduling of time and resources, application of cyber security best practices, development of risk mitigation strategies, and the generation of supporting documentation
  3. Develop and implement a quality management plan for a small software development project adhering to ethical responsibility
  4. Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders
  5. Work effectively as part of a development team
  6. Critically review individual and team performance, along with identifying areas for improvement.

The Australian Computer Society (ACS), the professional association for Australia's ICT sector, recognises the Skills Framework for the Information Age (SFIA). SFIA is adopted by organisations, governments, and individuals in many countries and provides a widely used and consistent definition of ICT skills. SFIA is increasingly being used when developing job descriptions and role profiles. ACS members can use the tool MySFIA to build a skills profile.

This unit contributes to the following workplace skills as defined by SFIA 8 (the SFIA code is included):

  • Requirements definition and management (REQM)
  • Programming/software development (PROG)
  • Software Design (SWDN)
  • Data modelling and design (DTAN)
  • User experience evaluation (USEV)
  • Database design (DBDS)
  • Systems integration and build (SINT)
  • Testing (TEST)
  • Configuration management (CFMG)
  • Application support (ASUP)
  • System installation and removal (HSIN)
  • Information Security (SCTY)

Alignment of Learning Outcomes, Assessment and Graduate Attributes
N/A Level
Introductory Level
Intermediate Level
Graduate Level
Professional Level
Advanced Level

Alignment of Assessment Tasks to Learning Outcomes

Assessment Tasks Learning Outcomes
1 2 3 4 5 6
1 - Written Assessment - 15%
2 - Written Assessment - 10%
3 - Written Assessment - 25%
4 - Project (applied) - 40%
5 - Presentation - 10%

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
Textbooks and Resources

Textbooks

There are no required textbooks.

IT Resources

You will need access to the following IT resources:
  • CQUniversity Student Email
  • Internet
  • Unit Website (Moodle)
  • JDK 11 - OpenJDK
  • Apache NetBeans IDE 12.4 (available from https://netbeans.apache.org/download/nb124/nb124.html)
  • Scene Builder 12 or later available from https://gluonhq.com/products/scene-builder/
  • MySQL Community Server 8.0.26 (available from https://dev.mysql.com/downloads/mysql/)
  • JavaFX 11.0.12 (available from https://gluonhq.com/products/javafx/)
  • Apache TomEE 8.0.0 TomEE Plus (available from https://tomee.apache.org/download.html)
  • Jakarta EE 8 (available from https://jakarta.ee/release/8/)
Referencing Style

All submissions for this unit must use the referencing styles below:

For further information, see the Assessment Tasks.

Teaching Contacts
Salahuddin Azad Unit Coordinator
s.azad@cqu.edu.au
Schedule
Week 1 Begin Date: 10 Jul 2023

Module/Topic

Project management and project planning

Chapter

Reference book: Software Engineering by Ian Sommerville

Chapter 1
Section 1.2 Software Engineering Ethics
Chapter 22
22.1 Risk Management
22.3 Teamwork
Chapter 23
23.2 Plan-driven development
23.3 Project Scheduling

Events and Submissions/Topic

  • Form project group, identify and discuss project topic
Week 2 Begin Date: 17 Jul 2023

Module/Topic

Requirements engineering and quality management

Chapter

Reference book: Software Engineering by Ian Sommerville

Chapter 23
23.4 Agile Planning
Chapter 4
4.1 Requirements elicitation
Chapter 5
5.1 Context Models
Chapter 24
24.2 Software Standards
24.4 Quality Management and Agile Development

Events and Submissions/Topic

  • Finalize project topic and scope
  • Work on project proposal
Week 3 Begin Date: 24 Jul 2023

Module/Topic

System modeling

Chapter

Reference book: Software Engineering by Ian Sommerville

Chapter 5
5.2 Interaction models

Events and Submissions/Topic

  • Finalize project proposal
  • Submit project proposal

Project Proposal Due: Week 3 Friday (28 July 2023) 11:45 pm AEST
Week 4 Begin Date: 31 Jul 2023

Module/Topic

Requirements engineering and architectural design

Chapter

Reference book: Software Engineering by Ian Sommerville

Chapter 4
4.1 Functional and Non-Functional Requirements
4.4 Requirements Specification
Chapter 6
6.3 Architectural Patterns

Events and Submissions/Topic

Work on:
  • detailed user stories,
  • user interfaces,
  • data structures,
  • database schema,
  • software architecture,
  • platforms/tools/frameworks,
  • test plan, and
  • project tracking tool
Week 5 Begin Date: 07 Aug 2023

Module/Topic

Object-Oriented design and testing

Chapter

Reference book: Software Engineering by Ian Sommerville

Chapter 7
7.1 Object-Oriented design using the UML
Chapter 8
8.2 Test-driven development

Events and Submissions/Topic

  • Start developing prototype
  • Submit Progress Report 1

Progress Report 1 Due: Week 5 Friday (11 Aug 2023) 11:45 pm AEST
Vacation Week Begin Date: 14 Aug 2023

Module/Topic

Enjoy the break.

Chapter

Events and Submissions/Topic

Week 6 Begin Date: 21 Aug 2023

Module/Topic

Complete requirements and design 

Chapter

Events and Submissions/Topic

  • Keep working on prototype
  • Track progress
  • Update GitHub repository
Week 7 Begin Date: 28 Aug 2023

Module/Topic

System implementation

Chapter

Reference book: Software Engineering by Ian Sommerville

Chapter 7
7.3 Implementation Issues

Events and Submissions/Topic

  • Start developing in-class presentation
  • Submit Progress Report 2

Progress Report 2 Due: Week 7 Friday (1 Sept 2023) 11:45 pm AEST
Week 8 Begin Date: 04 Sep 2023

Module/Topic

System implementation

Chapter

Events and Submissions/Topic

  • Keep working on in-class presentation
  • Keep working on prototype
  • Track progress
  • Update GitHub repository
Week 9 Begin Date: 11 Sep 2023

Module/Topic

Configuration management

Chapter

Reference book: Software Engineering by Ian Sommerville

Chapter 24
24.3 Reviews and Inspections
Chapter 25
25.1 Version Management
25.2 System Building

Events and Submissions/Topic

  • Keep working on in-class presentation
  • Keep working on prototype
  • Track progress
  • Update GitHub repository
Week 10 Begin Date: 18 Sep 2023

Module/Topic

Software testing

Chapter

Reference book: Software Engineering by Ian Sommerville

Chapter 8
8.3 Release Testing
8.4 User Testing

Events and Submissions/Topic

  • Deliver in-class presentation
  • Start writing report
  • Keep working on prototype
  • Track progress
  • Update GitHub repository

In-class Presentation and Demonstration Due: Week 10 Friday (22 Sep 2023) 11:45 pm AEST

Week 11 Begin Date: 25 Sep 2023

Module/Topic

Chapter

Events and Submissions/Topic

  • Keep working on report
  • Keep working on prototype
  • Test prototype
  • Track progress
  • Update GitHub repository
Week 12 Begin Date: 02 Oct 2023

Module/Topic

Chapter

Events and Submissions/Topic

  • Submit report
  • Complete software development
  • Complete user acceptance test
  • Complete final presentation development, and practice


Final Report
Due: Week 12 Friday (6 Oct 2023) 11:45 pm AEST

Review/Exam Week Begin Date: 09 Oct 2023

Module/Topic

Project Presentation

Chapter

Events and Submissions/Topic

  • Deliver public presentation

Public Presentation and Demonstration of Final Project Outcomes Due: Review/Exam Week Monday (9 Oct 2023) 9:00 am AEST
Exam Week Begin Date: 16 Oct 2023

Module/Topic

Chapter

Events and Submissions/Topic

Term Specific Information

Contact information for Dr Salahuddin Azad: Email: s.azad@cqu.edu.au; Office: Level 6, 120 Spencer Street, Melbourne Vic 3000; P +61 3 9616 0680 | X 50680.

If you have any queries, please email me and I will get back to you within one business day or so. For an individual discussion, please ring me during business hours (or leave a message if I am not in) and I will return your call as soon as possible.

Assessment Tasks

1 Written Assessment

Assessment Title
Project Proposal

Task Description

This is a group assessment. In this assessment, you are required to develop a project proposal for the development of an enterprise application. You should come up with an original or semi-original idea for an enterprise application, which should have some business value.

The project proposal should be written into a document including the following 5 components or sections:

  1. Project background
  2. Project objective
  3. High-level user requirements
  4. Hardware and software requirements
  5. Risk management and quality assurance plan

The detailed specification of this assessment will be provided on the Moodle unit website.


Assessment Due Date

Week 3 Friday (28 July 2023) 11:45 pm AEST

The assessment must be submitted to Moodle by the due date and time.


Return Date to Students

Week 5 Friday (11 Aug 2023)

The feedback will be returned within two weeks of the submission due date.


Weighting
10%

Assessment Criteria

The assessment criteria will be provided on the Moodle unit website.


Referencing Style

Submission
Online

Submission Instructions
You must upload your project proposal as a Microsoft Word document which should include all components or sections outlined in the assessment specification. All group members must submit the same copy of the assignment.

Learning Outcomes Assessed
  • Work effectively as part of a development team

2 Written Assessment

Assessment Title
Progress Report 1

Task Description

This is a group assessment, however, individuals may receive different scores based on their contributions.

In this assessment, you are required to report progress on the following 8 items:

  1. Detailed user stories
  2. Wireframes of all user interfaces
  3. Major data structures
  4. Database schema
  5. Software architecture illustrating all components
  6. Platforms/languages/tools/frameworks
  7. Test plan (should include user acceptance test)
  8. Project tracking tool

The detailed specification of this assessment will be provided on the Moodle unit website.


Assessment Due Date

Week 5 Friday (11 Aug 2023) 11:45 pm AEST

The assessment must be submitted to Moodle by the due date and time.


Return Date to Students

Week 7 Friday (1 Sept 2023)

The feedback will be returned within two weeks of the submission due date.


Weighting
15%

Assessment Criteria

The assessment criteria will be provided on the Moodle unit website.


Referencing Style

Submission
Online

Submission Instructions
You must upload your progress report as a Microsoft Word document which should include all components or sections outlined in the assessment specification. All group members must submit the same copy of the assignment.

Learning Outcomes Assessed
  • Manage a software development project, particularly the scheduling of time and resources, application of cyber security best practices, development of risk mitigation strategies, and the generation of supporting documentation

3 Written Assessment

Assessment Title
Progress Report 2

Task Description

This is a group assessment, however, individuals may receive different scores based on their contributions. For this assessment, you will demonstrate the current prototype of your enterprise application in the class as well as submit an update report on the progress.

In the demonstration, you will run the current prototype of your enterprise application in a lab computer/your personal computer/your mobile device to demonstrate the user stories/interfaces/features/business logic that have been fully or partially implemented during the current progress period. You are also required to show evidence of tracking the progress of your project using a project tracking tool (e.g., Jira).


In the update report, you will provide a brief update on the following 6 items for the current progress period:

  1. User stories/interfaces/features/business logic implemented (provide screenshots of your outputs)
  2. Implementation details of the various components of the prototype (provide screenshots of your code)
  3. Test results for the implemented user stories/interfaces/features/business logic (provide screenshots and annotations)
  4. Errors/problems with the implemented user stories/interfaces/features/business logic (provide screenshots, if possible).
  5. User stories or other features introduced (if any)
  6. User stories or other features dropped or modified (if any)

A copy of the prototype source code must be maintained in a GitHub repository and the link to the repository must be included in the report. The repository must contain the history of all changes in the source code.

The detailed specification of this assessment will be provided on the Moodle unit website.


Assessment Due Date

Week 7 Friday (1 Sept 2023) 11:45 pm AEST

The assessment must be submitted to Moodle by the due date and time.


Return Date to Students

Week 9 Friday (15 Sept 2023)

The feedback will be returned within two weeks of the submission due date.


Weighting
25%

Assessment Criteria

The assessment criteria will be provided on the Moodle unit website.


Referencing Style

Submission
Online

Submission Instructions
You must upload your progress report as a Microsoft Word document which should include all components or sections outlined in the assessment specification. All group members must submit the same copy of the assignment.

Learning Outcomes Assessed
  • Apply software engineering processes in the context of application development, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management
  • Develop and implement a quality management plan for a small software development project adhering to ethical responsibility
  • Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders

4 Project (applied)

Assessment Title
In-class Project Demonstration and Report

Task Description

This is a group assessment, however, individuals may receive different scores based on their contributions. This assessment has two components - Part 1: In-class Presentation and Demonstration, and Part 2: Final Report. Part1 and Part 2 submissions are due in Week 10 and Week 12 respectively.


Part 1: In-class Presentation and Demonstration (20 marks)

In this part, you are required to present all aspects of your enterprise application including the project background, objective, user stories, major data structures, database design, software architecture, sequence diagram, platforms/tools/frameworks, test results (including user acceptance test), and lessons learnt. Moreover, you will run the current prototype of your enterprise application in a lab computer/your personal computer/your mobile device to demonstrate the user stories/interfaces/features/business logic that have been fully or partially implemented during the current progress period. You are also required to show evidence of tracking the progress of your project using a project tracking tool (e.g., Jira).


For this part, you must submit a presentation file to Moodle by the end of Week 10.


Part 2: Final Report (20 marks)

In this part, you are required to develop a final report containing a final project summary, user stories, major data structures, database design, software architecture, sequence diagram, platforms/tools/frameworks, test results (including user acceptance test), user manual and a project reflection.


A copy of the prototype source code must be maintained in a GitHub repository and the link to the repository must be included in the report.


For this part, you must submit the report as well a copy of the final source code to Moodle by the end of Week 12.


The detailed specification of this assessment will be provided on the Moodle unit website.


Please note: This assessment task is selected to be included in your course-wide portfolio. The outcomes/artifacts of this assessment must be uploaded to Portfolium (https://portfolium.com/activity) by the submission due dates in addition to your submission to Moodle for marking.


Assessment Due Date

Part 1 presentation must be submitted by Week 10 Friday (22 Sep 2023) 11:45 pm AEST. Part 2 report and source code must be submitted by Week 12 Friday (6 Oct 2023) 11:45 pm AEST.


Return Date to Students

The feedback will be returned within two weeks of the corresponding submission due dates.


Weighting
40%

Assessment Criteria

The assessment criteria will be provided on the Moodle unit website.


Referencing Style

Submission
Online

Submission Instructions
You must upload your presentation as a PowerPoint Presentation file, your report as a Microsoft Word file, and the source code as a Zip file. All group members must submit the same copy of the assignment.

Learning Outcomes Assessed
  • Apply software engineering processes in the context of application development, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management
  • Manage a software development project, particularly the scheduling of time and resources, application of cyber security best practices, development of risk mitigation strategies, and the generation of supporting documentation
  • Develop and implement a quality management plan for a small software development project adhering to ethical responsibility
  • Work effectively as part of a development team
  • Critically review individual and team performance, along with identifying areas for improvement.

5 Presentation

Assessment Title
Public Presentation and Demonstration of Final Project Outcomes

Task Description

This is a group assessment. In this assessment, each group is required to present their final project outcomes in a public presentation. Each member of a group MUST take part in the presentation. In general, all team members will receive the same mark in this assessment. However, if performance varies significantly across team members, individual marks can be awarded.

The presentation will cover:

  1. Demonstration of a fully running enterprise application
  2. Presentation of the final project outcomes

Each group will have 15-20 minutes to present the above items to the plenary.

With (1) above, it is advised that each group must install their enterprise application on their personal computer/mobile device prior to the delivery of the presentation. The mobile app must be demonstrated during the presentation.

With (2) above, each group must also present all aspects of their enterprise application development project covering the project background, objective, user stories, major data structures, database design, software architecture, sequence diagram, platforms/tools/frameworks, test results (including user acceptance test), and lessons learnt.


The final presentation session will be held on Monday Review/Exam Week. The presentation session will be a conference-style event, running up to 1 day. Groups will be assigned to present at time slots during the day, and also be required to view presentations of other groups. You will have to make yourself available for the whole day on the day of presentation. The Head of Course or Unit Coordinator will schedule the time of presentation.


The detailed specification of this assessment will be provided on the Moodle unit website.


Please note:
This assessment task is selected to be included in your course-wide portfolio. The outcomes/artifacts of this assessment must be uploaded to Portfolium (https://portfolium.com/activity) by the submission due date in addition to your submission to Moodle for marking.


Assessment Due Date

Review/Exam Week Monday (9 Oct 2023) 9:00 am AEST

The assignment must be submitted to Moodle by the above time and date.


Return Date to Students

The feedback will be returned on the day of certification of grades.


Weighting
10%

Assessment Criteria

The feedback will be returned on the day of certification of grades.


Referencing Style

Submission
Online

Submission Instructions
The submission should contain your presentation file, fully running enterprise application, and a link to the GitHub repository of your source code. All group members must submit the same copy of the assignment.

Learning Outcomes Assessed
  • Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders

Academic Integrity Statement

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?