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

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

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 2 - 2017

Brisbane
Distance
Melbourne
Rockhampton
Sydney

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. Practical and Written Assessment
Weighting: 100%

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 Self reflection

Feedback

To review assessment strategy to suit Agile software development procedure.

Recommendation

Teaching team to review the assessment types and criteria.

Unit Learning Outcomes
On successful completion of this unit, you will be able to:
  1. Analyse software requirements and create technically sound and well documented software designs.
  2. Analyse software design documents and create test plans and technically sound and well documented software implementations.
  3. Apply quality assurance processes in the design and implementation phases of a software development project.
  4. Produce the project management artefacts required in a typical software development project
  5. Manage a small software development project.
  6. Demonstrate technical skills, communication skills, and both professional and ethical behaviour.

Australian Computer Society (ACS) recognises the Skills Framework for the Information Age (SFIA). SFIA is in use in over 100 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 at https://www.acs.org.au/professionalrecognition/mysfia-b2c.html
This unit contributes to the following workplace skills as defined by SFIA. The SFIA code is included:
  • Program ming/Software Development (PROG),

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

Alignment of Assessment Tasks to Graduate Attributes

Assessment Tasks Graduate Attributes
1 2 3 4 5 6 7 8 9
1 - Practical and Written Assessment - 100%
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)
  • NetBeans IDE
Referencing Style

All submissions for this unit must use the referencing style: Harvard (author-date)

For further information, see the Assessment Tasks.

Teaching Contacts
Lily Li Unit Coordinator
l.li@cqu.edu.au
Schedule
Week 1 Begin Date: 10 Jul 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Form groups.

Identify project titles.

Week 2 Begin Date: 17 Jul 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Week 3 Begin Date: 24 Jul 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Artifact 1 - Submit and present project plan.

Week 4 Begin Date: 31 Jul 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Artifact 2 (a) - Submit and present progress report 1.

Week 5 Begin Date: 07 Aug 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Artifact 3 - Submit and present requirements specification.

Vacation Week Begin Date: 14 Aug 2017

Module/Topic

Chapter

Events and Submissions/Topic

Week 6 Begin Date: 21 Aug 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Artifact 2(b) - Submit and present progress report 2.

Artifact 4 - Submit and present design document.

Week 7 Begin Date: 28 Aug 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Week 8 Begin Date: 04 Sep 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Artifact 2(c) - Submit and present progress report 3.

Week 9 Begin Date: 11 Sep 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Week 10 Begin Date: 18 Sep 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Artifact 2(d) - Submit and present progress report 4.

Artifact 5 - Submit and present implementation document.

Week 11 Begin Date: 25 Sep 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Project Presentation

Week 12 Begin Date: 02 Oct 2017

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Artifact 6 - Project review and final submission.

(submit final project report and related files)

Review/Exam Week Begin Date: 09 Oct 2017

Module/Topic

Chapter

Events and Submissions/Topic

Exam Week Begin Date: 16 Oct 2017

Module/Topic

Chapter

Events and Submissions/Topic

Assessment Tasks

1 Practical and Written Assessment

Assessment Title
Software Development Artefacts

Task Description

In this assignment, students will work in teams to produce the following artefacts for a small software development project:

  1. Project Plan
  2. Progress Reports
  3. Requirements Specification
  4. Design Document
  5. Documented Implementation
  6. 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. 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.


Assessment Due Date

Refer to the unit schedule for due dates.


Return Date to Students

Assessment items will be returned within two weeks of submission.


Weighting
100%

Assessment Criteria

Note:
  1. 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.
  2. 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 2A-2D: Progress Reports Total = 4* 2 marks
Schedule review 0.5
Risk Plan review 0.5
Presentation 1
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


Referencing Style

Submission
Online

Submission Instructions
Instruction is available on the unit website

Learning Outcomes Assessed
  • 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.


Graduate Attributes
  • Communication
  • Problem Solving
  • Critical Thinking
  • Information Literacy
  • Team Work
  • Information Technology Competence
  • Ethical practice

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?