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 - 2017
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 Students in Class
More Industry Engagement
Students to consider studying the Internship unit rather than the Project unit
- 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)
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
Module/Topic
Workshop: Read and Discuss Chapter 1 for 1.5 hours
Chapter
Chapter 1: Introduction from Reference book Software Engineering by Ivan Marsic
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 2
Chapter
Chapter 2: Object-Oriented Software Engineering (focus on: Software development methods, requirements engineering and architecture)
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 2 (continued)
Chapter
Chapter 2: Object-Oriented Software Engineering (focus on: use case modeling and analysis)
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 2 (continued)
Chapter
Chapter 2: Object-Oriented Software Engineering (focus on: Design and class diagrams)
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 2 (continued)
Chapter
Chapter 2: Object-Oriented Software Engineering (focus on: Software Testing)
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 3
Chapter
Chapter 3: Modeling and System Specification
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 4
Chapter
Chapter 4: Software Measurement and Estimation (Focus on: Fundamentals and Measuring Module cohesion)
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 4
Chapter
Chapter 4: Software Measurement and Estimation (Focus on: coupling and Effort Estimation)
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 7
Chapter
Chapter 7: Software Components
Events and Submissions/Topic
Module/Topic
Workshop: Read and Discuss Chapter 8
Chapter
Chapter 8: Web Services
Events and Submissions/Topic
Module/Topic
Workshop
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Module/Topic
Chapter
Events and Submissions/Topic
Mahesh Kayastha
Course Coordinator
Email: m.kayastha@cqu.edu.au
Mobile: 0430 363 864
1 Written Assessment
This assessment item is designed to test your skills in project initiation and planning including project scoping, resource scheduling, quality assurance planning, risk mitigation, collaboration, and documentation.
Your project will deliver a fully functional database based Android App or a mobile software application using Model-View-Controller design pattern and related technology stack. Refer to the Moodle course page for more information about the projects that you will be working on.
Week 3 Thursday (23 Mar 2017) 11:45 pm AEST
Week 5 Friday (7 Apr 2017)
Well documented project plan which includes main objectives, scope and constraints of the project, system architecture, hardware and software requirements, project organisation, work breakdown structure, project schedule, monitoring and reporting system, and risk plan and quality assurance plan.
- 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 assessment item is designed to test your skills in project management including quality assurance, resource scheduling, risk mitigation, collaboration, and documentation.
Week 4 Friday (31 Mar 2017) 11:45 pm AEST
Within one week of submission.
The progress reports should include a review of project schedule, quality assurance, and risk mitigation strategies providing corrective measures for any deviation.
- 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 assessment task is designed to test your skills in software requirement analysis and application software design, software test plan preparation, working in a collaborative team and effective documentation. Students will present their work in written documentation and oral presentation.
Week 6 Friday (21 Apr 2017) 11:45 pm AEST
Approximately two weeks after presentation and submssion of report.
Submission should include documentation depicting completed tasks of functional and non-functional requirements analysis, Use cases (UML), and mapping of use cases to requirements.
Your submission should include documentation on completed design of software architecture, database, and user interface. It should also include documentation on completed development of modelling for software layers, classes, and behaviour, and interactions of User Interface/Application Layer and Application Layer/Data access layer. The software test plan should include details of module/unit testing and complete system testing. The oral presentation should demonstrate the design details and viability of the project.
- 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 Practical and Written Assessment
This assessment task is used to test your skills in algorithm design, coding and debugging, software testing, effective collaboration and quality documentation meeting scheduled project timelines and following requirements specification. Students will demonstrate their project implementation using oral presentation.
Week 12 Friday (2 June 2017) 11:45 pm AEST
Oral presentation should be scheduled duiring Week 12 in consultation with local lecturer/tutor.
Certification date (required for non-exam units)
Submission should include a working software application as per the design, testing documentation following the test plan, documented source code, mapping of design to implementation, and installation and user manual. Project portfolio is a compilation of updated project documentation including requirement specification, design, and manuals.
- 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
5 Written Assessment
This assignment task is used to assess your understanding of the project planning and management in developing a software application that meets quality characteristics of functionality, usability, maintainability and dependability.
Exam Week Friday (16 June 2017) 11:45 pm AEST
Certification date (required for non-exam units)
Submission should include a critical review of project schedule, requirement analysis, design, risk mitigation strategies followed to evaluate performance and document lessons learned.
- 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
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?
