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

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

Brisbane
Cairns
Distance
Melbourne
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. Project (applied)
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

Assessment breakdown submission should be revised to satisfy the Agile software development life cycle.

Recommendation

Review assessment submission plan and the marking criteria.

Unit Learning Outcomes
On successful completion of this unit, you will be able to:
  1. Analyse software requirements and create well designed and documented software implementations.
  2. Work effectively as part of a development team.
  3. Develop and implement a quality management plan for a small software development project.
  4. Identify and produce the project management artefacts required for a smalll software development project
  5. Manage a small software development project
  6. Demonstrate work readiness in terms of 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:
  • 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 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 - 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

Alignment of Assessment Tasks to Graduate Attributes

Assessment Tasks Graduate Attributes
1 2 3 4 5 6 7 8 9
1 - Project (applied) - 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)
  • Various Software Development Environment
Referencing Style

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

For further information, see the Assessment Tasks.

Teaching Contacts
Khaleel Petrus Unit Coordinator
k.petrus@cqu.edu.au
Schedule
Week 1 Begin Date: 09 Jul 2018

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

Week 2 Begin Date: 16 Jul 2018

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

Week 3 Begin Date: 23 Jul 2018

Module/Topic


Workshop:


Chapter

Events and Submissions/Topic

Submit Project Plan and Requirement Specification

Week 4 Begin Date: 30 Jul 2018

Module/Topic

Workshop:


Chapter

Events and Submissions/Topic

No Submissions

Week 5 Begin Date: 06 Aug 2018

Module/Topic

Workshop on Software Design


Chapter

Events and Submissions/Topic

No Submissions

Vacation Week Begin Date: 13 Aug 2018

Module/Topic

Chapter

Events and Submissions/Topic

Week 6 Begin Date: 20 Aug 2018

Module/Topic

• Workshop on Software Design

Chapter

Events and Submissions/Topic

Submit Design Document

Week 7 Begin Date: 27 Aug 2018

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Submit Progress Report

Week 8 Begin Date: 03 Sep 2018

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

No Submissions

Week 9 Begin Date: 10 Sep 2018

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

No Submissions

Week 10 Begin Date: 17 Sep 2018

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

No Submissions

Week 11 Begin Date: 24 Sep 2018

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

No Submissions

Week 12 Begin Date: 01 Oct 2018

Module/Topic

Workshop

Chapter

Events and Submissions/Topic

Submit Final Project Document and Presentation

Review/Exam Week Begin Date: 08 Oct 2018

Module/Topic

Chapter

Events and Submissions/Topic

Exam Week Begin Date: 15 Oct 2018

Module/Topic

Chapter

Events and Submissions/Topic

Assessment Tasks

1 Project (applied)

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


Assessment Due Date

Refer to the unit schedule for due dates.


Return Date to Students

Assessments 1, 2 and 3 will be returned within 2 weeks of submission. Assessment 4 will be returned on Certification day.


Weighting
100%

Assessment Criteria

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.


Referencing Style

Submission

No submission method provided.


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


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

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?