Overview
In this integrative capstone project, you will develop a significant and authentic mobile application. Specifically, you will employ the technical and professional skills that you have developed in your course of study to contribute to the development of an authentic web, hybrid or native app. You are required to use and document typical project management processes to ensure that the project is delivered on time and budget.
Details
Pre-requisites or Co-requisites
Pre-Requisites: COIT20268 Responsive Web Design, COIT20269 Mobile Web Apps, COIT20270 App Development for Mobile Platforms, PPMP20007 Project Management Concepts
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 - 2022
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 Postgraduate 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 Feedback
More realistic projects rather than case studies
Some work towards this recommendation has already been done, with the Term 1, 2021 offering allowing us to target projects that are larger and students can complete a small part of the whole. This initiative will continue to be enhanced and refined in 2022.
Feedback from Student Feedback
Quicker feedback on assessment
Students have suggested that feedback could be provided more quickly on assessment. The team will look to do this through informal meetings about progress that enhances and augments the formal marking process.
- Apply a systems engineering process, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management, informed by research into best practice
- Demonstrate professional standards of software development including technical skills, documentation, software quality assurance, risk mitigation strategies and ethics
- Plan and manage the software development project, particularly the scheduling of time and resources and the generation of supporting documentation
- Work collaboratively as part of a productive team
- Communicate effectively by using written and oral presentation and understanding the needs of various stakeholders
- Review and critically evaluate team and individual performance, reflecting on the processes followed and identifying areas for improvement.
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:
- Software Development Process Improvement (SPIM)
- Project Management (PRMG)
- Systems Design (DESN)
- System Integration (SINT)
- Program ming/Software Development (PROG)
- Data Analysis (DTAN)
- Database/Repository Design (DBDS)
- Systems Development Management (DLMG)
- Testing (TEST), Network Support (NTAS)
- Release and Deployment (RELM)
- Applications Support (ASUP)
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 - Presentation and Written Assessment - 25% | ||||||
4 - Practical and Written Assessment - 40% | ||||||
5 - Written Assessment - 10% |
Alignment of Graduate Attributes to Learning Outcomes
Graduate Attributes | Learning Outcomes | |||||
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | |
1 - Knowledge | ||||||
2 - Communication | ||||||
3 - Cognitive, technical and creative skills | ||||||
4 - Research | ||||||
5 - Self-management | ||||||
6 - Ethical and Professional Responsibility | ||||||
7 - Leadership | ||||||
8 - 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 | |
1 - Written Assessment - 15% | ||||||||
2 - Written Assessment - 10% | ||||||||
3 - Presentation and Written Assessment - 25% | ||||||||
4 - Practical and Written Assessment - 40% | ||||||||
5 - Written Assessment - 10% |
Textbooks
There are no required textbooks.
IT Resources
- CQUniversity Student Email
- Internet
- Unit Website (Moodle)
- Android studio (latest version)
- Zoom (both microphone and webcam capability)
- Visual Studio Code (latest version)
- Gradle (latest version)
- MySQL Database Server or SQLite database
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
m.cowling@cqu.edu.au
Module/Topic
Introduction to Software Engineering
Chapter
Chapter 1
- Section 1.1 What is Software Engineering?
- Section 1.2 Software Engineering Life-cycle
- Section 1.4 The Object Model
Events and Submissions/Topic
- Form project group, identify and discuss project topic
Module/Topic
Object Oriented Software Engineering
Chapter
Chapter 2
- Section 2.1 Software Development Methods
- Section 2.2 Requirement Engineering
- Section 2.3 Software Architecture
Events and Submissions/Topic
- Finalize project topic and scope
- Work on project proposal
Module/Topic
Use Case Analysis and Modeling
Chapter
Chapter 2
Section 2.4 Use Case Modeling
Events and Submissions/Topic
- Finalize project proposal
- Submit project proposal
Project Proposal Due: Week 3 Tuesday (26 July 2022) 11:45 pm AEST
Module/Topic
Use Case Analysis and Modeling
Chapter
Continue Chapter 2
Section 2.4 Use Case Modeling
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
Module/Topic
Use Case Analysis and Modeling
Chapter
Chapter 2
- Focus on design and class diagrams
- Focus on software testing (2.6 Test-driven implementation)
Events and Submissions/Topic
- Submit Progress Report 1
Progress Report 1 Due: Week 5 Friday (12 Aug 2022) 11:45 pm AEST
Module/Topic
Enjoy the break.
Chapter
Events and Submissions/Topic
Module/Topic
Modeling and System Specification
Chapter
Chapter 3
Section 3.1 What is a system?
Section 3.2 Notation for System Specification
Events and Submissions/Topic
- Setup and configure platforms/frameworks/runtime environments
- Design and create database
- Commence prototype development
- Create user interface mockups
- Create API stubs
- Track project progress
Module/Topic
Chapter
Events and Submissions/Topic
- Submit Progress Report 2
Progress Report 2 Due: Week 7 Friday (2 Sept 2022) 11:45 pm AEST
Module/Topic
Future Trends
Chapter
Chapter 9
Section 9.4 Software-as-a-Service (SaaS)
Section 9.5 End user software development
Events and Submissions/Topic
- Work on prototype improvement
- Test the prototype after each cycle
- Receive customer feedback
- Add, drop or modify user stories/features, if needed
- Track project progress
Module/Topic
Chapter
Events and Submissions/Topic
- Demonstrate the current prototype in the class
-
Submit Stage 1 update report
Prototype Demonstration Stage 1 Due: Week 9 Friday (16 Sept 2022) 11:45 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
- Work on prototype improvement
- Test the prototype after each cycle
- Receive customer feedback
- Add, drop or modify user stories/features, if needed
- Track project progress
Module/Topic
Chapter
Events and Submissions/Topic
- Demonstrate the current prototype in the class
- Submit Stage 2 update report
- Start developing the presentation
Prototype Demonstration Stage 2 Due: Week 11 Friday (30 Sept 2022) 11:45 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
- Complete mobile app development
- Test the mobile app
- Perform user acceptance test
- Complete presentation development and practice
Module/Topic
Chapter
Events and Submissions/Topic
-
Deliver public presentation to demonstrate final project outcomes
Public presentation and demonstration of final project outcomes Due: Review/Exam Week Friday (14 Oct 2022) 11:45 pm AEST
Module/Topic
This unit does not have any examination.
Chapter
Events and Submissions/Topic
This unit has no prescribed textbook, but students should use resources from previous units. The content of most of the workshops are based on materials from the following reference textbook.
Software Engineering (2012)
Author: I. Marsic
Rutgers University, New Brunswick, New Jersey, USA
The book is available on https://www.ece.rutgers.edu/~marsic/books/SE/
1 Written Assessment
This is a group assessment. In this assessment, you are required to develop a project proposal for the development of a mobile application. The mobile application can be a native, or hybrid app. You should come up with a original or semi-original idea for a mobile application, which should have some business value.
The project proposal should be written into a document including the following 5 components or sections:
- Project background
- Project objective
- High-level user requirements
- Hardware and software requirements
-
Risk management and quality assurance plan
The detail specification of this assessment will be provided on the Moodle unit website.
Week 3 Tuesday (26 July 2022) 11:45 pm AEST
The assessment must be submitted to Moodle by the due date and time.
Week 5 Friday (12 Aug 2022)
The feedback will be returned within two weeks of the submission due date.
The assessment criteria will be provided on the Moodle unit website.
- Plan and manage the software development project, particularly the scheduling of time and resources and the generation of supporting documentation
- Work collaboratively as part of a productive team
- Knowledge
- Communication
- Self-management
- Leadership
2 Written Assessment
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:
- Detailed user stories
- Wireframes of all user interfaces
- Major data structures
- Database schema
- Software architecture illustrating all components
- Platforms/languages/tools/frameworks
- Test plan (should include user acceptance test)
- Project tracking tool
The detail specification of this assessment will be provided on the Moodle unit website.
Week 5 Friday (12 Aug 2022) 11:45 pm AEST
The assessment must be submitted to Moodle by the due date and time.
Week 7 Friday (2 Sept 2022)
The feedback will be returned within two weeks of the submission due date.
The assessment criteria will be provided on the Moodle unit website.
- Apply a systems engineering process, including requirement analysis, application software design, algorithm design, coding and debugging, software testing, and software project management, informed by research into best practice
- Plan and manage the software development project, particularly the scheduling of time and resources and the generation of supporting documentation
- Knowledge
- Communication
- Cognitive, technical and creative skills
- Research
- Self-management
3 Written Assessment
This is a group assessment, however, individuals may receive different scores based on their contributions.
In this assessment, you are required to report your progress on the following 4 items:
- Setup and configuration of platforms/frameworks/runtime environments
- Database design and creation
- Creation of user interface mockups on the client-side
- Creation of API stubs on the server-side
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. You are also required to show the evidence of tracking the progress of your project using a project tracking tool (e.g., Jira).
The detail specification of this assessment will be provided on the Moodle unit website.
Week 7 Friday (2 Sept 2022) 11:45 pm AEST
The assessment must be submitted to Moodle by the due date and time.
Week 9 Friday (16 Sept 2022)
The feedback will be returned within two weeks of the submission due date.
The assessment criteria will be provided on the Moodle unit website.
- Work collaboratively as part of a productive team
- Review and critically evaluate team and individual performance, reflecting on the processes followed and identifying areas for improvement.
- Knowledge
- Communication
- Cognitive, technical and creative skills
- Ethical and Professional Responsibility
4 Practical and Written Assessment
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 mobile app in the class as well as submit a brief update report on the progress. Demonstration of the prototype and submission of the update report will be done in two stages. The Stage 1 demonstration and submission will be accomplished in Week 9 and the Stage 2 demonstration and submission will be accomplished in Week 11. Each stage carries 20 marks.
In each stage of demonstration, you will run the current prototype of your mobile app 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.
In each update report, you will provide a brief update on the following items for the current progress period:
- User stories/interfaces/features/business logic implemented (provide screenshots)
- Test results for the user stories/interfaces/features/business logic (provide screenshots and annotations)
- Errors/problems with the implemented user stories/interfaces/features/business logic (provide screenshots, if possible).
- User stories or other features introduced (if any)
- 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. You are also required to show the evidence of tracking the progress of your project using a project tracking tool (e.g., Jira).
The detail specification of this assessment will be provided on the Moodle unit website.
Stage 1 update report must be submitted by Week 9 Friday (16 Sept 2022) 11:45 pm AEST. Stage 2 update report must be submitted by Week 11 Friday (30 Sept 2022) 11:45 pm AEST.
The feedback will be returned within two weeks of the corresponding submission due dates.
The assessment criteria will be provided on the Moodle unit website.
- Demonstrate professional standards of software development including technical skills, documentation, software quality assurance, risk mitigation strategies and ethics
- Communicate effectively by using written and oral presentation and understanding the needs of various stakeholders
- Knowledge
- Communication
- Cognitive, technical and creative skills
- Research
- Self-management
- Ethical and Professional Responsibility
- Leadership
5 Presentation and Written Assessment
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:
- Demonstration of a fully running Mobile App
- Presentation of the final project outcomes
Each group will have 15-20 minutes to present the above items to the plenary. You will have to make yourself available for the whole day on the day of presentation.
With (1) above, it is advised that each group must install their mobile app on their mobile devices 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 mobile application development project covering the project background, objective, user stories, software architecture, test results (including user acceptance test), and lessons learnt.
The presentation will be held on Monday Review/Exam Week. The Head of Course or Unit Coordinator will schedule the time of presentation.
The detail specification of this assessment will be provided on the Moodle unit website.
Review/Exam Week Friday (14 Oct 2022) 11:45 pm AEST
The assignment must be submitted to Moodle by the above time and date.
The feedback will be returned on the day of certification of grades.
The assessment criteria will be provided on the Moodle unit website.
- Demonstrate professional standards of software development including technical skills, documentation, software quality assurance, risk mitigation strategies and ethics
- Communicate effectively by using written and oral presentation and understanding the needs of various stakeholders
- Knowledge
- Communication
- Cognitive, technical and creative skills
- Research
- Self-management
- Ethical and Professional Responsibility
- Leadership
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.