Overview
In this integrative capstone project, students develop a significant and authentic mobile application. Students employ the technical and professional skills that they have developed in earlier IT units to contribute to the development of an authentic web, hybrid or native app. They 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-Reqs: 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 1 - 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 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 Classroom discussion
Students indicated they enjoyed the ability to develop their own individual project as part of the unit and found it useful.
Continue allowing students to select their own projects for future offerings.
Feedback from Observation
Some students struggled with the project nature of the unit and the replacement of lectures with a weekly project meeting.
Consider providing scaffolding in week 1 on the nature of the unit and the relationship of this type of project unit to the project work students will conduct in the industry (i.e. meetings rather than lectures, more self-driven goal setting).
- 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, 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)
- Access to MySQL Database Server or SQLite database (Mandatory)
All submissions for this unit must use the referencing style: Harvard (author-date)
For further information, see the Assessment Tasks.
m.kayastha@cqu.edu.au
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
- Read and discuss the recommended sections of Chapter 1 of the reference textbook
- 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
- Read and discuss the recommended sections of Chapter 2 of the reference textbook
- 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
- Read and discuss the recommended sections of Chapter 2 of the reference textbook
- Finalize project proposal
- Submit project proposal
Project Proposal and Project Plan Due: Week 3 Friday (23 Mar 2018) 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
Read and discuss the recommended section of Chapter 2 of the reference textbook.
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
- Read and discuss the recommended sections of Chapter 2 the reference textbook
- Submit Assessment 2A (Periodic Project Progress Report)
Periodic Project Progress Reports Due: Week 5 Friday (6 Apr 2018) 11:45 pm AEST
Module/Topic
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
Read and discuss the recommended sections of Chapter 3 of the reference textbook.
Module/Topic
Chapter
Events and Submissions/Topic
- In-class presentation and online submission of Project Requirement Specification and Design Documents
- Submit Assessment 2B (Periodic Project Progress Report)
In-class presentation of Project Requirement Specification and Design Documents Due: Week 7 Friday (27 Apr 2018) 9:00 pm AEST
Module/Topic
Future Trends
Chapter
Chapter 9
Sections 9.4 Software-as-a-Service (SaaS)
Sections 9.5 End user software development
Events and Submissions/Topic
Read and discuss the recommended sections of Chapter 9 of the reference textbook.
Module/Topic
Chapter
Events and Submissions/Topic
Submit Assessment 2C (Periodic Project Progress Report)
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
- In-class presentation and demonstration of final project products or outcomes
- Submit Assessment 2D (Periodic Project Progress Report)
In-class presentation and demonstration of final project products or outcomes Due: Week 11 Friday (25 May 2018) 9:00 pm AEST
Module/Topic
Chapter
Events and Submissions/Topic
Submit the final project (program codes, database schema, application execution file, and project documents)
Submission of final project (program codes, database schema, application execution file, and project documents) Due: Week 12 Friday (1 June 2018) 11:45 pm AEST
Module/Topic
This course does not have any examination.
Chapter
Events and Submissions/Topic
Mahesh Kayastha
Unit Coordinator
Email: m.kayastha@cqu.edu.au
Mobile: 0430 363 864
1 Written Assessment
This is a group assessment. In this assessment, you are required to include following 5 components or sections:
1. Project charter
2. Project plan
3. Risk management plan
4. User requirements
5. Quality assurance plan
The detail specification of this assessment will be provided in the Moodle course website.
Week 3 Friday (23 Mar 2018) 11:45 pm AEST
Week 5 Friday (6 Apr 2018)
The assessment specification and marking criteria will be provided in the Moodle course 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.
- 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, understanding the needs of various stakeholders.
- 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
- Research
- Self-management
2 Written Assessment
This is a group assessment. You (and your group) are required to submitted four Periodic Project Progress Report (2A, 2B, 2C, and 2D). Each progress report weighs 2.5 marks (totaling 10 marks for all project progress reports). All four reports must be presented using the standard template file provided in the Moodle course website.
The detail specification of this assessment will be provided in the Moodle course website.
The submission due dates for all 4 progress reports are as below:
Project Progress Report 1 (Assessment 2A) | Friday of Week 5 (11:45 PM) |
Project Progress Report 2 (Assessment 2B) | Friday of Week 7 (11:45 PM) |
Project Progress Report 3 (Assessment 2A) | Friday of Week 9 (11:45 PM) |
Project Progress Report 4 (Assessment 2A) | Friday of Week 11 (11:45 PM) |
Week 5 Friday (6 Apr 2018) 11:45 pm AEST
Week 7 Monday (23 Apr 2018)
The assessment specification and marking criteria will be provided in the Moodle course website.
- Plan and manage the software development project, particularly the scheduling of time and resources and the generation of supporting documentation.
- Knowledge
- Communication
- Self-management
- Leadership
3 Presentation and Written Assessment
This is a group assessment. All members of teams will give in-class presentation (for 15-20 minutes each group). All presentation slides should be prepared using Microsoft PowerPoint or other presentation software. Each member of the team MUST present his/her work in the project.
This assessment presents two components:
1. In-class presentation (5% mark)
2. Project specification and design documents (20%)
This presentation must cover the project requirement specification, and design documents
Requirement specification section should include (a) A list of functional requirements (b) A list of non-functional requirements (c) Use-case diagrams (UML) (d) Textual description of Use-case diagrams (e) Mapping of requirements to use-cases
Design section should include: a. Software architecture clearly depicting all components b. Class diagram containing all classes (using UML notations) c. Behavioural modelling d. Data dictionary e. Entity Relationship Diagram (ERD) f. Wireframes of all user interfaces
Each member of the group must submit the Microsoft Word document of above items (1) and (2) as the detailed system specification and design document.
Week 7 Friday (27 Apr 2018) 9:00 pm AEST
This presentation will be held during Week-7. The local Project Mentor (or the Lecturer) will schedule the day and time of the presentation. The Unit Coordinator will make separate provisions for the off-campus or distance students.
Week 9 Friday (11 May 2018)
The assessment specification and marking criteria will be provided in the Moodle course 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.
- Demonstrate professional standards of software development including technical skills, documentation, software quality assurance, risk mitigation strategies and ethics.
- Work collaboratively as part of a productive team.
- Communicate effectively by using written and oral presentation, understanding the needs of various stakeholders.
- Knowledge
- Communication
- Cognitive, technical and creative skills
- Research
- Self-management
- Ethical and Professional Responsibility
- Leadership
4 Written Assessment
This in-class presentation is a group work. Each member of the group MUST give presentation. The presentation will cover:
1. Demonstration of fully running Android App
2. Presentation of the draft version of their final project report
Each group will have 20-30 minutes to present above items to the plenary.
With (1) above. it is advised that each group must install their app in other participant's Android phone devices prior to deliver the presentation.
With (2) above, each group also must present their final project report (covering all aspects of projects such as the project charter, plan, formal and non-formal requirement specifications, design documents - model diagrams, user interfaces, reports; lessons learnt)
Week 11 Friday (25 May 2018) 9:00 pm AEST
This presentation will be held during Week-7. The local Project Mentor (or the Lecturer) will schedule the day and time of the presentation. The Unit Coordinator will make separate provisions for the off-campus or distance students.
Week 13
The assessment specification and marking criteria will be provided in the Moodle course website.
- Demonstrate professional standards of software development including technical skills, documentation, software quality assurance, risk mitigation strategies and ethics.
- 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
5 Practical and Written Assessment
This is a group assessment. Each group must submit following items in a single ZIP file:
1. The Project Report (1 Microsoft Word file – no word limitations will apply)
2. App program codes (ZIP file). The fully running application. The submission should also contain an Android .apk file.
3. Database schema (a .sql dump file, if any external database such as MySQL was used). This schema file must be submitted as a plain text document saved in any standard text editor such as Notepad, Notepad++, TextEdit. Please do not submit this schema in Microsoft Word document.
Note: the Project Report will include (but not limited to) following:
1. Cover page
2. Table of content
3. Project information
a. Introduction
b. Aims/objectives/scopes
4. Design documents
a. User requirements
b. Context diagram
c. Use cases
d. Class diagram
e. . Behavioural or UML Activity Diagram
f. User interface wireframes
g. Database design (schema)
5. Test plans and test results (in tabular forms)
a. Test plan (indicating test scenario including validations)
b. Test results (showing all anticipated results and actual results)
6. User manual (detailing how to operate the system)
7. References (if any)
Week 12 Friday (1 June 2018) 11:45 pm AEST
No Assessment Criteria
- 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, understanding the needs of various stakeholders.
- 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
- 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.